From: Kevin Wolf <kwolf@redhat.com>
To: "Daniel P. Berrange" <berrange@redhat.com>
Cc: stefanha@redhat.com, qemu-devel@nongnu.org, qemu-block@nongnu.org
Subject: Re: [Qemu-devel] How to specify the full block driver tree on the CLI ?
Date: Thu, 29 Oct 2015 09:31:28 +0100 [thread overview]
Message-ID: <20151029083128.GB3854@noname.redhat.com> (raw)
In-Reply-To: <20151029081520.GB32623@redhat.com>
Am 29.10.2015 um 09:15 hat Daniel P. Berrange geschrieben:
> On Thu, Oct 29, 2015 at 09:11:15AM +0100, Kevin Wolf wrote:
> > In qemu proper, you can use a dot syntax for -drive instead:
> >
> > qemu-system-x86_64 -drive \
> > driver=luks,\
> > secret=x,\
> > file.driver=file,\
> > file.filename=test.luks
> >
> > In qemu-io, you can't use such syntax on the command line, but the open
> > command supports an -o option that accepts the same dot syntax.
> >
> > Note that qemu-img can't deal with this stuff yet, so you'll have
> > trouble creating an image with such a specification. I guess you need to
> > create it as a local file first and then use non-qemu tools to copy it
> > somewhere where it's exported by rbd, iscsi or gluster.
>
> I wonder if my patches to qemu-io & qemu-img here do the right thing to
> make this dot syntax work....
>
> https://lists.gnu.org/archive/html/qemu-devel/2015-10/msg04382.html
> https://lists.gnu.org/archive/html/qemu-devel/2015-10/msg04375.html
I haven't looked at the series in detail yet, but considering that it's
probably harder to prevent it from working than getting it, I assume
that your patches do allow it.
Just passing the options QDict to bdrv_open() is enough, nesting is
represented with the dot syntax in the keys there. In fact, if you use
blockdev-add in QMP, it first converts the options to a flattened QDict
with dot syntax for the keys before it processes it.
Kevin
prev parent reply other threads:[~2015-10-29 8:31 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-10-28 23:58 [Qemu-devel] How to specify the full block driver tree on the CLI ? Daniel P. Berrange
2015-10-29 8:11 ` Kevin Wolf
2015-10-29 8:15 ` Daniel P. Berrange
2015-10-29 8:31 ` Kevin Wolf [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=20151029083128.GB3854@noname.redhat.com \
--to=kwolf@redhat.com \
--cc=berrange@redhat.com \
--cc=qemu-block@nongnu.org \
--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).