From: Avi Kivity <avi@redhat.com>
To: "Krumme, Chris" <Chris.Krumme@windriver.com>
Cc: Mark McLoughlin <markmc@redhat.com>,
Michael Tokarev <mjt@tls.msk.ru>,
qemu-devel@nongnu.org, KVM list <kvm@vger.kernel.org>
Subject: Re: [Qemu-devel] net packet storms with multiple NICs
Date: Mon, 26 Oct 2009 15:44:41 +0200 [thread overview]
Message-ID: <4AE5A7C9.6050809@redhat.com> (raw)
In-Reply-To: <58BD0469C48A7443A479A13D101685E3034AB9C1@ala-mail09.corp.ad.wrs.com>
On 10/26/2009 03:40 PM, Krumme, Chris wrote:
>
>> Well, it is. vlan=x really means "the ethernet segment named x". If
>> you connect all your guest nics to one vlan, you are
>> connecting them all
>> to one ethernet segment, so any packet transmitted on one will be
>> reflected on others.
>>
>> Whether this is a useful feature is another matter, but the code is
>> functioning as expected.
>>
> Hello,
>
> We had one environment where the NIC understood by u-boot and the NIC
> understood by the kernel where different. We just attached both to the
> same VLAN. During u-boot one was used for downloading the kernel, then
> once the kernel booted the other was used. Not ideal, and maybe not
> important enough to keep the "feature" around, but it does get used now
> and again.
>
You could get the same behaviour by using two different vlans connected
to the same bridge.
--
error compiling committee.c: too many arguments to function
next prev parent reply other threads:[~2009-10-26 13:44 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 [this message]
2009-11-11 1:38 ` Anthony Liguori
2009-11-11 1:19 ` Paul Brook
2009-11-11 9:23 ` Michael Tokarev
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=4AE5A7C9.6050809@redhat.com \
--to=avi@redhat.com \
--cc=Chris.Krumme@windriver.com \
--cc=kvm@vger.kernel.org \
--cc=markmc@redhat.com \
--cc=mjt@tls.msk.ru \
--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.