From mboxrd@z Thu Jan  1 00:00:00 1970
Received: from mailman by lists.gnu.org with tmda-scanned (Exim 4.43)
	id 1HNZpd-00045S-VB
	for qemu-devel@nongnu.org; Sat, 03 Mar 2007 14:23:49 -0500
Received: from exim by lists.gnu.org with spam-scanned (Exim 4.43)
	id 1HNZpc-000444-3r
	for qemu-devel@nongnu.org; Sat, 03 Mar 2007 14:23:49 -0500
Received: from [199.232.76.173] (helo=monty-python.gnu.org)
	by lists.gnu.org with esmtp (Exim 4.43) id 1HNZpb-00043w-T9
	for qemu-devel@nongnu.org; Sat, 03 Mar 2007 14:23:47 -0500
Received: from mis011-2.exch011.intermedia.net ([64.78.21.129])
	by monty-python.gnu.org with esmtp (Exim 4.52) id 1HNZpb-00082x-HD
	for qemu-devel@nongnu.org; Sat, 03 Mar 2007 14:23:47 -0500
Message-ID: <45E9C605.2090301@qumranet.com>
Date: Sat, 03 Mar 2007 21:01:25 +0200
From: Avi Kivity <avi@qumranet.com>
MIME-Version: 1.0
Subject: Re: [Qemu-devel] QEMU/pc and scsi disks
References: <45E70CCF.40800@bull.net>	<45E7E20A.8020704@bull.net>	<20070302110232.GC27636@networkno.de>	<200703021542.43161.paul@codesourcery.com>
	<45E84FB5.2020600@codemonkey.ws>
In-Reply-To: <45E84FB5.2020600@codemonkey.ws>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
Reply-To: qemu-devel@nongnu.org
List-Id: qemu-devel.nongnu.org
List-Unsubscribe: <http://lists.nongnu.org/mailman/listinfo/qemu-devel>,
	<mailto:qemu-devel-request@nongnu.org?subject=unsubscribe>
List-Archive: <http://lists.gnu.org/pipermail/qemu-devel>
List-Post: <mailto:qemu-devel@nongnu.org>
List-Help: <mailto:qemu-devel-request@nongnu.org?subject=help>
List-Subscribe: <http://lists.nongnu.org/mailman/listinfo/qemu-devel>,
	<mailto:qemu-devel-request@nongnu.org?subject=subscribe>
To: qemu-devel@nongnu.org
Cc: Laurent Vivier <Laurent.Vivier@bull.net>, Paul Brook <paul@codesourcery.com>

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.