qemu-devel.nongnu.org archive mirror
 help / color / mirror / Atom feed
From: Anthony Liguori <anthony@codemonkey.ws>
To: laurent.vivier@bull.net
Cc: kvm-devel@lists.sourceforge.net,
	"Jorge Lucángeli Obes" <t4m5yn@gmail.com>,
	qemu-devel@nongnu.org
Subject: [Qemu-devel] Re: Réf. : Re: [kvm-devel] [PATCH][RFC] Allowing QEMU to directly executeadirectory (and storing command line 	options in it)
Date: Fri, 31 Aug 2007 19:19:37 -0500	[thread overview]
Message-ID: <1188605977.6270.3.camel@squirrel> (raw)
In-Reply-To: <OF5352114A.9C6CEEE4-ONC1257348.006F117A-C1257348.006F1248@frec.bull.fr>


On Fri, 2007-08-31 at 22:13 +0200, laurent.vivier@bull.net wrote:
> Hi Anthony,
> 
> I think passing only the directory name is better because it can be like a
> "black box" : the user don't have to know how it is inside. And it is much
> more simple to use "qemu my_pc" than "qemu -c my_pc/config".

You're overriding what "qemu my_pc" means.  "qemu my_pc" create a QEMU
vm with 128m of memory and -hda my_pc with the default network card.

"qemu -c my_pc/config" only has one meaning: read command line arguments
from "my_pc/config".

Your suggested syntax may be simpler for your particular use-case, but
it makes QEMU much more difficult to understand for every other user.

Regards,

Anthony Liguori

> Regards,
> Laurent
> 
> ------------------------------------------------------
>       Pour :      Jorge Lucángeli Obes <t4m5yn@gmail.com>
>       cc :  kvm-devel@lists.sourceforge.net, qemu-devel@nongnu.org
>       ccc :
>       Objet :     Re: [kvm-devel] [PATCH][RFC] Allowing QEMU to directly
> execute a directory (and storing command line options in it)
> Anthony Liguori <anthony@codemonkey.ws>
> Envoyé par : kvm-devel-bounces@lists.sourceforge.net
> 31/08/2007 13:54 EST
>             <font size=-1></font>
> 
> 
> 
> 
> 
> 
> 
> 
> 
> 
> 
> 
> 
> 
> 
> 
> 
> 
> 
> 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
> 
> 
> 
> 
> 
> 

  parent reply	other threads:[~2007-09-01  0:19 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-08-31 20:13 [Qemu-devel] Réf. : Re: [kvm-devel] [PATCH][RFC] Allowing QEMU to directly executeadirectory (and storing command line options in it) laurent.vivier
2007-08-31 21:09 ` Johannes Schindelin
2007-09-01 14:22   ` [kvm-devel] [Qemu-devel] Réf. : " Avi Kivity
2007-09-01 22:59     ` Johannes Schindelin
2007-09-01  0:19 ` Anthony Liguori [this message]
2007-09-01  5:44   ` [Qemu-devel] Re: Réf. : Re: [kvm-devel] " Luke -Jr
2007-09-01  8:05     ` pterjan
2007-09-03  9:12   ` Laurent Vivier
2007-09-01  0:52 ` [Qemu-devel] Re: [kvm-devel] Réf. : " 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=1188605977.6270.3.camel@squirrel \
    --to=anthony@codemonkey.ws \
    --cc=kvm-devel@lists.sourceforge.net \
    --cc=laurent.vivier@bull.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).