On Thu, Jul 29, 2010 at 1:36 PM, Hardeep Uppal <[email protected]> wrote: > > r...@ettm:/home/ettm/Desktop/openvswitch-1.0.1# ovs-vswitchd > unix:/usr/local/var/run/openvswitch/db.sock > Jul 29 > 12:43:21|00001|reconnect|INFO|unix:/usr/local/var/run/openvswitch/db.sock: > connecting... > Jul 29 > 12:43:21|00002|reconnect|INFO|unix:/usr/local/var/run/openvswitch/db.sock: > connected > Jul 29 12:43:21|00003|dpif_linux|ERR|/proc/devices: openvswitch major not > found (is the module loaded?) > Jul 29 12:43:21|00004|dpif|WARN|failed to enumerate system datapaths: No > such device > Jul 29 12:55:12|00005|dpif_linux|ERR|/proc/devices: openvswitch major not > found (is the module loaded?) > Jul 29 12:55:12|00006|dpif|WARN|failed to create datapath br0: No such > device > > > I am not sure what the error corresponds to. I would appreciate any help.
The reason for these error messages is that by default Open vSwitch assumes that a kernel based datapath is being created, which it cannot do if the kernel module is not loaded. If you look at the next line in the INSTALL.userspace directions you'll see: ovs-vsctl set bridge br0 datapath_type=netdev The "netdev" datapath type corresponds to userspace, so the errors should go away once you give it that command. Since the kernel module is our primary datapath you may see a few additional error messages about not being able to contact it but you can safely ignore those.
_______________________________________________ discuss mailing list [email protected] http://openvswitch.org/mailman/listinfo/discuss_openvswitch.org
