Can´t start VMs - "failed: got timeout"

[patman1395]

Hi,
i´ve already spend a lot of time to seach for fitting threads regarding this error and also can find some, but non of them provided me a solution. On a 3 node cluster at version 8.1.10 I get a TASK ERROR at startup of mostly Windows VMs:

TASK ERROR: start failed: command '/usr/bin/kvm -id 110 -name 'VMNAME,debug-threads=on' -no-shutdown -chardev 'socket,id=qmp,path=/var/run/qemu-server/110.qmp,server=on,wait=off' -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/110.pid -daemonize -smbios 'type=1,uuid=27a934aa-9abe-4afd-aa8d-0b9947af5853' -drive 'if=pflash,unit=0,format=raw,readonly=on,file=/usr/share/pve-edk2-firmware//OVMF_CODE_4M.fd' -drive 'if=pflash,unit=1,id=drive-efidisk0,format=qcow2,file=/mnt/pve/STORAGENAME/images/110/vm-110-disk-1.qcow2' -smp '4,sockets=1,cores=4,maxcpus=4' -nodefaults -boot 'menu=on,strict=on,reboot-timeout=1000,splash=/usr/share/qemu-server/bootsplash.jpg' -vnc 'unix:/var/run/qemu-server/110.vnc,password=on' -cpu kvm64,enforce,+kvm_pv_eoi,+kvm_pv_unhalt,+lahf_lm,+sep -m 16384 -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 'vmgenid,guid=af48daa0-fbce-4675-bf45-31823c87d3c4' -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' -device 'virtio-balloon-pci,id=balloon0,bus=pci.0,addr=0x3,free-page-reporting=on' -iscsi 'initiator-name=iqn.1993-08.org.debian:01:f29ec65c5a4d' -device 'ahci,id=ahci0,multifunction=on,bus=pci.0,addr=0x7' -drive 'file=/mnt/pve/STORAGENAME/images/110/vm-110-disk-0.qcow2,if=none,id=drive-sata0,format=qcow2,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=tap110i0,script=/var/lib/qemu-server/pve-bridge,downscript=/var/lib/qemu-server/pve-bridgedown,vhost=on' -device 'virtio-net-pci,mac=BC:24:11:4A:51:D4,netdev=net0,bus=pci.0,addr=0x12,id=net0,rx_queue_size=1024,tx_queue_size=256' -machine 'type=pc+pve0'' failed: got timeout

I have no idea what is going on here - does somebody have the same issue and found already a solution?
Many thanks in advance!

EDIT: After a random time the VMs can be started again - sometimes after 10 minutes, sometimes after 1 hour

 

[bbgeek17]

Can you provide "qm config 110" output in CODE tags?

---

Blockbridge : Ultra low latency all-NVME shared storage for Proxmox - https://www.blockbridge.com/proxmox

 

[patman1395]

Hi,
this is the config:

bios: ovmf
boot: order=sata0;sata1
cores: 4
efidisk0: STORAGENAME:110/vm-110-disk-1.qcow2,efitype=4m,pre-enrolled-keys=1,size=528K
memory: 16384
name: VMNAME
net0: virtio=BC:24:11:4A:51:D4,bridge=vmbr0,firewall=1,tag=80
numa: 0
onboot: 1
sata0: STORAGENAME:110/vm-110-disk-0.qcow2,size=90G
smbios1: uuid=27a934aa-9abe-4afd-aa8d-0b9947af5853
sockets: 1
vmgenid: af48daa0-fbce-4675-bf45-31823c87d3c4

 

[bbgeek17]

There could be a few things wrong, ie hardware not up to par (slow disk, slow cpu, etc).

See if you can start an empty VM, ie remove the disks, just try to start a VM with BIOS screen, so it boots to "no disk found".
You can also try to use legacy BIOS, no network, etc.

Check "journalctl -n 100" after trying to start a VM in current state, perhaps there is something more in the log.

Good luck

---

Blockbridge : Ultra low latency all-NVME shared storage for Proxmox - https://www.blockbridge.com/proxmox