On Thu, Dec 12, 2013 at 02:10:23PM +0100, Fabio Fantoni wrote:
[...]
> I did some other tests, I narrowed down the commit range to the one between:
>
> commit c9fea5d701f8fd33f0843728ec264d95cee3ed37 Mon, 22 Jul 2013
> 15:14:18 (Merge remote-tracking branch 'bonzini/iommu-for-anthony')
> where there is virtio net regression with xen
>
> and
>
> commit 962b03fcf509db25c847aa67c4eff574c240dcfe Thu, 4 Jul 2013
> 15:42:43 +0000 (xen: Mark fixed platform I/O as unaligned)
> where virtio net is working
>
> I also tested:
> commit 2562becfc126ed7678c662ee23b7c1fe135d8966 Mon, 15 Jul 2013
> 19:02:41 +0000
> and
> commit dcb117bfda5af6f6ceb7231778d36d8bce4aee93 Thu, 4 Jul 2013
> 15:42:46 +0000
> but qemu crashes on xl create for another error and I haven't found
> which is the commit to apply with git cherry-pick so that I can
> check if the virtio net regression is present.
>
> Can someone help me please?
>
> I added also qemu-devel to cc.
>
I did a quick test with Xen's QEMU, currently at
commit 1c514a7734b7f98625a0d18d5e8ee7581f26e50c
Merge: 79c097d 35bdc13
Author: Stefano Stabellini <stefano.stabellini@xxxxxxxxxxxxx>
Date: Tue Jun 25 11:34:24 2013 +0000
Merge remote branch 'perard/cpu-hotplug-port-v2' into xen-staging-master-7
from git://xenbits.xen.org/qemu-upstream-unstable.git
My guest is Squeeze with stock kernel 2.6.32.
vif=['model=virtio-net-pci,bridge=xenbr0']
No pci=nomsi in guest kernel command line.
Everything worked fine. And /proc/interrupts shows that it's indeed
using MSI for virtio PCI.
I'm kind of confused. (And in the long run of this thread I probably
didn't remember everything.)
Wei.
> Thanks for any reply.
_______________________________________________
Spice-devel mailing list
Spice-devel@xxxxxxxxxxxxxxxxxxxxx
http://lists.freedesktop.org/mailman/listinfo/spice-devel