Well in your defense, brcompat isn't the solution to using openvswitch to it's full potential anyways. I think it's better to create the wrapper scripts to call ovsctl directly or whatever it's called now.
On Fri, Sep 14, 2012 at 10:09 AM, christopher barry <cba...@rjmetrics.com>wrote: > On Thu, 2012-09-13 at 17:05 -0400, christopher barry wrote: > > greetings, > > > > what's the plan for using openvswitch in the future, without requiring > > brcompat? > > > > while I can compile openvswitch master for use with my 3.5 kernel, the > > brcompat has issues: > > > > modprobe brcompat > > FATAL: Error inserting brcompat > > (/lib/modules/3.5.1/kernel/net/openvswitch/brcompat.ko): Unknown symbol > > in module, or unknown parameter (see dmesg) > > > > dmesg: brcompat: Unknown symbol ovs_dp_ioctl_hook (err 0) > > > > ...and it seems as though the idea is to move away from bridge > > compatibility anyway. > > > > I have made this error known upstream to the ovs developers, but have > > not heard back as of yet. > > > > but back to the longer term plan, is it just some scripts that need to > > change to use ovs without brcompat? > > > > > > Regards, > > -C > > So, this was totally my fault. > > The bridge module was loaded, and this caused the error, brcompat is > loaded fine now, so please excuse the noise... > > > > _______________________________________________ > Users mailing list > Users@lists.opennebula.org > http://lists.opennebula.org/listinfo.cgi/users-opennebula.org >
_______________________________________________ Users mailing list Users@lists.opennebula.org http://lists.opennebula.org/listinfo.cgi/users-opennebula.org