ev@openvswitch.org
> Betreff: Re: [ovs-dev] trying to use brcompat with the latest 3.4 kernel
>
> Hmm. Andre, can you comment on whether you're using the kernel module that
> came from the OVS distribution or the upstream kernel? If there's a bug,
> we'll defini
-
Von: Justin Pettit [mailto:jpet...@nicira.com]
Gesendet: Montag, 25. Juni 2012 06:43
An: Ben Pfaff
Cc: André Ruß; dev@openvswitch.org
Betreff: Re: [ovs-dev] trying to use brcompat with the latest 3.4 kernel
Hmm. Andre, can you comment on whether you're using the kernel module that
came fro
Hmm. Andre, can you comment on whether you're using the kernel module that
came from the OVS distribution or the upstream kernel? If there's a bug, we'll
definitely look to fix it. However, we generally encourage people to avoid
using bridge compatibility if they can avoid it. OVS support wa
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 rece
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 upst
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:
