From: Eric Blake <eblake@redhat.com>
To: Alberto Garcia <berto@igalia.com>, Kevin Wolf <kwolf@redhat.com>,
qemu-block@nongnu.org
Cc: armbru@redhat.com, qemu-devel@nongnu.org, mreitz@redhat.com
Subject: Re: [Qemu-devel] [Qemu-block] [PATCH 1/2] hmp: 'drive_add -n' for creating a node without BB
Date: Thu, 25 Feb 2016 09:05:44 -0700 [thread overview]
Message-ID: <56CF2658.7030709@redhat.com> (raw)
In-Reply-To: <w51h9gx0vy6.fsf@maestria.local.igalia.com>
[-- Attachment #1: Type: text/plain, Size: 622 bytes --]
On 02/25/2016 06:18 AM, Alberto Garcia wrote:
> On Tue 23 Feb 2016 06:16:38 PM CET, Kevin Wolf wrote:
>
>> However, libvirt can't use blockdev-add as long as it is still
>> experimental, and we're expecting that it will still take some time,
>> so we need to resort to drive_add.
>
> But how stable is the HMP API supposed to be?
In general, it's not stable. But for this particular API, as long as we
don't have a fully-working QMP replacement, we've been careful to keep
HMP working unchanged.
--
Eric Blake eblake redhat com +1-919-301-3266
Libvirt virtualization library http://libvirt.org
[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 604 bytes --]
next prev parent reply other threads:[~2016-02-25 16:06 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-02-23 17:16 [Qemu-devel] [PATCH 0/2] block: drive_add/del without BlockBackend Kevin Wolf
2016-02-23 17:16 ` [Qemu-devel] [PATCH 1/2] hmp: 'drive_add -n' for creating a node without BB Kevin Wolf
2016-02-24 17:50 ` Max Reitz
2016-02-24 18:24 ` Kevin Wolf
2016-02-25 13:18 ` [Qemu-devel] [Qemu-block] " Alberto Garcia
2016-02-25 16:05 ` Eric Blake [this message]
2016-02-23 17:16 ` [Qemu-devel] [PATCH 2/2] hmp: Extend drive_del to delete nodes " Kevin Wolf
2016-02-24 17:54 ` Max Reitz
2016-02-24 18:23 ` Kevin Wolf
2016-02-26 13:09 ` Max Reitz
2016-02-25 12:51 ` Peter Krempa
2016-02-26 13:11 ` Max Reitz
2016-03-09 10:54 ` [Qemu-devel] [PATCH 0/2] block: drive_add/del without BlockBackend Kevin Wolf
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=56CF2658.7030709@redhat.com \
--to=eblake@redhat.com \
--cc=armbru@redhat.com \
--cc=berto@igalia.com \
--cc=kwolf@redhat.com \
--cc=mreitz@redhat.com \
--cc=qemu-block@nongnu.org \
--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.