From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from mailman by lists.gnu.org with tmda-scanned (Exim 4.43) id 1IRBnz-0001Fv-Io for qemu-devel@nongnu.org; Fri, 31 Aug 2007 15:05:19 -0400 Received: from exim by lists.gnu.org with spam-scanned (Exim 4.43) id 1IRBnx-0001E2-VA for qemu-devel@nongnu.org; Fri, 31 Aug 2007 15:05:19 -0400 Received: from [199.232.76.173] (helo=monty-python.gnu.org) by lists.gnu.org with esmtp (Exim 4.43) id 1IRBnx-0001Do-Nv for qemu-devel@nongnu.org; Fri, 31 Aug 2007 15:05:17 -0400 Received: from nz-out-0506.google.com ([64.233.162.233]) by monty-python.gnu.org with esmtp (Exim 4.60) (envelope-from ) id 1IRBnx-00030E-BX for qemu-devel@nongnu.org; Fri, 31 Aug 2007 15:05:17 -0400 Received: by nz-out-0506.google.com with SMTP id f1so2513820nzc for ; Fri, 31 Aug 2007 12:05:16 -0700 (PDT) Message-ID: <59abf66e0708311205n6f6086d0g5d7c786ff2bef02b@mail.gmail.com> Date: Fri, 31 Aug 2007 16:05:15 -0300 From: "=?ISO-8859-1?Q?Jorge_Luc=E1ngeli_Obes?=" In-Reply-To: <1188586457.8543.2.camel@squirrel> 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> Subject: [Qemu-devel] Re: [kvm-devel] [PATCH][RFC] Allowing QEMU to directly execute a directory (and storing command line options in it) Reply-To: qemu-devel@nongnu.org List-Id: qemu-devel.nongnu.org List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , To: Anthony Liguori Cc: kvm-devel@lists.sourceforge.net, qemu-devel@nongnu.org On 8/31/07, Anthony Liguori wrote: > It makes little sense to pass a directory when you can pass a config > file and assume that the directory the config file is in is the CWD. > > For instance, if vm.cfg contained just the command line arguments, you > could have: > > MyImage/vm.cfg: -hda disk0.qcow -m 512 > MyImage/disk0.qcow: > > And then do: > > qemu -c MyImage/vm.cfg I thought about this when coding, and it's true. Maybe we could just leave a new explicit config file option. I insist on making this as simple as possible, that's why I chose to use the config file as a "written-down" command line. If this were the case, we could remove the restriction of having the config file refer only to images on the same directory, as the use of the config file would be explicit. Thoughts? Cheers, Jorge