Ok so openvswitch starts up fine. Everything seems good until I add the
virtual bridge (Log output at the bottom). 'ovs-vsctl show' still displays
the bridge I created and I can add ports to it. However it does not show up
under ifconfig. I am guessing  "2000-02-05T21:48:08Z|00007|
dpif|WARN|failed to create datapath ovs-system: Message too long" is the
problem. Does this have to do with the openvswitch kernel module
communicating with the linux network stack?

# /etc/init.d/openvswitch-switch start

ovs-brcompatd missing, disabling bridge compatibility ... (warning).

Inserting openvswitch module.

/etc/openvswitch/conf.db does not exist ... (warning).

Creating empty database /etc/openvswitch/conf.db.

Starting ovsdb-server.

Configuring Open vSwitch system IDs.

Starting ovs-vswitchd.

Enabling remote OVSDB managers.

unknown protocol gre ... failed!



cat /var/log/openvswitch/ovs-vswitchd.log

2000-02-05T21:44:26Z|00001|vlog|INFO|opened log
file/var/log/openvswitch/ovs-vswitchd.log

2000-02-05T21:44:26Z|00002|worker(worker)|INFO|worker process started

2000-02-05T21:44:26Z|00002|reconnect|INFO|unix:/var/run/openvswitch/db.sock:
connecting...

2000-02-05T21:44:26Z|00003|reconnect|INFO|unix:/var/run/openvswitch/db.sock:
connected

2000-02-05T21:44:26Z|00004|bridge|INFO|ovs-vswitchd (Open vSwitch) 1.10.0





#  cat /var/log/openvswitch/ovsdb-server.log

2000-02-05T21:44:26Z|00001|vlog|INFO|opened log file
/var/log/openvswitch/ovsdb-server.log

2000-02-05T21:44:26Z|00002|ovsdb_server|INFO|ovsdb-server (Open vSwitch)
1.10.0

2000-02-05T21:44:36Z|00003|memory|INFO|0 kB peak resident set size after
10.1 seconds

2000-02-05T21:44:36Z|00004|memory|INFO|cells:14 monitors:1 sessions:1

2000-02-05T21:44:46Z|00005|memory|INFO|0 kB peak resident set size after
20.1 seconds

2000-02-05T21:44:46Z|00006|memory|INFO|cells:14 monitors:1 sessions:1

2000-02-05T21:44:56Z|00007|memory|INFO|0 kB peak resident set size after
30.2 seconds

2000-02-05T21:44:56Z|00008|memory|INFO|cells:14 monitors:1 sessions:1

2000-02-05T21:45:06Z|00009|memory|INFO|0 kB peak resident set size after
40.2 seconds

2000-02-05T21:45:06Z|00010|memory|INFO|cells:14 monitors:1 sessions:1

2000-02-05T21:45:16Z|00011|memory|INFO|0 kB peak resident set size after
50.2 seconds

2000-02-05T21:45:16Z|00012|memory|INFO|cells:14 monitors:1 sessions:1

2000-02-05T21:45:26Z|00013|memory|INFO|0 kB peak resident set size after
60.2 seconds

2000-02-05T21:45:26Z|00014|memory|INFO|cells:14 monitors:1 sessions:1

2000-02-05T21:45:36Z|00015|memory|INFO|0 kB peak resident set size after
70.2 seconds

2000-02-05T21:45:36Z|00016|memory|INFO|cells:14 monitors:1 sessions:1

2000-02-05T21:45:46Z|00017|memory|INFO|0 kB peak resident set size after
80.3 seconds

2000-02-05T21:45:46Z|00018|memory|INFO|cells:14 monitors:1 sessions:1

2000-02-05T21:45:56Z|00019|memory|INFO|0 kB peak resident set size after
90.3 seconds

2000-02-05T21:45:56Z|00020|memory|INFO|cells:14 monitors:1 sessions:1



# ovs-vsctl add-br bro

# cat /var/log/openvswitch/ovs-vswitchd.log

2000-02-05T21:44:26Z|00001|vlog|INFO|opened log
file/var/log/openvswitch/ovs-vswitchd.log

2000-02-05T21:44:26Z|00002|worker(worker)|INFO|worker process started

2000-02-05T21:44:26Z|00002|reconnect|INFO|unix
/var/run/openvswitch/db.sock: connecting...

2000-02-05T21:44:26Z|00003|reconnect|INFO|unix
/var/run/openvswitch/db.sock: connected

2000-02-05T21:44:26Z|00004|bridge|INFO|ovs-vswitchd (Open vSwitch) 1.10.0

2000-02-05T21:48:08Z|00005|memory|INFO|0 kB peak resident set size after
222.0 seconds

2000-02-05T21:48:08Z|00006|memory|INFO|

2000-02-05T21:48:08Z|00007|dpif|WARN|failed to create datapath ovs-system:
Message too long

2000-02-05T21:48:08Z|00008|ofproto_dpif|ERR|failed to open datapath of type
system: Message too long

2000-02-05T21:48:08Z|00009|ofproto|ERR|failed to open datapath bro: Message
too long

2000-02-05T21:48:08Z|00010|bridge|ERR|failed to create bridge bro: Message
too long # /etc/init.d/openvswitch-switch start

ovs-brcompatd missing, disabling bridge compatibility ... (warning).

Inserting openvswitch module.

/etc/openvswitch/conf.db does not exist ... (warning).

Creating empty database /etc/openvswitch/conf.db.

Starting ovsdb-server.

Configuring Open vSwitch system IDs.

Starting ovs-vswitchd.

Enabling remote OVSDB managers.

unknown protocol gre ... failed!



cat /var/log/openvswitch/ovs-vswitchd.log

2000-02-05T21:44:26Z|00001|vlog|INFO|opened log file
/var/log/openvswitch/ovs-vswitchd.log

2000-02-05T21:44:26Z|00002|worker(worker)|INFO|worker process started

2000-02-05T21:44:26Z|00002|reconnect|INFO|unix
/var/run/openvswitch/db.sock: connecting...

2000-02-05T21:44:26Z|00003|reconnect|INFO|unix
/var/run/openvswitch/db.sock: connected

2000-02-05T21:44:26Z|00004|bridge|INFO|ovs-vswitchd (Open vSwitch) 1.10.0





#  cat /var/log/openvswitch/ovsdb-server.log

2000-02-05T21:44:26Z|00001|vlog|INFO|opened log file
/var/log/openvswitch/ovsdb-server.log

2000-02-05T21:44:26Z|00002|ovsdb_server|INFO|ovsdb-server (Open vSwitch)
1.10.0

2000-02-05T21:44:36Z|00003|memory|INFO|0 kB peak resident set size after
10.1 seconds

2000-02-05T21:44:36Z|00004|memory|INFO|cells:14 monitors:1 sessions:1

2000-02-05T21:44:46Z|00005|memory|INFO|0 kB peak resident set size after
20.1 seconds

2000-02-05T21:44:46Z|00006|memory|INFO|cells:14 monitors:1 sessions:1

2000-02-05T21:44:56Z|00007|memory|INFO|0 kB peak resident set size after
30.2 seconds

2000-02-05T21:44:56Z|00008|memory|INFO|cells:14 monitors:1 sessions:1

2000-02-05T21:45:06Z|00009|memory|INFO|0 kB peak resident set size after
40.2 seconds

2000-02-05T21:45:06Z|00010|memory|INFO|cells:14 monitors:1 sessions:1

2000-02-05T21:45:16Z|00011|memory|INFO|0 kB peak resident set size after
50.2 seconds

2000-02-05T21:45:16Z|00012|memory|INFO|cells:14 monitors:1 sessions:1

2000-02-05T21:45:26Z|00013|memory|INFO|0 kB peak resident set size after
60.2 seconds

2000-02-05T21:45:26Z|00014|memory|INFO|cells:14 monitors:1 sessions:1

2000-02-05T21:45:36Z|00015|memory|INFO|0 kB peak resident set size after
70.2 seconds

2000-02-05T21:45:36Z|00016|memory|INFO|cells:14 monitors:1 sessions:1

2000-02-05T21:45:46Z|00017|memory|INFO|0 kB peak resident set size after
80.3 seconds

2000-02-05T21:45:46Z|00018|memory|INFO|cells:14 monitors:1 sessions:1

2000-02-05T21:45:56Z|00019|memory|INFO|0 kB peak resident set size after
90.3 seconds

2000-02-05T21:45:56Z|00020|memory|INFO|cells:14 monitors:1 sessions:1



# ovs-vsctl add-br bro

# cat /log/openvswitch/ovs-vswitchd.log

2000-02-05T21:44:26Z|00001|vlog|INFO|opened log file
/var/log/openvswitch/ovs-vswitchd.log

2000-02-05T21:44:26Z|00002|worker(worker)|INFO|worker process started

2000-02-05T21:44:26Z|00002|reconnect|INFO|unix:/var/run/openvswitch/db.sock:
connecting...

2000-02-05T21:44:26Z|00003|reconnect|INFO|unix:/var/run/openvswitch/db.sock:
connected

2000-02-05T21:44:26Z|00004|bridge|INFO|ovs-vswitchd (Open vSwitch) 1.10.0

2000-02-05T21:48:08Z|00005|memory|INFO|0 kB peak resident set size after
222.0 seconds

2000-02-05T21:48:08Z|00006|memory|INFO|

2000-02-05T21:48:08Z|00007|dpif|WARN|failed to create datapath ovs-system:
Message too long

2000-02-05T21:48:08Z|00008|ofproto_dpif|ERR|failed to open datapath of type
system: Message too long

2000-02-05T21:48:08Z|00009|ofproto|ERR|failed to open datapath bro: Message
too long
2000-02-05T21:48:08Z|00010|bridge|ERR|failed to create bridge bro: Message
too lo


On Wed, Jun 26, 2013 at 8:17 AM, Ben Pfaff <[email protected]> wrote:

> On Wed, Jun 26, 2013 at 07:23:19AM -0700, Cali Ente wrote:
> > I'm working on porting over openvswitch to a MIPS based platform, and I
> > have run into an interesting issue. I have correctly compiled openvswitch
> > and it's kernel module, and have installed both. I can run all the
> > openvswitch executables and can even run the add-br and add-port
> commands.
> > However, these devices do not appear in ifconfig (not even when issued
> with
> > the -a switch), anybody have an idea of what could be causing this?
>
> Did you check the OVS log?
>
_______________________________________________
discuss mailing list
[email protected]
http://openvswitch.org/mailman/listinfo/discuss

Reply via email to