 
	
| [Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index] Re: [Xen-devel] [Spice-devel] Vdagent not working on xen linux hvm DomUs
 Il 06/12/2013 16:39, Wei Liu ha scritto: On Fri, Dec 06, 2013 at 02:55:46PM +0000, Wei Liu wrote: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 Thanks for your reply.Before starting bisection I tried with qemu 1.3.1 from qemu-upstream-4.3-testing.git No more crash with virtio net but it needs pci=nomsi to be working, same thing for vdagent, so seems that msi problem is with all virtio devices. Then the problems seem 2 different, on your build you have virtio devices working without setting pci=nomsi need to know the differences and find the cause. About the crash of qemu 1.6.1 with virtio net is confirmed that is a regression, is not critical because is not implement on libxl now but I'll do further research. _______________________________________________ Xen-devel mailing list Xen-devel@xxxxxxxxxxxxx http://lists.xen.org/xen-devel 
 
 
 | 
|  | Lists.xenproject.org is hosted with RackSpace, monitoring our |