From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from mailman by lists.gnu.org with tmda-scanned (Exim 4.43) id 1LN6eP-0004UM-H6 for qemu-devel@nongnu.org; Wed, 14 Jan 2009 09:23:21 -0500 Received: from exim by lists.gnu.org with spam-scanned (Exim 4.43) id 1LN6eO-0004SH-2W for qemu-devel@nongnu.org; Wed, 14 Jan 2009 09:23:21 -0500 Received: from [199.232.76.173] (port=42746 helo=monty-python.gnu.org) by lists.gnu.org with esmtp (Exim 4.43) id 1LN6eN-0004S3-Pf for qemu-devel@nongnu.org; Wed, 14 Jan 2009 09:23:19 -0500 Received: from mx2.suse.de ([195.135.220.15]:53141) by monty-python.gnu.org with esmtps (TLS-1.0:DHE_RSA_AES_256_CBC_SHA1:32) (Exim 4.60) (envelope-from ) id 1LN6eN-0000x6-FC for qemu-devel@nongnu.org; Wed, 14 Jan 2009 09:23:19 -0500 Received: from Relay1.suse.de (relay-ext.suse.de [195.135.221.8]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by mx2.suse.de (Postfix) with ESMTP id 598EB4857B for ; Wed, 14 Jan 2009 15:23:16 +0100 (CET) Message-ID: <496DF6AA.7000302@suse.de> Date: Wed, 14 Jan 2009 15:28:58 +0100 From: Kevin Wolf MIME-Version: 1.0 Subject: Re: [Qemu-devel] [PATCH] Stop VM on ENOSPC error References: <20090114120358.GS3267@redhat.com> <20090114121147.GI24995@redhat.com> <496DD884.60608@redhat.com> <20090114135231.GA4559@redhat.com> In-Reply-To: <20090114135231.GA4559@redhat.com> Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit Reply-To: qemu-devel@nongnu.org List-Id: qemu-devel.nongnu.org List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , To: qemu-devel@nongnu.org Gleb Natapov schrieb: > 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. I think you should add it. Not only because of management applications but also for the user. I for one would be at least a bit confused if my VM stopped automatically without saying anything about the reason. Kevin