From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from mailman by lists.gnu.org with tmda-scanned (Exim 4.43) id 1N3U50-00050p-Ak for qemu-devel@nongnu.org; Thu, 29 Oct 2009 08:26:14 -0400 Received: from exim by lists.gnu.org with spam-scanned (Exim 4.43) id 1N3U4s-0004vU-TY for qemu-devel@nongnu.org; Thu, 29 Oct 2009 08:26:11 -0400 Received: from [199.232.76.173] (port=33380 helo=monty-python.gnu.org) by lists.gnu.org with esmtp (Exim 4.43) id 1N3U4s-0004ur-DU for qemu-devel@nongnu.org; Thu, 29 Oct 2009 08:26:06 -0400 Received: from mx1.redhat.com ([209.132.183.28]:32151) by monty-python.gnu.org with esmtp (Exim 4.60) (envelope-from ) id 1N3U4r-0000Ok-MB for qemu-devel@nongnu.org; Thu, 29 Oct 2009 08:26:05 -0400 Date: Thu, 29 Oct 2009 14:23:34 +0200 From: "Michael S. Tsirkin" Message-ID: <20091029122334.GB3478@redhat.com> References: <1256807803.10825.39.camel@blaa> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <1256807803.10825.39.camel@blaa> Subject: [Qemu-devel] Re: qemu-kvm-0.11 regression, crashes on older guests with virtio network List-Id: qemu-devel.nongnu.org List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , To: Mark McLoughlin Cc: Scott Tsai , qemu-devel@nongnu.org, kvm@vger.kernel.org, Dustin Kirkland On Thu, Oct 29, 2009 at 09:16:43AM +0000, Mark McLoughlin wrote: > I agree we shouldn't exit in this scenario virtio in qemu generally seems to handle guest errors by calling exit(2). This probably makes it easier to notice the problems, but is likely not the right thing to do. A simple way to tell guest there's a problem is by writing a value > ring size into used ring. -- MST