[Spice-devel] Vdagent not working on xen linux hvm DomUs
Fabio Fantoni
fabio.fantoni at m2r.biz
Fri Dec 6 07:25:48 PST 2013
Il 06/12/2013 15:55, Wei Liu ha scritto:
> On Fri, Dec 06, 2013 at 03:49:30PM +0100, Fabio Fantoni wrote:
>> Il 06/12/2013 15:40, Wei Liu ha scritto:
>>> On Fri, Dec 06, 2013 at 02:51:50PM +0100, Fabio Fantoni wrote:
>>>> Il 06/12/2013 14:17, Wei Liu ha scritto:
>>>>> On Fri, Dec 06, 2013 at 02:10:24PM +0100, Fabio Fantoni wrote:
>>>>> [...]
>>>>>> I tried 2 cases with xen_emul_unplug=never:
>>>>>> - with xen platform disabled (xen_platform_pci=0 plus konrad patch)
>>>>>> and pci=nomsi
>>>>>> - with xen_platform_pci=1 and without pci kernel parameter
>>>>>> on both cases qemu crash with same error:
>>>>>> xen_ram_addr_from_mapcache, could not find 0x7fdecf624968
>>>>>>
>>>>>> On your virtio net test you have added only 'model=virtio-net-pci'
>>>>>> on vif line of domU's xl cfg or you did other changes?
>>>>>>
>>>>> No, nothing more. But I'm using Xen's QEMU upstream, not vanilla QEMU.
>>>> I'm using xen's upstream qemu (master of
>>>> git://xenbits.xen.org/qemu-upstream-unstable.git)
>>>>
>>> Not only the branch is important but also the changeset.
>>>
>>> I'm using the hash specified in Config.mk
>> qemu of my tests about virtio:
>> git log
>> commit b97307ecaad98360f41ea36cd9674ef810c4f8cf
>> Author: Matthew Daley <mattjd at gmail.com>
>> Date: Thu Oct 10 14:10:48 2013 +0000
>>
>> xen_disk: mark ioreq as mapped before unmapping in error case
>>
> There's lots of changesets between this one and the one I use so doing
> bisection is the only way to find out where the regression was
> introduced.
>
> Wei.
So your are still using qemu 1.3?
More information about the Spice-devel
mailing list