On Fri, May 02, 2014 at 02:21:08PM +0200, Richard Weinberger wrote:
On Fri, May 2, 2014 at 2:16 PM, Daniel P. Berrange <berrange@redhat.com> wrote:
On Fri, May 02, 2014 at 02:08:28PM +0200, Richard Weinberger wrote:
Hi!
My KVM hosts share the same filesystem and I'm facing an issue using managedsave. If I save vmX using managedsave on hostA and restore it later using "virsh restore" in hostB the qemu process consumes 100% CPU and makes no progress. On the other hand, if I save vmX using save the restore works fine on hostB.
FWIW, you use 'managedsave' then you shouldn't use 'restore' - you should just 'start' the guest as normal and libvirt will automagically use the managed save image.
I cannot use start because on hostB vmX is not defined. :-(
Oh, I missed that you were moving VMs from one host to another.
Of course this doesn't explain the problem you see - the result of managedsave should be identical to the result of save. They use the same QEMU code internally, the only difference being that in one case you decide the filename and in the other case libvirt decides the filename
Hmm, upon restore of a managesave'd vm libvirtd logs this: 2014-05-02 11:40:09.423+0000: 15974: error : qemuMonitorIO:614 : Interner Fehler End of file from monitor
Maybe it gives you a hint.
Indicates that QEMU quit - what is in /var/log/libvirt/qemu/$GUESTNAME.log 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 :|