hello. I have an issue with libvirt-1.2.6 and qemu-2.1.1. As soon as i do: "savevm $domain" the domain ist gone. Console says "unable to connect to monitor". Libvirt.log says: qemu-system-x86_64: /var/tmp/portage/app- emulation/qemu-2.1.1/work/qemu-2.1.1/hw/net/virtio-net.c:1348: virtio_net_save: Assertion `!n->vhost_started' fail ed. Googling for this error leads to a barely related qemu-dev thread. Has someone else experiencing this behaviour? Uh. Almost forgot to mention. Going back to qemu-2.1.0 solves the issue. best regards t.
On Sat, Sep 20, 2014 at 02:13:16PM +0200, Thomas Stein wrote:> hello. > > I have an issue with libvirt-1.2.6 and qemu-2.1.1. As soon as i do: > > "savevm $domain" > > the domain ist gone. Console says "unable to connect to monitor". Libvirt.log > says: > > qemu-system-x86_64: /var/tmp/portage/app- > emulation/qemu-2.1.1/work/qemu-2.1.1/hw/net/virtio-net.c:1348: > virtio_net_save: Assertion `!n->vhost_started' fail > ed. > > Googling for this error leads to a barely related qemu-dev thread. Has someone > else experiencing this behaviour? > > Uh. Almost forgot to mention. Going back to qemu-2.1.0 solves the issue.Yes, this version of QEMU is pretty much a disaster in terms of migration and save/restore working. Stick with 2.1.0 until 2.1.2 comes out. Regards, Daniel -- |: http://berrange.com -o- http://www.flickr.com/photos/dberrange/ :| |: http://libvirt.org -o- http://virt-manager.org :| |: http://autobuild.org -o- http://search.cpan.org/~danberr/ :| |: http://entangle-photo.org -o- http://live.gnome.org/gtk-vnc :|
Am 22.09.14 10:42, schrieb Daniel P. Berrange:> On Sat, Sep 20, 2014 at 02:13:16PM +0200, Thomas Stein wrote: >> hello. >> >> I have an issue with libvirt-1.2.6 and qemu-2.1.1. As soon as i do: >> >> "savevm $domain" >> >> the domain ist gone. Console says "unable to connect to monitor". Libvirt.log >> says: >> >> qemu-system-x86_64: /var/tmp/portage/app- >> emulation/qemu-2.1.1/work/qemu-2.1.1/hw/net/virtio-net.c:1348: >> virtio_net_save: Assertion `!n->vhost_started' fail >> ed. >> >> Googling for this error leads to a barely related qemu-dev thread. Has someone >> else experiencing this behaviour? >> >> Uh. Almost forgot to mention. Going back to qemu-2.1.0 solves the issue. > > Yes, this version of QEMU is pretty much a disaster in terms of migration > and save/restore working. Stick with 2.1.0 until 2.1.2 comes out.Thanks. Good to know. cheers t.