[SOLVED] vmbr0 misconfiguration - guests do not start

[gergogyerek]

Dear Experts,
I messed up the bridge config (created one, then deleted it from gui)
Today I updated the proxmox packages, then reboot and all interfaces were down. I managed to modify /etc/network/interfaces and I can access now the GUI/ssh but containers/vms do not start because they are looking for vmbr0, which does not exist anymore.

root@pve:~# 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 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!

auto lo
iface lo inet loopback

auto eno1
iface eno1 inet static
        address 192.168.0.5/24
        gateway 192.168.0.1

iface eno2 inet manual

source /etc/network/interfaces.d/*
root@pve:~#

Existing VMs/containers do not start:

Task viewer: CT 111 - Start
TASK ERROR: bridge 'vmbr0' does not exist

Existing machine's network properties.



When creating a new container I cannot move forward, because it needs a bridge, but it is empty.

Question:
How to clean up the config so it is not looking for vmbr0.


additional info:

root@pve:~# ip a
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 noprefixroute
       valid_lft forever preferred_lft forever
2: eno1: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc mq state UP group default qlen 1000
    link/ether d0:94:66:13:c1:3d brd ff:ff:ff:ff:ff:ff
    altname enp1s0f0
    inet 192.168.0.5/24 scope global eno1
       valid_lft forever preferred_lft forever
    inet6 fe80::d294:66ff:fe13:c13d/64 scope link
       valid_lft forever preferred_lft forever
3: eno2: <BROADCAST,MULTICAST> mtu 1500 qdisc noop state DOWN group default qlen 1000
    link/ether d0:94:66:13:c1:3e brd ff:ff:ff:ff:ff:ff
    altname enp1s0f1
root@pve:~#

root@pve:~# 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 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!

auto lo
iface lo inet loopback

auto eno1
iface eno1 inet static
        address 192.168.0.5/24
        gateway 192.168.0.1

iface eno2 inet manual

source /etc/network/interfaces.d/*
root@pve:~#

thank you inadvance
Gergo

 

[gergogyerek]

Ok ok ok.
I learned something today...

you should NOT delete the vmbr0, as the official documentation states:

A Linux bridge interface (commonly called vmbrX) is needed to connect guests to the underlying physical network. It can be thought of as a virtual switch which the guests and physical interfaces are connected to.

I modified interfaces file to this and now it is ok.

auto lo
iface lo inet loopback

iface eno1 inet manual

auto vmbr0
iface vmbr0 inet static
    address 192.168.0.5/24
    gateway 192.168.0.1
    bridge-ports eno1
    bridge-stp off
    bridge-fd 0