Pfsense VM is not stating

C

cariappa

New Member
Nov 15, 2022
16
0
1
i am not able to start pfsense - even proxmox boot screen is not coming . if i remove all the network from vm hardware i am able to start . [CODE]Linux pve2 6.5.11-7-pve #1 SMP PREEMPT_DYNAMIC PMX 6.5.11-7 (2023-12-05T09:44Z) x86_64 The programs included with the Debian GNU/Linux system are free software; the exact distribution terms for each program are described in the individual files in /usr/share/doc/*/copyright. Debian GNU/Linux comes with ABSOLUTELY NO WARRANTY, to the extent permitted by applicable law. Last login: Fri Dec 15 11:00:53 IST 2023 on pts/1 root@pve2:~# pveversion -v proxmox-ve: 8.1.0 (running kernel: 6.5.11-7-pve) pve-manager: 8.1.3 (running version: 8.1.3/b46aac3b42da5d15) proxmox-kernel-helper: 8.1.0 pve-kernel-5.15: 7.4-5 proxmox-kernel-6.5: 6.5.11-7 proxmox-kernel-6.5.11-7-pve-signed: 6.5.11-7 proxmox-kernel-6.2.16-20-pve: 6.2.16-20 proxmox-kernel-6.2: 6.2.16-20 proxmox-kernel-6.2.16-15-pve: 6.2.16-15 pve-kernel-5.15.111-1-pve: 5.15.111-1 pve-kernel-5.15.30-2-pve: 5.15.30-3 ceph-fuse: 16.2.11+ds-2 corosync: 3.1.7-pve3 criu: 3.17.1-2 glusterfs-client: 10.3-5 ifupdown2: 3.2.0-1+pmx7 ksm-control-daemon: 1.4-1 libjs-extjs: 7.0.0-4 libknet1: 1.28-pve1 libproxmox-acme-perl: 1.5.0 libproxmox-backup-qemu0: 1.4.1 libproxmox-rs-perl: 0.3.3 libpve-access-control: 8.0.7 libpve-apiclient-perl: 3.3.1 libpve-common-perl: 8.1.0 libpve-guest-common-perl: 5.0.6 libpve-http-server-perl: 5.0.5 libpve-network-perl: 0.9.5 libpve-rs-perl: 0.8.7 libpve-storage-perl: 8.0.5 libspice-server1: 0.15.1-1 lvm2: 2.03.16-2 lxc-pve: 5.0.2-4 lxcfs: 5.0.3-pve4 novnc-pve: 1.4.0-3 proxmox-backup-client: 3.1.2-1 proxmox-backup-file-restore: 3.1.2-1 proxmox-kernel-helper: 8.1.0 proxmox-mail-forward: 0.2.2 proxmox-mini-journalreader: 1.4.0 proxmox-offline-mirror-helper: 0.6.3 proxmox-widget-toolkit: 4.1.3 pve-cluster: 8.0.5 pve-container: 5.0.8 pve-docs: 8.1.3 pve-edk2-firmware: 4.2023.08-2 pve-firewall: 5.0.3 pve-firmware: 3.9-1 pve-ha-manager: 4.0.3 pve-i18n: 3.1.4 pve-qemu-kvm: 8.1.2-5 pve-xtermjs: 5.3.0-3 qemu-server: 8.0.10 smartmontools: 7.3-pve1 spiceterm: 3.3.0 swtpm: 0.8.0+pve1 vncterm: 1.8.0 zfsutils-linux: 2.2.2-pve1 [/CODE]

This is the error i am getting while starting VM

Code: 
TASK ERROR: start failed: command '/usr/bin/kvm -id 100 -name 'vm100,debug-threads=on' -no-shutdown -chardev 'socket,id=qmp,path=/var/run/qemu-server/100.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/100.pid -daemonize -smbios 'type=1,uuid=dec935af-5104-4c01-9b6e-e885000b690f' -smp '12,sockets=2,cores=6,maxcpus=12' -nodefaults -boot 'menu=on,strict=on,reboot-timeout=1000,splash=/usr/share/qemu-server/bootsplash.jpg' -vnc 'unix:/var/run/qemu-server/100.vnc,password=on' -cpu kvm64,enforce,+kvm_pv_eoi,+kvm_pv_unhalt,+lahf_lm,+sep -m 8832 -object 'iothread,id=iothread-virtioscsi0' -readconfig /usr/share/qemu-server/pve-q35-4.0.cfg -device 'vmgenid,guid=9b9a00d3-296b-4c56-9b2a-e749edab77e5' -device 'usb-tablet,id=tablet,bus=ehci.0,port=1' -device 'VGA,id=vga,bus=pcie.0,addr=0x1' -iscsi 'initiator-name=iqn.1993-08.org.debian:01:ba8f2ab9a44c' -drive 'file=/var/lib/vz/template/iso/pfSense-CE-2.6.0-RELEASE-amd64.iso,if=none,id=drive-ide2,media=cdrom,aio=io_uring' -device 'ide-cd,bus=ide.1,unit=0,drive=drive-ide2,id=ide2,bootindex=101' -device 'virtio-scsi-pci,id=virtioscsi0,bus=pci.3,addr=0x1,iothread=iothread-virtioscsi0' -drive 'file=/dev/pve/vm-100-disk-0,if=none,id=drive-scsi0,format=raw,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=tap100i0,script=/var/lib/qemu-server/pve-bridge,downscript=/var/lib/qemu-server/pve-bridgedown' -device 'e1000,mac=BC:24:11:4E:90:0E,netdev=net0,bus=pci.0,addr=0x12,id=net0,bootindex=102' -netdev 'type=tap,id=net1,ifname=tap100i1,script=/var/lib/qemu-server/pve-bridge,downscript=/var/lib/qemu-server/pve-bridgedown' -device 'e1000,mac=BC:24:11:A9:4E:20,netdev=net1,bus=pci.0,addr=0x13,id=net1' -netdev 'type=tap,id=net2,ifname=tap100i2,script=/var/lib/qemu-server/pve-bridge,downscript=/var/lib/qemu-server/pve-bridgedown' -device 'e1000,mac=BC:24:11:1E:62:B3,netdev=net2,bus=pci.0,addr=0x14,id=net2' -netdev 'type=tap,id=net3,ifname=tap100i3,script=/var/lib/qemu-server/pve-bridge,downscript=/var/lib/qemu-server/pve-bridgedown' -device 'e1000,mac=BC:24:11:9A:0A:66,netdev=net3,bus=pci.0,addr=0x15,id=net3' -netdev 'type=tap,id=net4,ifname=tap100i4,script=/var/lib/qemu-server/pve-bridge,downscript=/var/lib/qemu-server/pve-bridgedown' -device 'e1000,mac=BC:24:11:DD:3C:3C,netdev=net4,bus=pci.0,addr=0x16,id=net4' -netdev 'type=tap,id=net5,ifname=tap100i5,script=/var/lib/qemu-server/pve-bridge,downscript=/var/lib/qemu-server/pve-bridgedown' -device 'e1000,mac=BC:24:11:7C:A8:02,netdev=net5,bus=pci.0,addr=0x17,id=net5' -netdev 'type=tap,id=net6,ifname=tap100i6,script=/var/lib/qemu-server/pve-bridge,downscript=/var/lib/qemu-server/pve-bridgedown' -device 'e1000,mac=BC:24:11:98:83:B0,netdev=net6,bus=pci.1,addr=0x1,id=net6' -netdev 'type=tap,id=net7,ifname=tap100i7,script=/var/lib/qemu-server/pve-bridge,downscript=/var/lib/qemu-server/pve-bridgedown' -device 'e1000,mac=BC:24:11:A6:BD:A8,netdev=net7,bus=pci.1,addr=0x2,id=net7' -netdev 'type=tap,id=net8,ifname=tap100i8,script=/var/lib/qemu-server/pve-bridge,downscript=/var/lib/qemu-server/pve-bridgedown' -device 'e1000,mac=BC:24:11:73:87:9F,netdev=net8,bus=pci.1,addr=0x3,id=net8' -netdev 'type=tap,id=net9,ifname=tap100i9,script=/var/lib/qemu-server/pve-bridge,downscript=/var/lib/qemu-server/pve-bridgedown' -device 'e1000,mac=BC:24:11:56:03:43,netdev=net9,bus=pci.1,addr=0x4,id=net9' -netdev 'type=tap,id=net10,ifname=tap100i10,script=/var/lib/qemu-server/pve-bridge,downscript=/var/lib/qemu-server/pve-bridgedown' -device 'e1000,mac=BC:24:11:1A:9F:CB,netdev=net10,bus=pci.1,addr=0x5,id=net10' -netdev 'type=tap,id=net11,ifname=tap100i11,script=/var/lib/qemu-server/pve-bridge,downscript=/var/lib/qemu-server/pve-bridgedown' -device 'e1000,mac=BC:24:11:83:18:BA,netdev=net11,bus=pci.1,addr=0x6,id=net11' -netdev 'type=tap,id=net12,ifname=tap100i12,script=/var/lib/qemu-server/pve-bridge,downscript=/var/lib/qemu-server/pve-bridgedown' -device 'e1000,mac=BC:24:11:A6:2C:7B,netdev=net12,bus=pci.1,addr=0x7,id=net12' -netdev 'type=tap,id=net13,ifname=tap100i13,script=/var/lib/qemu-server/pve-bridge,downscript=/var/lib/qemu-server/pve-bridgedown' -device 'e1000,mac=BC:24:11:1D:7E:2F,netdev=net13,bus=pci.1,addr=0x8,id=net13' -netdev 'type=tap,id=net14,ifname=tap100i14,script=/var/lib/qemu-server/pve-bridge,downscript=/var/lib/qemu-server/pve-bridgedown' -device 'e1000,mac=BC:24:11:72:7C:84,netdev=net14,bus=pci.1,addr=0x9,id=net14' -netdev 'type=tap,id=net15,ifname=tap100i15,script=/var/lib/qemu-server/pve-bridge,downscript=/var/lib/qemu-server/pve-bridgedown' -device 'e1000,mac=BC:24:11:58:F5:9C,netdev=net15,bus=pci.1,addr=0xa,id=net15' -netdev 'type=tap,id=net16,ifname=tap100i16,script=/var/lib/qemu-server/pve-bridge,downscript=/var/lib/qemu-server/pve-bridgedown' -device 'e1000,mac=BC:24:11:6F:0E:B7,netdev=net16,bus=pci.1,addr=0xb,id=net16' -netdev 'type=tap,id=net17,ifname=tap100i17,script=/var/lib/qemu-server/pve-bridge,downscript=/var/lib/qemu-server/pve-bridgedown' -device 'e1000,mac=BC:24:11:A6:09:F2,netdev=net17,bus=pci.1,addr=0xc,id=net17' -netdev 'type=tap,id=net18,ifname=tap100i18,script=/var/lib/qemu-server/pve-bridge,downscript=/var/lib/qemu-server/pve-bridgedown' -device 'e1000,mac=BC:24:11:0A:D1:77,netdev=net18,bus=pci.1,addr=0xd,id=net18' -netdev 'type=tap,id=net19,ifname=tap100i19,script=/var/lib/qemu-server/pve-bridge,downscript=/var/lib/qemu-server/pve-bridgedown' -device 'e1000,mac=BC:24:11:9B:40:3C,netdev=net19,bus=pci.1,addr=0xe,id=net19' -netdev 'type=tap,id=net20,ifname=tap100i20,script=/var/lib/qemu-server/pve-bridge,downscript=/var/lib/qemu-server/pve-bridgedown' -device 'e1000,mac=BC:24:11:54:23:4E,netdev=net20,bus=pci.1,addr=0xf,id=net20' -netdev 'type=tap,id=net21,ifname=tap100i21,script=/var/lib/qemu-server/pve-bridge,downscript=/var/lib/qemu-server/pve-bridgedown' -device 'e1000,mac=BC:24:11:F0:6F:DF,netdev=net21,bus=pci.1,addr=0x10,id=net21' -netdev 'type=tap,id=net22,ifname=tap100i22,script=/var/lib/qemu-server/pve-bridge,downscript=/var/lib/qemu-server/pve-bridgedown' -device 'e1000,mac=BC:24:11:68:B9:A0,netdev=net22,bus=pci.1,addr=0x11,id=net22' -netdev 'type=tap,id=net23,ifname=tap100i23,script=/var/lib/qemu-server/pve-bridge,downscript=/var/lib/qemu-server/pve-bridgedown' -device 'e1000,mac=BC:24:11:79:44:E7,netdev=net23,bus=pci.1,addr=0x12,id=net23' -netdev 'type=tap,id=net24,ifname=tap100i24,script=/var/lib/qemu-server/pve-bridge,downscript=/var/lib/qemu-server/pve-bridgedown' -device 'e1000,mac=BC:24:11:6D:0D:CA,netdev=net24,bus=pci.1,addr=0x13,id=net24' -netdev 'type=tap,id=net25,ifname=tap100i25,script=/var/lib/qemu-server/pve-bridge,downscript=/var/lib/qemu-server/pve-bridgedown' -device 'e1000,mac=BC:24:11:F6:53:ED,netdev=net25,bus=pci.1,addr=0x14,id=net25' -netdev 'type=tap,id=net26,ifname=tap100i26,script=/var/lib/qemu-server/pve-bridge,downscript=/var/lib/qemu-server/pve-bridgedown' -device 'e1000,mac=BC:24:11:1D:FD:77,netdev=net26,bus=pci.1,addr=0x15,id=net26' -netdev 'type=tap,id=net27,ifname=tap100i27,script=/var/lib/qemu-server/pve-bridge,downscript=/var/lib/qemu-server/pve-bridgedown' -device 'e1000,mac=BC:24:11:5A:51:74,netdev=net27,bus=pci.1,addr=0x16,id=net27' -netdev 'type=tap,id=net28,ifname=tap100i28,script=/var/lib/qemu-server/pve-bridge,downscript=/var/lib/qemu-server/pve-bridgedown' -device 'e1000,mac=BC:24:11:D2:44:68,netdev=net28,bus=pci.1,addr=0x17,id=net28' -netdev 'type=tap,id=net29,ifname=tap100i29,script=/var/lib/qemu-server/pve-bridge,downscript=/var/lib/qemu-server/pve-bridgedown' -device 'e1000,mac=BC:24:11:D6:4D:86,netdev=net29,bus=pci.1,addr=0x18,id=net29' -machine 'type=q35+pve0'' failed: got timeout
 
Last edited:
Yes, we understand that. Have you tried the work-around? Maybe it helps, maybe not. You have nothing to lose.
 
sb-jw said:
Yes, we understand that. Have you tried the work-around? Maybe it helps, maybe not. You have nothing to lose.
Click to expand...
Yes i tried installing new pfsense , but proxmox bios screen itself not coming while starting vm. if i remove network addaptor it boots. gor two pci card
 
Code: 
agent: 1
balloon: 0
boot: order=scsi0;ide2
cores: 4
cpu: kvm64
ide2: local:iso/pfSense-CE-2.7.0-RELEASE-amd64.iso,media=cdrom,size=747284K
machine: q35
memory: 8096
meta: creation-qemu=8.1.2,ctime=1702537346
net0: virtio=BC:24:11:24:06:F6,bridge=vmbr1,tag=110
net1: virtio=BC:24:11:8C:64:5E,bridge=vmbr1,tag=111
net10: virtio=BC:24:11:C8:3D:76,bridge=vmbr1,tag=121
net11: virtio=BC:24:11:F1:E3:4D,bridge=vmbr1,tag=121
net12: virtio=BC:24:11:5B:9E:A7,bridge=vmbr1,tag=122
net13: virtio=BC:24:11:B4:25:E6,bridge=vmbr1,tag=123
net14: virtio=BC:24:11:2E:BA:F7,bridge=vmbr1,tag=124
net15: virtio=BC:24:11:F1:3A:5B,bridge=vmbr1,tag=125
net16: virtio=BC:24:11:5E:75:2E,bridge=vmbr1,tag=126
net17: virtio=BC:24:11:A4:9E:89,bridge=vmbr1,tag=127
net18: virtio=BC:24:11:5A:CD:8B,bridge=vmbr1,tag=128
net19: virtio=BC:24:11:2E:70:AC,bridge=vmbr1,tag=129
net2: virtio=BC:24:11:D2:E6:89,bridge=vmbr1,tag=112
net20: virtio=BC:24:11:04:EB:EF,bridge=vmbr1,tag=130
net21: virtio=BC:24:11:0A:B6:62,bridge=vmbr1,tag=131
net22: virtio=BC:24:11:E7:5F:5E,bridge=vmbr1,tag=132
net23: virtio=BC:24:11:3C:7A:77,bridge=vmbr1,tag=133
net24: virtio=BC:24:11:BD:84:D4,bridge=vmbr1,tag=134
net25: virtio=BC:24:11:54:68:88,bridge=vmbr1,tag=136
net26: virtio=BC:24:11:65:87:4E,bridge=vmbr1,tag=137
net27: virtio=BC:24:11:35:67:9D,bridge=vmbr1,tag=150
net28: virtio=BC:24:11:5F:AC:CC,bridge=vmbr1,tag=151
net29: virtio=BC:24:11:A7:0E:F9,bridge=vmbr1,tag=153
net3: virtio=BC:24:11:CA:66:12,bridge=vmbr1,tag=114
net4: virtio=BC:24:11:94:38:64,bridge=vmbr1,tag=115
net5: virtio=BC:24:11:8C:43:54,bridge=vmbr1,tag=116
net6: virtio=BC:24:11:99:5D:68,bridge=vmbr1,tag=117
net7: virtio=BC:24:11:79:59:F5,bridge=vmbr1,tag=118
net8: virtio=BC:24:11:30:CF:3A,bridge=vmbr1,tag=119
net9: virtio=BC:24:11:90:CB:38,bridge=vmbr1,tag=120
numa: 0
ostype: l26
scsi0: local-lvm:vm-102-disk-0,iothread=1,size=32G
scsihw: virtio-scsi-single
smbios1: uuid=7cd0c0c2-2706-4950-98a1-9b7494296d1c
sockets: 2
 
inux pve2 6.5.11-7-pve #1 SMP PREEMPT_DYNAMIC PMX 6.5.11-7 (2023-12-05T09:44Z) x86_64 The programs included with the Debian GNU/Linux system are free software; the exact distribution terms for each program are described in the individual files in /usr/share/doc/*/copyright. Debian GNU/Linux comes with ABSOLUTELY NO WARRANTY, to the extent permitted by applicable law. Last login: Fri Dec 15 14:26:24 IST 2023 on pts/1 root@pve2:~# qm config 100 balloon: 0 boot: order=scsi0;ide2 cores: 4 cpu: host ide2: local:iso/pfSense-CE-2.7.2-RELEASE-amd64.iso,media=cdrom,size=854172K machine: q35 memory: 8832 meta: creation-qemu=8.1.2,ctime=1702605151 net0: e1000=BC:24:11:D4:5C:9B,bridge=vmbr1,firewall=1,tag=500 net1: e1000=BC:24:11:29:DD:7A,bridge=vmbr1,firewall=1,tag=501 net10: e1000=BC:24:11:1A:9F:CB,bridge=vmbr1,firewall=1,tag=310 net11: e1000=BC:24:11:83:18:BA,bridge=vmbr1,firewall=1,tag=311 net12: e1000=BC:24:11:A6:2C:7B,bridge=vmbr1,firewall=1,tag=312 net13: e1000=BC:24:11:1D:7E:2F,bridge=vmbr1,firewall=1,tag=313 net14: e1000=BC:24:11:72:7C:84,bridge=vmbr1,firewall=1,tag=314 net15: e1000=BC:24:11:58:F5:9C,bridge=vmbr1,firewall=1,tag=315 net16: e1000=BC:24:11:6F:0E:B7,bridge=vmbr1,firewall=1,tag=316 net17: e1000=BC:24:11:A6:09:F2,bridge=vmbr1,firewall=1,tag=317 net18: e1000=BC:24:11:0A:D1:77,bridge=vmbr1,firewall=1,tag=318 net19: e1000=BC:24:11:9B:40:3C,bridge=vmbr1,firewall=1,tag=319 net2: e1000=BC:24:11:C6:6F:D0,bridge=vmbr1,firewall=1,tag=502 net20: e1000=BC:24:11:54:23:4E,bridge=vmbr1,firewall=1,tag=320 net21: e1000=BC:24:11:F0:6F:DF,bridge=vmbr1,firewall=1,tag=321 net22: e1000=BC:24:11:68:B9:A0,bridge=vmbr1,firewall=1,tag=322 net23: e1000=BC:24:11:79:44:E7,bridge=vmbr1,firewall=1,tag=323 net24: e1000=BC:24:11:6D:0D:CA,bridge=vmbr1,firewall=1,tag=324 net25: e1000=BC:24:11:F6:53:ED,bridge=vmbr1,firewall=1,tag=325 net26: e1000=BC:24:11:1D:FD:77,bridge=vmbr1,firewall=1,tag=326 net27: e1000=BC:24:11:D8:2B:5B,bridge=vmbr1,firewall=1,tag=527 net28: e1000=BC:24:11:35:F6:F1,bridge=vmbr1,firewall=1,tag=528 net29: e1000=BC:24:11:D0:B1:70,bridge=vmbr1,firewall=1,tag=529 net3: e1000=BC:24:11:37:82:4B,bridge=vmbr1,firewall=1,tag=503 net4: e1000=BC:24:11:90:3C:27,bridge=vmbr1,firewall=1,tag=504 net5: e1000=BC:24:11:9A:05:C9,bridge=vmbr1,firewall=1,tag=505 net6: e1000=BC:24:11:98:83:B0,bridge=vmbr1,firewall=1,tag=306 net7: e1000=BC:24:11:A6:BD:A8,bridge=vmbr1,firewall=1,tag=307 net8: e1000=BC:24:11:73:87:9F,bridge=vmbr1,firewall=1,tag=308 net9: e1000=BC:24:11:56:03:43,bridge=vmbr1,firewall=1,tag=309 numa: 0 ostype: l26 parent: rawhardware scsi0: local-lvm:vm-100-disk-0,iothread=1,size=32G scsihw: virtio-scsi-single smbios1: uuid=dec935af-5104-4c01-9b6e-e885000b690f sockets: 1 vga: std vmgenid: 9b9a00d3-296b-4c56-9b2a-e749edab77e5 root@pve2:~#
 
If the Redheat article [1] is true, then you are over the limit of what VirtIO can do. You can create a maximum of 32 VirtIO devices, but 4 of them are already reserved, leaving 28. But you have already created 29 network adapters.

My suggestion would be to remove a network adapter and then try to start the VM. You do this until the VM starts.

[1] https://access.redhat.com/documenta...on-virtualization_limitations-kvm_limitations
 
sb-jw said:
If the Redheat article [1] is true, then you are over the limit of what VirtIO can do. You can create a maximum of 32 VirtIO devices, but 4 of them are already reserved, leaving 28. But you have already created 29 network adapters.

My suggestion would be to remove a network adapter and then try to start the VM. You do this until the VM starts.

[1] https://access.redhat.com/documenta...on-virtualization_limitations-kvm_limitations
Click to expand...
i have one more server which is running fine.
5 (2023-09-28T13:53Z) x86_64 The programs included with the Debian GNU/Linux system are free software; the exact distribution terms for each program are described in the individual files in /usr/share/doc/*/copyright. Debian GNU/Linux comes with ABSOLUTELY NO WARRANTY, to the extent permitted by applicable law. Last login: Fri Dec 15 16:52:52 IST 2023 from 192.168.100.4 on pts/0 root@pve3:~# qm config 103 boot: order=scsi0;ide2 cores: 8 cpu: x86-64-v2-AES hotplug: disk,network,usb ide2: local:iso/pfSense-CE-2.7.0-RELEASE-amd64.iso,media=cdrom,size=747284K memory: 12064 meta: creation-qemu=8.0.2,ctime=1701509204 name: pf2.7-new-master net0: virtio=C2:AD:94:93:6C:4E,bridge=vmbr2,link_down=1,tag=31 net1: virtio=5A:52:02:BD:F6:C0,bridge=vmbr2,tag=1 net10: virtio=42:D4:F3:64:E4:16,bridge=vmbr2,tag=10 net11: virtio=3A:88:E3:93:F5:B4,bridge=vmbr2,tag=11 net12: virtio=4E:30:CD:E0:3D:12,bridge=vmbr2,tag=12 net13: virtio=CE:95:1D:FF:0C:F6,bridge=vmbr2,tag=13 net14: virtio=72:D1:5A:DD:67:DE,bridge=vmbr2,tag=14 net15: virtio=D2:DF:C3:B3:9A:CD,bridge=vmbr2,tag=15 net16: virtio=9A:9A:83:63:DD:24,bridge=vmbr2,tag=16 net17: virtio=5E:92:63:63:C4:B0,bridge=vmbr2,tag=17 net18: virtio=42:8C:CA:9D:75:E9,bridge=vmbr2,tag=18 net19: virtio=2E:69:D1:2C:3C:4D,bridge=vmbr2,tag=19 net2: virtio=E2:17:2C:8F:85:5C,bridge=vmbr2,tag=51 net20: virtio=12:47:01:C4:7E:41,bridge=vmbr2,tag=20 net21: virtio=86:4C:66:59:B4:79,bridge=vmbr2,tag=21 net22: virtio=F6:61:C7:26:5A:3C,bridge=vmbr2,tag=22 net23: virtio=F6:00:F8:1B:21:FA,bridge=vmbr2,tag=23 net24: virtio=3A:4E:3B:1F:86:EB,bridge=vmbr2,tag=24 net25: virtio=FE:3A:DE:DD:D2:66,bridge=vmbr2,tag=25 net26: virtio=FE:7F:58:87:8E:68,bridge=vmbr2,tag=100 net27: virtio=7A:1E:5E:ED:8A:C4,bridge=vmbr1,tag=32 net28: virtio=C2:0A:C2:6F:DD:88,bridge=vmbr1,tag=33 net29: virtio=EE:CF:57:A4:D3:ED,bridge=vmbr1,tag=34 net3: virtio=8A:86:75:34:1A:CA,bridge=vmbr2,tag=52 net4: virtio=26:1D:02:E0:65:B3,bridge=vmbr2,tag=4 net5: virtio=32:DE:1E:CA:04:1E,bridge=vmbr2,tag=5 net6: virtio=22:64:03:4A:38:C9,bridge=vmbr2,tag=6 net7: virtio=C2:F0:B0:07:00:02,bridge=vmbr2,tag=7 net8: virtio=F2:97:39:DF:99:88,bridge=vmbr2,tag=8 net9: virtio=C2:6C:AE:0A:24:64,bridge=vmbr2,tag=9 numa: 0 ostype: l26 parent: before scsi0: pve3-thin:vm-103-disk-0,iothread=1,size=32G scsihw: virtio-scsi-single smbios1: uuid=38053a5a-7233-4ae3-bf31-f3c8ed3bc09f sockets: 2 vmgenid: 2cf3d3b6-880a-49b0-bd18-fbb1b45cc0fa root@pve3:~#
 
sb-jw said:
Okay, but what role does that play now? We're trying to evaluate why one VM isn't running and not find out which one is running well and working.
Click to expand...
i am saying 29 nics should not be a problem. but proxmox 8.1 i am not able to boot. i am not understanding why i am not able to start a VM if i increase the nics. if its a proxmox limitation then how is it running on my other server. Can anyone help me
 
I'm trying to help you, but you refuse to try anything to get close to it.

I don't have access to your infrastructure, so I can only tell you what I would try, but if you don't want to do it, then I can't help you.
 
sb-jw said:
I'm trying to help you, but you refuse to try anything to get close to it.

I don't have access to your infrastructure, so I can only tell you what I would try, but if you don't want to do it, then I can't help you.
Click to expand...
I have tried deleting one nic it did not start . i have deleted it 19 nics then it started, if i shutdown again same error, i have changed the processor then it started. dono what is the reason
 
You must log in or register to reply here.

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!

Quick Navigation

Home Get Subscription Wiki Downloads Proxmox Customer Portal About

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!
Community platform by XenForo® © 2010-2024 XenForo Ltd.
Top Bottom