From: Eric Blake <eblake@redhat.com>
To: Jeff Cody <jcody@redhat.com>
Cc: kwolf@redhat.com, benoit.canet@irqsave.net, pkrempa@redhat.com,
famz@redhat.com, qemu-devel@nongnu.org, stefanha@redhat.com
Subject: Re: [Qemu-devel] [PATCH 5/5] block: extend block-commit to accept a string for the backing file
Date: Thu, 15 May 2014 12:52:25 -0600 [thread overview]
Message-ID: <53750CE9.3060607@redhat.com> (raw)
In-Reply-To: <20140515182203.GL8452@localhost.localdomain>
[-- Attachment #1: Type: text/plain, Size: 2315 bytes --]
On 05/15/2014 12:22 PM, Jeff Cody wrote:
>> Hmm - how will this be discoverable by libvirt? Maybe when libvirt is
>> doing the 'qemu -m none' probing, it can hotplug a device pointing to
>> /dev/null (libvirt _already_ does that to test if add-fd works), and
>> intentionally omit a node name. If libvirt then queries the device, and
>> sees that the __qemu##000NNNN node-name was auto-assigned, then it can
>> be assumed that this qemu is new enough to provide node-names for ALL
>> operations (but that means this series is incomplete unless we add
>> node-name support to all remaining block commands, such as block-stream,
>> drive-mirror, and drive-backup). This part is where I wonder if patch
>> 1/5 should be rebased to be last in the series.
>>
>
> Ah... I had originally planned on submitting separate patches for each
> of the block jobs, to make reviewing easier. But your idea on how
> libvirt can discover this is a good one, and would mandate changing
> those commands all in one series to be effective. So this series will
> grow by a few patches. :)
>
> If libvirt is going to use the autogenerated string format for
> decisions, we should also document the string format in the QAPI docs.
Adding a new command is much easier to probe for (a single
query-commands, which we are already using) than requiring a sequence of
operations (hotplug, then query to see if a name was assigned), and
probably even more direct (if the standalone command exists, then so
does the integrated use of setting backing names).
>>
>> In short, this new command option allows the equivalent of 'qemu-img
>> rebase -u' on a live image. Definitely a needed functionality.
>>
>
> Would it be useful to have a stand-alone QMP command to change the
> backing-file, as well? As this stands, it will only change the
> backing file if you are also merging data down the chain.
>
> If you want/need the ability to do a true 'qemu-img rebase -u' on any
> given image without other chain modification, that needs a new
> command.
Yes, I think that's probably a wise idea to provide a dedicated command
for just changing the name recorded in a backing file.
--
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 --]
prev parent reply other threads:[~2014-05-15 18:52 UTC|newest]
Thread overview: 35+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-05-15 3:20 [Qemu-devel] [PATCH 0/5] block: Modify block-commit to use node-names Jeff Cody
2014-05-15 3:20 ` [Qemu-devel] [PATCH 1/5] block: Auto-generate node_names for each BDS entry Jeff Cody
2014-05-15 11:58 ` Benoît Canet
2014-05-15 12:06 ` Jeff Cody
2014-05-15 12:32 ` Benoît Canet
2014-05-15 12:37 ` Jeff Cody
2014-05-15 14:11 ` Eric Blake
2014-05-15 15:59 ` Eric Blake
2014-05-15 18:41 ` Jeff Cody
2014-05-15 19:12 ` Eric Blake
2014-05-16 9:39 ` Kevin Wolf
2014-05-16 11:35 ` Jeff Cody
2014-05-16 12:47 ` Eric Blake
2014-05-16 17:16 ` Kevin Wolf
2014-05-15 3:20 ` [Qemu-devel] [PATCH 2/5] block: add helper function to determine if a BDS is in a chain Jeff Cody
2014-05-15 11:48 ` Benoît Canet
2014-05-15 14:16 ` Eric Blake
2014-05-15 14:24 ` Kevin Wolf
2014-05-15 14:31 ` Jeff Cody
2014-05-15 3:20 ` [Qemu-devel] [PATCH 3/5] block: make 'top' argument to block-commit optional Jeff Cody
2014-05-15 11:47 ` Benoît Canet
2014-05-15 11:49 ` Jeff Cody
2014-05-15 15:07 ` Eric Blake
2014-05-15 3:20 ` [Qemu-devel] [PATCH 4/5] block: Accept node-name arguments for block-commit Jeff Cody
2014-05-15 12:09 ` Benoît Canet
2014-05-15 15:42 ` Eric Blake
2014-05-15 18:04 ` Jeff Cody
2014-05-15 3:20 ` [Qemu-devel] [PATCH 5/5] block: extend block-commit to accept a string for the backing file Jeff Cody
2014-05-15 12:26 ` Benoît Canet
2014-05-15 12:57 ` Eric Blake
2014-05-15 13:10 ` Jeff Cody
2014-05-15 13:14 ` Eric Blake
2014-05-15 16:06 ` Eric Blake
2014-05-15 18:22 ` Jeff Cody
2014-05-15 18:52 ` Eric Blake [this message]
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=53750CE9.3060607@redhat.com \
--to=eblake@redhat.com \
--cc=benoit.canet@irqsave.net \
--cc=famz@redhat.com \
--cc=jcody@redhat.com \
--cc=kwolf@redhat.com \
--cc=pkrempa@redhat.com \
--cc=qemu-devel@nongnu.org \
--cc=stefanha@redhat.com \
/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.