From: Eric Blake <eblake@redhat.com>
To: Max Reitz <mreitz@redhat.com>, qemu-block@nongnu.org
Cc: Kevin Wolf <kwolf@redhat.com>, John Snow <jsnow@redhat.com>,
Vladimir Sementsov-Ogievskiy <vsementsov@virtuozzo.com>,
Peter Krempa <pkrempa@redhat.com>,
qemu-devel@nongnu.org
Subject: Re: [PATCH 0/2] qcow2: Release read-only bitmaps when inactivated
Date: Thu, 30 Jul 2020 09:19:58 -0500 [thread overview]
Message-ID: <c6a84a92-d2f2-cdfb-154d-470dbb24ed8e@redhat.com> (raw)
In-Reply-To: <20200730120234.49288-1-mreitz@redhat.com>
On 7/30/20 7:02 AM, Max Reitz wrote:
> Hi,
>
> When beginning migration, the qcow2 driver syncs all persistent bitmaps
> to disk and then releases them. If the user decides to continue on the
> source after migration, those bitmaps are re-loaded from the qcow2
> image.
>
> However, we only do this for bitmaps that were actively synced, i.e. R/W
> bitmaps. RO bitmaps (those on backing images) are not written and thus
> not released. However, we still try to re-load them when continuing,
> and that will then fail.
>
> To fix this problem, I think we should just consider RO bitmaps to be in
> sync from the beginning, so we can release them just like bitmaps that
> we have actively written back to the image. This is done by patch 1.
>
> However, there’s a catch: Peter Krempa noted that it isn’t in libvirt’s
> interest for the bitmaps to be released before migration at all, because
> this makes them disappear from query-named-block-node’s dirty-bitmaps
> list, but libvirt needs the bitmaps to be there:
>
> https://bugzilla.redhat.com/show_bug.cgi?id=1858739#c3
And that is enough to make me think this series is -rc3 material.
Although I'm not yet sure whether the solution is this series as
written, or to patch libvirt to look elsewhere for bitmap information,
or to patch qemu on incoming migration to not complain when reloading a
RO bitmap, or something else.
>
> If it’s really not feasible to keep the bitmaps around, then I suppose
> what might work for libvirt is to query
> image/format-specific/data/bitmaps in addition to dirty-bitmaps (every
> bitmap that we released before migration must be a persistent bitmap).
>
> What are your thoughts on this?
I'd really like to hear from Virtuozzo on the topic before committing to
this series, but I will at least review it in the meantime.
>
>
> Max Reitz (2):
> qcow2: Release read-only bitmaps when inactivated
> iotests/169: Test source cont with backing bmap
>
> block/qcow2-bitmap.c | 23 +++++++++++---
> tests/qemu-iotests/169 | 64 +++++++++++++++++++++++++++++++++++++-
> tests/qemu-iotests/169.out | 4 +--
> 3 files changed, 84 insertions(+), 7 deletions(-)
>
--
Eric Blake, Principal Software Engineer
Red Hat, Inc. +1-919-301-3226
Virtualization: qemu.org | libvirt.org
next prev parent reply other threads:[~2020-07-30 14:27 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-07-30 12:02 [PATCH 0/2] qcow2: Release read-only bitmaps when inactivated Max Reitz
2020-07-30 12:02 ` [PATCH 1/2] " Max Reitz
2020-07-30 14:22 ` Peter Krempa
2020-07-30 14:54 ` Eric Blake
2020-08-05 11:06 ` Vladimir Sementsov-Ogievskiy
2020-07-30 12:02 ` [PATCH 2/2] iotests/169: Test source cont with backing bmap Max Reitz
2020-07-30 14:38 ` Eric Blake
2020-07-30 14:19 ` Eric Blake [this message]
2020-08-05 8:15 ` [PATCH 0/2] qcow2: Release read-only bitmaps when inactivated Vladimir Sementsov-Ogievskiy
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=c6a84a92-d2f2-cdfb-154d-470dbb24ed8e@redhat.com \
--to=eblake@redhat.com \
--cc=jsnow@redhat.com \
--cc=kwolf@redhat.com \
--cc=mreitz@redhat.com \
--cc=pkrempa@redhat.com \
--cc=qemu-block@nongnu.org \
--cc=qemu-devel@nongnu.org \
--cc=vsementsov@virtuozzo.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).