From: Eric Blake <eblake@redhat.com>
To: "Benoît Canet" <benoit.canet@irqsave.net>,
"Jeff Cody" <jcody@redhat.com>
Cc: kwolf@redhat.com, pkrempa@redhat.com, famz@redhat.com,
qemu-devel@nongnu.org, stefanha@redhat.com
Subject: Re: [Qemu-devel] [PATCH v5 01/10] block: Auto-generate node_names for each BDS entry
Date: Mon, 16 Jun 2014 08:15:54 -0600 [thread overview]
Message-ID: <539EFC1A.2040701@redhat.com> (raw)
In-Reply-To: <20140616141041.GA12177@irqsave.net>
[-- Attachment #1: Type: text/plain, Size: 1140 bytes --]
On 06/16/2014 08:10 AM, Benoît Canet wrote:
>> The prefix is to aid in identifying it as a qemu-generated name, the
>> numeric portion is to guarantee uniqueness in a given qemu session, and
>> the random characters are to further avoid any accidental collisions
>> with user-specified node-names.
>
> if the __qemu## determined a different name space no collision resolution would be
> needed.
>
> Also Eric you must take care that these node name does not ends up in libvirt
> XML since a new qemu process can generate a new different set of node name.
Correct. Either libvirt will always generate its own node names (and the
presence of a qemu-generated name is a bug in libvirt), or libvirt will
query node-names as it runs, and clear them out when the qemu process
goes away. It will NOT expose qemu names to user-visible XML (although
it should be safe to save the qemu names to internal-only XML used to
cache results across libvirtd restarts while still communicating to the
same qemu process).
--
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:[~2014-06-16 14:16 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-06-13 18:52 [Qemu-devel] [PATCH v5 00/10] Modify block jobs to use node-names Jeff Cody
2014-06-13 18:52 ` [Qemu-devel] [PATCH v5 01/10] block: Auto-generate node_names for each BDS entry Jeff Cody
2014-06-16 14:10 ` Benoît Canet
2014-06-16 14:15 ` Eric Blake [this message]
2014-06-16 14:18 ` Jeff Cody
2014-06-13 18:52 ` [Qemu-devel] [PATCH v5 02/10] block: add helper function to determine if a BDS is in a chain Jeff Cody
2014-06-13 18:52 ` [Qemu-devel] [PATCH v5 03/10] block: simplify bdrv_find_base() and bdrv_find_overlay() Jeff Cody
2014-06-16 14:25 ` Benoît Canet
2014-06-13 18:52 ` [Qemu-devel] [PATCH v5 04/10] block: make 'top' argument to block-commit optional Jeff Cody
2014-06-13 18:52 ` [Qemu-devel] [PATCH v5 05/10] block: Accept node-name arguments for block-commit Jeff Cody
2014-06-17 12:28 ` Eric Blake
2014-06-13 18:52 ` [Qemu-devel] [PATCH v5 06/10] block: extend block-commit to accept a string for the backing file Jeff Cody
2014-06-13 18:52 ` [Qemu-devel] [PATCH v5 07/10] block: add ability for block-stream to use node-name Jeff Cody
2014-06-13 18:52 ` [Qemu-devel] [PATCH v5 08/10] block: add backing-file option to block-stream Jeff Cody
2014-06-13 18:52 ` [Qemu-devel] [PATCH v5 09/10] block: Add QMP documentation for block-stream Jeff Cody
2014-06-16 14:29 ` Benoît Canet
2014-06-13 18:52 ` [Qemu-devel] [PATCH v5 10/10] block: add QAPI command to allow live backing file change Jeff Cody
2014-06-17 12:19 ` [Qemu-devel] [PATCH v5 00/10] Modify block jobs to use node-names Eric Blake
2014-06-17 12:25 ` Jeff Cody
2014-06-17 21:57 ` Jeff Cody
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=539EFC1A.2040701@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).