Machine not creating vmbr0

E

elyograg

New Member
May 17, 2022
4
0
1
We have a proxmox system (7.2-1) that was not able to do DNS lookups when it was trying to self-update. What other info do you need about the environment to be able to help?

I went in and tried to add nameservers to /etc/network/interfaces, tried to ifdown and ifup vmbr0, and lost connectivity.

On power cycle by another member of my team, we found that it did not have vmbr0. So I drove to the DC, restored /etc/network/interfaces to EXACTLY what it was before, and rebooted again. It still has no vmbr0.

I commented everything for vmbr0 and put the IP address directly on enp8s0f0. Which makes it so we can get to the machine, but I really doubt that VM networking is going to function without the bridge.

Manually trying to create and configure vmbr0 does not work. This is the current config:

Code: 
auto lo
iface lo inet loopback

auto enp8s0f0
iface enp8s0f0 inet static
    address 10.10.11.79/22
    netmask 255.255.252.0
    gateway 10.10.10.1

#auto vmbr0
#iface vmbr0 inet static
#    address 10.10.11.79/22
#    netmask 255.255.252.0
#    gateway 10.10.10.1
#    bridge-prts enp8s0f0
#    bridge-sp off
#    bridge-fd 0

iface eno1 inet manual

iface eno2 inet manual

iface enp8s0f1 inet manual
 
Last edited:
Hi,

without the bridge the VMs can't connect to the network. I looks like you have more then one interface in this server. You could connect interface (for example enp8s0f1) and use this one for the bridge. This way you wouldn't lose the connection:

Code: 
auto enp8s0f0
iface enp8s0f0 inet static
    address 10.10.11.79/22
    netmask 255.255.252.0
    gateway 10.10.10.1

auto vmbr0
iface vmbr0 inet manual
    bridge-prts enp8s0f1
    bridge-sp off
    bridge-fd 0

What would be interesting is the last journalctl log where it was configured an not working and grepping for vmbr0 to see if it shows up in there.
 
I tried that config where the IP is on the real interface and no IP on bridge, just as you showed above.

Code: 
root@PVE-IT-02:~# ifup vmbr0
warning: vmbr0: invalid use of bridge attribute (bridge-fd) on non-bridge stanza
warning: vmbr0: interface not recognized - please check interface configuration

I don't see anything else in journalctl output. This is the current state of interfaces -- vmbr0 is not there.

Code: 
root@PVE-IT-02:~# 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 
       valid_lft forever preferred_lft forever
2: eno1: <BROADCAST,MULTICAST> mtu 1500 qdisc noop state DOWN group default qlen 1000
    link/ether 90:b1:1c:51:45:c7 brd ff:ff:ff:ff:ff:ff
    altname enp2s0f0
3: eno2: <BROADCAST,MULTICAST> mtu 1500 qdisc noop state DOWN group default qlen 1000
    link/ether 90:b1:1c:51:45:c8 brd ff:ff:ff:ff:ff:ff
    altname enp2s0f1
4: enp8s0f0: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc mq state UP group default qlen 1000
    link/ether a0:36:9f:0c:f7:04 brd ff:ff:ff:ff:ff:ff
    inet 10.10.11.79/22 scope global enp8s0f0
       valid_lft forever preferred_lft forever
    inet6 fe80::a236:9fff:fe0c:f704/64 scope link 
       valid_lft forever preferred_lft forever
5: enp8s0f1: <BROADCAST,MULTICAST> mtu 1500 qdisc noop state DOWN group default qlen 1000
    link/ether a0:36:9f:0c:f7:06 brd ff:ff:ff:ff:ff:ff
 
I found something in another topic, including in case it's useful:

Code: 
root@PVE-IT-02:~# pveversion -v
proxmox-ve: 7.2-1 (running kernel: 5.15.39-1-pve)
pve-manager: 7.2-7 (running version: 7.2-7/d0dd0e85)
pve-kernel-5.15: 7.2-6
pve-kernel-helper: 7.2-6
pve-kernel-5.13: 7.1-9
pve-kernel-5.15.39-1-pve: 5.15.39-1
pve-kernel-5.13.19-6-pve: 5.13.19-15
pve-kernel-5.13.19-2-pve: 5.13.19-4
ceph-fuse: 15.2.15-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.24-pve1
libproxmox-acme-perl: 1.4.2
libproxmox-backup-qemu0: 1.3.1-1
libpve-access-control: 7.2-4
libpve-apiclient-perl: 3.2-1
libpve-common-perl: 7.2-2
libpve-guest-common-perl: 4.1-2
libpve-http-server-perl: 4.1-3
libpve-storage-perl: 7.2-7
libspice-server1: 0.14.3-2.1
lvm2: 2.03.11-2.1
lxc-pve: 5.0.0-3
lxcfs: 4.0.12-pve1
novnc-pve: 1.3.0-3
proxmox-backup-client: 2.2.5-1
proxmox-backup-file-restore: 2.2.5-1
proxmox-mini-journalreader: 1.3-1
proxmox-widget-toolkit: 3.5.1
pve-cluster: 7.2-2
pve-container: 4.2-2
pve-docs: 7.2-2
pve-edk2-firmware: 3.20210831-2
pve-firewall: 4.2-5
pve-firmware: 3.5-1
pve-ha-manager: 3.4.0
pve-i18n: 2.7-2
pve-qemu-kvm: 6.2.0-11
pve-xtermjs: 4.16.0-1
qemu-server: 7.2-3
smartmontools: 7.2-pve3
spiceterm: 3.2-2
swtpm: 0.7.1~bpo11+1
vncterm: 1.7-1
zfsutils-linux: 2.1.4-pve1
 
Apparently I was blind the last time:

Code: 
#replace this:
bridge-prts
# with this:
bridge-ports

# and replace this:
bridge-sp
# with this:
bridge-stp

it should look like this now:

Code: 
auto lo
iface lo inet loopback

auto enp8s0f0
iface enp8s0f0 inet static
    address 10.10.11.79/22
    netmask 255.255.252.0
    gateway 10.10.10.1

auto vmbr0
iface vmbr0 inet static
    address 10.10.11.79/22
    netmask 255.255.252.0
    gateway 10.10.10.1
    bridge-ports enp8s0f0
    bridge-stp off
    bridge-fd 0

iface eno1 inet manual

iface eno2 inet manual

iface enp8s0f1 inet manual
 
Will having the IP address on two interfaces be problematic? If so, I need to drive to the DC before I do that. I suspect that it will still not work because for some reason vmbr0 is not being created.
 
You must log in or register to reply here.
Top Bottom