From mboxrd@z Thu Jan  1 00:00:00 1970
Received: from mailman by lists.gnu.org with tmda-scanned (Exim 4.43)
	id 1N82Aj-0004Mq-BV
	for qemu-devel@nongnu.org; Tue, 10 Nov 2009 20:38:57 -0500
Received: from exim by lists.gnu.org with spam-scanned (Exim 4.43)
	id 1N82Ae-0004ET-6m
	for qemu-devel@nongnu.org; Tue, 10 Nov 2009 20:38:56 -0500
Received: from [199.232.76.173] (port=60015 helo=monty-python.gnu.org)
	by lists.gnu.org with esmtp (Exim 4.43) id 1N82Ad-0004Dz-SO
	for qemu-devel@nongnu.org; Tue, 10 Nov 2009 20:38:51 -0500
Received: from mail-yw0-f176.google.com ([209.85.211.176]:46346)
	by monty-python.gnu.org with esmtp (Exim 4.60)
	(envelope-from <anthony@codemonkey.ws>) id 1N82Ad-0003Gw-FT
	for qemu-devel@nongnu.org; Tue, 10 Nov 2009 20:38:51 -0500
Received: by ywh6 with SMTP id 6so576213ywh.4
	for <qemu-devel@nongnu.org>; Tue, 10 Nov 2009 17:38:50 -0800 (PST)
Message-ID: <4AFA15A8.4070402@codemonkey.ws>
Date: Tue, 10 Nov 2009 19:38:48 -0600
From: Anthony Liguori <anthony@codemonkey.ws>
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>
In-Reply-To: <1256316218.31881.85.camel@blaa>
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: Mark McLoughlin <markmc@redhat.com>
Cc: Michael Tokarev <mjt@tls.msk.ru>, "qemu-devel@nongnu.org" <qemu-devel@nongnu.org>, KVM list <kvm@vger.kernel.org>

Mark McLoughlin wrote:
> On Fri, 2009-10-23 at 20:25 +0400, Michael Tokarev wrote:
>   
>> I've two questions:
>>
>> o what's the intended usage of all-vlan-equal case, when kvm (or qemu)
>>    reflects packets from one interface to another?  It's what bridge
>>    in linux is for, I think.
>>     
>
> I don't think it's necessarily an intended use-case for the vlan feature
>
>   
>> o why different -net guest -net host pairs are not getting different
>>    vlan= indexes by default, to stop the above-mentioned packet
>>    storms right away?  I think it's a wise default to assign different
>>    pairs to different vlans, by counting -net host and -net guest
>>    sequences.
>>     
>
> With 0.12, we're going to be de-emphasising the vlan feature and instead
> have NICs directly connected to host backends. The vlan feature will be
> just another host backend, but optional
>
> You'll start guests with e.g.:
>
>   -netdev tap,id=tap.0 -device virtio-net-pci,netdev=tap.0
>   

Which is not necessarily more friendly to a user, but it lays the 
foundation to be able to do a config file which in turns could be easily 
generated from a nic GUI/command line tool.

Regards,

Anthony Liguori