Strange VM Boot Issue

JasonJensen

New Member
Mar 7, 2023
3
0
1
I have the following VM:

balloon: 0 bios: seabios boot: order=scsi0 cores: 4 hotplug: 0 kvm: 1 memory: 4096 meta: creation-qemu=7.1.0,ctime=1677543000 name: OpenMPTCProuter net0: virtio=86:10:91:5B:07:DB,bridge=vmbr4 net1: virtio=82:10:91:EE:9F:43,bridge=vmbr60 net2: virtio=1A:20:55:8D:2B:9F,bridge=vmbr3 net3: virtio=4A:07:62:52:B9:BD,bridge=vmbr100 numa: 0 onboot: 1 ostype: l26 scsi0: SecureNVMESSD:200/vm-200-disk-1.qcow2,size=590336K scsihw: virtio-scsi-single smbios1: uuid=de5bd55b-d3d3-4799-a149-876379de4c34 sockets: 1 vmgenid: 4f023491-75f6-4cd3-b9b1-3801b7370d70 vmstatestorage: SecureNVMESSD

WITH THE FOLLOWING Debian Proxmox Install network config:

# network interface settings; autogenerated # Please do NOT modify this file directly, unless you know what # you're doing. # # If you want to manage parts of the network configuration manually, # please utilize the 'source' or 'source-directory' directives to do # so. # PVE will preserve these directives, but will NOT read its network # configuration from sourced files, so do not attempt to move any of # the PVE managed interfaces into external files! source /etc/network/interfaces.d/* auto lo iface lo inet loopback auto eno3 iface eno3 inet manual auto eno4 iface eno4 inet manual auto enx8cae4cff4461 iface enx8cae4cff4461 inet manual auto bond0 iface bond0 inet manual bond-slaves eno3 eno4 bond-miimon 100 bond-mode 802.3ad auto vmbr0 iface vmbr0 inet static address 192.168.1.12/24 gateway 192.168.1.1 bridge-ports bond0.30 bridge-stp off bridge-fd 0 bridge-vlan-aware yes bridge-vids 2-4094 #eno3.30 JHOME auto vmbr1 iface vmbr1 inet static address 192.168.200.4/24 bridge-ports none bridge-stp off bridge-fd 0 #eno4 auto vmbr2 iface vmbr2 inet static address 192.168.55.2/24 bridge-ports bond0.50 bridge-stp off bridge-fd 0 bridge-vlan-aware yes bridge-vids 2-4094 #eno3.50 OPP8GW auto vmbr3 iface vmbr3 inet manual bridge-ports none bridge-stp off bridge-fd 0 auto vmbr4 iface vmbr4 inet static address 192.168.100.2/24 bridge-ports bond0 bridge-stp off bridge-fd 0 bridge-vlan-aware yes bridge-vids 2-4094 #eno3 -JRVHOME auto vmbr100 iface vmbr100 inet static address 192.168.19.2/24 bridge-ports bond0.40 bridge-stp off bridge-fd 0 bridge-vlan-aware yes bridge-vids 2-4094 #eno3.40 ATT-FMCA auto vmbr9999 iface vmbr9999 inet manual bridge-ports none bridge-stp off bridge-fd 0 auto vmbr60 iface vmbr60 inet static address 192.168.91.3/24 bridge-ports bond0.60 bridge-stp off bridge-fd 0 bridge-vlan-aware yes bridge-vids 2-4094 #WIFI-CLIENT

The problem is with vmbr60 in the VM config it will not start. I get:

TASK ERROR: start failed: command '/usr/bin/kvm -id 200 -name 'OpenMPTCProuter,debug-threads=on' -no-shutdown -chardev 'socket,id=qmp,path=/var/run/qemu-server/200.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/200.pid -daemonize -smbios 'type=1,uuid=de5bd55b-d3d3-4799-a149-876379de4c34' -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/200.vnc,password=on' -cpu kvm64,enforce,+kvm_pv_eoi,+kvm_pv_unhalt,+lahf_lm,+sep -m 4096 -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 'pci-bridge,id=pci.3,chassis_nr=3,bus=pci.0,addr=0x5' -device 'vmgenid,guid=4f023491-75f6-4cd3-b9b1-3801b7370d70' -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' -iscsi 'initiator-name=iqn.1993-08.org.debian:01:9cdd9ad7453' -device 'virtio-scsi-pci,id=virtioscsi0,bus=pci.3,addr=0x1' -drive 'file=/mnt/pve/SecureNVMESSD/images/200/vm-200-disk-1.qcow2,if=none,id=drive-scsi0,format=qcow2,cache=none,aio=io_uring,detect-zeroes=on' -device 'scsi-hd,bus=virtioscsi0.0,channel=0,scsi-id=0,lun=0,drive=drive-scsi0,id=scsi0,bootindex=100' -netdev 'type=tap,id=net0,ifname=tap200i0,script=/var/lib/qemu-server/pve-bridge,downscript=/var/lib/qemu-server/pve-bridgedown,vhost=on' -device 'virtio-net-pci,mac=86:10:91:5B:07:DB,netdev=net0,bus=pci.0,addr=0x12,id=net0,rx_queue_size=1024,tx_queue_size=1024' -netdev 'type=tap,id=net1,ifname=tap200i1,script=/var/lib/qemu-server/pve-bridge,downscript=/var/lib/qemu-server/pve-bridgedown,vhost=on' -device 'virtio-net-pci,mac=82:10:91:EE:9F:43,netdev=net1,bus=pci.0,addr=0x13,id=net1,rx_queue_size=1024,tx_queue_size=1024' -netdev 'type=tap,id=net2,ifname=tap200i2,script=/var/lib/qemu-server/pve-bridge,downscript=/var/lib/qemu-server/pve-bridgedown,vhost=on' -device 'virtio-net-pci,mac=1A:20:55:8D:2B:9F,netdev=net2,bus=pci.0,addr=0x14,id=net2,rx_queue_size=1024,tx_queue_size=1024' -netdev 'type=tap,id=net3,ifname=tap200i3,script=/var/lib/qemu-server/pve-bridge,downscript=/var/lib/qemu-server/pve-bridgedown,vhost=on' -device 'virtio-net-pci,mac=4A:07:62:52:B9:BD,netdev=net3,bus=pci.0,addr=0x15,id=net3,rx_queue_size=1024,tx_queue_size=1024' -machine 'type=pc+pve0'' failed: got timeout


However, if I swap vmbr60 with vmbr9999 or any other one it starts...

Any Ideas?

I should tell you that this was an abnormal install. I installed Debian on an encrypted LUKS fs and then installed proxmox on top. That really shouldn't be the issue tho.
 
It ended up being the .VLAN notation on that bond0..

I removed the bond and it works now.. wish i could do the bond tho..
 

About

The Proxmox community has been around for many years and offers help and support for Proxmox VE, Proxmox Backup Server, and Proxmox Mail Gateway.
We think our community is one of the best thanks to people like you!

Get your subscription!

The Proxmox team works very hard to make sure you are running the best software and getting stable updates and security enhancements, as well as quick enterprise support. Tens of thousands of happy customers have a Proxmox subscription. Get yours easily in our online shop.

Buy now!