Message ID | 4DF1B5C0.2070301@web.de (mailing list archive) |
---|---|
State | New, archived |
Headers | show |
Jan Kiszka <jan.kiszka <at> web.de> writes: > > On 2011-06-10 05:08, Amos Kong wrote: > > host kernel: 2.6.39-rc2+ > > qemu-kvm : 05f1737582ab6c075476bde931c5eafbc62a9349 > > > > (gdb) r -monitor stdio -m 800 ~/RHEL-Server-6.0-64-virtio.qcow2 -snapshot -device > virtio-net-pci,netdev=he -netdev tap,vhost=on,id=he > > > > I already came across that symptom in a different context. Fixed by the > patch below. > > However, the real issue is related to an upstream cleanup of the > virtio-pci build. That reveals some unneeded build dependencies in > qemu-kvm. Will post a fix. > > Jan FYI I encountered the same problem and applied the patch. Well this results in the following error while starting the guest: qemu-system-x86_64: unable to start vhost net: 38: falling back on userspace virtio and i have no network at all. I will disable vhost=on for now. Greetz Georg -- To unsubscribe from this list: send the line "unsubscribe kvm" in the body of a message to majordomo@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html
On 2011-06-17 09:10, Georg Hopp wrote: > Jan Kiszka <jan.kiszka <at> web.de> writes: >> >> On 2011-06-10 05:08, Amos Kong wrote: >>> host kernel: 2.6.39-rc2+ >>> qemu-kvm : 05f1737582ab6c075476bde931c5eafbc62a9349 >>> >>> (gdb) r -monitor stdio -m 800 ~/RHEL-Server-6.0-64-virtio.qcow2 -snapshot > -device >> virtio-net-pci,netdev=he -netdev tap,vhost=on,id=he >>> >> >> I already came across that symptom in a different context. Fixed by the >> patch below. >> >> However, the real issue is related to an upstream cleanup of the >> virtio-pci build. That reveals some unneeded build dependencies in >> qemu-kvm. Will post a fix. >> >> Jan > > FYI > > I encountered the same problem and applied the patch. > > Well this results in the following error while starting the guest: > > qemu-system-x86_64: unable to start vhost net: 38: > falling back on userspace virtio > > and i have no network at all. I will disable vhost=on for now. Hmm, works fine for me. The vhost-net module is loaded (though I got a different message when I forgot to load it)? Jan
On 06/10/2011 09:12 AM, Jan Kiszka wrote: > From: Jan Kiszka<jan.kiszka@siemens.com> > qemu-kvm: Fix error path of virtio_pci_set_guest_notifiers > > The mask notifier is never installed on error, so this deinstallation > will just trigger an assert in msix_unset_mask_notifier. Applied, thanks.
diff --git a/hw/virtio-pci.c b/hw/virtio-pci.c index c4735c5..311c47b 100644 --- a/hw/virtio-pci.c +++ b/hw/virtio-pci.c @@ -688,10 +688,6 @@ static int virtio_pci_set_guest_notifiers(void *opaque, bool assign) assign_error: /* We get here on assignment failure. Recover by undoing for VQs 0 .. n. */ - if (assign) { - msix_unset_mask_notifier(&proxy->pci_dev); - } - while (--n >= 0) { virtio_pci_set_guest_notifier(opaque, n, !assign); }