Re: [libvirt] qemu: managedsave vs. save
On Fri, May 2, 2014 at 2:26 PM, Daniel P. Berrange <berrange(a)redhat.com> wrote:
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(a)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.
Yep. I can also not define them on hostB because the .save files are not located
in /var/lib/libvirt/qemu/save and therefore the start command would
not find them.
> > 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
Nothing special:
2014-05-02 11:38:19.544+0000: starting up
LC_ALL=C PATH=/sbin:/usr/sbin:/bin:/usr/bin HOME=/root USER=root
LOGNAME=root QEMU_AUDIO_DRV=none /usr/libexec/qemu-kvm -name
2ndvm,process=qemu:2ndvm -S -M rhel6.1.0 -enable-kvm -m 512 -realtime
mlock=off -smp 1,sockets=1,cores=1,threads=1 -uuid
735b6912-3cf4-4c68-9780-c6d979c88ac8 -nodefconfig -nodefaults -chardev
socket,id=charmonitor,path=/var/lib/libvirt/qemu/2ndvm.monitor,server,nowait
-mon chardev=charmonitor,id=monitor,mode=control -rtc base=utc
-no-shutdown -device piix3-usb-uhci,id=usb,bus=pci.0,addr=0x1.0x2
-drive
file=/srv/galadriel_vms1/vmdisks/2ndvm/hd0.raw,if=none,id=drive-virtio-disk0,format=raw,cache=none,aio=native
-device
virtio-blk-pci,scsi=off,bus=pci.0,addr=0x4,drive=drive-virtio-disk0,id=virtio-disk0,bootindex=1
-netdev tap,fd=23,id=hostnet0,vhost=on,vhostfd=24 -device
virtio-net-pci,netdev=hostnet0,id=net0,mac=02:00:0a:00:01:1c,bus=pci.0,addr=0x3
-vnc 127.0.0.1:1 -k de -vga cirrus -incoming fd:21 -device
virtio-balloon-pci,id=balloon0,bus=pci.0,addr=0x5
qemu: terminating on signal 15 from pid 15604
The SIGTERM was sent by me after a few minuues...
--
Thanks,
//richard