From: Paolo Bonzini <pbonzini@redhat.com>
To: Luiz Capitulino <lcapitulino@redhat.com>
Cc: kwolf@redhat.com, qemu-devel@nongnu.org, armbru@redhat.com
Subject: Re: [Qemu-devel] [RFC 3/7] block: bdrv_img_create(): move param printing to qemu-img
Date: Fri, 12 Oct 2012 10:29:37 +0200 [thread overview]
Message-ID: <5077D4F1.2030704@redhat.com> (raw)
In-Reply-To: <1349990825-2659-4-git-send-email-lcapitulino@redhat.com>
Il 11/10/2012 23:27, Luiz Capitulino ha scritto:
> bdrv_img_create() is being used by the transaction QMP command and
> therefore shouldn't print directly to the user.
>
> Move the param printing to qemu-img instead. Has the side effect of
> only printing it when the bdrv_img_create() call succeeds, otherwise
> we can print errors before the action being taken, eg:
>
> ~/work/virt/ ./qemu-img create -f qcow2 /foo/foo 10G
> qemu-img: /foo/foo: error while creating qcow2: No such file or directory
> Formatting '/foo/foo', fmt=qcow2 size=10737418240 encryption=off cluster_size=65536 lazy_refcounts=off
It is a small regression with -monitor stdio (and also with QMP it
doesn't appear anymore in the logs). Do we care? What alternatives
exist besides writing a QAPI key-value store and converting the output
QEMUOptionParameters to it (which I'm not suggesting to do)?
Paolo
> Signed-off-by: Luiz Capitulino <lcapitulino@redhat.com>
> ---
> block.c | 4 ----
> qemu-img.c | 10 +++++++++-
> 2 files changed, 9 insertions(+), 5 deletions(-)
>
> diff --git a/block.c b/block.c
> index 13cf04d..235423e 100644
> --- a/block.c
> +++ b/block.c
> @@ -4411,10 +4411,6 @@ int bdrv_img_create(const char *filename, const char *fmt,
> }
> }
>
> - printf("Formatting '%s', fmt=%s ", filename, fmt);
> - print_option_parameters(param);
> - puts("");
> -
> ret = bdrv_create(drv, filename, param);
>
> if (ret < 0) {
> diff --git a/qemu-img.c b/qemu-img.c
> index b841012..ac66459 100644
> --- a/qemu-img.c
> +++ b/qemu-img.c
> @@ -301,6 +301,7 @@ static int img_create(int argc, char **argv)
> const char *filename;
> const char *base_filename = NULL;
> char *options = NULL;
> + QEMUOptionParameter *params = NULL;
>
> for(;;) {
> c = getopt(argc, argv, "F:b:f:he6o:");
> @@ -362,7 +363,14 @@ static int img_create(int argc, char **argv)
> }
>
> ret = bdrv_img_create(filename, fmt, base_filename, base_fmt,
> - options, img_size, BDRV_O_FLAGS, NULL);
> + options, img_size, BDRV_O_FLAGS, ¶ms);
> + if (ret == 0 && params) {
> + printf("Formatting '%s', fmt=%s ", filename, fmt);
> + print_option_parameters(params);
> + free_option_parameters(params);
> + puts("");
> + }
> +
> out:
> if (ret) {
> return 1;
>
next prev parent reply other threads:[~2012-10-12 8:29 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-10-11 21:26 [Qemu-devel] [RFC 0/7] block: bdrv_img_create(): propagate errors Luiz Capitulino
2012-10-11 21:26 ` [Qemu-devel] [RFC 1/7] error: add error_set_errno and error_setg_errno Luiz Capitulino
2012-10-11 21:27 ` [Qemu-devel] [RFC 2/7] block: bdrv_img_create(): add param_ret argument Luiz Capitulino
2012-10-11 21:27 ` [Qemu-devel] [RFC 3/7] block: bdrv_img_create(): move param printing to qemu-img Luiz Capitulino
2012-10-12 8:29 ` Paolo Bonzini [this message]
2012-10-15 21:39 ` Luiz Capitulino
2012-10-11 21:27 ` [Qemu-devel] [RFC 4/7] block: bdrv_img_create(): add Error ** argument Luiz Capitulino
2012-10-11 21:27 ` [Qemu-devel] [RFC 5/7] qemu-img: img_create(): use Error object Luiz Capitulino
2012-10-11 21:27 ` [Qemu-devel] [RFC 6/7] qmp: qmp_transaction(): pass Error object to bdrv_img_create() Luiz Capitulino
2012-10-11 21:27 ` [Qemu-devel] [RFC 7/7] block: bdrv_img_create(): drop unused code Luiz Capitulino
2012-10-12 8:31 ` [Qemu-devel] [RFC 0/7] block: bdrv_img_create(): propagate errors Paolo Bonzini
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=5077D4F1.2030704@redhat.com \
--to=pbonzini@redhat.com \
--cc=armbru@redhat.com \
--cc=kwolf@redhat.com \
--cc=lcapitulino@redhat.com \
--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).