From mboxrd@z Thu Jan  1 00:00:00 1970
Received: from mailman by lists.gnu.org with tmda-scanned (Exim 4.43)
	id 1HNdo5-00053V-2H
	for qemu-devel@nongnu.org; Sat, 03 Mar 2007 18:38:29 -0500
Received: from exim by lists.gnu.org with spam-scanned (Exim 4.43)
	id 1HNdo2-00053E-Kw
	for qemu-devel@nongnu.org; Sat, 03 Mar 2007 18:38:27 -0500
Received: from [199.232.76.173] (helo=monty-python.gnu.org)
	by lists.gnu.org with esmtp (Exim 4.43) id 1HNdo2-00053B-F3
	for qemu-devel@nongnu.org; Sat, 03 Mar 2007 18:38:26 -0500
Received: from wx-out-0506.google.com ([66.249.82.229])
	by monty-python.gnu.org with esmtp (Exim 4.52) id 1HNdo2-0002cY-5U
	for qemu-devel@nongnu.org; Sat, 03 Mar 2007 18:38:26 -0500
Received: by wx-out-0506.google.com with SMTP id i30so1833206wxd
	for <qemu-devel@nongnu.org>; Sat, 03 Mar 2007 15:38:25 -0800 (PST)
Message-ID: <45EA06EE.3000509@codemonkey.ws>
Date: Sat, 03 Mar 2007 17:38:22 -0600
From: Anthony Liguori <anthony@codemonkey.ws>
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>
	<45E9C605.2090301@qumranet.com>
In-Reply-To: <45E9C605.2090301@qumranet.com>
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

Avi Kivity wrote:
> 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>.

I think we should still provide the ability to set the most common 
options via the command line.  I'm also fine with specifying single 
options on the command line.  I suspect though that being able to do 
-config - is more useful for management tools than building large 
strings of command line options.

> 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}.

Yeah, I've never liked their printf syntax.  I was interested in 
interpolation, the syntax really doesn't matter to me.  sh is probably a 
bit easier on the eyes.

> 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.

Yeah, definitely.

Regards,

Anthony Liguor