From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from mailman by lists.gnu.org with tmda-scanned (Exim 4.43) id 1LN8sn-0002rs-Ci for qemu-devel@nongnu.org; Wed, 14 Jan 2009 11:46:21 -0500 Received: from exim by lists.gnu.org with spam-scanned (Exim 4.43) id 1LN8sm-0002qb-Kj for qemu-devel@nongnu.org; Wed, 14 Jan 2009 11:46:20 -0500 Received: from [199.232.76.173] (port=41791 helo=monty-python.gnu.org) by lists.gnu.org with esmtp (Exim 4.43) id 1LN8sm-0002qG-Aw for qemu-devel@nongnu.org; Wed, 14 Jan 2009 11:46:20 -0500 Received: from mail2.shareable.org ([80.68.89.115]:57674) by monty-python.gnu.org with esmtps (TLS-1.0:RSA_AES_256_CBC_SHA1:32) (Exim 4.60) (envelope-from ) id 1LN8sl-0002lW-Ra for qemu-devel@nongnu.org; Wed, 14 Jan 2009 11:46:20 -0500 Date: Wed, 14 Jan 2009 16:46:17 +0000 From: Jamie Lokier Subject: Re: [Qemu-devel] [PATCH] Stop VM on ENOSPC error Message-ID: <20090114164617.GB6431@shareable.org> References: <20090114120358.GS3267@redhat.com> <20090114121147.GI24995@redhat.com> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20090114121147.GI24995@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: "Daniel P. Berrange" , qemu-devel@nongnu.org Daniel P. Berrange wrote: > 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. I think the behaviour should always be enabled (unless explicitly disabled, but I'm not sure why you'd want to do that). A corrupt VM with data loss sounds much worse than a stopped VM to me. If the VM is in some critical server role, you probably have a watchdog or something pinging it anyway, same as real hardware. -- Jamie