From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from mailman by lists.gnu.org with tmda-scanned (Exim 4.43) id 1FR56B-0006Oc-8m for qemu-devel@nongnu.org; Wed, 05 Apr 2006 06:18:51 -0400 Received: from exim by lists.gnu.org with spam-scanned (Exim 4.43) id 1FR56A-0006OM-HW for qemu-devel@nongnu.org; Wed, 05 Apr 2006 06:18:50 -0400 Received: from [199.232.76.173] (helo=monty-python.gnu.org) by lists.gnu.org with esmtp (Exim 4.43) id 1FR56A-0006OD-7o for qemu-devel@nongnu.org; Wed, 05 Apr 2006 06:18:50 -0400 Received: from [131.111.8.137] (helo=ppsw-7.csi.cam.ac.uk) by monty-python.gnu.org with esmtp (Exim 4.52) id 1FR59e-0000Ye-KU for qemu-devel@nongnu.org; Wed, 05 Apr 2006 06:22:26 -0400 Received: from hermes-2.csi.cam.ac.uk ([131.111.8.54]:48074) by ppsw-7.csi.cam.ac.uk (smtp.hermes.cam.ac.uk [131.111.8.157]:25) with esmtpa (EXTERNAL:maw48) id 1FR55t-0000O9-Of (Exim 4.54) for qemu-devel@nongnu.org (return-path ); Wed, 05 Apr 2006 11:18:35 +0100 Received: from prayer by hermes-2.csi.cam.ac.uk (hermes.cam.ac.uk) with local (PRAYER:maw48) id 1FR55t-0005cg-Ji (Exim 4.53) for qemu-devel@nongnu.org (return-path ); Wed, 05 Apr 2006 11:18:33 +0100 From: "M.A. Williamson" Subject: Re: [Qemu-devel] vmware puts up specs for it's disk format Date: 05 Apr 2006 11:18:33 +0100 In-Reply-To: <443394CC.6050301@sjsoft.com> Message-ID: References: <20060403222341.GB1254@muon.de> <20060403235535.GA10338@jbrown.mylinuxbox.org> <1144138146.10154.28.camel@localhost> <443394CC.6050301@sjsoft.com> Mime-Version: 1.0 Content-Type: text/plain; format=flowed; charset=ISO-8859-1 Sender: "M.A. Williamson" Reply-To: mark.williamson@cl.cam.ac.uk, 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 >> Basically, if u want split images to be supported in qemu, speak up >> now. ;) >> >I speak! It would be great to be able to use the split images, so that >you don't have to alter the files to import them into qemu... >Particularly using split files directly and then being able to use the >same image from vmware... I've missed this feature too, actually. Cheers, Mark