From: Michael Tokarev <mjt@tls.msk.ru>
To: Paul Brook <paul@codesourcery.com>
Cc: qemu-devel@nongnu.org, KVM list <kvm@vger.kernel.org>
Subject: Re: [Qemu-devel] net packet storms with multiple NICs
Date: Wed, 11 Nov 2009 12:23:01 +0300 [thread overview]
Message-ID: <4AFA8275.2080306@msgid.tls.msk.ru> (raw)
In-Reply-To: <200911110119.18839.paul@codesourcery.com>
Paul Brook wrote:
>> I immediately reproduced the problem locally. It turns out that
>> kvm reflects packets coming from one guest NIC on another guest
>> NIC, and since both are connected to the same bridge we're getting
>> endless packet storm. To a level when kvm process becomes 100%
>> busy and does not respond to anything but `kill -9'.
>
> You created a network loop. It is working exactly as expected.
> Create the same topology with a physical network hub and a pair of NICs and
> you'll get the same end result.
Paul, I know what the result is. But mind you, I talked about something
different, namely: why, using "obvious" way, you get a packet storm/loop
instead of a working network. And if that loop is useful in the first
place.
I've got answers to both already :)
Thanks
/mjt
prev parent reply other threads:[~2009-11-11 9:22 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-10-23 16:25 net packet storms with multiple NICs Michael Tokarev
2009-10-23 16:25 ` [Qemu-devel] " Michael Tokarev
2009-10-23 16:33 ` Andreas Plesner Jacobsen
2009-10-23 16:33 ` [Qemu-devel] " Andreas Plesner Jacobsen
2009-10-23 16:57 ` Michael Tokarev
2009-10-23 16:57 ` [Qemu-devel] " Michael Tokarev
2009-10-23 16:43 ` [Qemu-devel] " Mark McLoughlin
2009-10-25 14:22 ` Avi Kivity
2009-10-26 13:40 ` Krumme, Chris
2009-10-26 13:40 ` Krumme, Chris
2009-10-26 13:44 ` Avi Kivity
2009-11-11 1:38 ` Anthony Liguori
2009-11-11 1:19 ` Paul Brook
2009-11-11 9:23 ` Michael Tokarev [this message]
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=4AFA8275.2080306@msgid.tls.msk.ru \
--to=mjt@tls.msk.ru \
--cc=kvm@vger.kernel.org \
--cc=paul@codesourcery.com \
--cc=qemu-devel@nongnu.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.