Today I run aptitude dist-upgrade on my proxmox 2 and now....

I cannot start my sbs 2011 vm after rebooting the proxmox server!! I get this error when manually trying to start my vm:

root@proxmox:~# qm start 100 Warning: option deprecated, use lost_tick_policy
property of kvm-pit instead. Warning: option deprecated, use lost_tick_policy
property of kvm-pit instead. start failed: command '/usr/bin/kvm -id 100
-chardev 'socket,id=qmp,path=/var/run/qemu-server/100.qmp,server,nowait' -mon
'chardev=qmp,mode=control' -vnc unix:/var/run/qemu-server/100.vnc,x509,
password -pidfile /var/run/qemu-server/100.pid -daemonize -usbdevice tablet
-name SBS2011 -smp 'sockets=2,cores=12' -nodefaults -boot 'menu=on' -vga std
-localtime -rtc-td-hack -no-kvm-pit-reinjection -no-hpet -k it -drive 'if=none,
id=drive-ide2,media=cdrom,aio=native' -device 'ide-cd,bus=ide.1,unit=0,
drive=drive-ide2,id=ide2,bootindex=100' -drive
'file=/dev/DATASTORAGE/vm-100-disk-1,if=none,id=drive-virtio0,aio=native,
cache=none' -device 'virtio-blk-pci,drive=drive-virtio0,id=virtio0,bus=pci.0,
addr=0xa,bootindex=200' -m 16384 -netdev 'type=tap,id=net0,ifname=tap100i0,
script=/var/lib/qemu-server/pve-bridge,vhost=on' -device 'virtio-net-pci,
romfile=,mac=52:46:1C:2C:0D:F1,netdev=net0,bus=pci.0,addr=0x12,id=net0'
-no-hpet -no-kvm-pit-reinjection' failed: got timeout


Please help!

Hello, here it is:

root@proxmox:/var/log# pveversion -v
pve-manager: 2.1-12 (pve-manager/2.1/be112d89)
running kernel: 2.6.32-13-pve
proxmox-ve-2.6.32: 2.1-72
pve-kernel-2.6.32-13-pve: 2.6.32-72
pve-kernel-2.6.32-7-pve: 2.6.32-60
lvm2: 2.02.95-1pve2
clvm: 2.02.95-1pve2
corosync-pve: 1.4.3-1
openais-pve: 1.1.4-2
libqb: 0.10.1-2
redhat-cluster-pve: 3.1.92-2
resource-agents-pve: 3.9.2-3
fence-agents-pve: 3.1.8-1
pve-cluster: 1.0-27
qemu-server: 2.0-45
pve-firmware: 1.0-17
libpve-common-perl: 1.0-28
libpve-access-control: 1.0-24
libpve-storage-perl: 2.0-27
vncterm: 1.0-2
vzctl: 3.0.30-2pve5
vzprocps: 2.0.11-2
vzquota: 3.0.12-3
pve-qemu-kvm: 1.1-6
ksm-control-daemon: 1.1-1

#args: -no-hpet -no-kvm-pit-reinjection
boot: dc
bootdisk: virtio0
cores: 12
ide2: none,media=cdrom
memory: 16384
name: SBS2011
net0: virtio=52:46:1C:2C:0D:F1,bridge=vmbr1
onboot: 1
ostype: win7
sockets: 2
virtio0: RAID5_LVM:vm-100-disk-1
virtio1: RAID5_LVM:vm-100-disk-2,backup=no

The args: paramenter was commented out by me because of the received warning. I've put that args because my sbs 2011 standard had issue qith time sync.

I've two more vm (win7 pro / winxp pro) that I use for testing purposes. Normally they stay in a stopped state.

tom said:

and do they work?

Click to expand...

I'm sorry but I had to recover from this situation very fast because ca 20 users were angry and waiting to work on the vm! So I've restored the vm, without doing more tests (maybe for panic!) from a dump and commented out the args: -no-hpet -no-kvm-pit-reinjection, and it worked ( but how to have the time sync in the vm again without those option??). About this I would like to know if it's normal that restoring a dump of c drive of the vm (the sbs system itself) has destroyed also the data partition of the vm (another lvm volume)! I had to recreate the lvm storage and recover from a backup of the day before with sbs software backup! Is it a normal behaviour? THis is what has done the dump restore (in /etc/lvm/archive):

description = "Created *before* executing '/sbin/lvremove -f DATASTORAGE/vm-100-disk-2'"

description = "Created *before* executing '/sbin/lvremove -f DATASTORAGE/vm-100-disk-1'"

I wonder if it was mandatory to remove also the lvm (vm-100-disk-2) the lvm configured in the sbs vm as a data partition, to restore the dump. I don't do the dump of that partition because I do it inside sbs with ntbackup.

Ok, is it an option restoring from the web interface or it must be done using the console? Do you know also what options to use with the updated kvm version to fix the time sync issue in 2008 r2 vm, previously done with the mentione args? Thanks a lot.

tom said:

you can restore via gui.

and regarding time, there is no issue known, should just work out of the box.

Click to expand...

Ok, for the time drift there's a lot of discussions on the forum: http://forum.proxmox.com/threads/6250-Windows-2011-SBS-Clock-lags-behind.

Anyway until today the time is still in sync, so I suppose that it was a problem of the version at the time I installed the system. Thanks.