From: Fam Zheng <famz@redhat.com>
To: "Daniel P. Berrange" <berrange@redhat.com>
Cc: qemu-devel@nongnu.org, Kevin Wolf <kwolf@redhat.com>,
qemu-block@nongnu.org, Max Reitz <mreitz@redhat.com>
Subject: Re: [Qemu-devel] [PATCH v1 2/6] qemu-img: fix --image-opts usage with dd command
Date: Thu, 26 Jan 2017 20:28:24 +0800 [thread overview]
Message-ID: <20170126122824.GA23095@lemon.Home> (raw)
In-Reply-To: <20170126110435.2777-3-berrange@redhat.com>
On Thu, 01/26 11:04, Daniel P. Berrange wrote:
> The --image-opts flag can only be used to affect the parsing
> of the source image. The target image has to be specified in
> the traditional style regardless, since it needs to be passed
> to the brdv_create() API which does not support the new style
"bdrv_create", if you respin :)
> opts.
>
> Signed-off-by: Daniel P. Berrange <berrange@redhat.com>
> ---
> qemu-img.c | 9 +++++++--
> 1 file changed, 7 insertions(+), 2 deletions(-)
>
> diff --git a/qemu-img.c b/qemu-img.c
> index 391a141..629f9e9 100644
> --- a/qemu-img.c
> +++ b/qemu-img.c
> @@ -4098,8 +4098,13 @@ static int img_dd(int argc, char **argv)
> goto out;
> }
>
> - blk2 = img_open(image_opts, out.filename, out_fmt, BDRV_O_RDWR,
> - false, false);
> + /* TODO, we can't honour --image-opts for the target,
> + * since it needs to be given in a format compatible
> + * with the bdrv_create() call above which does not
> + * support image-opts style.
> + */
> + blk2 = img_open_file(out.filename, out_fmt, BDRV_O_RDWR,
> + false, false);
>
> if (!blk2) {
> ret = -1;
> --
> 2.9.3
>
>
next prev parent reply other threads:[~2017-01-26 12:28 UTC|newest]
Thread overview: 28+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-01-26 11:04 [Qemu-devel] [PATCH v1 0/6] qemu-img: improve convert & dd commands Daniel P. Berrange
2017-01-26 11:04 ` [Qemu-devel] [PATCH v1 1/6] qemu-img: add support for --object with 'dd' command Daniel P. Berrange
2017-01-30 16:48 ` Eric Blake
2017-01-26 11:04 ` [Qemu-devel] [PATCH v1 2/6] qemu-img: fix --image-opts usage with dd command Daniel P. Berrange
2017-01-26 12:28 ` Fam Zheng [this message]
2017-01-26 11:04 ` [Qemu-devel] [PATCH v1 3/6] qemu-img: add support for -n arg to " Daniel P. Berrange
2017-01-26 12:35 ` Fam Zheng
2017-01-26 13:27 ` Daniel P. Berrange
2017-01-28 11:55 ` Fam Zheng
2017-01-30 18:37 ` Eric Blake
2017-02-01 12:13 ` Max Reitz
2017-02-01 12:16 ` Daniel P. Berrange
2017-02-01 12:23 ` Max Reitz
2017-02-01 12:28 ` Daniel P. Berrange
2017-02-01 12:31 ` Max Reitz
2017-02-01 12:40 ` Daniel P. Berrange
2017-02-01 12:50 ` Max Reitz
2017-02-02 7:36 ` Markus Armbruster
2017-02-02 7:32 ` Markus Armbruster
2017-02-03 18:56 ` Max Reitz
2017-02-06 10:31 ` Daniel P. Berrange
2017-02-07 22:15 ` Max Reitz
2017-02-08 9:19 ` Markus Armbruster
2017-02-08 13:16 ` Max Reitz
2017-01-26 11:04 ` [Qemu-devel] [PATCH v1 4/6] qemu-img: add support for -o " Daniel P. Berrange
2017-01-26 11:04 ` [Qemu-devel] [PATCH v1 5/6] qemu-img: introduce --target-image-opts for 'convert' command Daniel P. Berrange
2017-01-26 11:04 ` [Qemu-devel] [PATCH v1 6/6] qemu-img: copy *key-secret opts when opening newly created files Daniel P. Berrange
2017-01-30 18:39 ` Eric Blake
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=20170126122824.GA23095@lemon.Home \
--to=famz@redhat.com \
--cc=berrange@redhat.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 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).