VM Start Timeout with PCI GPU

Z

Zac8236

Member
Apr 27, 2018
20
0
21
25
Hello,

I have a very intermidant problem when starting my Windows 10 guest with a GPU passed in.

Sometimes it will start first time through the WebGUI, others it will give the following error:

Code: 
TASK ERROR: start failed: command '/usr/bin/kvm -id 109 -name HTPC -chardev 'socket,id=qmp,path=/var/run/qemu-server/109.qmp,server,nowait' -mon 'chardev=qmp,mode=control' -pidfile /var/run/qemu-server/109.pid -daemonize -smbios 'type=1,uuid=adef74e2-c9d6-4b8f-bf06-803f42b1e43a' -drive 'if=pflash,unit=0,format=raw,readonly,file=/usr/share/pve-edk2-firmware//OVMF_CODE.fd' -drive 'if=pflash,unit=1,format=raw,id=drive-efidisk0,file=/tmp/109-ovmf.fd' -smp '8,sockets=1,cores=8,maxcpus=8' -nodefaults -boot 'menu=on,strict=on,reboot-timeout=1000,splash=/usr/share/qemu-server/bootsplash.jpg' -vga none -nographic -no-hpet -cpu 'kvm64,+lahf_lm,+sep,+kvm_pv_unhalt,+kvm_pv_eoi,hv_vendor_id=proxmox,hv_spinlocks=0x1fff,hv_vapic,hv_time,hv_reset,hv_vpindex,hv_runtime,hv_relaxed,enforce,kvm=off' -m 8192 -readconfig /usr/share/qemu-server/pve-q35.cfg -device 'vfio-pci,host=02:00.0,id=hostpci0.0,bus=ich9-pcie-port-1,addr=0x0.0,multifunction=on' -device 'vfio-pci,host=02:00.1,id=hostpci0.1,bus=ich9-pcie-port-1,addr=0x0.1' -device 'usb-host,vendorid=0x05e3,productid=0x0719,id=usb0' -device 'usb-host,vendorid=0x046d,productid=0xc52e,id=usb1' -chardev 'socket,path=/var/run/qemu-server/109.qga,server,nowait,id=qga0' -device 'virtio-serial,id=qga0,bus=pci.0,addr=0x8' -device 'virtserialport,chardev=qga0,name=org.qemu.guest_agent.0' -iscsi 'initiator-name=iqn.1993-08.org.debian:01:cee8b9ae454f' -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' -drive 'file=/dev/pve/vm-109-disk-2,if=none,id=drive-virtio0,cache=writeback,format=raw,aio=threads,detect-zeroes=on' -device 'virtio-blk-pci,drive=drive-virtio0,id=virtio0,bus=pci.0,addr=0xa,bootindex=100' -drive 'file=/dev/disk/by-id/scsi-3600605b002a93e7022d76b5013d9678a,if=none,id=drive-virtio1,cache=writeback,format=raw,aio=threads,detect-zeroes=on' -device 'virtio-blk-pci,drive=drive-virtio1,id=virtio1,bus=pci.0,addr=0xb' -netdev 'type=tap,id=net0,ifname=tap109i0,script=/var/lib/qemu-server/pve-bridge,downscript=/var/lib/qemu-server/pve-bridgedown,vhost=on' -device 'virtio-net-pci,mac=D2:B6:EA:78:55:25,netdev=net0,bus=pci.0,addr=0x12,id=net0' -rtc 'driftfix=slew,base=localtime' -machine 'type=q35' -global 'kvm-pit.lost_tick_policy=discard'' failed: got timeout


If I start the VM with the error command through SSH, it will boot everytime:

Code: 
/usr/bin/kvm -id 109 -name HTPC -chardev 'socket,id=qmp,path=/var/run/qemu-server/109.qmp,server,nowait' -mon 'chardev=qmp,mode=control' -pidfile /var/run/qemu-server/109.pid -daemonize -smbios 'type=1,uuid=adef74e2-c9d6-4b8f-bf06-803f42b1e43a' -drive 'if=pflash,unit=0,format=raw,readonly,file=/usr/share/pve-edk2-firmware//OVMF_CODE.fd' -drive 'if=pflash,unit=1,format=raw,id=drive-efidisk0,file=/tmp/109-ovmf.fd' -smp '8,sockets=1,cores=8,maxcpus=8' -nodefaults -boot 'menu=on,strict=on,reboot-timeout=1000,splash=/usr/share/qemu-server/bootsplash.jpg' -vga none -nographic -no-hpet -cpu 'kvm64,+lahf_lm,+sep,+kvm_pv_unhalt,+kvm_pv_eoi,hv_vendor_id=proxmox,hv_spinlocks=0x1fff,hv_vapic,hv_time,hv_reset,hv_vpindex,hv_runtime,hv_relaxed,enforce,kvm=off' -m 8192 -readconfig /usr/share/qemu-server/pve-q35.cfg -device 'vfio-pci,host=02:00.0,id=hostpci0.0,bus=ich9-pcie-port-1,addr=0x0.0,multifunction=on' -device 'vfio-pci,host=02:00.1,id=hostpci0.1,bus=ich9-pcie-port-1,addr=0x0.1' -device 'usb-host,vendorid=0x05e3,productid=0x0719,id=usb0' -device 'usb-host,vendorid=0x046d,productid=0xc52e,id=usb1' -chardev 'socket,path=/var/run/qemu-server/109.qga,server,nowait,id=qga0' -device 'virtio-serial,id=qga0,bus=pci.0,addr=0x8' -device 'virtserialport,chardev=qga0,name=org.qemu.guest_agent.0' -iscsi 'initiator-name=iqn.1993-08.org.debian:01:cee8b9ae454f' -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' -drive 'file=/dev/pve/vm-109-disk-2,if=none,id=drive-virtio0,cache=writeback,format=raw,aio=threads,detect-zeroes=on' -device 'virtio-blk-pci,drive=drive-virtio0,id=virtio0,bus=pci.0,addr=0xa,bootindex=100' -drive 'file=/dev/disk/by-id/scsi-3600605b002a93e7022d76b5013d9678a,if=none,id=drive-virtio1,cache=writeback,format=raw,aio=threads,detect-zeroes=on' -device 'virtio-blk-pci,drive=drive-virtio1,id=virtio1,bus=pci.0,addr=0xb' -netdev 'type=tap,id=net0,ifname=tap109i0,script=/var/lib/qemu-server/pve-bridge,downscript=/var/lib/qemu-server/pve-bridgedown,vhost=on' -device 'virtio-net-pci,mac=D2:B6:EA:78:55:25,netdev=net0,bus=pci.0,addr=0x12,id=net0' -rtc 'driftfix=slew,base=localtime' -machine 'type=q35' -global 'kvm-pit.lost_tick_policy=discard'


My backups also fail due to the timeout.

How can I increase the time it allows the VM to start within please?

Thanks,
Zac.
 
I'm having the same issue. I have the VM in question set to autostart, currently only about %25 of starts will actually boot without a timeout. Running the command manually via SSH also works for me.

Not sure when this issue began, but It used to boot %100 without timeouts.
 
I have been experiencing the same thing on about 50% of my GPU enabled machines that have over 100 GB of RAM. I would also appreciate some way to make this timeout longer. is like the original poster said it always starts for me if I run the command by hand through SSH
 
Anyone a update? i run in the same issue.

I have a Server with 512 GB of RAM and 4x2018TI
My VM starts with 64 GB RAM but more is not possible.

I found this, but it is not working.


qm showcmd VMID | bash


This should bypass the startup timeout.

one error is, pid file is

kvm: cannot create PID file: Cannot lock pid file: Resource temporarily unavailable
or the vm is off, can´t find the hard disk of the vm.
Click to expand...

I am using the latest version 6.1
 
Still an issue for me as well. Had to do `qm stop VMID` then tomcat's nifty bash version of showcmd. Is there a bug filed for this somewhere?
 
Hi, I'm having the same problem with one of my virtual machines.
After update to Proxmox 6.2 I can not start it form the user interface (I get the timeout error), I have to start it from command line.
 
You must log in or register to reply here.
Top Bottom