qemu-devel.nongnu.org archive mirror
 help / color / mirror / Atom feed
From: Anthony Liguori <anthony@codemonkey.ws>
To: "Jorge Lucángeli Obes" <t4m5yn@gmail.com>
Cc: kvm-devel@lists.sourceforge.net, qemu-devel@nongnu.org
Subject: [Qemu-devel] Re: [kvm-devel] [PATCH][RFC] Allowing QEMU to directly execute a directory (and storing command line options in it)
Date: Fri, 31 Aug 2007 14:13:29 -0500	[thread overview]
Message-ID: <1188587609.10527.0.camel@squirrel> (raw)
In-Reply-To: <59abf66e0708311205n6f6086d0g5d7c786ff2bef02b@mail.gmail.com>


On Fri, 2007-08-31 at 16:05 -0300, Jorge Lucángeli Obes wrote:
> On 8/31/07, Anthony Liguori <anthony@codemonkey.ws> wrote:
> > It makes little sense to pass a directory when you can pass a config
> > file and assume that the directory the config file is in is the CWD.
> >
> > For instance, if vm.cfg contained just the command line arguments, you
> > could have:
> >
> > MyImage/vm.cfg:        -hda disk0.qcow -m 512
> > MyImage/disk0.qcow:    <disk image>
> >
> > And then do:
> >
> > qemu -c MyImage/vm.cfg
> 
> I thought about this when coding, and it's true. Maybe we could just
> leave a new explicit config file option. I insist on making this as
> simple as possible, that's why I  chose to use the config file as a
> "written-down" command line.
> 
> If this were the case, we could remove the restriction of having the
> config file refer only to images on the same directory, as the use of
> the config file would be explicit. Thoughts?

Yes.  It should be a very simple patch.

Regards,

Anthony Liguori

> Cheers,
> Jorge

  reply	other threads:[~2007-08-31 19:13 UTC|newest]

Thread overview: 17+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-08-31 18:19 [Qemu-devel] [PATCH][RFC] Allowing QEMU to directly execute a directory (and storing command line options in it) Jorge Lucángeli Obes
2007-08-31 18:54 ` [Qemu-devel] Re: [kvm-devel] " Anthony Liguori
2007-08-31 19:05   ` Jorge Lucángeli Obes
2007-08-31 19:13     ` Anthony Liguori [this message]
2007-09-01 11:02   ` Markus Hitter
2007-09-01 14:26     ` Luke -Jr
2007-09-01 14:49       ` Andreas Färber
2007-09-01 14:39     ` Andreas Färber
2007-09-01 18:45       ` Jorge Lucángeli Obes
2007-09-01 19:52         ` Andreas Färber
2007-09-01 20:26           ` Jorge Lucángeli Obes
2007-09-03  9:19             ` Philip Boulain
2007-09-03 10:01               ` Christian Brunschen
2007-09-03 11:10                 ` Philip Boulain
2007-09-03 11:40                 ` Andreas Färber
2007-09-03 13:54                   ` Andreas Färber
2007-09-03 14:54               ` Luke -Jr

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=1188587609.10527.0.camel@squirrel \
    --to=anthony@codemonkey.ws \
    --cc=kvm-devel@lists.sourceforge.net \
    --cc=qemu-devel@nongnu.org \
    --cc=t4m5yn@gmail.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).