Re: [libvirt] qemu-kvm-0.10.5, kvm-kmod-2.6.30, libvirt-0.6.4 - save/restore still unreliable

Nikola Ciprich
2009-06-12T20:11:20Z

Hello Charlie,
thanks for the reply
> That should work fine. Your "..." sets up the drives, memory amount,
> etc., right? Why do you say it "doesn't seem to be the proper way"? What
> fails?
sure, I'm (hopefully) providing all the needed arguments.

>
> BTW, you might also do this: -incoming 'exec:cat .../img.vm', avoiding
> the need to pipe through stdin.
yup, I tried that, but it allways ends with following:

cat /home/LVS/hibernated/vmroo55.vm | /usr/bin/qemu-kvm -M pc -m 768 -smp 2 -name vmroo55 -uuid 987e7a85-0e15-11de-a522-00304892f672 -monitor pty -boot c -kernel /home/LVS/boot/vmlinuz-2.6.29lb.00_01_PRE14-x86_64 -initrd /home/LVS/boot/kvm-initrd-2.6.29lb.00_01_PRE14-x86_64.cpio.gz -append "root=/dev/sda ro vmhostname=vmroo55" -drive file=/dev/vgshared/vmroo55-1,if=ide,index=0,boot=on -drive file=/dev/vgshared/vmroo55-2,if=ide,index=1 -drive file=/dev/vgshared/vmroo55-3,if=virtio,index=0 -net nic,macaddr=00:16:3e:18:37:00,vlan=0,model=virtio -net tap,script=/etc/qemu-ifup.sh,vlan=0 -serial none -parallel none -usb -vnc0.0.0.0:24155 -incoming exec:cat

Executing /etc/qemu-ifup
Bringing up tap0 for bridged mode...
Adding tap0 to br0...
char device redirected to /dev/pts/7
qemu_popen: returning result of qemu_fopen_ops
load of migration failed
cat: write error: Broken pipe
/etc/qemu-ifdown: could not launch network script

using
... -incoming exec:cat /home/...image.vm
seems to start the machine, but it seems to be stuck, even though I removed -S parameter.

>
> --
> Libvir-list mailing list
> Libvir-list@redhat.com
> https://www.redhat.com/mailman/listinfo/libvir-list