qemu-devel.nongnu.org archive mirror
 help / color / mirror / Atom feed
From: "Daniel P. Berrange" <berrange@redhat.com>
To: laurent.vivier@bull.net
Cc: kvm-devel@lists.sourceforge.net, qemu-devel@nongnu.org
Subject: [Qemu-devel] Re: [kvm-devel] Réf. : Re:  [PATCH][RFC] Allowing QEMU  to directly executeadirectory (and storing command line options in it)
Date: Sat, 1 Sep 2007 01:52:12 +0100	[thread overview]
Message-ID: <20070901005212.GA13901@redhat.com> (raw)
In-Reply-To: <OF5352114A.9C6CEEE4-ONC1257348.006F117A-C1257348.006F1248@frec.bull.fr>

On Fri, Aug 31, 2007 at 10:13:11PM +0200, laurent.vivier@bull.net wrote:
> 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".

If you need this incredible 'simplicity', a 1 line shell script can easily
provide it for you;

    $ cat myqemu
    #!/bin/sh
    exec qemu -c $1/config

One of the great strengths of QEMU is its predictability - it may have a
huge number of command line args, but this is exactly what gives QEMU such
power & utility. It makes it very straightforward to build applications
around QEMU, and ensure it behaviours in a 100% reliable & predictable manner.
We should be wary of putting policy & heuristics into QEMU to turn it into
a 'black box' because that will compromise the use cases at which it currently
excels. A simple '-c' arg which takes a path to a config file is more than
sufficient, without needing heuristics to look for magical named files in
directories.

Dan.
-- 
|=- Red Hat, Engineering, Emerging Technologies, Boston.  +1 978 392 2496 -=|
|=-           Perl modules: http://search.cpan.org/~danberr/              -=|
|=-               Projects: http://freshmeat.net/~danielpb/               -=|
|=-  GnuPG: 7D3B9505   F3C9 553F A1DA 4AC2 5648 23C1 B3DF F742 7D3B 9505  -=| 

      parent reply	other threads:[~2007-09-01  0:52 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 ` [Qemu-devel] Re: Réf. : Re: [kvm-devel] " Anthony Liguori
2007-09-01  5:44   ` Luke -Jr
2007-09-01  8:05     ` pterjan
2007-09-03  9:12   ` Laurent Vivier
2007-09-01  0:52 ` Daniel P. Berrange [this message]

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=20070901005212.GA13901@redhat.com \
    --to=berrange@redhat.com \
    --cc=kvm-devel@lists.sourceforge.net \
    --cc=laurent.vivier@bull.net \
    --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).