VM fails to start

O

Octavian

New Member
Proxmox Subscriber
Dec 29, 2020
24
0
1
45
Hello guys,

Im getting this when I start the VM:

Code: 
Jan 07 09:54:00 orion systemd-udevd[1929]: Using default interface naming scheme 'v240'.
Jan 07 09:54:00 orion systemd-udevd[1929]: link_config: autonegotiation is unset or enabled, the speed and duplex are not writable.
Jan 07 09:54:00 orion systemd-udevd[1929]: Could not generate persistent MAC address for tap100i0: No such file or directory
Jan 07 09:54:00 orion systemd[1]: Started Proxmox VE replication runner.
Jan 07 09:54:01 orion kernel: device tap100i0 entered promiscuous mode
Jan 07 09:54:01 orion systemd-udevd[1929]: link_config: autonegotiation is unset or enabled, the speed and duplex are not writable.
Jan 07 09:54:01 orion systemd-udevd[1929]: Could not generate persistent MAC address for fwbr100i0: No such file or directory
Jan 07 09:54:01 orion systemd-udevd[1927]: link_config: autonegotiation is unset or enabled, the speed and duplex are not writable.
Jan 07 09:54:01 orion systemd-udevd[1927]: Using default interface naming scheme 'v240'.
Jan 07 09:54:01 orion systemd-udevd[1927]: Could not generate persistent MAC address for fwpr100p0: No such file or directory
Jan 07 09:54:01 orion systemd-udevd[1944]: link_config: autonegotiation is unset or enabled, the speed and duplex are not writable.
Jan 07 09:54:01 orion systemd-udevd[1944]: Using default interface naming scheme 'v240'.
Jan 07 09:54:01 orion systemd-udevd[1944]: Could not generate persistent MAC address for fwln100i0: No such file or directory
Jan 07 09:54:01 orion kernel: fwbr100i0: port 1(fwln100i0) entered blocking state
Jan 07 09:54:01 orion kernel: fwbr100i0: port 1(fwln100i0) entered disabled state
Jan 07 09:54:01 orion kernel: device fwln100i0 entered promiscuous mode
Jan 07 09:54:01 orion kernel: fwbr100i0: port 1(fwln100i0) entered blocking state
Jan 07 09:54:01 orion kernel: fwbr100i0: port 1(fwln100i0) entered forwarding state
Jan 07 09:54:01 orion kernel: vmbr0: port 2(fwpr100p0) entered blocking state
Jan 07 09:54:01 orion kernel: vmbr0: port 2(fwpr100p0) entered disabled state
Jan 07 09:54:01 orion kernel: device fwpr100p0 entered promiscuous mode
Jan 07 09:54:01 orion kernel: vmbr0: port 2(fwpr100p0) entered blocking state
Jan 07 09:54:01 orion kernel: vmbr0: port 2(fwpr100p0) entered forwarding state
Jan 07 09:54:01 orion kernel: fwbr100i0: port 2(tap100i0) entered blocking state
Jan 07 09:54:01 orion kernel: fwbr100i0: port 2(tap100i0) entered disabled state
Jan 07 09:54:01 orion kernel: fwbr100i0: port 2(tap100i0) entered blocking state
Jan 07 09:54:01 orion kernel: fwbr100i0: port 2(tap100i0) entered forwarding state

Any thoughts why...

Code: 
root@orion:/var/lock/qemu-server# pveversion -v
proxmox-ve: 6.3-1 (running kernel: 5.4.78-2-pve)
pve-manager: 6.3-3 (running version: 6.3-3/eee5f901)
pve-kernel-5.4: 6.3-3
pve-kernel-helper: 6.3-3
pve-kernel-5.4.78-2-pve: 5.4.78-2
pve-kernel-5.4.73-1-pve: 5.4.73-1
ceph-fuse: 12.2.11+dfsg1-2.1+b1
corosync: 3.0.4-pve1
criu: 3.11-3
glusterfs-client: 5.5-3
ifupdown: 0.8.35+pve1
ksm-control-daemon: 1.3-1
libjs-extjs: 6.0.1-10
libknet1: 1.16-pve1
libproxmox-acme-perl: 1.0.5
libproxmox-backup-qemu0: 1.0.2-1
libpve-access-control: 6.1-3
libpve-apiclient-perl: 3.1-3
libpve-common-perl: 6.3-2
libpve-guest-common-perl: 3.1-3
libpve-http-server-perl: 3.0-6
libpve-storage-perl: 6.3-3
libqb0: 1.0.5-1
libspice-server1: 0.14.2-4~pve6+1
lvm2: 2.03.02-pve4
lxc-pve: 4.0.3-1
lxcfs: 4.0.3-pve3
novnc-pve: 1.1.0-1
proxmox-backup-client: 1.0.6-1
proxmox-mini-journalreader: 1.1-1
proxmox-widget-toolkit: 2.4-3
pve-cluster: 6.2-1
pve-container: 3.3-1
pve-docs: 6.3-1
pve-edk2-firmware: 2.20200531-1
pve-firewall: 4.1-3
pve-firmware: 3.1-3
pve-ha-manager: 3.1-1
pve-i18n: 2.2-2
pve-qemu-kvm: 5.1.0-7
pve-xtermjs: 4.7.0-3
qemu-server: 6.3-2
smartmontools: 7.1-pve2
spiceterm: 3.1-1
vncterm: 1.6-2
zfsutils-linux: 0.8.5-pve1


Thanks!
 
Was it working before and now is not?
start it from shell
Code: 
qm start VMID
read carefully the errors and if is not clear, report back.
AFAIR you can also do it from gui, start the vm, double click on the start task in the lower part of the GUI, and read the message
If is just created and never worked, give us
Code: 
qm config VMID
and/also try to reboot Proxmox server
 
Last edited:
mmenaz said:
Was it working before and now is not?
start it from shell
Code: 
qm start VMID
read carefully the errors and if is not clear, report back.
AFAIR you can also do it from gui, start the vm, double click on the start task in the lower part of the GUI, and read the message
If is just created and never worked, give us
Code: 
qm config VMID
and/also try to reboot Proxmox server
Click to expand...
executed
Code: 
qm start 100

from the logs:

Code: 
Jan 07 10:24:00 orion systemd[1]: Started Proxmox VE replication runner.
Jan 07 10:24:35 orion qm[8259]: <root@pam> starting task UPID:orion:00002044:003C1C8F:5FF727B3:qmstart:100:root@pam:
Jan 07 10:24:35 orion qm[8260]: start VM 100: UPID:orion:00002044:003C1C8F:5FF727B3:qmstart:100:root@pam:
Jan 07 10:24:35 orion systemd[1]: Started 100.scope.
Jan 07 10:24:35 orion systemd-udevd[8273]: Using default interface naming scheme 'v240'.
Jan 07 10:24:35 orion systemd-udevd[8273]: link_config: autonegotiation is unset or enabled, the speed and duplex are not writable.
Jan 07 10:24:35 orion systemd-udevd[8273]: Could not generate persistent MAC address for tap100i0: No such file or directory
Jan 07 10:24:35 orion kernel: device tap100i0 entered promiscuous mode
Jan 07 10:24:35 orion systemd-udevd[8273]: link_config: autonegotiation is unset or enabled, the speed and duplex are not writable.
Jan 07 10:24:35 orion systemd-udevd[8273]: Could not generate persistent MAC address for fwbr100i0: No such file or directory
Jan 07 10:24:36 orion systemd-udevd[8267]: link_config: autonegotiation is unset or enabled, the speed and duplex are not writable.
Jan 07 10:24:36 orion systemd-udevd[8267]: Using default interface naming scheme 'v240'.
Jan 07 10:24:36 orion systemd-udevd[8267]: Could not generate persistent MAC address for fwpr100p0: No such file or directory
Jan 07 10:24:36 orion systemd-udevd[8269]: link_config: autonegotiation is unset or enabled, the speed and duplex are not writable.
Jan 07 10:24:36 orion systemd-udevd[8269]: Using default interface naming scheme 'v240'.
Jan 07 10:24:36 orion systemd-udevd[8269]: Could not generate persistent MAC address for fwln100i0: No such file or directory
Jan 07 10:24:36 orion kernel: fwbr100i0: port 1(fwln100i0) entered blocking state
Jan 07 10:24:36 orion kernel: fwbr100i0: port 1(fwln100i0) entered disabled state
Jan 07 10:24:36 orion kernel: device fwln100i0 entered promiscuous mode
Jan 07 10:24:36 orion kernel: fwbr100i0: port 1(fwln100i0) entered blocking state
Jan 07 10:24:36 orion kernel: fwbr100i0: port 1(fwln100i0) entered forwarding state
Jan 07 10:24:36 orion kernel: vmbr0: port 2(fwpr100p0) entered blocking state
Jan 07 10:24:36 orion kernel: vmbr0: port 2(fwpr100p0) entered disabled state
Jan 07 10:24:36 orion kernel: device fwpr100p0 entered promiscuous mode
Jan 07 10:24:36 orion kernel: vmbr0: port 2(fwpr100p0) entered blocking state
Jan 07 10:24:36 orion kernel: vmbr0: port 2(fwpr100p0) entered forwarding state
Jan 07 10:24:36 orion kernel: fwbr100i0: port 2(tap100i0) entered blocking state
Jan 07 10:24:36 orion kernel: fwbr100i0: port 2(tap100i0) entered disabled state
Jan 07 10:24:36 orion kernel: fwbr100i0: port 2(tap100i0) entered blocking state
Jan 07 10:24:36 orion kernel: fwbr100i0: port 2(tap100i0) entered forwarding state
Jan 07 10:24:36 orion qm[8259]: <root@pam> end task UPID:orion:00002044:003C1C8F:5FF727B3:qmstart:100:root@pam: OK
Jan 07 10:25:00 orion systemd[1]: Starting Proxmox VE replication runner...
Jan 07 10:25:00 orion systemd[1]: pvesr.service: Succeeded.
Jan 07 10:25:00 orion systemd[1]: Started Proxmox VE replication runner.
 
Code: 
root@orion:~# cat /etc/network/interfaces
auto lo
iface lo inet loopback

iface eno1 inet manual

auto vmbr0
iface vmbr0 inet static
        address 192.168.1.100/24
        gateway 192.168.1.1
        bridge_ports eno1
        bridge_stp off
        bridge_fd 0

iface eno2 inet manual
root@orion:~#

Code: 
root@orion:~# lspci | grep Ethernet
04:00.0 Ethernet controller: Intel Corporation I350 Gigabit Network Connection (rev 01)
04:00.1 Ethernet controller: Intel Corporation I350 Gigabit Network Connection (rev 01)
root@orion:~#
 
Octavian said:
executed
Code: 
qm start 100
Click to expand...

And...? No message in the console? I don't mean in the logs, just after you entered that command, did you had any message telling why VM could not start?


Octavian said:
from the logs:

Code: 
Jan 07 10:24:00 orion systemd[1]: Started Proxmox VE replication runner.
Jan 07 10:24:35 orion qm[8259]: <root@pam> starting task UPID:orion:00002044:003C1C8F:5FF727B3:qmstart:100:root@pam:
Jan 07 10:24:35 orion qm[8260]: start VM 100: UPID:orion:00002044:003C1C8F:5FF727B3:qmstart:100:root@pam:
Jan 07 10:24:35 orion systemd[1]: Started 100.scope.
Jan 07 10:24:35 orion systemd-udevd[8273]: Using default interface naming scheme 'v240'.
Jan 07 10:24:35 orion systemd-udevd[8273]: link_config: autonegotiation is unset or enabled, the speed and duplex are not writable.
Jan 07 10:24:35 orion systemd-udevd[8273]: Could not generate persistent MAC address for tap100i0: No such file or directory
Jan 07 10:24:35 orion kernel: device tap100i0 entered promiscuous mode
Jan 07 10:24:35 orion systemd-udevd[8273]: link_config: autonegotiation is unset or enabled, the speed and duplex are not writable.
Jan 07 10:24:35 orion systemd-udevd[8273]: Could not generate persistent MAC address for fwbr100i0: No such file or directory
Jan 07 10:24:36 orion systemd-udevd[8267]: link_config: autonegotiation is unset or enabled, the speed and duplex are not writable.
Jan 07 10:24:36 orion systemd-udevd[8267]: Using default interface naming scheme 'v240'.
Jan 07 10:24:36 orion systemd-udevd[8267]: Could not generate persistent MAC address for fwpr100p0: No such file or directory
Jan 07 10:24:36 orion systemd-udevd[8269]: link_config: autonegotiation is unset or enabled, the speed and duplex are not writable.
Jan 07 10:24:36 orion systemd-udevd[8269]: Using default interface naming scheme 'v240'.
Jan 07 10:24:36 orion systemd-udevd[8269]: Could not generate persistent MAC address for fwln100i0: No such file or directory
Jan 07 10:24:36 orion kernel: fwbr100i0: port 1(fwln100i0) entered blocking state
Jan 07 10:24:36 orion kernel: fwbr100i0: port 1(fwln100i0) entered disabled state
Jan 07 10:24:36 orion kernel: device fwln100i0 entered promiscuous mode
Jan 07 10:24:36 orion kernel: fwbr100i0: port 1(fwln100i0) entered blocking state
Jan 07 10:24:36 orion kernel: fwbr100i0: port 1(fwln100i0) entered forwarding state
Jan 07 10:24:36 orion kernel: vmbr0: port 2(fwpr100p0) entered blocking state
Jan 07 10:24:36 orion kernel: vmbr0: port 2(fwpr100p0) entered disabled state
Jan 07 10:24:36 orion kernel: device fwpr100p0 entered promiscuous mode
Jan 07 10:24:36 orion kernel: vmbr0: port 2(fwpr100p0) entered blocking state
Jan 07 10:24:36 orion kernel: vmbr0: port 2(fwpr100p0) entered forwarding state
Jan 07 10:24:36 orion kernel: fwbr100i0: port 2(tap100i0) entered blocking state
Jan 07 10:24:36 orion kernel: fwbr100i0: port 2(tap100i0) entered disabled state
Jan 07 10:24:36 orion kernel: fwbr100i0: port 2(tap100i0) entered blocking state
Jan 07 10:24:36 orion kernel: fwbr100i0: port 2(tap100i0) entered forwarding state
Jan 07 10:24:36 orion qm[8259]: <root@pam> end task UPID:orion:00002044:003C1C8F:5FF727B3:qmstart:100:root@pam: OK
Jan 07 10:25:00 orion systemd[1]: Starting Proxmox VE replication runner...
Jan 07 10:25:00 orion systemd[1]: pvesr.service: Succeeded.
Jan 07 10:25:00 orion systemd[1]: Started Proxmox VE replication runner.
Click to expand...
Here are my logs when I successfully start a VM (VM n. 999), and are almost identical to yours, as far as I can see
Code: 
Jan  8 22:21:15 proxmm01 pvedaemon[10717]: start VM 999: UPID:proxmm01:000029DD:0647E07D:5FF8CCCB:qmstart:999:root@pam:
Jan  8 22:21:15 proxmm01 pvedaemon[22603]: <root@pam> starting task UPID:proxmm01:000029DD:0647E07D:5FF8CCCB:qmstart:999:root@pam:
Jan  8 22:21:15 proxmm01 systemd[1]: Started 999.scope.
Jan  8 22:21:15 proxmm01 systemd-udevd[10724]: Using default interface naming scheme 'v240'.
Jan  8 22:21:15 proxmm01 systemd-udevd[10724]: link_config: autonegotiation is unset or enabled, the speed and duplex are not writable.
Jan  8 22:21:15 proxmm01 systemd-udevd[10724]: Could not generate persistent MAC address for tap999i0: No such file or directory
Jan  8 22:21:16 proxmm01 systemd-udevd[10724]: link_config: autonegotiation is unset or enabled, the speed and duplex are not writable.
Jan  8 22:21:16 proxmm01 systemd-udevd[10724]: Could not generate persistent MAC address for fwbr999i0: No such file or directory
Jan  8 22:21:16 proxmm01 systemd-udevd[10728]: link_config: autonegotiation is unset or enabled, the speed and duplex are not writable.
Jan  8 22:21:16 proxmm01 systemd-udevd[10728]: Using default interface naming scheme 'v240'.
Jan  8 22:21:16 proxmm01 systemd-udevd[10728]: Could not generate persistent MAC address for fwpr999p0: No such file or directory
Jan  8 22:21:16 proxmm01 systemd-udevd[10725]: link_config: autonegotiation is unset or enabled, the speed and duplex are not writable.
Jan  8 22:21:16 proxmm01 systemd-udevd[10725]: Using default interface naming scheme 'v240'.
Jan  8 22:21:16 proxmm01 systemd-udevd[10725]: Could not generate persistent MAC address for fwln999i0: No such file or directory
Jan  8 22:21:16 proxmm01 pvedaemon[22603]: <root@pam> end task UPID:proxmm01:000029DD:0647E07D:5FF8CCCB:qmstart:999:root@pam: OK
Jan  8 22:21:19 proxmm01 pvedaemon[28702]: VM 999 qmp command failed - VM 999 qmp command 'guest-ping' failed - got timeout

but you tell us that your VM does not start? How can you tell it? The start task has an error in the tasks in the GUI? You can't open the VM console? You can't ssh into it? I'm puzzled, please clarify
 
Octavian said:
thanks @mmenaz for reply.
about not starting - my bad - had to change the boot order to start installing the OS.
about random VMs crash - still the same KVM: entry failed, hardware error 0x5 in logs.
https://forum.proxmox.com/threads/vm-ubuntu-server-random-running-issues.81483/#post-360650

Installed ESXi. Everything seems to be working.
Click to expand...
for posterity, please remember to provide the solutions when you find them :)

So what resolved the non-starting error ???

Code: 
Jan 07 10:24:35 orion systemd-udevd[8273]: Could not generate persistent MAC address for fwbr100i0: No such file or directory
Jan 07 10:24:36 orion systemd-udevd[8267]: link_config: autonegotiation is unset or enabled, the speed and duplex are not writable.

"Change boot order" doesn't make sense in the context of my problem yet I see the exact same error, so it isn't clear what you did. Are you sure the boot order was relevant ? Could it have been something else that resolved it ?

Thanks,

-=dave
 
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
Back