From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from mailman by lists.gnu.org with tmda-scanned (Exim 4.43) id 1LN6C9-0005xO-HQ for qemu-devel@nongnu.org; Wed, 14 Jan 2009 08:54:09 -0500 Received: from exim by lists.gnu.org with spam-scanned (Exim 4.43) id 1LN6C6-0005tS-A8 for qemu-devel@nongnu.org; Wed, 14 Jan 2009 08:54:08 -0500 Received: from [199.232.76.173] (port=54088 helo=monty-python.gnu.org) by lists.gnu.org with esmtp (Exim 4.43) id 1LN6C6-0005tD-3H for qemu-devel@nongnu.org; Wed, 14 Jan 2009 08:54:06 -0500 Received: from mx2.redhat.com ([66.187.237.31]:43058) by monty-python.gnu.org with esmtp (Exim 4.60) (envelope-from ) id 1LN6C5-0003jV-Gp for qemu-devel@nongnu.org; Wed, 14 Jan 2009 08:54:05 -0500 Received: from int-mx2.corp.redhat.com (int-mx2.corp.redhat.com [172.16.27.26]) by mx2.redhat.com (8.13.8/8.13.8) with ESMTP id n0EDs4gL008777 for ; Wed, 14 Jan 2009 08:54:04 -0500 Date: Wed, 14 Jan 2009 15:52:31 +0200 From: Gleb Natapov Subject: Re: [Qemu-devel] [PATCH] Stop VM on ENOSPC error Message-ID: <20090114135231.GA4559@redhat.com> References: <20090114120358.GS3267@redhat.com> <20090114121147.GI24995@redhat.com> <496DD884.60608@redhat.com> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <496DD884.60608@redhat.com> Reply-To: qemu-devel@nongnu.org List-Id: qemu-devel.nongnu.org List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , To: dlaor@redhat.com, qemu-devel@nongnu.org On Wed, Jan 14, 2009 at 02:20:20PM +0200, Dor Laor wrote: > Daniel P. Berrange wrote: >> On Wed, Jan 14, 2009 at 02:03:58PM +0200, Gleb Natapov wrote: >> >>> And repeat last IDE command after VM restart. >>> >> >> How is a management application to determine when this occurs ? >> It is not desirable to poll for whether the VM is stopped all >> the time, and we need a reliable way to detect this, otherwise >> the user and/or mgmt app will just think their VM has hung. >> >> Thus I'd suggest we need an async notification of this event, >> and only enable this behaviour if the app controlling QEMU has >> explicitly enabled this notification / feature. >> >> > Correct. There is async message for it (==printf...). > Once the libmonitor is introduced it will be real async event There is not printf in this version of the patch, but I can add it if needed. -- Gleb.