VM backed up on 4.4-24, restored on 6.4-13 host won't start

[willdashwood]

Hello,

I'm migrating VMs from an old Proxmox 4.4-24 server to a new server running 6.4-13. This process has been working fine. But I've come across an old Windows 2012 VM that just won't start on the new host even though a CentOS VM migrated from the same server worked fine.

I've checked the hardware config for this VM and it all looks in order but when I try to start the VM I get the following:

root@prox5:/etc/pve/nodes/prox5/qemu-server# qm start 852
start failed: command '/usr/bin/kvm -id 852 -name win.domain.co.uk -no-shutdown -chardev 'socket,id=qmp,path=/var/run/qemu-server/852.qmp,server,nowait' -mon 'chardev=qmp,mode=control' -chardev 'socket,id=qmp-event,path=/var/run/qmeventd.sock,reconnect=5' -mon 'chardev=qmp-event,mode=control' -pidfile /var/run/qemu-server/852.pid -daemonize -smbios 'type=1,uuid=ee2c007e-9f55-4fdc-8ca0-f7a322be8616' -smp '4,sockets=2,cores=2,maxcpus=4' -nodefaults -boot 'menu=on,strict=on,reboot-timeout=1000,splash=/usr/share/qemu-server/bootsplash.jpg' -vnc unix:/var/run/qemu-server/852.vnc,password -no-hpet -cpu 'kvm64,enforce,hv_ipi,hv_relaxed,hv_reset,hv_runtime,hv_spinlocks=0x1fff,hv_stimer,hv_synic,hv_time,hv_vapic,hv_vpindex,+kvm_pv_eoi,+kvm_pv_unhalt,+lahf_lm,+sep' -m 8192 -device 'pci-bridge,id=pci.1,chassis_nr=1,bus=pci.0,addr=0x1e' -device 'pci-bridge,id=pci.2,chassis_nr=2,bus=pci.0,addr=0x1f' -device 'piix3-usb-uhci,id=uhci,bus=pci.0,addr=0x1.0x2' -device 'usb-tablet,id=tablet,bus=uhci.0,port=1' -device 'VGA,id=vga,bus=pci.0,addr=0x2,edid=off' -iscsi 'initiator-name=iqn.1993-08.org.debian:01:b0abf843bdda' -drive 'if=none,id=drive-ide2,media=cdrom,aio=threads' -device 'ide-cd,bus=ide.1,unit=0,drive=drive-ide2,id=ide2,bootindex=200' -device 'ahci,id=ahci0,multifunction=on,bus=pci.0,addr=0x7' -drive 'file=/dev/pve/vm-852-disk-0,if=none,id=drive-sata0,format=raw,cache=none,aio=native,detect-zeroes=on' -device 'ide-hd,bus=ahci0.0,drive=drive-sata0,id=sata0,bootindex=100' -netdev 'type=tap,id=net0,ifname=tap852i0,script=/var/lib/qemu-server/pve-bridge,downscript=/var/lib/qemu-server/pve-bridgedown' -device 'e1000,mac=FE:EA:12:06:80:0B,netdev=net0,bus=pci.0,addr=0x12,id=net0,bootindex=300' -rtc 'driftfix=slew,base=localtime' -machine 'type=pc-i440fx-5.1+pve0' -global 'kvm-pit.lost_tick_policy=discard'' failed: got timeout

I've not come across this before. Does anyone have any ideas?

Thanks!

 

[datschlatscher]

Not quite sure what the problem is, though I found a thread about this here on the forum (albeit rather old, but on PVE 6).

Aaron suggested that it might have to do with RAM usage and the host not being able to clear it quickly enough, could you verify whether you have enough RAM available?
A possible fix for the original problem was to change the "OS-type" parameter to something else. While I think this is a rather wonky solution, could you check if your OS-type setting is set correctly (and for that matter, if some other maybe related settings are still correct)?

 

[willdashwood]

Thank you! Setting the OS type to "Other" fixed it. Many thanks.