From mboxrd@z Thu Jan 1 00:00:00 1970 From: Avi Kivity Subject: Re: [Qemu-devel] Re: Storing command line options in images Date: Fri, 10 Aug 2007 22:41:39 +0300 Message-ID: <46BCBF73.5060406@qumranet.com> References: <59abf66e0708092155t2e3cd5o32f23c018bed65af@mail.gmail.com> <46BC8C18.6020108@codemonkey.ws> <46BC9CDB.3080900@qumranet.com> <46BCB1DA.6060102@codemonkey.ws> Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit Cc: kvm-devel-5NWGOfrQmneRv+LV9MX5uipxlwaOVQ5f@public.gmane.org, qemu-devel-qX2TKyscuCcdnm+yROfE0A@public.gmane.org To: Anthony Liguori Return-path: In-Reply-To: <46BCB1DA.6060102-rdkfGonbjUSkNkDKm+mE6A@public.gmane.org> List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Sender: kvm-devel-bounces-5NWGOfrQmneRv+LV9MX5uipxlwaOVQ5f@public.gmane.org Errors-To: kvm-devel-bounces-5NWGOfrQmneRv+LV9MX5uipxlwaOVQ5f@public.gmane.org List-Id: kvm.vger.kernel.org Anthony Liguori wrote: > Avi Kivity wrote: >>> This is a big effort but a config file is the right long term solution. >>> >>> >> >> For which use case? management-full or management-less? >> > > Both. A config file will be useful not just for expressing the > functionality we have today, but also for describing the guest's > environment in greater detail. For instance, if you want to support a > bunch of different kinds of embedded systems, it would be very nice if > the machine description was a config file instead of hard coded such > that it was easy to tweak what hardware was present for the particular > embedded system. > Maybe I'm dense today. Which use case is this? >> A managed system will want to supply arguments out of a central >> database. For a management-less use case, the config file is a hassle. >> > > As long as all options are still settable via command line (or stdio), > then it's not at all a hassle. > Yes. But if you don't plan to use it, why implement it? My feeling is that config files are outdated. When used with a gui, you end up writing silly parsers and stuff and still wrecking things horribly when the the gui writer's expectations don't match reality. When used without a gui, they increase the amount of details one has to remember (where's that config file? I renamed my image, did I remember to update the config file?). They also make upgrading more difficult. ------------------------------------------------------------------------- This SF.net email is sponsored by: Splunk Inc. Still grepping through log files to find problems? Stop. Now Search log events and configuration files using AJAX and a browser. Download your FREE copy of Splunk now >> http://get.splunk.com/