From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from mailman by lists.gnu.org with tmda-scanned (Exim 4.43) id 1IKr1S-0000pP-7d for qemu-devel@nongnu.org; Tue, 14 Aug 2007 03:41:02 -0400 Received: from exim by lists.gnu.org with spam-scanned (Exim 4.43) id 1IKr1Q-0000o8-6F for qemu-devel@nongnu.org; Tue, 14 Aug 2007 03:41:01 -0400 Received: from [199.232.76.173] (helo=monty-python.gnu.org) by lists.gnu.org with esmtp (Exim 4.43) id 1IKr1Q-0000o2-2r for qemu-devel@nongnu.org; Tue, 14 Aug 2007 03:41:00 -0400 Received: from ns.suse.de ([195.135.220.2] helo=mx1.suse.de) by monty-python.gnu.org with esmtps (TLS-1.0:DHE_RSA_AES_256_CBC_SHA1:32) (Exim 4.60) (envelope-from ) id 1IKr1P-00049g-Ly for qemu-devel@nongnu.org; Tue, 14 Aug 2007 03:40:59 -0400 Message-ID: <46C15D68.8090406@suse.de> Date: Tue, 14 Aug 2007 09:44:40 +0200 From: Kevin Wolf MIME-Version: 1.0 Subject: Re: [kvm-devel] [Qemu-devel] Re: Storing command line options in images References: <59abf66e0708092155t2e3cd5o32f23c018bed65af@mail.gmail.com> <46BC8C18.6020108@codemonkey.ws> <46BC9CDB.3080900@qumranet.com> <46BCB1DA.6060102@codemonkey.ws> <46BCBF73.5060406@qumranet.com> <46BCC666.6050406@codemonkey.ws> <59abf66e0708101841i76e26a35vcbc8df14b21f1ac0@mail.gmail.com> <20070813193927.GA21215@networkno.de> <1187061429.16054.2.camel@squirrel> <59abf66e0708132139y3d5dc5e7yf033aa4896d16093@mail.gmail.com> In-Reply-To: <59abf66e0708132139y3d5dc5e7yf033aa4896d16093@mail.gmail.com> Content-Type: text/plain; charset=ISO-8859-1 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 Jorge Luc=E1ngeli Obes schrieb: > qemu: could not open hard disk image '@config' I think this was a suggestion for implementation, not a working feature. > I did not know about '@config', and if I can get it to work, I like it > better than a shell script. However, I think it does not completely > solve the problem. It still means two files per VM. As long as it is not possible to store more than one image in one file, this problem won't be solved completely anyway. Kevin