From: Eric Blake <eblake@redhat.com>
To: Corey Bryant <bryntcor@us.ibm.com>
Cc: libvir-list@redhat.com, Anthony Liguori <aliguori@us.ibm.com>,
qemu-devel@nongnu.org, Tyler C Hicks <tchicks@us.ibm.com>
Subject: Re: [Qemu-devel] [libvirt] [PATCH v2] Add support for fd: protocol
Date: Tue, 14 Jun 2011 15:52:51 -0600 [thread overview]
Message-ID: <4DF7D833.7090306@redhat.com> (raw)
In-Reply-To: <4DF7D512.5010909@us.ibm.com>
[-- Attachment #1: Type: text/plain, Size: 1095 bytes --]
On 06/14/2011 03:39 PM, Corey Bryant wrote:
>> Incremental support is fine by me, but we'll need it sooner or later.
>
> Qemu currently opens the specified copy-on-write file, finds a backing
> file name in the opened file's header, opens that backing file, and
> repeats.
>
> So it seems that either a backingN= would be needed or a way to map a
> file descriptor to the file name in the header.
>
> I think the latter is along the lines of what was discussed here with
> -blockdev:
> http://lists.gnu.org/archive/html/qemu-devel/2011-05/msg02417.html
>
> Repeating the syntax specified in that thread, you'd have:
>
> -blockdev id=foo-base,path=fd:4,format=raw
> -blockdev id=foo,path=fd:3,format=qcow2,backing_file=foo-base
>
> where id is the file name. This chains the backing files on the command
> line.
I like it. It scales as deep as we want by adding as many additional
-blockdev entries prior to the -drive that uses the nested -blockdevs.
--
Eric Blake eblake@redhat.com +1-801-349-2682
Libvirt virtualization library http://libvirt.org
[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 619 bytes --]
next prev parent reply other threads:[~2011-06-14 21:53 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-06-14 13:31 [Qemu-devel] [PATCH v2] Add support for fd: protocol Corey Bryant
2011-06-14 16:13 ` [Qemu-devel] [libvirt] " Eric Blake
2011-06-14 19:55 ` Corey Bryant
2011-06-14 20:18 ` Eric Blake
2011-06-14 21:39 ` Corey Bryant
2011-06-14 21:52 ` Eric Blake [this message]
2011-06-15 19:12 ` [Qemu-devel] " Blue Swirl
2011-06-16 14:48 ` Corey Bryant
2011-06-18 20:50 ` Blue Swirl
2011-06-20 13:08 ` Corey Bryant
2011-06-20 13:40 ` Avi Kivity
2011-06-20 13:50 ` Anthony Liguori
2011-06-20 17:35 ` Avi Kivity
2011-06-20 19:11 ` Anthony Liguori
2011-06-21 8:21 ` Avi Kivity
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=4DF7D833.7090306@redhat.com \
--to=eblake@redhat.com \
--cc=aliguori@us.ibm.com \
--cc=bryntcor@us.ibm.com \
--cc=libvir-list@redhat.com \
--cc=qemu-devel@nongnu.org \
--cc=tchicks@us.ibm.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).