From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from mailman by lists.gnu.org with tmda-scanned (Exim 4.43) id 1LcOrJ-00052p-As for qemu-devel@nongnu.org; Wed, 25 Feb 2009 13:51:53 -0500 Received: from exim by lists.gnu.org with spam-scanned (Exim 4.43) id 1LcOrG-00052L-Qg for qemu-devel@nongnu.org; Wed, 25 Feb 2009 13:51:51 -0500 Received: from [199.232.76.173] (port=39126 helo=monty-python.gnu.org) by lists.gnu.org with esmtp (Exim 4.43) id 1LcOrG-00052G-Jl for qemu-devel@nongnu.org; Wed, 25 Feb 2009 13:51:50 -0500 Received: from mail2.shareable.org ([80.68.89.115]:57879) by monty-python.gnu.org with esmtps (TLS-1.0:RSA_AES_256_CBC_SHA1:32) (Exim 4.60) (envelope-from ) id 1LcOrG-0001RS-3D for qemu-devel@nongnu.org; Wed, 25 Feb 2009 13:51:50 -0500 Date: Wed, 25 Feb 2009 18:51:48 +0000 From: Jamie Lokier Subject: Re: [Qemu-devel] [6388] Stop VM on ENOSPC error. Message-ID: <20090225185148.GD16453@shareable.org> References: <49A577FD.60701@codemonkey.ws> <20090225172051.GT24969@redhat.com> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20090225172051.GT24969@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 Cc: Gleb Natapov Daniel P. Berrange wrote: > > Any objection to changing to default to enospc? > > >From a managment POV having QEMU change its state from running to > paused behind our back is hard. >>From a management POV, the manager can just set the behaviour to 'report' if that's what you prefer :-) > If we get async notifications available via the monitor, then making > the default enospc is very sensible. Async notifications are obviously best, but can QEMU's logging be used? Can it log the ENOSPC event, and the management app watch the log? -- Jamie