From: Anthony Liguori <anthony@codemonkey.ws>
To: kirkland@canonical.com
Cc: Jamie Lokier <jamie@shareable.org>,
Mark McLoughlin <markmc@redhat.com>,
Scott Tsai <scottt.tw@gmail.com>, kvm <kvm@vger.kernel.org>,
Rusty Russell <rusty@rustcorp.com.au>,
qemu-devel <qemu-devel@nongnu.org>,
jdstrand@canonical.com,
Marc Deslauriers <marc.deslauriers@canonical.com>,
kees.cook@canonical.com
Subject: Re: [Qemu-devel] Re: [PATCH] whitelist host virtio networking features [was Re: qemu-kvm-0.11 regression, crashes on older ...]
Date: Mon, 02 Nov 2009 14:50:34 -0600 [thread overview]
Message-ID: <4AEF461A.4020407@codemonkey.ws> (raw)
In-Reply-To: <1257189955.3512.236.camel@x200>
Dustin Kirkland wrote:
> On Mon, 2009-11-02 at 12:55 -0600, Anthony Liguori wrote:
>
>> They can exit qemu via an ACPI shutdown. I don't see the difference.
>>
>
> An ACPI shutdown is triggered by an authenticated user inside of the
> guest.
>
> The present exit is triggered by any other anonymous user on the
> network, with the ability to send a lot of packets very quickly to the
> VM guest. The guest isn't able to handle this properly (and rightly
> that guest's kernel should be fixed). But I do see a difference.
>
Well the problem is triggered by the guest kernel writing garbage to
virtio-net's backend. That's why we're suggesting it's really a guest
kernel issue.
If the guest kernel writes something bad to qemu, we're may kill the
guest. That's not a qemu bug, it's the designed behavior.
Regards,
Anthony Liguori
> :-Dustin
>
next prev parent reply other threads:[~2009-11-02 20:50 UTC|newest]
Thread overview: 36+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-10-28 19:22 qemu-kvm-0.11 regression, crashes on older guests with virtio network Dustin Kirkland
2009-10-28 19:29 ` Dustin Kirkland
2009-10-29 3:12 ` [Qemu-devel] " Scott Tsai
2009-10-29 9:16 ` Mark McLoughlin
2009-10-29 12:00 ` Scott Tsai
2009-10-29 12:16 ` Mark McLoughlin
2009-10-29 12:21 ` Scott Tsai
2009-10-29 14:11 ` Anthony Liguori
2009-10-29 14:25 ` Mark McLoughlin
2009-10-29 14:34 ` Dustin Kirkland
2009-10-29 14:46 ` Dustin Kirkland
2009-10-29 14:50 ` Mark McLoughlin
2009-10-29 14:39 ` Anthony Liguori
2009-10-29 14:48 ` Mark McLoughlin
2009-10-29 15:01 ` Dustin Kirkland
2009-10-29 15:01 ` Mark McLoughlin
2009-10-29 15:13 ` Dustin Kirkland
2009-10-29 15:15 ` Mark McLoughlin
2009-10-29 15:34 ` [PATCH] whitelist host virtio networking features [was Re: qemu-kvm-0.11 regression, crashes on older ...] Dustin Kirkland
2009-10-30 21:15 ` Dustin Kirkland
2009-11-02 14:38 ` Mark McLoughlin
2009-11-02 15:42 ` Anthony Liguori
2009-11-02 15:52 ` [Qemu-devel] " Jamie Lokier
2009-11-02 18:20 ` Michael Tokarev
2009-11-02 19:39 ` Jamie Lokier
2009-11-02 18:55 ` Anthony Liguori
2009-11-02 19:25 ` Dustin Kirkland
2009-11-02 20:50 ` Anthony Liguori [this message]
2009-11-05 5:06 ` Jamie Lokier
2009-11-02 16:58 ` Dustin Kirkland
2009-10-29 14:39 ` [Qemu-devel] qemu-kvm-0.11 regression, crashes on older guests with virtio network Dustin Kirkland
2009-10-29 23:22 ` Scott Tsai
2009-10-29 12:23 ` Michael S. Tsirkin
2009-10-29 14:38 ` Avi Kivity
2009-10-29 15:03 ` Michael S. Tsirkin
2009-10-29 14:43 ` [Qemu-devel] " Dustin Kirkland
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=4AEF461A.4020407@codemonkey.ws \
--to=anthony@codemonkey.ws \
--cc=jamie@shareable.org \
--cc=jdstrand@canonical.com \
--cc=kees.cook@canonical.com \
--cc=kirkland@canonical.com \
--cc=kvm@vger.kernel.org \
--cc=marc.deslauriers@canonical.com \
--cc=markmc@redhat.com \
--cc=qemu-devel@nongnu.org \
--cc=rusty@rustcorp.com.au \
--cc=scottt.tw@gmail.com \
/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