From: Vladimir Sementsov-Ogievskiy <vsementsov@virtuozzo.com>
To: qemu-block@nongnu.org
Cc: fam@euphon.net, kwolf@redhat.com, vsementsov@virtuozzo.com,
quintela@redhat.com, qemu-devel@nongnu.org, dgilbert@redhat.com,
stefanha@redhat.com, den@openvz.org, mreitz@redhat.com,
jsnow@redhat.com
Subject: [PATCH v2 0/5] fix migration with bitmaps and mirror
Date: Thu, 19 Dec 2019 11:51:01 +0300 [thread overview]
Message-ID: <20191219085106.22309-1-vsementsov@virtuozzo.com> (raw)
Hi all!
It's a continuation for
"bitmap migration bug with -drive while block mirror runs"
<315cff78-dcdb-a3ce-2742-da3cc9f0ca97@redhat.com>
https://lists.gnu.org/archive/html/qemu-devel/2019-09/msg07241.html
The problem is that bitmaps migrated to node with same node-name or
blk-parent name. And currently only the latter actually work in libvirt.
And with mirror-top filter it doesn't work, because
bdrv_get_device_or_node_name don't go through filters.
Fix this by handling filtered children of block backends in separate.
v2: rebase on current master
Max Reitz (1):
block: Mark commit and mirror as filter drivers
Vladimir Sementsov-Ogievskiy (4):
migretion/block-dirty-bitmap: refactor init_dirty_bitmap_migration
block/dirty-bitmap: add bdrv_has_named_bitmaps helper
migration/block-dirty-bitmap: fix bitmaps migration during mirror job
iotests: 194: test also migration of dirty bitmap
include/block/block_int.h | 8 ++-
include/block/dirty-bitmap.h | 1 +
block/commit.c | 2 +
block/dirty-bitmap.c | 13 ++++
block/mirror.c | 2 +
migration/block-dirty-bitmap.c | 114 +++++++++++++++++++++++----------
tests/qemu-iotests/194 | 14 ++--
tests/qemu-iotests/194.out | 6 ++
8 files changed, 119 insertions(+), 41 deletions(-)
--
2.21.0
next reply other threads:[~2019-12-19 8:52 UTC|newest]
Thread overview: 25+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-12-19 8:51 Vladimir Sementsov-Ogievskiy [this message]
2019-12-19 8:51 ` [PATCH v2 1/5] block: Mark commit and mirror as filter drivers Vladimir Sementsov-Ogievskiy
2020-01-31 19:23 ` Eric Blake
2020-05-14 18:51 ` Eric Blake
2019-12-19 8:51 ` [PATCH v2 2/5] migretion/block-dirty-bitmap: refactor init_dirty_bitmap_migration Vladimir Sementsov-Ogievskiy
2020-01-31 19:28 ` Eric Blake
2019-12-19 8:51 ` [PATCH v2 3/5] block/dirty-bitmap: add bdrv_has_named_bitmaps helper Vladimir Sementsov-Ogievskiy
2020-05-14 18:30 ` Eric Blake
2019-12-19 8:51 ` [PATCH v2 4/5] migration/block-dirty-bitmap: fix bitmaps migration during mirror job Vladimir Sementsov-Ogievskiy
2020-05-14 18:52 ` Eric Blake
2019-12-19 8:51 ` [PATCH v2 5/5] iotests: 194: test also migration of dirty bitmap Vladimir Sementsov-Ogievskiy
2019-12-19 10:36 ` [PATCH v2 0/5] fix migration with bitmaps and mirror Peter Krempa
2019-12-19 11:39 ` Vladimir Sementsov-Ogievskiy
2020-04-03 11:02 ` Vladimir Sementsov-Ogievskiy
2020-04-03 11:23 ` Peter Krempa
2020-04-03 11:29 ` Vladimir Sementsov-Ogievskiy
2020-04-03 11:52 ` Vladimir Sementsov-Ogievskiy
2020-04-03 15:05 ` Dr. David Alan Gilbert
2020-04-03 15:34 ` Vladimir Sementsov-Ogievskiy
2020-05-14 18:29 ` Eric Blake
2020-05-15 5:52 ` Vladimir Sementsov-Ogievskiy
2020-05-15 11:15 ` Vladimir Sementsov-Ogievskiy
2020-05-15 17:51 ` Eric Blake
2020-05-15 19:49 ` Vladimir Sementsov-Ogievskiy
2020-01-20 9:04 ` 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=20191219085106.22309-1-vsementsov@virtuozzo.com \
--to=vsementsov@virtuozzo.com \
--cc=den@openvz.org \
--cc=dgilbert@redhat.com \
--cc=fam@euphon.net \
--cc=jsnow@redhat.com \
--cc=kwolf@redhat.com \
--cc=mreitz@redhat.com \
--cc=qemu-block@nongnu.org \
--cc=qemu-devel@nongnu.org \
--cc=quintela@redhat.com \
--cc=stefanha@redhat.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.