From mboxrd@z Thu Jan 1 00:00:00 1970 From: Avi Kivity Subject: Re: [Qemu-devel] net packet storms with multiple NICs Date: Mon, 26 Oct 2009 15:44:41 +0200 Message-ID: <4AE5A7C9.6050809@redhat.com> References: <4AE1D903.5030709@msgid.tls.msk.ru><1256316218.31881.85.camel@blaa> <4AE45F3E.5090208@redhat.com> <58BD0469C48A7443A479A13D101685E3034AB9C1@ala-mail09.corp.ad.wrs.com> Mime-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Cc: Mark McLoughlin , Michael Tokarev , qemu-devel@nongnu.org, KVM list To: "Krumme, Chris" Return-path: Received: from mx1.redhat.com ([209.132.183.28]:55015 "EHLO mx1.redhat.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1751992AbZJZNow (ORCPT ); Mon, 26 Oct 2009 09:44:52 -0400 In-Reply-To: <58BD0469C48A7443A479A13D101685E3034AB9C1@ala-mail09.corp.ad.wrs.com> Sender: kvm-owner@vger.kernel.org List-ID: 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