can't start because bridge 'vmbr0' does not exist but it does

bobzer

Well-Known Member
Nov 14, 2017
36
5
48
36
Hi,

Just done a fresh install of the latest Proxmox on a Debian Stretch following the guide on the wiki.
But network didn't work so i change to :
Code:
 cat /etc/network/interfaces
# network interface settings; autogenerated
# Please do NOT modify this file directly, unless you know what
# you're doing.
#
# If you want to manage part of the network configuration manually,
# please utilize the 'source' or 'source-directory' directives to do
# so.
# PVE will preserve these directives, but will NOT 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

allow-hotplug eno1

auto eno1
iface eno1 inet static
        address  192.10.20.100
        netmask  255.255.255.0
        gateway  192.10.20.1

auto vmbr0
iface vmbr0 inet static
        bridge_ports eno1
        bridge_stp off
        bridge_fd 0

So now it seems to works because i can connect with ssh and htpps to the Proxmox and it got internet.
Still when i start a vm i got this :
Code:
bridge 'vmbr0' does not exist
kvm: -netdev type=tap,id=net0,ifname=tap100i0,script=/var/lib/qemu-server/pve-bridge,downscript=/var/lib/qemu-server/pve-bridgedown: network script /var/lib/qemu-server/pve-bridge failed with status 512
TASK ERROR: start failed: command '/usr/bin/kvm -id 100 -chardev 'socket,id=qmp,path=/var/run/qemu-server/100.qmp,server,nowait' -mon 'chardev=qmp,mode=control' -pidfile /var/run/qemu-server/100.pid -daemonize -smbios 'type=1,uuid=b49ace46-0e05-4b0d-b923-9238e751626a' -name raid6 -smp '4,sockets=1,cores=4,maxcpus=4' -nodefaults -boot 'menu=on,strict=on,reboot-timeout=1000,splash=/usr/share/qemu-server/bootsplash.jpg' -vga std -vnc unix:/var/run/qemu-server/100.vnc,x509,password -cpu kvm64,+lahf_lm,+sep,+kvm_pv_unhalt,+kvm_pv_eoi,enforce -m 4096 -readconfig /usr/share/qemu-server/pve-q35.cfg -device 'usb-tablet,id=tablet,bus=ehci.0,port=1' -chardev 'socket,path=/var/run/qemu-server/100.qga,server,nowait,id=qga0' -device 'virtio-serial,id=qga0,bus=pci.0,addr=0x8' -device 'virtserialport,chardev=qga0,name=org.qemu.guest_agent.0' -device 'virtio-balloon-pci,id=balloon0,bus=pci.0,addr=0x3' -iscsi 'initiator-name=iqn.1993-08.org.debian:01:9c921687fadc' -drive 'if=none,id=drive-ide2,media=cdrom,aio=threads' -device 'ide-cd,bus=ide.1,unit=0,drive=drive-ide2,id=ide2,bootindex=200' -device 'virtio-scsi-pci,id=scsihw0,bus=pci.0,addr=0x5' -drive 'file=/dev/Gladys-vg/vm-100-disk-1,if=none,id=drive-scsi0,format=raw,cache=none,aio=native,detect-zeroes=on' -device 'scsi-hd,bus=scsihw0.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=C2:34:07:31:F7:FE,netdev=net0,bus=pci.0,addr=0x12,id=net0,bootindex=300' -machine 'type=q35'' failed: exit code 1

for information i tried :
Code:
auto lo
iface lo inet loopback

iface eno1 inet manual

auto vmbr0
iface vmbr0 inet static
        address 192.168.10.2
        netmask 255.255.255.0
        gateway 192.168.10.1
        bridge_ports eno1
        bridge_stp off
        bridge_fd 0
it doesn't work

don't know what to do, can you help me ?

thanks
 
what does
Code:
ip addr
ip link
say?
 
ip addr say:

Code:
# ip addr
1: lo: <LOOPBACK,UP,LOWER_UP> mtu 65536 qdisc noqueue state UNKNOWN group default qlen 1000
    link/loopback 00:00:00:00:00:00 brd 00:00:00:00:00:00
    inet 127.0.0.1/8 scope host lo
       valid_lft forever preferred_lft forever
    inet6 ::1/128 scope host
       valid_lft forever preferred_lft forever
2: eno1: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc pfifo_fast state UP group default qlen 1000
    link/ether 00:22:4d:9a:cf:83 brd ff:ff:ff:ff:ff:ff
    inet 192.10.20.100/24 brd 192.10.20.255 scope global eno1
       valid_lft forever preferred_lft forever
    inet6 2607:fa48:6c08:9a0:222:4dff:fe9a:cf83/64 scope global mngtmpaddr dynamic
       valid_lft 569sec preferred_lft 569sec
    inet6 fe80::222:4dff:fe9a:cf83/64 scope link
       valid_lft forever preferred_lft forever
3: rename3: <BROADCAST,MULTICAST> mtu 1500 qdisc noop state DOWN group default qlen 1000
    link/ether 00:22:4d:9a:cf:7f brd ff:ff:ff:ff:ff:ff

and ip link say:

Code:
# ip link
1: lo: <LOOPBACK,UP,LOWER_UP> mtu 65536 qdisc noqueue state UNKNOWN mode DEFAULT group default qlen 1000
    link/loopback 00:00:00:00:00:00 brd 00:00:00:00:00:00
2: eno1: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc pfifo_fast state UP mode DEFAULT group default qlen 1000
    link/ether 00:22:4d:9a:cf:83 brd ff:ff:ff:ff:ff:ff
3: rename3: <BROADCAST,MULTICAST> mtu 1500 qdisc noop state DOWN mode DEFAULT group default qlen 1000
    link/ether 00:22:4d:9a:cf:7f brd ff:ff:ff:ff:ff:ff

by the way i don't know why i got an interface name rename3...
here is a part of a lspci -v if it can help
Code:
00:19.0 Ethernet controller: Intel Corporation 82579V Gigabit Network Connection (rev 04)
        Subsystem: Intel Corporation 82579V Gigabit Network Connection
        Flags: bus master, fast devsel, latency 0, IRQ 42
        Memory at efe00000 (32-bit, non-prefetchable) [size=128K]
        Memory at efe39000 (32-bit, non-prefetchable) [size=4K]
        I/O ports at f080 [size=32]
        Capabilities: [c8] Power Management version 2
        Capabilities: [d0] MSI: Enable+ Count=1/1 Maskable- 64bit+
        Capabilities: [e0] PCI Advanced Features
        Kernel driver in use: e1000e
        Kernel modules: e1000e

04:00.0 Ethernet controller: Intel Corporation 82574L Gigabit Network Connection
        Subsystem: Intel Corporation 82574L Gigabit Network Connection
        Flags: bus master, fast devsel, latency 0, IRQ 16
        Memory at efc20000 (32-bit, non-prefetchable) [size=128K]
        Memory at efc00000 (32-bit, non-prefetchable) [size=128K]
        I/O ports at c000 [size=32]
        Memory at efc40000 (32-bit, non-prefetchable) [size=16K]
        Capabilities: [c8] Power Management version 2
        Capabilities: [d0] MSI: Enable- Count=1/1 Maskable- 64bit+
        Capabilities: [e0] Express Endpoint, MSI 00
        Capabilities: [a0] MSI-X: Enable+ Count=5 Masked-
        Capabilities: [100] Advanced Error Reporting
        Capabilities: [140] Device Serial Number 00-22-4d-ff-ff-9a-cf-7f
        Kernel driver in use: e1000e
        Kernel modules: e1000e
 
did you reboot after changing your network setup ? only changing /etc/network/interfaces does not change the current network devices, you have to reboot afterwards
 
Yes I did after each test because a simple /etc/init.d/networking restart fail always
 
can you post the output of
Code:
pveversion -v
?
 
here it is:
Code:
# pveversion -v
proxmox-ve: 5.1-32 (running kernel: 4.13.13-2-pve)
pve-manager: 5.1-41 (running version: 5.1-41/0b958203)
pve-kernel-4.13.13-2-pve: 4.13.13-32
libpve-http-server-perl: 2.0-8
lvm2: 2.02.168-pve6
corosync: 2.4.2-pve3
libqb0: 1.0.1-1
pve-cluster: 5.0-19
qemu-server: 5.0-18
pve-firmware: 2.0-3
libpve-common-perl: 5.0-25
libpve-guest-common-perl: 2.0-14
libpve-access-control: 5.0-7
libpve-storage-perl: 5.0-17
pve-libspice-server1: 0.12.8-3
vncterm: 1.5-3
pve-docs: 5.1-12
pve-qemu-kvm: 2.9.1-5
pve-container: 2.0-18
pve-firewall: 3.0-5
pve-ha-manager: 2.0-4
ksm-control-daemon: not correctly installed
glusterfs-client: 3.8.8-1
lxc-pve: 2.1.1-2
lxcfs: 2.0.8-1
criu: 2.11.1-1~bpo90
novnc-pve: 0.6-4
smartmontools: 6.5+svn4324-1

thank you to take some time to help me :)
 
i can boot the vm if i change my ethernet to NAT but there i don't have internet inside the vm
i don't know what to try :-(
any ideas ?
please
 
Code:
auto lo
iface lo inet loopback

iface eno1 inet manual

auto vmbr0
iface vmbr0 inet static
        address 192.168.10.2
        netmask 255.255.255.0
        gateway 192.168.10.1
        bridge_ports eno1
        bridge_stp off
        bridge_fd 0

can you try this config again, and post the ip link and ip addr commands again?
for some reason the vbmr0 gets not created, maybe you find something in the journal ? (journalctl)
 
thanks
I don't know what stuff exactly change but i'm ashame because it's working so i'm sorry to bother you
so i'm glad and sad because i waste so much time without knowing why...

BTW in the console i got some message saying:
vmbr0 entered blocking state
vmbr0 entered disabled state
vmbr0 entered blocking state
vmbr0 entered forwarding state

what does it mean? is it normal ? should i do something?

thanks again
 
hey, what is going on. same problem here. I just setup proxmox 5.1, but nothing can come in. I can ping the outside world, but i cannot ssh nor connect to web gui. is there something wrong with 5.1 ?
 
Don't know about you but i finally figure out that my actual problem was the router ... a static ip was set
 
## have similar situation:

install `pve6.3` on pure `debian 10.8`
```
Bash:
$ cat /etc/debian_version
10.8

$ apt list proxmox-ve
Listing... Done
proxmox-ve/stable,now 6.3-1 all [installed]

$ apt list ifupdown ifupdown2
Listing... Done
ifupdown2/stable,now 3.0.0-1+pve3 all [installed]
ifupdown/stable,now 0.8.35+pve1 amd64 [residual-config]
```

PS: I installed `ifupdown2` manully, cause pve web setup vmbr0, apply need it.

after reboot, network not up.
enp1s0 not up, and vmbr0 not exist.

err msg in /var/log/syslog
```
C-like:
Mar  5 17:47:02 PVE00 networking[429]: error: vmbr0 : enp1s0 : (enp1s0: up cmd '/etc/network/if-up.d/avahi-autoipd' failed: returned 2 (Error: Device for nexthop is not up.
Mar  5 17:47:02 PVE00 networking[429]: ))
Mar  5 17:47:02 PVE00 networking[429]: warning: vmbr0: interface not recognized - please check interface configuration
```


after litter search on net, and try.
just share my solutin, wish helped.

## my solution

edit /etc/network/interfaces

1. comment out source line:
```
Bash:
#source /etc/network/interfaces.d/*
```
// this fix `ifquery -a` got `eth0`, but I really has is `enp1s0`.

2. set enp1s0 as manual

```
Bash:
#iface enp1s0 inet dhcp
#iface enp1s0 inet static  # static not work
iface enp1s0 inet manual
```
// this fix `error: vmbr0 : enp1s0 : (enp1s0: up cmd '/etc/network/if-up.d/avahi-autoipd' failed: returned 2`

then restart networking by:
```
Bash:
sudo systemctl  restart networking.service
```
-- OR --
```
Bash:
sudo /usr/share/ifupdown2/sbin/start-networking start
```
// through `systemctl status networking.service` output, known this script do the realy job, and output result imedialy on console.

-------


## finaly, my total conf

cat /etc/network/interfaces
```
Bash:
# 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 enp1s0
#iface enp1s0 inet dhcp
#iface enp1s0 inet static
iface enp1s0 inet manual

auto vmbr0
iface vmbr0 inet static
    address 10.1.2.3/24
    gateway 10.1.2.1
    bridge-ports enp1s0
    bridge-stp off
    bridge-fd 0

```
 
Last edited:
Had same error after an upgrade from 5.1 to 5.4 (if I remember well).
Resolved the problem by commenting source /etc/network/interfaces.d/* in /etc/network/interfaces
Even if this folder was empty, those line was the problem.
 
I also have this issue. it doesn't work after a boot, I have to use ifup each time to bring it up, then it works, but I do still get this error message when checking the status, I also like to have it start the interface by it self when it boots

Interfaces:
Code:
auto lo
iface lo inet loopback

auto enp8s0
iface enp8s0 inet manual

auto vmbr0
iface vmbr0 inet static
        address 192.10.20.20/24
        gateway 192.10.20.1
        bridge-ports enp8s0
        bridge-stp off
        bridge-fd 0

iface wlp2s0 inet manual

systemctl status networking.service:
Bash:
Mar 04 08:53:01 pve systemd[1]: Starting Network initialization...
Mar 04 08:53:01 pve networking[546]: networking: Configuring network interfaces
Mar 04 08:53:02 pve networking[630]: error: vmbr0: bridge port enp8s0 does not exist
Mar 04 08:53:02 pve systemd[1]: Finished Network initialization.

ip addr:
Bash:
1: lo: <LOOPBACK,UP,LOWER_UP> mtu 65536 qdisc noqueue state UNKNOWN group default qlen 1000
    link/loopback 00:00:00:00:00:00 brd 00:00:00:00:00:00
    inet 127.0.0.1/8 scope host lo
       valid_lft forever preferred_lft forever
    inet6 ::1/128 scope host
       valid_lft forever preferred_lft forever
2: wlp2s0: <BROADCAST,MULTICAST> mtu 1500 qdisc noop state DOWN group default qlen 1000
    link/ether c8:f7:33:90:e2:a0 brd ff:ff:ff:ff:ff:ff
3: vmbr0: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc noqueue state UP group default qlen 1000
    link/ether 68:5b:35:90:3b:79 brd ff:ff:ff:ff:ff:ff
    inet 192.10.20.20/24 scope global vmbr0
       valid_lft forever preferred_lft forever
    inet6 fe80::6a5b:35ff:fe90:3b79/64 scope link
       valid_lft forever preferred_lft forever
4: enp8s0: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc mq master vmbr0 state UP group default qlen 1000
    link/ether 68:5b:35:90:3b:79 brd ff:ff:ff:ff:ff:ff

ip link:
Bash:
1: lo: <LOOPBACK,UP,LOWER_UP> mtu 65536 qdisc noqueue state UNKNOWN mode DEFAULT group default qlen 1000
    link/loopback 00:00:00:00:00:00 brd 00:00:00:00:00:00
2: wlp2s0: <BROADCAST,MULTICAST> mtu 1500 qdisc noop state DOWN mode DEFAULT group default qlen 1000
    link/ether c8:f7:33:90:e2:a0 brd ff:ff:ff:ff:ff:ff
3: vmbr0: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc noqueue state UP mode DEFAULT group default qlen 1000
    link/ether 68:5b:35:90:3b:79 brd ff:ff:ff:ff:ff:ff
4: enp8s0: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc mq master vmbr0 state UP mode DEFAULT group default qlen 1000
    link/ether 68:5b:35:90:3b:79 brd ff:ff:ff:ff:ff:ff

pveversion -v:
Code:
proxmox-ve: 7.2-1 (running kernel: 5.15.30-2-pve)
pve-manager: 7.2-3 (running version: 7.2-3/c743d6c1)
pve-kernel-helper: 7.2-2
pve-kernel-5.15: 7.2-1
pve-kernel-5.15.30-2-pve: 5.15.30-3
ceph-fuse: 15.2.16-pve1
corosync: 3.1.5-pve2
criu: 3.15-1+pve-1
glusterfs-client: 9.2-1
ifupdown2: 3.1.0-1+pmx3
ksm-control-daemon: 1.4-1
libjs-extjs: 7.0.0-1
libknet1: 1.22-pve2
libproxmox-acme-perl: 1.4.2
libproxmox-backup-qemu0: 1.2.0-1
libpve-access-control: 7.1-8
libpve-apiclient-perl: 3.2-1
libpve-common-perl: 7.1-6
libpve-guest-common-perl: 4.1-2
libpve-http-server-perl: 4.1-1
libpve-storage-perl: 7.2-2
libspice-server1: 0.14.3-2.1
lvm2: 2.03.11-2.1
lxc-pve: 4.0.12-1
lxcfs: 4.0.12-pve1
novnc-pve: 1.3.0-3
proxmox-backup-client: 2.1.8-1
proxmox-backup-file-restore: 2.1.8-1
proxmox-mini-journalreader: 1.3-1
proxmox-widget-toolkit: 3.4-10
pve-cluster: 7.2-1
pve-container: 4.2-1
pve-docs: 7.2-2
pve-edk2-firmware: 3.20210831-2
pve-firewall: 4.2-5
pve-firmware: 3.4-1
pve-ha-manager: 3.3-4
pve-i18n: 2.7-1
pve-qemu-kvm: 6.2.0-5
pve-xtermjs: 4.16.0-1
qemu-server: 7.2-2
smartmontools: 7.2-pve3
spiceterm: 3.2-2
swtpm: 0.7.1~bpo11+1
vncterm: 1.7-1
zfsutils-linux: 2.1.4-pve1
 
Last edited:
Remove the: auto enp8s0 line from: /etc/network/interfaces and see if this helps after a reboot of the PVE-host.

You should also update your host; see here how to:
https://forum.proxmox.com/threads/reboot-occurs-randomly.119840/post-520320
Same result as before

I don't know it it have any influence but I do use a thunderbolt to wlan converter as the computer do not have a wlan port itself

Also I do not use enterprise
Code:
deb http://ftp.dk.debian.org/debian bullseye main contrib

deb http://ftp.dk.debian.org/debian bullseye-updates main contrib

# security updates
deb http://security.debian.org bullseye-security main contrib
 
Last edited:

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!