From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from eggs.gnu.org ([140.186.70.92]:47210) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1QjS9P-0004WI-3A for qemu-devel@nongnu.org; Wed, 20 Jul 2011 04:29:04 -0400 Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1QjS9N-0001h2-6m for qemu-devel@nongnu.org; Wed, 20 Jul 2011 04:29:02 -0400 Received: from mx1.redhat.com ([209.132.183.28]:47753) by eggs.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1QjS9M-0001gd-KW for qemu-devel@nongnu.org; Wed, 20 Jul 2011 04:29:01 -0400 Message-ID: <4E269149.4090904@redhat.com> Date: Wed, 20 Jul 2011 10:26:49 +0200 From: Jes Sorensen MIME-Version: 1.0 References: <4E2055AE.8090107@redhat.com> <4E253136.4080509@redhat.com> <4E258635.2040108@redhat.com> <4E258D70.6000205@redhat.com> <4E25902D.2000403@redhat.com> <4E2593B0.1030508@redhat.com> <4E2594FB.4050203@redhat.com> <20110719164755.GF12026@redhat.com> In-Reply-To: <20110719164755.GF12026@redhat.com> Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 7bit Subject: Re: [Qemu-devel] live snapshot wiki updated List-Id: List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , To: "Daniel P. Berrange" Cc: "libvir-list@redhat.com" , Stefan Hajnoczi , Eric Blake , QEMU Developers , Stefan Hajnoczi On 07/19/11 18:47, Daniel P. Berrange wrote: > On Tue, Jul 19, 2011 at 04:30:19PM +0200, Jes Sorensen wrote: >> On 07/19/11 16:24, Eric Blake wrote: >>> Besides, I feel that having a well-documented file format, so that >>> independent applications can both parse the same file with the same >>> semantics by obeying the file format specification, is a good design goal. >> >> We all know that documentation is rarely uptodate, new features may not >> get added and libvirt will never be able to keep up. The driver for a >> file format belongs in QEMU and nowhere else. > > This would be possible if QEMU to provide a libblockformat.so library > which allowed apps to extract metadata from file formats using a stable > API. There is no reason for libvirt or any external process to mess about with the internals of image files. You have the same problem if the image file is encrypted. Jes