From mboxrd@z Thu Jan 1 00:00:00 1970 From: "Michael S. Tsirkin" Subject: Re: qemu-kvm-0.11 regression, crashes on older guests with virtio network Date: Thu, 29 Oct 2009 14:23:34 +0200 Message-ID: <20091029122334.GB3478@redhat.com> References: <1256807803.10825.39.camel@blaa> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Cc: Dustin Kirkland , qemu-devel@nongnu.org, kvm@vger.kernel.org, Anthony Liguori , Scott Tsai To: Mark McLoughlin Return-path: Received: from mx1.redhat.com ([209.132.183.28]:39249 "EHLO mx1.redhat.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1751798AbZJ2M0B (ORCPT ); Thu, 29 Oct 2009 08:26:01 -0400 Content-Disposition: inline In-Reply-To: <1256807803.10825.39.camel@blaa> Sender: kvm-owner@vger.kernel.org List-ID: 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