From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from eggs.gnu.org ([2001:4830:134:3::10]:49271) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1XHulD-0002QO-Kj for qemu-devel@nongnu.org; Thu, 14 Aug 2014 09:08:13 -0400 Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1XHul7-000296-GG for qemu-devel@nongnu.org; Thu, 14 Aug 2014 09:08:07 -0400 Received: from mx1.redhat.com ([209.132.183.28]:4478) by eggs.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1XHul7-000292-8V for qemu-devel@nongnu.org; Thu, 14 Aug 2014 09:08:01 -0400 Received: from int-mx10.intmail.prod.int.phx2.redhat.com (int-mx10.intmail.prod.int.phx2.redhat.com [10.5.11.23]) by mx1.redhat.com (8.14.4/8.14.4) with ESMTP id s7ED80WZ008879 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-GCM-SHA384 bits=256 verify=OK) for ; Thu, 14 Aug 2014 09:08:00 -0400 Date: Thu, 14 Aug 2014 09:07:56 -0400 From: Luiz Capitulino Message-ID: <20140814090756.3b47979c@redhat.com> In-Reply-To: <53E0CBCF.2040600@redhat.com> References: <1406121438-23083-1-git-send-email-lcapitulino@redhat.com> <1406121438-23083-4-git-send-email-lcapitulino@redhat.com> <53E0CBCF.2040600@redhat.com> MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Subject: Re: [Qemu-devel] [RFC 3/3] QMP: extend BLOCK_IO_ERROR event with no-space indicator List-Id: List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , To: Eric Blake Cc: kwolf@redhat.com, pbonzini@redhat.com, qemu-devel@nongnu.org, armbru@redhat.com On Tue, 05 Aug 2014 06:19:27 -0600 Eric Blake wrote: > On 07/23/2014 07:17 AM, Luiz Capitulino wrote: > > Management software, such as OpenStack and RHEV's vdsm, want to be able > > to allocate disk space on demand. The basic use case is to start a VM > > with a small disk and then the disk is enlarged when QEMU hits a ENOSPC > > condition. > > I'd still like feedback from OpenStack or vdsm folks stating what they > do with this information, if a bool for ENOSPC is good enough. You're right, that's the most important item for this series. Do you know whom I should contact from OpenStack?