[SOLVED] Bridge does not exist

A

AlSam

New Member
Nov 5, 2014
8
1
1
Hey everyone. I am having trouble using an OVS Bridge in a CT. My interface config is the following:
allow-vmbr1 eth1
iface eth1 inet manual
ovs_type OVSPort
ovs_bridge vmbr1

auto vmbr1
allow-ovs vmbr1
iface vmbr1 inet manual
ovs_type OVSBridge
ovs_ports eth1

When I start the CT the error message is: bridge 'vmbr1' does not exist.
What am I missing? Thanks in advance.
 
Last edited:
root@proxmox:~# ovs-vsctl show
82367e69-b28e-44ef-ab8c-3c49d8ef5f9b
ovs_version: "1.4.2"
 
root@proxmox:~# apt-get install openvswitch-switch
Reading package lists... Done
Building dependency tree
Reading state information... Done
openvswitch-switch is already the newest version.
0 upgraded, 0 newly installed, 0 to remove and 59 not upgraded.

How do I verify if my repos are correct?
 
Thank you for your help spirit and tom. The issue seems to be resolved now. The CT no longer fails when starting. I now have the proper version of ovs. I had to manually add allow-ovs vmbr1 to the vmbr1 bridge definition for it to start, without it the CT kept failing to start.

Code: 
root@proxmox:~# ovs-vsctl show
876e2087-39ba-42fc-9fba-81912b25c0dc
    ovs_version: "2.3.0"

Here are my network interface settings (/etc/network/interfaces)

Code: 
# network interface settings
 ...
allow-vmbr1 eth1
iface eth1 inet manual
        ovs_type OVSPort
        ovs_bridge vmbr1
...

auto vmbr1
[B][SIZE=4]allow-ovs vmbr1[/SIZE][/B]
iface vmbr1 inet manual
        ovs_type OVSBridge
        ovs_ports eth1
 
For posterity, here is a recap of the steps I took to resolve the problem:

  1. removed existing OVS bridge (GUI)
  2. rebooted proxmox node
  3. added non-subscription repository to sources.list
  4. apt-get update
  5. apt-get install openvswitch-switch
  6. created new OVS Bridge (vmbr1) using GUI
  7. rebooted proxmox node
  8. manually added allow-ovs vmbr1 to the vmbr1 bridge definition in /etc/network/interfaces
  9. restarted networking
  10. added vmbr1 to CT (GUI)
  11. configured interface from within CT

Again, many thanks to both tom and spirit for their help.
 
  • Like
Reactions: elriti
Please note that 'allow-ovs' is not needed if the openvswitch start order is correct.
Service 'openvswitch-switch' should start before service 'networking'. Please check
correct order in /etc/rcS.d.

You can try to restore correct order with:

# insserv -d /etc/init.d/openvswitch-switch
 
It appears that openvswitch-switch is not contemplated at all in /etc/rcS.d. Should the provided command correct that?
Code: 
root@proxmox:/etc/rcS.d# ls
README
S01mountkernfs.sh
S02udev
S03mountdevsubfs.sh
S04bootlogd
S05keymap.sh
S06hdparm
S06hostname.sh
S06hwclock.sh
S06lvm2
S07checkroot.sh
S08checkroot-bootclean.sh
S08kmod
S08mtab.sh
S08pvenetcommit
S09checkfs.sh
S10mountall.sh
S11mountall-bootclean.sh
S12procps
S12udev-mtab
S12urandom
S13networking
S14rpcbind
S15nfs-common
S16mountnfs.sh
S17mountnfs-bootclean.sh
S18console-screen.sh
S19bootmisc.sh
S19open-iscsi
S19x11-common
S20stop-bootlogd-single
 
Thanks, dietmar. I ran the command and removed 'allow-ovs'. The CT is running just fine.
 
Hi All,
thanks for your post and suggestions!
I'm still in stuck with repository, indeed last version 3.3 of Proxmox is based on Wheezy that use an old version of openvswitch (1.4.2) - with that version, I've built my ovs bridge, but I get some weird error on interface: RX traffic on eth0 (the one connected wired) and TX traffic on vmbr0 (ovs port of bridge that has eth0 port also) - and no network is unreachable.

I've also tried to compile module openvswitch–datapath, but no way cause no header for linux-header***-pve.

Any suggestion?

Thanks to all!
 
jokojojojo said:
Hi All,
thanks for your post and suggestions!
I'm still in stuck with repository, indeed last version 3.3 of Proxmox is based on Wheezy that use an old version of openvswitch (1.4.2) - with that version, I've built my ovs bridge, but I get some weird error on interface: RX traffic on eth0 (the one connected wired) and TX traffic on vmbr0 (ovs port of bridge that has eth0 port also) - and no network is unreachable.

I've also tried to compile module openvswitch–datapath, but no way cause no head
er for linux-header***-pve.

Any suggestion?

Thanks to all!
Click to expand...

Hi, you need to configure proxmox no-subscription repository
https://pve.proxmox.com/wiki/Package_repositories
 
On a fresh installation, I had to: insserv -d /etc/init.d/openvswitch-switch to get the networking up at boot time after installing openvswitch to a fresh install

root@hv1:~# dpkg -l|grep openv
ii openvswitch-common 2.5.0-1 amd64 Open vSwitch common components
ii openvswitch-switch 2.5.0-1 amd64 Open vSwitch switch implementations
root@hv1:~# pveversion
pve-manager/4.2-17/e1400248 (running kernel: 4.4.15-1-pve)
root@hv1:~#
 
Im having some issues also, a fresh install of the latest pve and installed openvswitch-swicth.
Im runnign the suggetsed command:
insserv -d /etc/init.d/openvswitch-switch
And after that /etc/init.d/networking restart

Then the network is up and running, how do i I make it autostart when rebooting??

This is the results from ls /etc/rcS.d/

S01mountkernfs.sh S09checkroot-bootclean.sh S17mountnfs-bootclean.sh
S02udev S09kmod S18kbd
S03mountdevsubfs.sh S10mountall.sh S19console-setup
S04bootlogd S11mountall-bootclean.sh S20apparmor
S05keyboard-setup S12procps S20bootmisc.sh
S06hdparm S12udev-finish S20open-iscsi
S06hostname.sh S12urandom S20x11-common
S06hwclock.sh S13networking S21stop-bootlogd-single
S06lvm2 S14rpcbind
S07checkroot.sh S15nfs-common
 
You must log in or register to reply here.
Top Bottom