Thanks for the response Ben!
Here's the test process:
Clean boot:
[root@prv-10-11-ksupp user]# ovs-vsctl show
cf2a15bb-ca36-481a-aa3c-80df59814c76
Bridge "br0"
Port "br0"
Interface "br0"
type: internal
Port "eth3"
Interface "eth3"
Port "vnet0"
Interface "vnet0"
Port "vnet1"
Interface "vnet1"
Port "patch_0-1"
Interface "patch_0-1"
type: patch
options: {peer="patch_1-0"}
Bridge "br1"
Port "br1"
Interface "br1"
type: internal
Port "patch_1-0"
Interface "patch_1-0"
type: patch
options: {peer="patch_0-1"}
ovs_version: "2.5.0"
&&
[root@prv-10-11-ksupp user]# virsh list
Id Name State
----------------------------------------------------
1 vm1 running
2 vm2 running
-----
Service openvswitch restart:
[root@prv-10-11-ksupp user]# ovs-vsctl show
cf2a15bb-ca36-481a-aa3c-80df59814c76
Bridge "br0"
Port "br0"
Interface "br0"
type: internal
Port "eth3"
Interface "eth3"
Port "vnet0"
Interface "vnet0"
Port "vnet1"
Interface "vnet1"
Port "patch_0-1"
Interface "patch_0-1"
type: patch
options: {peer="patch_1-0"}
Bridge "br1"
Port "br1"
Interface "br1"
type: internal
Port "patch_1-0"
Interface "patch_1-0"
type: patch
options: {peer="patch_0-1"}
ovs_version: "2.5.0"
-----
service network restart:
[root@prv-10-11-ksupp user]# ovs-vsctl show
cf2a15bb-ca36-481a-aa3c-80df59814c76
Bridge "br1"
Port "br1"
Interface "br1"
type: internal
Bridge "br0"
Port "eth3"
Interface "eth3"
Port "br0"
Interface "br0"
type: internal
ovs_version: "2.5.0"
&&
[root@prv-10-11-ksupp user]# virsh list
Id Name State
----------------------------------------------------
1 vm1 running
2 vm2 running
I was chatting with a kind fellow on the IRC channel that pointed me to
this link:
https://github.com/openvswitch/ovs/blob/master/rhel/README.RHEL#L204
I hadn't considered the need to create startup scripts for the patch
interfaces. Once I did that, they would come back up consistently! As far
as the libvirt vnet interfaces auto-rejoining a bridge upon it being downed
and brought back up, he gave me some ideas to work with on that as well. If
anyone has any ideas that have worked for them on this, I'm all ears!
Thanks!
On Sat, Jun 25, 2016 at 11:47 AM, Ben Pfaff <b...@ovn.org> wrote:
> On Sat, Jun 25, 2016 at 12:26:04AM -0600, Sterdnot Shaken wrote:
> > I have 2 OVS (2.5) bridges (on one host) connected to each other with a
> > patch interface, which works great. If I restart networking though, the
> > patch interfaces disappear (as does the vnet interfaces connecting KVM
> VM's
> > to the bridge) and all ovs-vsctl show displays are the bridge interfaces
> > and some physical interfaces.
> >
> > Looking in conf.db, I can see the patch interfaces, so I thought that by
> > restarting the openvswitch service, the patch interfaces would reappear
> and
> > reconnect the bridges, but that didn't happen. Out side of restarting the
> > whole host, what's the fix for this?
>
> Restarting OVS shouldn't have any effect on patch ports, so I'm as
> puzzled as you are.
>
> What's in the database? Start with "ovs-vsctl show".
>
> Thanks,
>
> Ben.
>
_______________________________________________
discuss mailing list
discuss@openvswitch.org
http://openvswitch.org/mailman/listinfo/discuss
