From: Luiz Capitulino <lcapitulino@redhat.com>
To: Eric Blake <eblake@redhat.com>
Cc: kwolf@redhat.com, pbonzini@redhat.com, qemu-devel@nongnu.org,
armbru@redhat.com
Subject: Re: [Qemu-devel] [RFC 3/3] QMP: extend BLOCK_IO_ERROR event with no-space indicator
Date: Thu, 14 Aug 2014 09:07:56 -0400 [thread overview]
Message-ID: <20140814090756.3b47979c@redhat.com> (raw)
In-Reply-To: <53E0CBCF.2040600@redhat.com>
On Tue, 05 Aug 2014 06:19:27 -0600
Eric Blake <eblake@redhat.com> 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?
next prev parent reply other threads:[~2014-08-14 13:08 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-07-23 13:17 [Qemu-devel] [RFC 0/3] QMP: extend BLOCK_IO_ERROR event Luiz Capitulino
2014-07-23 13:17 ` [Qemu-devel] [RFC 1/3] qapi: block-core.json: improve query-block doc Luiz Capitulino
2014-08-05 12:13 ` Eric Blake
2014-07-23 13:17 ` [Qemu-devel] [RFC 2/3] QMP: rate limit BLOCK_IO_ERROR Luiz Capitulino
2014-08-05 12:14 ` Eric Blake
2014-08-11 8:17 ` Daniel P. Berrange
2014-08-11 11:07 ` Markus Armbruster
2014-08-11 11:15 ` Daniel P. Berrange
2014-08-17 6:08 ` Paolo Bonzini
2014-08-14 13:13 ` Luiz Capitulino
2014-07-23 13:17 ` [Qemu-devel] [RFC 3/3] QMP: extend BLOCK_IO_ERROR event with no-space indicator Luiz Capitulino
2014-08-05 12:19 ` Eric Blake
2014-08-14 13:07 ` Luiz Capitulino [this message]
2014-08-05 9:13 ` [Qemu-devel] [RFC 0/3] QMP: extend BLOCK_IO_ERROR event Kevin Wolf
2014-08-14 13:05 ` Luiz Capitulino
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20140814090756.3b47979c@redhat.com \
--to=lcapitulino@redhat.com \
--cc=armbru@redhat.com \
--cc=eblake@redhat.com \
--cc=kwolf@redhat.com \
--cc=pbonzini@redhat.com \
--cc=qemu-devel@nongnu.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.