[ovs-discuss] Difference in behavior between master branch and latest download version

[Ben Pfaff]

No one has looked at it yet.

If only one userspace switch works at a time, then that's a bug.

On Thu, Feb 07, 2013 at 07:41:34AM -0800, Aishwarya wrote:
> Hi,
> 
> Any update on this issue?
> 
> Thanks.
> On Feb 6, 2013 10:28 AM, "Aishwarya" <aishu85 at gmail.com> wrote:
> 
> > Hi,
> >
> > I am working with creating multiple userspace only switches on a host. I
> > am not using the kernel module. While I am able to do this successfully
> > with the latest 1.7.3 download version, it fails in the latest snapshot of
> > the master version:
> >
> > Steps:
> >
> > 1. Create conf.db, start ovsdb-server, and start vswitchd.(point to separate conf.db and separate OVS_RUNDIR for the 2 switches that I am trying to create)
> >
> > 2. Create the 2 switches:
> >
> > 1st switch:
> >
> > ovs-vsctl --db=<path to db.sock> add-br dp0
> > ovs-vsctl --db=<path to db.sock> set bridge dp0 datapath_type=netdev
> >
> > 2nd switch:
> > ovs-vsctl --db=<path to db.sock> add-br dp1
> > ovs-vsctl --db=<path to db.sock> set bridge dp1 datapath_type=netdev
> >
> > In 1.7.3, after the above steps, I successfully see 2 switches dp0 and dp1 on the host with ifconfig -a.
> >
> > In the latest snapshot of the master version, after the 1st switch is created, ifconfig -a
> >
> > shows a dp0 and additionally another device called ovs-netdev.
> >
> > When I try to create the second switch, while the steps do not fail upfront(i.e. no error messages), ifconfig -a *does not* show a dp1, and any subsequent commands referring to dp1 give the error message: dp1 is not a bridge or a socket.
> >
> > Since the master branch is more updated, is this behaviour expected i.e. not being to able to create more than one user space switch on a host?
> >
> > Thanks.
> >
> >
> >
> >
> >
> >
> >

> _______________________________________________
> discuss mailing list
> discuss at openvswitch.org
> http://openvswitch.org/mailman/listinfo/discuss