I just updated from Proxmox VE beta1 to beta2 using the apt-get dist-upgrade method. Everything was fine except my Win2k Server KVM. The FreeBSD 6.3/i386 KVM was perfectly fine and happy, it was just the Win2k server KVM that blew up:
So I tried and tried various things to get it running again (including yesterday's backups) to no avail. After a couple hours I finally found and then double-checked and double-tested the conditions needed to reverse the problem: downgrade qemu-server to beta1's. That's it, I'm now using beta2's pve-kvm and beta2's kernel, but I have to use beta1's older qemu-server package or Win2k Server explodes.
I can upgrade to beta2's qemu-server and put the updated /etc/qemu-server/XXX.conf in there in the newer format that it likes and Win2k will explode. I can downgrade to beta1's qemu-server and put the older appropriate /etc/qemu-server/XXX.conf back in and Win2k works fine again.
I took a look at the kvm command line differences between qemu-server versions, the only significant (to my eyes) thing I could find was that beta1 does -drive file=/var/whatever,media=disk and beta2 does not use ,media=disk on the primary IDE drive's -drive file line. That must not have been it, though, because I tried beta2's qemu-server and added ,media=disk to my ide0 line and it showed up in the kvm command line but Win2k still blew up.
So I'm not sure what differences in the older and newer qemu-server are causing the issue, here are the kvm command lines used by each:
beta1 (works fine, Win2k is happy):
beta2 (Win2k explodes):
So I tried and tried various things to get it running again (including yesterday's backups) to no avail. After a couple hours I finally found and then double-checked and double-tested the conditions needed to reverse the problem: downgrade qemu-server to beta1's. That's it, I'm now using beta2's pve-kvm and beta2's kernel, but I have to use beta1's older qemu-server package or Win2k Server explodes.
I can upgrade to beta2's qemu-server and put the updated /etc/qemu-server/XXX.conf in there in the newer format that it likes and Win2k will explode. I can downgrade to beta1's qemu-server and put the older appropriate /etc/qemu-server/XXX.conf back in and Win2k works fine again.
I took a look at the kvm command line differences between qemu-server versions, the only significant (to my eyes) thing I could find was that beta1 does -drive file=/var/whatever,media=disk and beta2 does not use ,media=disk on the primary IDE drive's -drive file line. That must not have been it, though, because I tried beta2's qemu-server and added ,media=disk to my ide0 line and it showed up in the kvm command line but Win2k still blew up.
So I'm not sure what differences in the older and newer qemu-server are causing the issue, here are the kvm command lines used by each:
beta1 (works fine, Win2k is happy):
Code:
/usr/bin/kvm
-monitor pty
-vnc unix:/tmp/qemu-server-vnc-101.socket,password
-usbdevice tablet
-name host.domain.com
-localtime
-k en-us
-drive file=/var/lib/vz/images/101/vm-101-default.qcow2,index=0,if=ide,media=disk
-drive index=2,media=cdrom
-m 1024
-net nic,macaddr=52:54:00:12:34:55,model=e1000
-net tap
Code:
/usr/bin/kvm
-monitor pty
-vnc unix:/tmp/qemu-server-vnc-101.socket,password
-usbdevice tablet
-name host.domain.com
-boot c
-localtime
-k en-us
-drive file=/var/lib/vz/images/101/vm-101-default.qcow2,if=ide,index=0,boot=on
-drive file=,if=ide,index=2,media=cdrom
-m 1024
-net tap,vlan=0,script=/var/lib/qemu-server/bridge-vlan0
-net nic,vlan=0,model=e1000,macaddr=52:54:00:12:34:55