From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from mailman by lists.gnu.org with tmda-scanned (Exim 4.43) id 1JwcSN-00012E-8N for qemu-devel@nongnu.org; Thu, 15 May 2008 08:21:11 -0400 Received: from exim by lists.gnu.org with spam-scanned (Exim 4.43) id 1JwcSI-00011n-R1 for qemu-devel@nongnu.org; Thu, 15 May 2008 08:21:09 -0400 Received: from [199.232.76.173] (port=52367 helo=monty-python.gnu.org) by lists.gnu.org with esmtp (Exim 4.43) id 1JwcSI-00011d-KZ for qemu-devel@nongnu.org; Thu, 15 May 2008 08:21:06 -0400 Received: from ecfrec.frec.bull.fr ([129.183.4.8]:47321) by monty-python.gnu.org with esmtp (Exim 4.60) (envelope-from ) id 1JwcSH-0000qz-Oz for qemu-devel@nongnu.org; Thu, 15 May 2008 08:21:06 -0400 Subject: Re: [kvm-devel] [Qemu-devel] Re: [PATCH] Add support for a configuration file From: Laurent Vivier In-Reply-To: <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> <482C26CA.8030702@qumranet.com> Content-Type: text/plain; charset=utf-8 Date: Thu, 15 May 2008 14:20:41 +0200 Message-Id: <1210854041.4298.11.camel@frecb07144> Mime-Version: 1.0 Content-Transfer-Encoding: quoted-printable Reply-To: qemu-devel@nongnu.org List-Id: qemu-devel.nongnu.org List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , To: qemu-devel@nongnu.org Cc: kvm-devel@lists.sourceforge.net, Paul Brook Le jeudi 15 mai 2008 =C3=A0 15:04 +0300, Avi Kivity a =C3=A9crit : > Daniel P. Berrange wrote: > > On Thu, May 15, 2008 at 11:04:47AM +0300, Avi Kivity wrote: > > =20 > >> Daniel P. Berrange wrote: > >> =20 > >>> 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. > >>> =20 > >>> =20 > >> I would hope that tools don't have to resort to reading and writing=20 > >> these config files. Usually a management system would prefer storin= g=20 > >> parameters in its own database, and writing a temporary config file = just=20 > >> to pass the data seems awkward. I would much prefer to see the comm= and=20 > >> line and monitor retain full control over every configurable paramet= er. > >> =20 > > > > 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 su= pport > > guests with > 16 disks, and > 8 network cards so command lines get ve= ry > > long.=20 > > =20 >=20 > What are those limits, btw? ISTR 10240 words, but how many chars? ARG_MAX - _SC_ARG_MAX The maximum length of the arguments to the exec(3) family of functions. Must not be less than _POSIX_ARG_MAX (4096). getconf ARG_MAX 131072 And from a configure log I have: checking the maximum length of command line arguments: 98304 Regards, Laurent --=20 ------------- Laurent.Vivier@bull.net --------------- "The best way to predict the future is to invent it." - Alan Kay