From: Avi Kivity <avi@redhat.com>
To: Gleb Natapov <gleb@redhat.com>
Cc: Beth Kon <eak@us.ibm.com>, qemu-devel <qemu-devel@nongnu.org>
Subject: Re: [Qemu-devel] accidental mistyping of command line kills networking
Date: Wed, 28 Oct 2009 10:55:50 +0200 [thread overview]
Message-ID: <4AE80716.3040102@redhat.com> (raw)
In-Reply-To: <20091028083429.GS29477@redhat.com>
On 10/28/2009 10:34 AM, Gleb Natapov wrote:
>
>> It shouldn't kill networking though. If a guest has two nics
>> connected to the same host bridge (a reasonable configuration), and
>> then connects these two nics through its own bridge, it creates the
>> same sort of loop. If that kills networking, we have a
>> guest-initiated DoS (not that the userspace-initiated DoS was much
>> better).
>>
>>
> That's what STP is for.
>
>
The guest need not respect it. The host must survive network loopbacks.
--
error compiling committee.c: too many arguments to function
next prev parent reply other threads:[~2009-10-28 8:56 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-10-27 19:12 [Qemu-devel] accidental mistyping of command line kills networking Beth Kon
2009-10-27 21:10 ` Beth Kon
2009-10-27 21:44 ` Anthony Liguori
2009-10-28 6:29 ` Avi Kivity
2009-10-28 8:34 ` Gleb Natapov
2009-10-28 8:55 ` Avi Kivity [this message]
2009-10-28 9:07 ` Gleb Natapov
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=4AE80716.3040102@redhat.com \
--to=avi@redhat.com \
--cc=eak@us.ibm.com \
--cc=gleb@redhat.com \
--cc=qemu-devel@nongnu.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).