On Fri, 7 Sep 2012 12:37:04 +0200
Timm Essigke wrote:
> I hope you can understand the cause of the problem from the ethregs
> output included in the files.
>
> Thank you very much!
looks like the attachment(s) either wasn't included or didn't make it
through the list filters, can you upload to
Hi Jesse,
thank you for picking up my problem!
I made a script and ran it on my system. Attached is the script and the
output. So it should be very easy for you to reproduce my problem.
At the top of the script you need to make some adjustments for your
network; the only command line argumen
On Wed, 5 Sep 2012 17:13:52 +0200
Timm Essigke wrote:
> First, I asked on the openvswitch mailing list and they consider it as a
> driver problem.
>
> My system is:
> Ubuntu 12.04
> Supermicro: Kernel 3.2.0-29-generic, 64-bit
> Fujitsu: Kernel 3.2.0-29-generic-pae, 32-bit
> Openvswitch 1.4.0-1ub
t: [E1000-devel] Intel 82546GB chip does not work with
> OpenVSwitch
>
> Dear e1000 developers,
>
> I use OpenVSwitch http://openvswitch.org/ on a number of servers. It
> replaces the bridge kernel module and does VLANs in a different way
> than the original kernel implementatio
Dear e1000 developers,
I use OpenVSwitch http://openvswitch.org/ on a number of servers. It
replaces the bridge kernel module and does VLANs in a different way than
the original kernel implementation. It is much more convenient and
performs better when you have a virtualization servers where th
