From mboxrd@z Thu Jan  1 00:00:00 1970
Received: from eggs.gnu.org ([2001:4830:134:3::10]:47218)
	by lists.gnu.org with esmtp (Exim 4.71)
	(envelope-from <kwolf@redhat.com>) id 1Zz4Gv-0006Ey-AM
	for qemu-devel@nongnu.org; Wed, 18 Nov 2015 10:03:49 -0500
Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71)
	(envelope-from <kwolf@redhat.com>) id 1Zz4Gu-0007M0-8p
	for qemu-devel@nongnu.org; Wed, 18 Nov 2015 10:03:45 -0500
Date: Wed, 18 Nov 2015 16:03:34 +0100
From: Kevin Wolf <kwolf@redhat.com>
Message-ID: <20151118150334.GF4817@noname.str.redhat.com>
References: <1447108773-6836-1-git-send-email-mreitz@redhat.com>
	<1447108773-6836-4-git-send-email-mreitz@redhat.com>
	<20151112062349.GC4082@ad.usersys.redhat.com>
	<56466916.6040300@redhat.com>
	<20151116012745.GA21478@ad.usersys.redhat.com>
	<564A0D60.6080704@redhat.com>
	<20151117042251.GD28076@ad.usersys.redhat.com>
	<564B5E4B.4000406@redhat.com>
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: <564B5E4B.4000406@redhat.com>
Subject: Re: [Qemu-devel] Closing Bitmaps (Was: Re: [PATCH v7 03/24] block:
 Release dirty bitmaps in bdrv_close())
List-Id: <qemu-devel.nongnu.org>
List-Unsubscribe: <https://lists.nongnu.org/mailman/options/qemu-devel>,
	<mailto:qemu-devel-request@nongnu.org?subject=unsubscribe>
List-Archive: <http://lists.nongnu.org/archive/html/qemu-devel>
List-Post: <mailto:qemu-devel@nongnu.org>
List-Help: <mailto:qemu-devel-request@nongnu.org?subject=help>
List-Subscribe: <https://lists.nongnu.org/mailman/listinfo/qemu-devel>,
	<mailto:qemu-devel-request@nongnu.org?subject=subscribe>
To: John Snow <jsnow@redhat.com>
Cc: Vladimir Sementsov-Ogievskiy <vsementsov@virtuozzo.com>, Alberto Garcia <berto@igalia.com>, qemu-block@nongnu.org, qemu-devel@nongnu.org, Markus Armbruster <armbru@redhat.com>, Stefan Hajnoczi <stefanha@redhat.com>, Paolo Bonzini <pbonzini@redhat.com>, Fam Zheng <famz@redhat.com>, Max Reitz <mreitz@redhat.com>

Am 17.11.2015 um 18:05 hat John Snow geschrieben:
> Still the subject of debate on-list, but the thought is roughly this:
> 
> Bitmaps will be able to flush-to-file on close. (If they have no
> persistence data, it's a no-op (maybe.)) This might mean being flushed
> to their own BDS -- the one they are describing -- as a qcow2 extension.
> Or, it could be to an arbitrary new standalone file format designed for
> the sole purpose of containing bitmap data.
> 
> The discussion hasn't progressed beyond "Max and Kevin do not think
> storing arbitrary bitmaps in .qcow2 files is a good idea." The logical
> conclusion is "We need a new standalone format, then" but we haven't
> decided what that format will look like or how it will be used.

I think the actual logical conclusion is that you use qcow2 images in
order to use the feature.

Kevin