From mboxrd@z Thu Jan 1 00:00:00 1970 From: Avi Kivity Subject: Re: [Qemu-devel] net packet storms with multiple NICs Date: Sun, 25 Oct 2009 16:22:54 +0200 Message-ID: <4AE45F3E.5090208@redhat.com> References: <4AE1D903.5030709@msgid.tls.msk.ru> <1256316218.31881.85.camel@blaa> Mime-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Cc: Michael Tokarev , "qemu-devel@nongnu.org" , KVM list To: Mark McLoughlin Return-path: Received: from mx1.redhat.com ([209.132.183.28]:59287 "EHLO mx1.redhat.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1751766AbZJYOW5 (ORCPT ); Sun, 25 Oct 2009 10:22:57 -0400 In-Reply-To: <1256316218.31881.85.camel@blaa> Sender: kvm-owner@vger.kernel.org List-ID: On 10/23/2009 06:43 PM, 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 > 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. -- error compiling committee.c: too many arguments to function