From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from mailman by lists.gnu.org with tmda-scanned (Exim 4.43) id 1LN4b9-0007gf-MT for qemu-devel@nongnu.org; Wed, 14 Jan 2009 07:11:51 -0500 Received: from exim by lists.gnu.org with spam-scanned (Exim 4.43) id 1LN4b8-0007eo-7C for qemu-devel@nongnu.org; Wed, 14 Jan 2009 07:11:51 -0500 Received: from [199.232.76.173] (port=44545 helo=monty-python.gnu.org) by lists.gnu.org with esmtp (Exim 4.43) id 1LN4b7-0007eh-Ts for qemu-devel@nongnu.org; Wed, 14 Jan 2009 07:11:50 -0500 Received: from mx1.redhat.com ([66.187.233.31]:38211) by monty-python.gnu.org with esmtp (Exim 4.60) (envelope-from ) id 1LN4b7-000655-KP for qemu-devel@nongnu.org; Wed, 14 Jan 2009 07:11:49 -0500 Received: from int-mx1.corp.redhat.com (int-mx1.corp.redhat.com [172.16.52.254]) by mx1.redhat.com (8.13.8/8.13.8) with ESMTP id n0ECBneQ031654 for ; Wed, 14 Jan 2009 07:11:49 -0500 Received: from file.fab.redhat.com (file.fab.redhat.com [10.33.63.6]) by int-mx1.corp.redhat.com (8.13.1/8.13.1) with ESMTP id n0ECBnep032150 for ; Wed, 14 Jan 2009 07:11:49 -0500 Received: from file.fab.redhat.com (localhost.localdomain [127.0.0.1]) by file.fab.redhat.com (8.13.1/8.13.1) with ESMTP id n0ECBmYo014126 for ; Wed, 14 Jan 2009 12:11:48 GMT Received: (from berrange@localhost) by file.fab.redhat.com (8.13.1/8.13.1/Submit) id n0ECBmNT014122 for qemu-devel@nongnu.org; Wed, 14 Jan 2009 12:11:48 GMT Date: Wed, 14 Jan 2009 12:11:48 +0000 From: "Daniel P. Berrange" Subject: Re: [Qemu-devel] [PATCH] Stop VM on ENOSPC error Message-ID: <20090114121147.GI24995@redhat.com> References: <20090114120358.GS3267@redhat.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20090114120358.GS3267@redhat.com> Reply-To: "Daniel P. Berrange" , 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 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. Daniel -- |: Red Hat, Engineering, London -o- http://people.redhat.com/berrange/ :| |: http://libvirt.org -o- http://virt-manager.org -o- http://ovirt.org :| |: http://autobuild.org -o- http://search.cpan.org/~danberr/ :| |: GnuPG: 7D3B9505 -o- F3C9 553F A1DA 4AC2 5648 23C1 B3DF F742 7D3B 9505 :|