From mboxrd@z Thu Jan  1 00:00:00 1970
Received: from mailman by lists.gnu.org with tmda-scanned (Exim 4.43)
	id 1N2PsR-0005Ey-NF
	for qemu-devel@nongnu.org; Mon, 26 Oct 2009 09:44:51 -0400
Received: from exim by lists.gnu.org with spam-scanned (Exim 4.43)
	id 1N2PsN-0005D8-6s
	for qemu-devel@nongnu.org; Mon, 26 Oct 2009 09:44:51 -0400
Received: from [199.232.76.173] (port=34617 helo=monty-python.gnu.org)
	by lists.gnu.org with esmtp (Exim 4.43) id 1N2PsN-0005D5-2G
	for qemu-devel@nongnu.org; Mon, 26 Oct 2009 09:44:47 -0400
Received: from mx1.redhat.com ([209.132.183.28]:4630)
	by monty-python.gnu.org with esmtp (Exim 4.60)
	(envelope-from <avi@redhat.com>) id 1N2PsM-0006PO-LM
	for qemu-devel@nongnu.org; Mon, 26 Oct 2009 09:44:46 -0400
Message-ID: <4AE5A7C9.6050809@redhat.com>
Date: Mon, 26 Oct 2009 15:44:41 +0200
From: Avi Kivity <avi@redhat.com>
MIME-Version: 1.0
Subject: Re: [Qemu-devel] net packet storms with multiple NICs
References: <4AE1D903.5030709@msgid.tls.msk.ru><1256316218.31881.85.camel@blaa>
	<4AE45F3E.5090208@redhat.com>
	<58BD0469C48A7443A479A13D101685E3034AB9C1@ala-mail09.corp.ad.wrs.com>
In-Reply-To: <58BD0469C48A7443A479A13D101685E3034AB9C1@ala-mail09.corp.ad.wrs.com>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
List-Id: qemu-devel.nongnu.org
List-Unsubscribe: <http://lists.nongnu.org/mailman/listinfo/qemu-devel>,
	<mailto:qemu-devel-request@nongnu.org?subject=unsubscribe>
List-Archive: <http://lists.gnu.org/pipermail/qemu-devel>
List-Post: <mailto:qemu-devel@nongnu.org>
List-Help: <mailto:qemu-devel-request@nongnu.org?subject=help>
List-Subscribe: <http://lists.nongnu.org/mailman/listinfo/qemu-devel>,
	<mailto:qemu-devel-request@nongnu.org?subject=subscribe>
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>

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