[SOLVED] Newbie - it doesn't start any VM

[Nick_L71]

Dear all,

sorry but I am completely lost. I managed installing Proxmox (latest version) on my old linux server. Proxmox is starting fine but whenever I want to start a VM I get the following error messages:

Apr 04 15:48:12 virtual pvedaemon[851]: <root@pam> starting task UPID:virtual:000010BC:0001AAD6:660EAF9C:qmstart:100:root@pam:
Apr 04 15:48:13 virtual systemd[1]: Started 100.scope.
Apr 04 15:48:13 virtual kernel: tap100i0: entered promiscuous mode
Apr 04 15:48:13 virtual kernel: vmbr0: port 2(tap100i0) entered blocking state
Apr 04 15:48:13 virtual kernel: vmbr0: port 2(tap100i0) entered disabled state
Apr 04 15:48:13 virtual kernel: tap100i0: entered allmulticast mode
Apr 04 15:48:13 virtual kernel: vmbr0: port 2(tap100i0) entered blocking state
Apr 04 15:48:13 virtual kernel: vmbr0: port 2(tap100i0) entered forwarding state
Apr 04 15:48:14 virtual kernel: tap100i0: left allmulticast mode
Apr 04 15:48:14 virtual kernel: vmbr0: port 2(tap100i0) entered disabled state
Apr 04 15:48:14 virtual systemd[1]: 100.scope: Deactivated successfully.
Apr 04 15:48:14 virtual systemd[1]: 100.scope: Consumed 1.152s CPU time.
Apr 04 15:48:14 virtual pvedaemon[4284]: start failed: QEMU exited with code 1
Apr 04 15:48:14 virtual pvedaemon[851]: <root@pam> end task UPID:virtual:000010BC:0001AAD6:660EAF9C:qmstart:100:root@pam: start failed: QEMU exited with code 1
Apr 04 15:48:12 virtual pvedaemon[851]: <root@pam> starting task UPID:virtual:000010BC:0001AAD6:660EAF9C:qmstart:100:root@pam:
Apr 04 15:48:13 virtual systemd[1]: Started 100.scope.
Apr 04 15:48:13 virtual kernel: tap100i0: entered promiscuous mode
Apr 04 15:48:13 virtual kernel: vmbr0: port 2(tap100i0) entered blocking state
Apr 04 15:48:13 virtual kernel: vmbr0: port 2(tap100i0) entered disabled state
Apr 04 15:48:13 virtual kernel: tap100i0: entered allmulticast mode
Apr 04 15:48:13 virtual kernel: vmbr0: port 2(tap100i0) entered blocking state
Apr 04 15:48:13 virtual kernel: vmbr0: port 2(tap100i0) entered forwarding state
Apr 04 15:48:14 virtual kernel: tap100i0: left allmulticast mode
Apr 04 15:48:14 virtual kernel: vmbr0: port 2(tap100i0) entered disabled state
Apr 04 15:48:14 virtual systemd[1]: 100.scope: Deactivated successfully.
Apr 04 15:48:14 virtual systemd[1]: 100.scope: Consumed 1.152s CPU time.
Apr 04 15:48:14 virtual pvedaemon[4284]: start failed: QEMU exited with code 1
Apr 04 15:48:14 virtual pvedaemon[851]: <root@pam> end task UPID:virtual:000010BC:0001AAD6:660EAF9C:qmstart:100:root@pam: start failed: QEMU exited with code 1

I can see some lines here mentioning vmbr0 - I haven't changed any network settings after installation and I don't know how to fix it.

Thanks for your advice!
Nick

please find some information about my first vm here:

root@virtual:~# qm config <vmid>
-bash: syntax error near unexpected token `newline'
root@virtual:~# qm config 100
boot: order=scsi0;ide2;net0
cores: 1
cpu: x86-64-v2-AES
ide2: local:iso/debian-12.5.0-amd64-netinst.iso,media=cdrom,size=629M
memory: 2048
meta: creation-qemu=8.1.5,ctime=1712237550
net0: virtio=BC:24:11:6A:B2:AF,bridge=vmbr0
numa: 0
ostype: l26
scsi0: local-lvm:vm-100-disk-0,iothread=1,size=256G
scsihw: virtio-scsi-single
smbios1: uuid=337f0c09-f3a3-4a8d-9bc0-5b6633964fb0
sockets: 1
vmgenid: ae507ddb-d023-49a5-9213-04758b47ec42

 

[bbgeek17]

Try to change your CPU to "host"
And double check the ISO, try to detach/remove it as a test.

---

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

 

[Nick_L71]

Hello bbgeek17!

The CPU change did the trick! Thanks for your support. The VM is working like a charm.
My 2 x Intel(R) Pentium(R) CPU G3220 is quite outdated and the selected default setting was obviously causing the issue...



Cheers
Nick
p.s. is there any log with more information? The system log or journalctl was not really helpful.