It sounds like your init function isn't getting called, I'd check on that. I usually use printk() to debug kernel issues.
On Tue, Jan 17, 2012 at 09:54:17AM +1100, Joseph Glanville wrote: > Hi Ben, > > I first took the original patch and applied it to 1.3.0 with minimal > changes. This seems to apply pretty cleanly but it fails to register > vxlan as a type ( I get netdev unrecognized protocol error ). > Attached is what I have so far, if you can spot any obvious errors > that would be awesome.. > Also how do I best debug changes to the datapath? VLOG seems like an > obvious way of getting debug info out but I can't work out how to get > the messages. > > Joseph. > > On 17 January 2012 05:38, Ben Pfaff <[email protected]> wrote: > > I don't think we've made any subtle or surprising changes. ?Let us > > know if you have questions. > > > > On Mon, Jan 16, 2012 at 07:05:46PM +1100, Joseph Glanville wrote: > >> Hi Ben > >> > >> All, good. I'm in the process of porting the patchset labeled v2 ( > >> http://openvswitch.org/pipermail/dev/2011-October/012207.html. > >> As far as I can see some stuff has moved around to accomodate inclusion in > >> mainline and many variables have been namespaced with ovs_ etc. > >> Is there anything specific I should be wary of? > >> > >> Joseph. > >> > >> On 16 January 2012 16:39, Ben Pfaff <[email protected]> wrote: > >> > >> > I have not rebased the patches. > >> > > >> > On Mon, Jan 16, 2012 at 04:43:20PM +1100, Joseph Glanville wrote: > >> > > Hi Jesse, Ben > >> > > > >> > > Have the VXLAN patches previously posted been rebased to a more recent > >> > > version of Open vSwitch? > >> > > I'm considering doing this myself and don't want to duplicate effort. > >> > > My aim is to implement it against current 1.4 or HEAD so that I can > >> > compile > >> > > it against Linux 3.2.1. > >> > > > >> > > Joseph. > >> > > > >> > > 2011/12/24 Jesse Gross <[email protected]> > >> > > > >> > > > 2011/12/19 Rog?rio Vinhal Nunes <[email protected]>: > >> > > > > Hello, > >> > > > > > >> > > > > I would like to know what is the status of implementing the VXLan > >> > > > > functionality to VSwitch. Version 1.3.0 has nothing related to it > >> > > > > in > >> > the > >> > > > > Changelog, so I was wondering if it is planned to be launched at > >> > 1.4.0. I > >> > > > > really hope to see this feature implemented soon because I have > >> > > > > some > >> > > > > projects that would benefit from it, so any kind of status update > >> > you can > >> > > > > give would be nice. > >> > > > > >> > > > There's some more infrastructure work that needs to be done before it > >> > > > can be properly integrated. ?This work hasn't been done yet, so I > >> > > > can't say when support might be available. ?In the meantime, I > >> > > > recommend using a GRE tunnel. > >> > > > _______________________________________________ > >> > > > dev mailing list > >> > > > [email protected] > >> > > > http://openvswitch.org/mailman/listinfo/dev > >> > > > > >> > > > >> > > > >> > > > >> > > -- > >> > > * > >> > > Founder | Director | VP Research > >> > > Orion Virtualisation Solutions* | www.orionvm.com.au | Phone: 1300 56 > >> > 99 52 > >> > > | Mobile: 0428 754 846 > >> > > >> > >> > >> > >> -- > >> * > >> Founder | Director | VP Research > >> Orion Virtualisation Solutions* | www.orionvm.com.au | Phone: 1300 56 99 52 > >> | Mobile: 0428 754 846 > > > > -- > Founder | Director | VP Research > Orion Virtualisation Solutions?|?www.orionvm.com.au?| Phone: 1300 56 > 99 52 | Mobile: 0428 754 846 _______________________________________________ dev mailing list [email protected] http://openvswitch.org/mailman/listinfo/dev
