I think what you're seeing is a race condition.
> ovs-vsctl -- --may-exist add-br br0

Here, you've created a bridge of type system.

Time happens  . . .

> ovs-vsctl set bridge br0 datapath_type=netdev

Here you change it to netdev.

You can fix the race condition by doing it all in one transaction.

ovs-vsctl -- --may-exist add-br br0 -- set bridge br0 datapath_type=netdev

Hope that's helpful,
Ethan

> ovs-vsctl -- --may-exist add-port br0 eth1
> ovs-vsctl -- --may-exist add-port br0 eth0
>
> On Thu, Jun 7, 2012 at 6:41 PM, Ethan Jackson <[email protected]> wrote:
>>
>> Sounds like the datapath_type of the bridge you created is "system".
>> Since the kernel module is not loaded, it's failing to create the
>> bridge.  You want "netdev" if you're planning to stick with userspace.
>>
>> Ethan
>>
>> On Wed, Jun 6, 2012 at 7:18 PM, Dong Jin <[email protected]> wrote:
>> > 1. I am using the userspace mode of ovs. When I execute the following
>> > commands to start the ovs daemon, I got one error and one warning are
>> > shown below. It looks that the ovs daemon is started and able to
>> > perform learning switch functionality. Just want to check if I can
>> > safely ignore them due to the userspace mode of ovs?
>> >
>> > ovsdb-server --remote=punix:/usr/local/var/run/openvswitch/db.sock
>> > --remote=db:Open_vSwitch,manager_options --pidfile --detach;
>> > ovs-vsctl --no-wait init;
>> > ovs-vswitchd --pidfile --detach
>> >
>> > Jun 07
>> > 06:01:39|00001|reconnect|INFO|unix:/usr/local/var/run/openvswitch/db.sock:
>> > connecting...
>> > Jun 07
>> > 06:01:39|00002|reconnect|INFO|unix:/usr/local/var/run/openvswitch/db.sock:
>> > connected
>> > Jun 07 06:01:39|00003|dpif_linux|ERR|Generic Netlink family
>> > 'ovs_datapath' does not exist. The Open vSwitch kernel module is
>> > probably not loaded.
>> > Jun 07 06:01:39|00004|dpif|WARN|failed to enumerate system datapaths:
>> > No such file or directory
>> >
>> > 2. I applied the following rate limiting rules (no error is shown
>> > after executing the commands),  but the rate limiting does not work. I
>> > can send 100 Mb/s traffic from one host to another. just wondering if
>> > it is because the userspace mode does not support QoS?
>> >
>> > ovs-vsctl set Interface tap0 ingress_policing_rate=1000
>> > ovs-vsctl set Interface tap0 ingress_policing_burst=100
>> >
>> > my topology
>> > VM1 (eth0) --- (eth0) VM2 (eth1) --- (eth0)VM3
>> > the ovs needs to run inside VM2 for some reason of our project.
>> > The virtualization technology I used is OpenVZ, which is a OS-level
>> > virtualization. Therefore, I am not able to load any kernel module in
>> > VM, and I choose to run userspace mode of ovs.
>> >
>> > Thank you for your help.
>> > _______________________________________________
>> > discuss mailing list
>> > [email protected]
>> > http://openvswitch.org/mailman/listinfo/discuss
>
>
_______________________________________________
discuss mailing list
[email protected]
http://openvswitch.org/mailman/listinfo/discuss

Reply via email to