From mboxrd@z Thu Jan  1 00:00:00 1970
From: Anthony Liguori <anthony@codemonkey.ws>
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
Message-ID: <4AEF461A.4020407@codemonkey.ws>
References: <1256815818-sup-7805@xpc65.scottt>	 <1256818566.10825.58.camel@blaa> <4AE9A299.5060003@codemonkey.ws>	 <1256826351.10825.69.camel@blaa> <4AE9A90F.1060108@codemonkey.ws>	 <1256827719.10825.75.camel@blaa> <1256830455.25064.155.camel@x200>	 <d9c105ea0910301415n74efc9f2i3f8b2646217f44cb@mail.gmail.com>	 <1257172722.5075.7.camel@blaa> <4AEEFDCE.1000006@codemonkey.ws>	 <20091102155228.GB9655@shareable.org>  <4AEF2B28.6000303@codemonkey.ws> <1257189955.3512.236.camel@x200>
Mime-Version: 1.0
Content-Type: text/plain; charset=UTF-8; format=flowed
Content-Transfer-Encoding: 7bit
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
To: kirkland@canonical.com
Return-path: <kvm-owner@vger.kernel.org>
Received: from qw-out-2122.google.com ([74.125.92.24]:37389 "EHLO
	qw-out-2122.google.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org
	with ESMTP id S932408AbZKBUuc (ORCPT <rfc822;kvm@vger.kernel.org>);
	Mon, 2 Nov 2009 15:50:32 -0500
Received: by qw-out-2122.google.com with SMTP id 9so1197239qwb.37
        for <kvm@vger.kernel.org>; Mon, 02 Nov 2009 12:50:37 -0800 (PST)
In-Reply-To: <1257189955.3512.236.camel@x200>
Sender: kvm-owner@vger.kernel.org
List-ID: <kvm.vger.kernel.org>

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
>