From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from mailman by lists.gnu.org with tmda-scanned (Exim 4.43) id 1LN4j4-0001pD-Hu for qemu-devel@nongnu.org; Wed, 14 Jan 2009 07:20:03 -0500 Received: from exim by lists.gnu.org with spam-scanned (Exim 4.43) id 1LN4j3-0001nT-Ff for qemu-devel@nongnu.org; Wed, 14 Jan 2009 07:20:01 -0500 Received: from [199.232.76.173] (port=42576 helo=monty-python.gnu.org) by lists.gnu.org with esmtp (Exim 4.43) id 1LN4j3-0001n9-8R for qemu-devel@nongnu.org; Wed, 14 Jan 2009 07:20:01 -0500 Received: from mx2.redhat.com ([66.187.237.31]:49372) by monty-python.gnu.org with esmtp (Exim 4.60) (envelope-from ) id 1LN4j2-0006y0-SZ for qemu-devel@nongnu.org; Wed, 14 Jan 2009 07:20:01 -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 n0ECK0jM024533 for ; Wed, 14 Jan 2009 07:20:00 -0500 Message-ID: <496DD884.60608@redhat.com> Date: Wed, 14 Jan 2009 14:20:20 +0200 From: Dor Laor MIME-Version: 1.0 Subject: Re: [Qemu-devel] [PATCH] Stop VM on ENOSPC error References: <20090114120358.GS3267@redhat.com> <20090114121147.GI24995@redhat.com> In-Reply-To: <20090114121147.GI24995@redhat.com> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Reply-To: dlaor@redhat.com, qemu-devel@nongnu.org List-Id: qemu-devel.nongnu.org List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , To: "Daniel P. Berrange" , qemu-devel@nongnu.org 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 > Daniel >