Proxmox 2.3.13 KVM's wont boot - got timeout

[sean]

I realise this is a very old version of Proxmox which is running on a clients site but they have a problem that since the weekend where 2x 2008r2 Servers running in KVM instances will not boot.

On one I manage to get to a very slow scrolling green windows bar as if it is starting up, on the other I managed to get it to try and start in safe mode but it seemed to get stuck on sysvol.

If I try and run almost any command while one instance is trying to boot I simply get 'got timeout' and the command cancels.

In either case I can only seem to try and start one machine, if it try start the second they fail -
TASK ERROR: start failed: command '/usr/bin/kvm -id 102 -chardev 'socket,id=qmp,path=/var/run/qemu-server/102.qmp,server,nowait' -mon 'chardev=qmp,mode=control' -vnc unix:/var/run/qemu-server/102.vnc,x509,password -pidfile /var/run/qemu-server/102.pid -daemonize -name win7 -smp 'sockets=2,cores=2' -nodefaults -boot 'menu=on' -vga std -no-hpet -k en-gb -m 2048 -device 'piix3-usb-uhci,id=uhci,bus=pci.0,addr=0x1.0x2' -device 'usb-tablet,id=tablet,bus=uhci.0,port=1' -device 'virtio-balloon-pci,id=balloon0,bus=pci.0,addr=0x3' -drive 'if=none,id=drive-ide2,media=cdrom,aio=native' -device 'ide-cd,bus=ide.1,unit=0,drive=drive-ide2,id=ide2,bootindex=200' -drive 'file=/var/lib/vz/images/102/vm-102-disk-1.qcow2,if=none,id=drive-virtio0,aio=native,cache=none' -device 'virtio-blk-pci,drive=drive-virtio0,id=virtio0,bus=pci.0,addr=0xa' -netdev 'type=tap,id=net0,ifname=tap102i0,script=/var/lib/qemu-server/pve-bridge' -device 'rtl8139,mac=720:0D:89:0B:F6,netdev=net0,bus=pci.0,addr=0x12,id=net0,bootindex=300' -rtc 'driftfix=slew,base=localtime' -global 'kvm-pit.lost_tick_policy=discard'' failed: got timeout

There appears to be free disk space.

Does anyone have any idea how to troubleshoot this further? Any help appreciated.

 

[GadgetPig]

Have you checked the hard drive SMART status using smartctl? Hopefully it's not failing. Since we're in rescue mode, what I would do first is create a backup of each VM by mounting an internal hard drive (or USB hard drive) and add to proxmox storage as directory.

https://www.linuxtutorial.co.uk/proxmox-add-a-second-hard-drive-to-node-for-backups/

Once that's complete, I would setup a separate/new ProxMox server node with at least 16gb memory, create 2008 VMs with similar VM settings [except slightly larger hard drive size], then do V2V clone (source to target) by booting the old source VM with clonezilla ISO and cloning into the new target VM.

https://pve.proxmox.com/wiki/Migrat...roxmox_VE_.28KVM.29_using_Clonezilla_Live_CDs

If you want to skip V2V, you can move the backup drive into the new host, mount and add as directory, and just restore the VM locally.

 

[sean]

Thanks for the suggestion. It is a dell box and I can run megaclisas-status and it says the array is 'optimal' which doesn't indicate any disk failure as far as I can tell.

CPU usage seems to just be out of control for no apparent reason but i see this in the logs which I dont understand -
Mar 20 15:39:42 px1 kernel: CE: hpet increasing min_delta_ns to 458180 nsec

 

[GadgetPig]

If it's running a really old version of ProxMox, I assume it's probably running on a really old server. I would prioritize backing up the VM's and VM data before it's too late. Some things to try for troubleshooting, adjust VM settings to 1 socket/1 or 2 cores, and drive cache="writeback" and make sure the server's date/time and BIOS settings look correct.