From: Avi Kivity <avi@qumranet.com>
To: qemu-devel@nongnu.org
Cc: Laurent Vivier <Laurent.Vivier@bull.net>,
Paul Brook <paul@codesourcery.com>
Subject: Re: [Qemu-devel] QEMU/pc and scsi disks
Date: Sat, 03 Mar 2007 21:01:25 +0200 [thread overview]
Message-ID: <45E9C605.2090301@qumranet.com> (raw)
In-Reply-To: <45E84FB5.2020600@codemonkey.ws>
Anthony Liguori wrote:
>
> I think most people agree that we need a config file. I haven't seen
> any comments on my config file patch though.
>
> So, any comments on that patch? Any requirements on a format?
>
1. Any option should be settable either in the config file or command
line. In other words, the user should not be forced to use a config
file. This is useful for management programs who keep all options in an
internal database, and for users who can experiment via a ^P edit edit
edit <enter>.
2. The %(blah)s syntax is a bit ugly. It's one of the few things in
python I dislike. I'd prefer ${blah} and ${blah:modifier}.
3. It would be nice to be able to embed a config file in a qcow3 format
so that one can ship an image with some default options in one file.
--
Do not meddle in the internals of kernels, for they are subtle and quick to panic.
next prev parent reply other threads:[~2007-03-03 19:23 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-03-01 17:26 [Qemu-devel] QEMU/pc and scsi disks Laurent Vivier
2007-03-01 17:36 ` Paul Brook
2007-03-02 8:36 ` Laurent Vivier
2007-03-02 11:02 ` Thiemo Seufer
2007-03-02 15:42 ` Paul Brook
2007-03-02 16:24 ` Anthony Liguori
2007-03-02 16:45 ` Joe Batt
2007-03-25 17:05 ` Anthony Liguori
2007-03-25 20:38 ` Thiemo Seufer
2007-03-03 19:01 ` Avi Kivity [this message]
2007-03-03 23:38 ` Anthony Liguori
2007-03-04 9:28 ` Avi Kivity
2007-03-04 11:43 ` Paul Brook
2007-03-04 11:48 ` Avi Kivity
2007-03-04 12:05 ` Paul Brook
2007-03-04 13:44 ` Chris Wilson
2007-03-04 17:50 ` Avi Kivity
2007-03-04 17:06 ` Anthony Liguori
2007-03-06 17:59 ` Joseph Miller
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=45E9C605.2090301@qumranet.com \
--to=avi@qumranet.com \
--cc=Laurent.Vivier@bull.net \
--cc=paul@codesourcery.com \
--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).