From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from eggs.gnu.org ([2001:4830:134:3::10]:58274) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1dpCJi-0006TR-4b for qemu-devel@nongnu.org; Tue, 05 Sep 2017 07:46:58 -0400 Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1dpCJd-00028z-MI for qemu-devel@nongnu.org; Tue, 05 Sep 2017 07:46:54 -0400 Date: Tue, 5 Sep 2017 13:46:24 +0200 From: Kevin Wolf Message-ID: <20170905114624.GI4633@localhost.localdomain> References: MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: Subject: Re: [Qemu-devel] Persistent bitmaps for non-qcow2 formats List-Id: List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , To: John Snow Cc: Qemu-block , qemu-devel , Vladimir Sementsov-Ogievskiy , Manos Pitsidianakis , Fam Zheng , Stefan Hajnoczi , Max Reitz Am 22.08.2017 um 21:07 hat John Snow geschrieben: > Well, we knew we'd want this sooner or later. I've got some pings > downstream over whether or not we support persistent bitmaps for > non-qcow2 formats. > > Currently: no, we don't. I was going to write some things about r/w backing file, and I might still do that later, but for now, let me take a step back: What is the use case here? Using a specific image format is not a value in and of itself; it should be chosen depending on which features you need. What prevents those downstream users from simply choosing qcow2 for their data, too? Kevin