Thanks Shetty, your suggestion worked, problem solved by removing OVS related lines in ifcfg-ovsbr. Sorry to bother. On Fri, Nov 13, 2015 at 11:33 Gurucharan Shetty <[email protected]> wrote:
> If you are connecting your VM interfaces to this bridge, I suggest > that you don't create this bridge via ifcfg script. Rather create the > bridge itself via ovs-vsctl. > > Another strategy *could* be to create a separate bridge for your vms > and connect the 2 bridges via patch port. > > On Thu, Nov 12, 2015 at 7:09 PM, Tashi Lu <[email protected]> wrote: > > Shetty, > > > > Many thanks for your help even when you're busy. > > > > The port with tag is the internal port, so yes. > > > > Is the loss of the virtual ports, which I created with ovs-ctl, the same > > reason as the vlan tag's? I can easily add a line to ifcfg-ovsbr0 to > > configure the vlan tag for the internal port, but if I have to create a > > ifcfg script for each virtual port for vm to make them persistent, that's > > very unmanageable. We have 7 vms, each with 4 virtual NICs, which means I > > have to create 28+ ifcfg scripts. > > > > I thought ovs-db could store those states and restore them after a > reboot. > > If that's not possible now, we can make it, that will make op's life > easier. >
_______________________________________________ discuss mailing list [email protected] http://openvswitch.org/mailman/listinfo/discuss
