From: Anthony Liguori <anthony@codemonkey.ws>
To: qemu-devel@nongnu.org
Subject: Re: [Qemu-devel] [PATCH 4/4][RFC] Add logic to QEMU to read command line options from qcow2 images
Date: Sat, 11 Aug 2007 18:17:48 -0500 [thread overview]
Message-ID: <1186874268.11306.1.camel@squirrel> (raw)
In-Reply-To: <46BE29F9.9050904@ecs.soton.ac.uk>
On Sat, 2007-08-11 at 22:28 +0100, Philip Boulain wrote:
> > Yes, I think that another argument should be required as Dan suggested
> > although I'd like something more explicit like "-read-args-from-image".
> > In the case where the image was directly executable, it would be
> > embedded as part of the interpreter arguments.
>
> This works, so long as qemu disregards "-read-args-from-image" unless it's
> being called as an interpreter. Otherwise, you've put the lock and the key in
> the same place. :)
>
> If an image says:
> #!/whatever/qemu -read-args-from-image
> -curious-and-interesting-flags
>
> This should use those flags:
> $ ./image.qcow2
>
> And this shouldn't, because you don't need to have made it executable:
> $ qemu -hda image.qcow2
>
> (But this would:)
> $ qemu -read-args-from-image -hda image.qcow2
Yes. This is exactly what I think the behavior ought to be.
> (Side thought: presumably, we're assuming that the in-file and on-command-line
> arguments are unioned, ideally with the latter taking precidence if mutually
> exclusive.)
Yup, I was thinking the same thing too. Once the KVM wiki comes back
online I'll write something up on a wiki page.
Regards,
Anthony Liguori
> >> This also doesn't apply outside of UNIX-like environments, e.g.
> >> Windows...
> > I think this is covered by requiring the additional argument.
>
> Agreed.
>
> LionsPhil
>
>
next prev parent reply other threads:[~2007-08-11 23:18 UTC|newest]
Thread overview: 25+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <59abf66e0708081124g14901b01i841b70d17ae1e097@mail.gmail.com>
2007-08-08 19:52 ` [Qemu-devel] [PATCH 4/4][RFC] Add logic to QEMU to read command line options from qcow2 images Jorge Lucángeli Obes
2007-08-08 20:24 ` Daniel P. Berrange
2007-08-09 14:54 ` Anthony Liguori
2007-08-09 15:07 ` Daniel P. Berrange
2007-08-09 20:16 ` Avi Kivity
2007-08-09 20:25 ` Anthony Liguori
2007-08-09 20:30 ` Avi Kivity
2007-08-09 20:32 ` Anthony Liguori
2007-08-09 20:39 ` Avi Kivity
2007-08-09 20:44 ` Brian Wheeler
2007-08-09 20:49 ` Anthony Liguori
2007-08-10 3:51 ` dmc
2007-08-10 13:26 ` Carlos A. M. dos Santos
2007-08-09 20:55 ` Brian Wheeler
2007-08-10 0:48 ` Anthony Liguori
2007-08-11 17:11 ` andrzej zaborowski
2007-08-11 18:06 ` Philip Boulain
2007-08-11 19:08 ` Christian Brunschen
2007-08-11 19:53 ` Anthony Liguori
2007-08-11 19:52 ` Anthony Liguori
2007-08-11 21:28 ` Philip Boulain
2007-08-11 23:17 ` Anthony Liguori [this message]
2007-08-13 5:34 ` Jorge Lucángeli Obes
2007-08-13 15:15 ` [kvm-devel] " Anthony Liguori
2007-08-11 19:49 ` Anthony Liguori
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=1186874268.11306.1.camel@squirrel \
--to=anthony@codemonkey.ws \
--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).