VM won't start at boot

[EdzioEd]

So i have a simple setup on this machine

2 VM's, half the resources of the physical machine to then, and 2 usb passthroughs on each.

VM 100 runs beautiful, server goes does, comes back up, starts amazing.
VM 101 never seems to truly "start up" unless i enter the GUI and press start.

This is the error i get

TASK ERROR: start failed: command '/usr/bin/kvm -id 101 -name Trumpf -no-shutdown -chardev 'socket,id=qmp,path=/var/run/qemu-server/101.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/101.pid -daemonize -smbios 'type=1,uuid=eaa97667-1196-4d76-848d-e8174e9b2b00' -smp '8,sockets=2,cores=4,maxcpus=8' -nodefaults -boot 'menu=on,strict=on,reboot-timeout=1000,splash=/usr/share/qemu-server/bootsplash.jpg' -vnc 'unix:/var/run/qemu-server/101.vnc,password=on' -no-hpet -cpu 'host,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' -m 51200 -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=abf13e62-9a68-4e1e-a458-6a999df50911' -device 'piix3-usb-uhci,id=uhci,bus=pci.0,addr=0x1.0x2' -readconfig /usr/share/qemu-server/pve-usb.cfg -device 'usb-tablet,id=tablet,bus=uhci.0,port=1' -device 'usb-host,vendorid=0x064f,productid=0x2af9,id=usb0' -device 'VGA,id=vga,bus=pci.0,addr=0x2,edid=off' -chardev 'socket,path=/var/run/qemu-server/101.qga,server=on,wait=off,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:f8226955ee70' -device 'ahci,id=ahci0,multifunction=on,bus=pci.0,addr=0x7' -drive 'file=/dev/zvol/rpool/data/vm-101-disk-0,if=none,id=drive-sata0,cache=writeback,format=raw,aio=io_uring,detect-zeroes=on' -device 'ide-hd,bus=ahci0.0,drive=drive-sata0,id=sata0,rotation_rate=1,bootindex=100' -drive 'file=/mnt/pve/DadosTrumpf/images/101/vm-101-disk-0.qcow2,if=none,id=drive-sata1,cache=writeback,discard=on,format=qcow2,aio=io_uring,detect-zeroes=unmap' -device 'ide-hd,bus=ahci0.1,drive=drive-sata1,id=sata1' -drive 'file=/mnt/pve/BackupTrumpf/images/101/vm-101-disk-0.qcow2,if=none,id=drive-sata2,cache=writeback,format=qcow2,aio=io_uring,detect-zeroes=on' -device 'ide-hd,bus=ahci0.2,drive=drive-sata2,id=sata2' -netdev 'type=tap,id=net1,ifname=tap101i1,script=/var/lib/qemu-server/pve-bridge,downscript=/var/lib/qemu-server/pve-bridgedown' -device 'e1000,mac=72:B8:F4:1E:65:0D,netdev=net1,bus=pci.0,addr=0x13,id=net1' -rtc 'driftfix=slew,base=localtime' -machine 'type=pc-i440fx-6.0+pve0' -global 'kvm-pit.lost_tick_policy=discard'' failed: got timeout

is there anything i can try to do?

 

[UdoB]

You are describing the reboot of the hardware? And VM 100+101 have "Start at boot" enabled?

VM 100 starts first, right? Then you can delay the start of next VMs:

Go to VM "Options --> Start/Shutdown order --> Startup delay" and try with something like 60 seconds or so.

If this solves your "failed: got timeout" you may decrease the number.

Reference: https://pve.proxmox.com/pve-docs/chapter-qm.html#qm_startup_and_shutdown

Good luck


Edit: please use [CODE]...[/CODE] for better readability.

 

[EdzioEd]

You are describing the reboot of the hardware? And VM 100+101 have "Start at boot" enabled?

VM 100 starts first, right? Then you can delay the start of next VMs:

Go to VM "Options --> Start/Shutdown order --> Startup delay" and try with something like 60 seconds or so.

If this solves your "failed: got timeout" you may decrease the number.

Reference: https://pve.proxmox.com/pve-docs/chapter-qm.html#qm_startup_and_shutdown

Good luck


Edit: please use [CODE]...[/CODE] for better readability.

Yes, when i reboot the "physical" server, power goes out, wtv, the 100 boots correclty but the 101, after a bit gives out that message.

ive already done the boot delay part, by 240s, but the error persisted. (might need more time?)

Now what ive done is enable the start at boot on vm 100, and set a crontab to check every 5 min if the vm 101 is running (and if not, start it)

lets see if that helps