[Qemu-devel] 1.1.1 -> 1.1.2 migrate / managed save issue

[Doug Goldstein]

I'm using libvirt 0.10.2 and I had qemu-kvm 1.1.1 running all my VMs.
I used libvirt's managedsave command to pause all the VMs and write
them to disk and when I brought up the machine again I had upgraded to
qemu-kvm 1.1.2 and attempted to resume the VMs from their state. It
unfortunately fails. During the life of the VM I did not attempt to
adjust the amount of memory it had via the balloon device unless of
course libvirt did behind the scenes on me. Below is the command line
invocation and the error:

LC_ALL=C 
PATH=/bin:/sbin:/bin:/sbin:/usr/bin:/usr/sbin:/usr/bin:/usr/sbin:/usr/local/bin:/usr/local/sbin:/opt/bin
HOME=/root USER=root QEMU_AUDIO_DRV=spice /usr/bin/qemu-kvm -name expo
-S -M pc-1.0 -cpu
Penryn,+pdcm,+xtpr,+tm2,+est,+smx,+vmx,+ds_cpl,+monitor,+dtes64,+pbe,+tm,+ht,+ss,+acpi,+ds,+vme
-enable-kvm -m 1024 -smp 1,sockets=1,cores=1,threads=1 -uuid
19034754-aa3f-9671-d247-1bc53134e3f0 -no-user-config -nodefaults
-chardev 
socket,id=charmonitor,path=/var/lib/libvirt/qemu/expo.monitor,server,nowait
-mon chardev=charmonitor,id=monitor,mode=control -rtc base=utc
-no-shutdown -device
virtio-serial-pci,id=virtio-serial0,bus=pci.0,addr=0x4 -device
piix3-usb-uhci,id=usb,bus=pci.0,addr=0x1.0x2 -drive
file=/var/lib/libvirt/images/expo.img,if=none,id=drive-ide0-0-0,format=raw,cache=none
-device ide-hd,bus=ide.0,unit=0,drive=drive-ide0-0-0,id=ide0-0-0,bootindex=1
-netdev tap,fd=23,id=hostnet0 -device
rtl8139,netdev=hostnet0,id=net0,mac=52:54:00:0b:29:d9,bus=pci.0,addr=0x3
-chardev pty,id=charserial0 -device
isa-serial,chardev=charserial0,id=serial0 -chardev
spicevmc,id=charchannel0,name=vdagent -device
virtserialport,bus=virtio-serial0.0,nr=1,chardev=charchannel0,id=channel0,name=com.redhat.spice.0
-spice port=5901,addr=127.0.0.1,disable-ticketing -vga qxl -global
qxl-vga.vram_size=67108864 -incoming fd:20 -device
virtio-balloon-pci,id=balloon0,bus=pci.0,addr=0x5
char device redirected to /dev/pts/7
qemu: warning: error while loading state for instance 0x0 of device 'ram'
load of migration failed


-- 
Doug Goldstein