All of lore.kernel.org
 help / color / mirror / Atom feed
From: "Daniel P. Berrange" <berrange@redhat.com>
To: Kevin Wolf <kwolf@redhat.com>
Cc: qemu-block@nongnu.org, qemu-devel@nongnu.org,
	"Markus Armbruster" <armbru@redhat.com>,
	"Paolo Bonzini" <pbonzini@redhat.com>,
	"Andreas Färber" <afaerber@suse.de>
Subject: Re: [Qemu-devel] [PATCH v4 05/10] qemu-io: allow specifying image as a set of options args
Date: Tue, 2 Feb 2016 10:13:32 +0000	[thread overview]
Message-ID: <20160202101332.GD18461@redhat.com> (raw)
In-Reply-To: <20160127142651.GC9484@noname.str.redhat.com>

On Wed, Jan 27, 2016 at 03:26:51PM +0100, Kevin Wolf wrote:
> Am 26.01.2016 um 14:34 hat Daniel P. Berrange geschrieben:
> > -    if ((argc - optind) == 1) {
> > +    if (imageOpts) {
> > +        char *file;
> > +        qopts = qemu_opts_parse_noisily(&file_opts, argv[optind], false);
> > +        if (!qopts) {
> > +            exit(1);
> > +        }
> > +        if (opts) {
> > +            error_report("--image-opts and -f are mutually exclusive");
> > +            exit(1);
> > +        }
> > +        file = g_strdup(qemu_opt_get(qopts, "file"));
> > +        qemu_opt_unset(qopts, "file");
> 
> I'm not sure if special casing "file" is a good idea. I think you're
> doing it in order to support something that looks like -drive, but it's
> not the same anyway - all of the options that are parsed in drive_new()
> or blockdev_init() aren't supported.
> 
> We could change things so that qemu-io actually goes through
> drive_new() or blockdev_init(), at the cost of forbidding node
> references for the "file" options like -drive unfortunately does. Or we
> can require that you use actual bdrv_open() options and specify
> file.filename=... for raw-posix.
> 
> But I would like to avoid creating a new type of option parsing with yet
> another behaviour.

Mostly this special casing of 'file' was based on my confusion /
misunderstanding of the recommended best API usage around bdrv_open.
I thought I was being compatible with -drive from the system emulators
by doing this, but you point out I'm not actually doing it properly.

Lets just keep this simple and use bdrv_open() options explicitly
since IIUC that looks like the "best practice" approach these days


Regards,
Daniel
-- 
|: http://berrange.com      -o-    http://www.flickr.com/photos/dberrange/ :|
|: http://libvirt.org              -o-             http://virt-manager.org :|
|: http://autobuild.org       -o-         http://search.cpan.org/~danberr/ :|
|: http://entangle-photo.org       -o-       http://live.gnome.org/gtk-vnc :|

  reply	other threads:[~2016-02-02 10:13 UTC|newest]

Thread overview: 19+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-01-26 13:34 [Qemu-devel] [PATCH v4 00/10] Make qemu-img/qemu-nbd/qemu-io CLI more flexible Daniel P. Berrange
2016-01-26 13:34 ` [Qemu-devel] [PATCH v4 01/10] qom: add helpers for UserCreatable object types Daniel P. Berrange
2016-01-26 13:34 ` [Qemu-devel] [PATCH v4 02/10] qemu-img: add support for --object command line arg Daniel P. Berrange
2016-01-27 13:26   ` Kevin Wolf
2016-02-02 10:45     ` Daniel P. Berrange
2016-01-26 13:34 ` [Qemu-devel] [PATCH v4 03/10] qemu-nbd: " Daniel P. Berrange
2016-01-27 13:57   ` Kevin Wolf
2016-02-02 11:40     ` Daniel P. Berrange
2016-01-26 13:34 ` [Qemu-devel] [PATCH v4 04/10] qemu-io: " Daniel P. Berrange
2016-01-26 13:34 ` [Qemu-devel] [PATCH v4 05/10] qemu-io: allow specifying image as a set of options args Daniel P. Berrange
2016-01-27 14:26   ` Kevin Wolf
2016-02-02 10:13     ` Daniel P. Berrange [this message]
2016-01-26 13:34 ` [Qemu-devel] [PATCH v4 06/10] qemu-nbd: " Daniel P. Berrange
2016-01-26 13:34 ` [Qemu-devel] [PATCH v4 07/10] qemu-img: " Daniel P. Berrange
2016-01-27 14:30   ` Kevin Wolf
2016-02-02 11:40     ` Daniel P. Berrange
2016-01-26 13:34 ` [Qemu-devel] [PATCH v4 08/10] qemu-nbd: don't overlap long option values with short options Daniel P. Berrange
2016-01-26 13:34 ` [Qemu-devel] [PATCH v4 09/10] qemu-nbd: use no_argument/required_argument constants Daniel P. Berrange
2016-01-26 13:34 ` [Qemu-devel] [PATCH v4 10/10] qemu-io: " Daniel P. Berrange

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=20160202101332.GD18461@redhat.com \
    --to=berrange@redhat.com \
    --cc=afaerber@suse.de \
    --cc=armbru@redhat.com \
    --cc=kwolf@redhat.com \
    --cc=pbonzini@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.