[ovs-dev] Bug#691438: openvswitch packages do not work well together with upstream's kernel module
blp at nicira.com
Thu Oct 25 19:51:35 UTC 2012
On Thu, Oct 25, 2012 at 07:20:48PM +0200, Arno Töll wrote:
> Package: openvswitch
> Severity: important
> As you are certainly aware, Open vSwitch is included upstream since
> kernel 3.3. Post-Wheezy kernels also enable CONFIG_OPENVSWITCH in
> pristine Debian kernel builds (see #675010).
> However, the Debian packages do not work well together with this
> upstream module. Generally, your user space daemons do support the
> kernel module but your packaging (in particular the init script)
> makes it really hard not to use your package without the DKMS module
> you ship as well.
Can you explain how the initscript makes it really hard to use the
package without the DKMS module? The packaging is oriented toward
using the kernel modules supplied with the packages, but we do not
intentionally make it difficult to use the integrated upstream module.
> Moreover, the brcompat module does not seem to work together with
> the kernel module upstream (i.e. not the DKMS module from your
> source package). Is there a way to get these working together?
No. From the FAQ available at http://openvswitch.org/faq/:
Q: What features are not available in the Open vSwitch kernel datapath
that ships as part of the upstream Linux kernel?
A: The kernel module in upstream Linux 3.3 and later does not include
the following features:
- Bridge compatibility, that is, support for the ovs-brcompatd
daemon that (if you enable it) lets "brctl" and other Linux
bridge tools transparently work with Open vSwitch instead.
We do not expect bridge compatibility to ever be available in
upstream Linux. If you need bridge compatibility, use the
kernel module from the Open vSwitch distribution instead of the
upstream Linux kernel module.
- Tunnel virtual ports, that is, interfaces with type "gre",
"ipsec_gre", "capwap". It is possible to create tunnels in
Linux and attach them to Open vSwitch as system devices.
However, they cannot be dynamically created through the OVSDB
protocol or set the tunnel ids as a flow action.
Work is in progress in adding these features to the upstream
Linux version of the Open vSwitch kernel module. For now, if
you need these features, use the kernel module from the Open
vSwitch distribution instead of the upstream Linux kernel
- Patch virtual ports, that is, interfaces with type "patch".
You can use Linux "veth" devices as a substitute.
We don't have any plans to add patch ports upstream.
> For Post-Wheezy this may become more critical as you may want to
> stop shipping the DKMS/kernel module source at some point.
Yes, that would be nice.
More information about the dev