Hello. After upgrading to qemu-1.1.2-r2 my kvm machine is not starting anymore. Error message: LC_ALL=C PATH=/bin:/sbin:/bin:/sbin:/usr/bin:/usr/sbin:/usr/bin:/usr/sbin:/usr/local/bin:/usr/local/sbin:/opt/bin:/usr/x86_64-pc-linux-gnu/gcc-bin/4.5.3 HOME=/root USER=root QEMU_AUDIO_DRV=none /usr/bin/qemu-kvm -name f5-virtual -S -M pc-1.0 -enable-kvm -m 4096 -smp 4,sockets=4,cores=1,threads=1 -uuid ed6f2a2a-6fef-dcbf-01f4-044b082261b4 -no-user-config -nodefaults -chardev socket,id=charmonitor,path=/var/lib/libvirt/qemu/f5-virtual.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=/var/lib/libvirt/images/bigip.qcow2,if=none,id=drive-ide0-0-0,format=qcow2 -device ide-hd,bus=ide.0,unit=0,drive=drive-ide0-0-0,id=ide0-0-0,bootindex=1 -netdev tap,fd=20,id=hostnet0 -device rtl8139,netdev=hostnet0,id=net0,mac=52:54:00:09:05:98,bus=pci.0,addr=0x3 -chardev pty,id=charserial0 -device isa-serial,chardev=charserial0,id=serial0 -vnc 127.0.0.1:0 -vga cirrus -incoming fd:18 -device virtio-balloon-pci,id=balloon0,bus=pci.0,addr=0x4 char device redirected to /dev/pts/1 Unknown savevm section or instance 'kvm-tpr-opt' 0 load of migration failed 2012-11-04 09:01:58.009+0000: shutting down What does this "Unknown savevm section or instance 'kvm-tpr-opt' 0" mean? After downgrading to qemu-1.1.1-r1 everything runs fine again. Bye the way. There are 2 windows kvms running fine even with qemu-1.1.2-r2. So this behaviour isn't quit clear to me. best regards Thomas Reproducible: Always
You have a managedsave for that VM and something has changed which prevents it from using that save state. Run virsh managedsave-remove f5-virtual and try to start it again.
Hello Doug. Thanks. You are right. The machine seemed to have a strange state. Now everything is running as expected.
I think this is not Gentoo-related issue, so it should be closed, but maybe also we should add a warning message about that fact, that using managedsave feature and then upgrade qemu is a bad idea?
(In reply to comment #3) > I think this is not Gentoo-related issue, so it should be closed, but maybe > also we should add a warning message about that fact, that using managedsave > feature and then upgrade qemu is a bad idea? Actually it is a Gentoo issue since we don't use the stock upstream ROMs which each release and let users build their own. I'm working on a generic solution for this problem which is why we don't have 1.2.0 in yet so I can solve this for people rather than breaking everyone.
This is solved in 1.2.0 and I've also handled this for upgrades to 1.3.0, when we put that in the tree.
I've fixed this by pegging each QEMU release against its corresponding binary blob.
