Paul Brook wrote:
I immediately reproduced the problem locally. It turns out that
kvm reflects packets coming from one guest NIC on another guest
NIC, and since both are connected to the same bridge we're getting
endless packet storm. To a level when kvm process becomes 100%
busy and does not
I immediately reproduced the problem locally. It turns out that
kvm reflects packets coming from one guest NIC on another guest
NIC, and since both are connected to the same bridge we're getting
endless packet storm. To a level when kvm process becomes 100%
busy and does not respond to
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
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
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
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
Hello.
I vaguely remember something like this has been reported and/or
discussed already, but I can't find anything related. I'm also
not sure if it's kvm-specific or exists in qemu too.
I want some clarification wrt vlan= parameter in -net definition.
What started this all is a problem report
On Fri, Oct 23, 2009 at 08:25:39PM +0400, Michael Tokarev wrote:
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
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
Andreas Plesner Jacobsen wrote:
On Fri, Oct 23, 2009 at 08:25:39PM +0400, Michael Tokarev wrote:
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
10 matches
Mail list logo
