RE: [Qemu-devel] net packet storms with multiple NICs

Krumme, Chris
2009-10-26T13:40:39Z

> -----Original Message-----
> From:
> qemu-devel-bounces+chris.krumme=windriver.com@nongnu.org
> [mailto:qemu-devel-bounces+chris.krumme=windriver.com@nongnu.o
rg] On Behalf Of Avi Kivity
> Sent: Sunday, October 25, 2009 9:23 AM
> To: Mark McLoughlin
> Cc: Michael Tokarev; qemu-devel@nongnu.org; KVM list
> Subject: Re: [Qemu-devel] net packet storms with multiple NICs
>
> 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.

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.

Thanks

Chris

>
> --
> error compiling committee.c: too many arguments to function
>
>
>
>