From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from mailman by lists.gnu.org with tmda-scanned (Exim 4.43) id 1Jwc46-0004AX-W9 for qemu-devel@nongnu.org; Thu, 15 May 2008 07:56:07 -0400 Received: from exim by lists.gnu.org with spam-scanned (Exim 4.43) id 1Jwc42-000447-DP for qemu-devel@nongnu.org; Thu, 15 May 2008 07:56:06 -0400 Received: from [199.232.76.173] (port=55735 helo=monty-python.gnu.org) by lists.gnu.org with esmtp (Exim 4.43) id 1Jwc42-00043m-AP for qemu-devel@nongnu.org; Thu, 15 May 2008 07:56:02 -0400 Received: from mx1.redhat.com ([66.187.233.31]:33044) by monty-python.gnu.org with esmtp (Exim 4.60) (envelope-from ) id 1Jwc41-0003Z2-8U for qemu-devel@nongnu.org; Thu, 15 May 2008 07:56:01 -0400 Date: Thu, 15 May 2008 12:52:48 +0100 From: "Daniel P. Berrange" Subject: Re: [kvm-devel] [Qemu-devel] Re: [PATCH] Add support for a configuration file Message-ID: <20080515115248.GA25607@redhat.com> References: <1210713545-11916-1-git-send-email-aliguori@us.ibm.com> <482A1F1C.2020902@codemonkey.ws> <482AA268.9080501@bellard.org> <482ABF6E.6090100@qumranet.com> <482ADA80.3000309@bellard.org> <20080514133158.GB15783@redhat.com> <482BEE9F.3010700@qumranet.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <482BEE9F.3010700@qumranet.com> Reply-To: "Daniel P. Berrange" , qemu-devel@nongnu.org List-Id: qemu-devel.nongnu.org List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , To: Avi Kivity Cc: kvm-devel@lists.sourceforge.net, Paul Brook , qemu-devel@nongnu.org On Thu, May 15, 2008 at 11:04:47AM +0300, Avi Kivity wrote: > Daniel P. Berrange wrote: > >With this kind of syntax, now tools generating config files need to make > >up unique names for each drive. So you'll probably end up with them just > >naming things based on the class name + a number appended. > > > > I would hope that tools don't have to resort to reading and writing > these config files. Usually a management system would prefer storing > parameters in its own database, and writing a temporary config file just > to pass the data seems awkward. I would much prefer to see the command > line and monitor retain full control over every configurable parameter. I expect that libvirt will create config files - it is only a matter of time before we hit the command line ARGV length limits - particularly with the -net and -drive syntax. People already requesting that we support guests with > 16 disks, and > 8 network cards so command lines get very long. I wouldn't write out the config file to disk though - I'd just send it on the fly on stdin -, eg 'qemu -config -' to tell it to read the config on its stdin. Regards, Daniel. -- |: Red Hat, Engineering, Boston -o- http://people.redhat.com/berrange/ :| |: http://libvirt.org -o- http://virt-manager.org -o- http://ovirt.org :| |: http://autobuild.org -o- http://search.cpan.org/~danberr/ :| |: GnuPG: 7D3B9505 -o- F3C9 553F A1DA 4AC2 5648 23C1 B3DF F742 7D3B 9505 :|