From mboxrd@z Thu Jan 1 00:00:00 1970 From: Avi Kivity Subject: Re: [Qemu-devel] Re: [PATCH] Add support for a configuration file Date: Thu, 15 May 2008 15:04:26 +0300 Message-ID: <482C26CA.8030702@qumranet.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> <20080515115248.GA25607@redhat.com> Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit Cc: kvm-devel@lists.sourceforge.net, Paul Brook , Fabrice Bellard , qemu-devel@nongnu.org To: "Daniel P. Berrange" Return-path: In-Reply-To: <20080515115248.GA25607@redhat.com> List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Sender: kvm-devel-bounces@lists.sourceforge.net Errors-To: kvm-devel-bounces@lists.sourceforge.net List-Id: kvm.vger.kernel.org Daniel P. Berrange wrote: > 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. > What are those limits, btw? ISTR 10240 words, but how many chars? > 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. > That's fine from my point of view. -- error compiling committee.c: too many arguments to function ------------------------------------------------------------------------- This SF.net email is sponsored by: Microsoft Defy all challenges. Microsoft(R) Visual Studio 2008. http://clk.atdmt.com/MRT/go/vse0120000070mrt/direct/01/