All of lore.kernel.org
 help / color / mirror / Atom feed
From: Nikolay Aleksandrov <nikolay@cumulusnetworks.com>
To: "Jiri Pirko" <jiri@resnulli.us>, "Bjørnar Ness" <bjornar.ness@gmail.com>
Cc: netdev <netdev@vger.kernel.org>
Subject: Re: bonding (IEEE 802.3ad) not working with qemu/virtio
Date: Thu, 28 Jan 2016 15:10:51 +0100	[thread overview]
Message-ID: <56AA216B.3040105@cumulusnetworks.com> (raw)
In-Reply-To: <56AA1D65.2000509@cumulusnetworks.com>

On 01/28/2016 02:53 PM, Nikolay Aleksandrov wrote:
> On 01/28/2016 02:33 PM, Jiri Pirko wrote:
>> Mon, Jan 25, 2016 at 05:24:48PM CET, bjornar.ness@gmail.com wrote:
>>> As subject says, 802.3ad bonding is not working with virtio network model.
>>>
>>> The only errors I see is:
>>>
>>> No 802.3ad response from the link partner for any adapters in the bond.
>>>
>>> Dumping the network traffic shows that no LACP packets are sent from the
>>> host running with virtio driver, changing to for example e1000 solves
>>> this problem
>>> with no configuration changes.
>>>
>>> Is this a known problem?
> Can you show your bond's /proc/net/bonding/bond<X> ? And also in order to
> better see what's going on I'd suggest enabling the pr_debug() calls in the 3ad
> code:
> echo 'file bond_3ad.c +p' > /sys/kernel/debug/dynamic_debug/control
> (assuming you have debugfs mounted at /sys/kernel/debug)
> Then you can follow the logs to see what's going on.
> I can clearly see LACP packets sent over virtio net devices:
> 14:53:05.323490 52:54:00:51:25:3c > 01:80:c2:00:00:02, ethertype Slow Protocols (0x8809), length 124: LACPv1, length 110
Nevermind my message, Jiri was right. My setup wasn't correct.
I have a virtio_net get_settings hack that enables me to test 802.3ad over virtio_net
locally.
Sorry about the noise.

> 
>>
>> I believe the problem is virtio_net for obvious reasons does not report
>> speed and duplex. Bonding 3ad mode makes that unconfortable :)
[snip]
Right, of course. My setup has some patches that add get_settings to virtio_net
to make it play nice for testing 803.2ad.

>>
>> Use team ;)
> 
:-)

  reply	other threads:[~2016-01-28 14:10 UTC|newest]

Thread overview: 18+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-01-25 16:24 bonding (IEEE 802.3ad) not working with qemu/virtio Bjørnar Ness
2016-01-28 13:33 ` Jiri Pirko
2016-01-28 13:53   ` Nikolay Aleksandrov
2016-01-28 14:10     ` Nikolay Aleksandrov [this message]
2016-01-29 21:31 ` Nikolay Aleksandrov
2016-01-29 21:45   ` Jay Vosburgh
2016-01-29 21:48     ` Nikolay Aleksandrov
2016-01-30  6:59       ` David Miller
2016-01-30 11:34         ` Jiri Pirko
2016-01-30 11:34         ` Jiri Pirko
2016-01-30 11:41         ` Nikolay Aleksandrov
2016-01-30 11:41         ` Nikolay Aleksandrov
2016-01-31 14:50           ` Michael S. Tsirkin
2016-01-31 14:50           ` Michael S. Tsirkin
2016-02-01 18:49         ` Rick Jones
2016-01-31 14:58       ` Michael S. Tsirkin
2016-01-29 21:48     ` Nikolay Aleksandrov
2016-01-31 14:35     ` Michael S. Tsirkin

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=56AA216B.3040105@cumulusnetworks.com \
    --to=nikolay@cumulusnetworks.com \
    --cc=bjornar.ness@gmail.com \
    --cc=jiri@resnulli.us \
    --cc=netdev@vger.kernel.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.