That was my first thought oo, but I don't see why there'd be brcompat messages in the kernel log if that was the case.
On Sun, Jun 24, 2012 at 11:46:05PM -0400, Justin Pettit wrote: > I assume you mean that you're trying to use the upstream kernel module. If > so, that won't work. From our recently added 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 and patch virtual ports, that is, interfaces with type > "gre", "ipsec_gre", "capwap", or "patch". 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 > module. > -=-=-=-=-=-=-=-=- > > The FAQ is linked from the website and available here: > > > http://openvswitch.org/cgi-bin/gitweb.cgi?p=openvswitch;a=blob_plain;f=FAQ;hb=HEAD > > The FAQ will be included as part of the 1.8 release. > > --Justin > > > On Jun 24, 2012, at 8:12 PM, André Ruß wrote: > > > Hi, > > > > I am trying to use the brcompatd in the latest 3.4 kernel with the latest > > git checkout (1.7.90). > > > > After starting the brcompatd the following line is posted every 5 seconds > > to the syslog: > > > > Jun 25 02:02:37 pod1-bl1 kernel: [ 2402.712848] brcompat: timed out waiting > > for userspace > > Jun 25 02:02:42 pod1-bl1 kernel: [ 2407.699981] brcompat: timed out waiting > > for userspace > > Jun 25 02:02:47 pod1-bl1 kernel: [ 2412.687175] brcompat: timed out waiting > > for userspace > > > > Using commands like “brctl” does work (at least addbr / delbr / addif / > > delif) but they are issueing a “connection time out”: > > > > root@pod1-bl1:~# ovs-vsctl show > > 60b13c13-0e13-44d2-8c1b-c7ca7b9c2459 > > ovs_version: "1.7.0" > > root@pod1-bl1:~# brctl addbr br0 > > add bridge failed: Connection timed out > > root@pod1-bl1:~# ovs-vsctl show > > 60b13c13-0e13-44d2-8c1b-c7ca7b9c2459 > > Bridge "br0" > > Port "br0" > > Interface "br0" > > type: internal > > ovs_version: "1.7.0" > > root@pod1-bl1:~# brctl addif br0 eth1 > > can't add eth1 to bridge br0: Connection timed out > > root@pod1-bl1:~# > > root@pod1-bl1:~# ovs-vsctl show > > 60b13c13-0e13-44d2-8c1b-c7ca7b9c2459 > > Bridge "br0" > > Port "br0" > > Interface "br0" > > type: internal > > Port "eth1" > > Interface "eth1" > > ovs_version: "1.7.0" > > root@pod1-bl1:~# > > > > So brcompat is working but tools like libvirt fail since they are > > timeoutet. Is there a solution for that issue? > > > > Regards > > Andre > > > > _______________________________________________ > > dev mailing list > > dev@openvswitch.org > > http://openvswitch.org/mailman/listinfo/dev > > _______________________________________________ > dev mailing list > dev@openvswitch.org > http://openvswitch.org/mailman/listinfo/dev _______________________________________________ dev mailing list dev@openvswitch.org http://openvswitch.org/mailman/listinfo/dev
