[ovs-discuss] openvswitch on the latest Linux kernel 3.7

[Qin, Xiaohong]

Hi Jesse,

Thanks for the tip. I have loaded it into the kernel by running the insmod CLI and now I can launch the "ovs-vswitchd" CLI successfully. Then I did this,

ovs-vsctl show
6a792107-75e2-44fb-a3f0-019c29042283

It didn't print out the version number as previous release,

ovs-vsctl show
a5532ff9-1024-4d26-856f-09e8dcc3d67d
ovs_version: "1.4.0+build0"

Is this expected or I still miss something here?

Thanks.

Dennis Qin

-----Original Message-----
From: Jesse Gross [mailto:jesse at nicira.com] 
Sent: Tuesday, January 08, 2013 10:59 AM
To: Qin, Xiaohong
Cc: Ben Pfaff; discuss at openvswitch.org
Subject: Re: [ovs-discuss] openvswitch on the latest Linux kernel 3.7

On Tue, Jan 8, 2013 at 10:49 AM, Qin, Xiaohong <Xiaohong.Qin at emc.com> wrote:
> Hi Ben,
>
> I was able to get rid of that schema problem but still I'm running 
> into the kernel module issue; here is the error message,
>
> ovs-vswitchd --pidfile --detach
> 2013-01-08T11:27:40Z|00001|reconnect|INFO|unix:/usr/local/var/run/openvswitch/db.sock: connecting...
> 2013-01-08T11:27:40Z|00002|reconnect|INFO|unix:/usr/local/var/run/open
> vswitch/db.sock: connected 2013-01-08T11:27:40Z|00003|dpif_linux|ERR|Generic Netlink family 'ovs_datapath' does not exist. The Open vSwitch kernel module is probably not loaded.
> 2013-01-08T11:27:40Z|00004|dpif|WARN|failed to enumerate system 
> datapaths: No such file or directory
>
> The openvswitch kernel module is still loaded as the following CLI 
> shows,

That just means that it's on the disk.  Does it show up in lsmod?

> /sbin/modinfo openvswitch
> filename:       /lib/modules/3.7.0-030700-generic/kernel/net/openvswitch/openvswitch.ko
> license:        GPL
> description:    Open vSwitch switching datapath
> srcversion:     7EFC7E464483C3CCF09C124
> depends:
> intree:         Y
> vermagic:       3.7.0-030700-generic SMP mod_unload modversions
>
> Looks like OVS userspace package has a problem to connect to this preloaded kernel module.

Building it as a module in the kernel doesn't cause it to automatically load.