From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from [140.186.70.92] (port=33277 helo=eggs.gnu.org) by lists.gnu.org with esmtp (Exim 4.43) id 1Ou1F9-0004R4-CT for qemu-devel@nongnu.org; Fri, 10 Sep 2010 06:54:08 -0400 Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.69) (envelope-from ) id 1Ou1F8-0005Ij-Bz for qemu-devel@nongnu.org; Fri, 10 Sep 2010 06:54:07 -0400 Received: from mx1.redhat.com ([209.132.183.28]:41478) by eggs.gnu.org with esmtp (Exim 4.69) (envelope-from ) id 1Ou1F8-0005IS-4k for qemu-devel@nongnu.org; Fri, 10 Sep 2010 06:54:06 -0400 Message-ID: <4C8A0E44.6090307@redhat.com> Date: Fri, 10 Sep 2010 13:53:56 +0300 From: Avi Kivity MIME-Version: 1.0 References: <1283767478-16740-1-git-send-email-stefanha@linux.vnet.ibm.com> <4C84E738.3020802@codemonkey.ws> <4C865187.6090508@redhat.com> <4C865CFE.7010508@codemonkey.ws> <4C8663C4.1090508@redhat.com> <4C866773.2030103@codemonkey.ws> <4C86BC6B.5010809@codemonkey.ws> <4C874812.9090807@redhat.com> <4C87860A.3060904@codemonkey.ws> <4C888287.8020209@redhat.com> <4C88D7CC.5000806@codemonkey.ws> <4C890FD1.6060105@redhat.com> <4C891322.9020104@codemonkey.ws> In-Reply-To: <4C891322.9020104@codemonkey.ws> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Subject: [Qemu-devel] Re: [RFC] qed: Add QEMU Enhanced Disk format List-Id: qemu-devel.nongnu.org List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , To: Anthony Liguori Cc: Kevin Wolf , Paolo Bonzini , Stefan Hajnoczi , qemu-devel@nongnu.org On 09/09/2010 08:02 PM, Anthony Liguori wrote: > On 09/09/2010 11:48 AM, Paolo Bonzini wrote: >> On 09/09/2010 02:49 PM, Anthony Liguori wrote: >>> We should optimize for the future. That means a btrfs file system >>> and/or >>> enterprise storage. >> >> So we should just implement a copy-on-read wrapper that generates a >> sparse raw image and uses FIEMAP (or whatever it is called these >> days) to test for the presence of extents. Then you let btrfs handle >> everything else... > > My position is that we'll need a sparse image format well into the > future because while btrfs may be ubiquitous as a file system, IRL, > people transfer images around all of the time through dumb transports > like HTTP and fat-formatted USB keys. A 100GB image with 1GB > allocated cannot explode to 100GB just because HTTP is a dump transport. > An 'Export' and 'Upload' buttons would do the job. For command line users, compressing the image will remove the unallocated extents, as will 'qemu-img convert -O qcow2'. It's not as nice as having a sparse format, but on the other hand, performance and data integrity will be better, as well as the excellent snapshot support. -- I have a truly marvellous patch that fixes the bug which this signature is too narrow to contain.