On 1/29/21 6:58 PM, Jasper Wallace wrote: > Package: openvswitch-common > Version: 2.10.6+ds1-0+deb10u1 > Severity: important > > Dear Maintainer, > > We run some VM's under kvm/libvirt/virsh with openvswitch for networking. > > The ovs bridge is configured by /etc/network/interfaces.d/br0, which contains: > > # Ansible managed > > # one of the physical interfaces > allow-bond0 eno1 > iface eno1 inet manual > ovs_type OVSPort > ovs_bonds bond0 > > # the other one > allow-bond0 eno2 > iface eno2 inet manual > ovs_type OVSPort > ovs_bonds bond0 > > # bond them together with LACP > # XXX the old config had "bond-xmit-hash-policy layer2", needed? > auto bond0 > allow-br0 bond0 > iface bond0 inet manual > ovs_bridge br0 > ovs_type OVSBond > ovs_bonds eno1 eno2 > ovs_options bond_mode=balance-tcp lacp=active other_config:lacp-time=fast > up ifup eno1 > up ifup eno2 > > # and add the bond to the bridge > # XXX the old config might of had spanning tree on > # but I don't think we need it really. > auto br0 > allow-ovs br0 > iface br0 inet static > address 192.168.7.41/24 > gateway 192.168.7.1 > ovs_type OVSBridge > ovs_ports bond0 > > Then when the libvirt/kvm VM's are created there ports get added to br0. > > After the security upgrade of ovs on the 23rd the switch was > re-created but all the ports connected to the vm's where lost. > > I'm not sure how to resolve this situtaion other then rebooting the > machine - is there some way make the OVS DB be persist over restarts? > > Should we be configuring OVS some other way? > > Thanks, > > Jasper
Hi Jasper, This is a well known issue in OpenVSwitch that I haven't been able to solve either. Indeed, you will need to reboot. If you find a workaround, let me know. Cheers, Thomas Goirand (zigo)
