From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from mailman by lists.gnu.org with tmda-scanned (Exim 4.43) id 1IRXyA-0006mB-D0 for qemu-devel@nongnu.org; Sat, 01 Sep 2007 14:45:18 -0400 Received: from exim by lists.gnu.org with spam-scanned (Exim 4.43) id 1IRXy8-0006ky-Tz for qemu-devel@nongnu.org; Sat, 01 Sep 2007 14:45:18 -0400 Received: from [199.232.76.173] (helo=monty-python.gnu.org) by lists.gnu.org with esmtp (Exim 4.43) id 1IRXy8-0006kj-Qm for qemu-devel@nongnu.org; Sat, 01 Sep 2007 14:45:16 -0400 Received: from wa-out-1112.google.com ([209.85.146.177]) by monty-python.gnu.org with esmtp (Exim 4.60) (envelope-from ) id 1IRXy8-0003CA-8h for qemu-devel@nongnu.org; Sat, 01 Sep 2007 14:45:16 -0400 Received: by wa-out-1112.google.com with SMTP id k22so1440152waf for ; Sat, 01 Sep 2007 11:45:13 -0700 (PDT) Message-ID: <59abf66e0709011145o20aae4fft5169bfb80e529bb2@mail.gmail.com> Date: Sat, 1 Sep 2007 15:45:13 -0300 From: "=?ISO-8859-1?Q?Jorge_Luc=E1ngeli_Obes?=" Subject: Re: [Qemu-devel] Re: [kvm-devel] [PATCH][RFC] Allowing QEMU to directly execute a directory (and storing command line options in it) In-Reply-To: MIME-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit Content-Disposition: inline References: <59abf66e0708311119p2b83fcffg31fac1c298cfc10a@mail.gmail.com> <1188586457.8543.2.camel@squirrel> <7CB48D77-249D-4DD9-83B8-D3DB8553C058@jump-ing.de> Reply-To: qemu-devel@nongnu.org List-Id: qemu-devel.nongnu.org List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , To: =?ISO-8859-1?Q?Andreas_F=E4rber?= Cc: kvm-devel@lists.sourceforge.net, dev@cordney.com, q.app@kberg.ch, qemu-devel@nongnu.org > And I don't understand why, when going along with the bundle idea, > you are suddenly creating a new configuration file format of your > own. There is a standard format, XML or text based, which can be > easily parsed with OSX APIs (and thus likely *Step APIs as well) as a > dictionary, allowing structured information to be stored and thus > allowing Qemu backends to store their own settings alongside. See > attached one my bundles' configuration.plist file (XML serialized) - > relevant is only the Arguments entry, everything else is GUI > specific. I'm not saying this format (the structure) were perfect but > the underlying "property list" format (key, value-type) is standard > for such bundles, so instead of re-inventing the wheel please take a > look at how it's being done! I would like to think that having command line options separated by spaces or newlines is a new configuration file format, but it's not. This patch is not meant as a replacement for libvirt or any other backend. It's just a replacement for shell scripts that serve the only purpose of storing command line options. It should be a simple solution for a simple problem. The complex solution for the complex problem is already there and is called libvirt. I don't want to have QEMU parse serialized XML just to replace my '-m 512 -soundhw es1370 -net nic,model=rtl8139' command line. I would simply like to store that command line somewhere. Anyways, it's obvious that this is a delicate issue for many people here. I think the most non-disruptive way of doing this is the '-c' command line option. It doesn't change QEMU default behaviour, it doesn't add new hyphen-less options. I insist on the fact that this should be a simple solution for a simple problem. Cheers, Jorge