From: Eric Blake <eblake@redhat.com>
To: "Denis V. Lunev" <den@openvz.org>
Cc: qemu-devel@nongnu.org, qemu-block@nongnu.org,
Peter Xu <peterx@redhat.com>, Fabiano Rosas <farosas@suse.de>,
Vladimir Sementsov-Ogievskiy <vsementsov@yandex-team.ru>
Subject: Re: [PATCH v2 0/3] migration/block-dirty-bitmap: fix postcopy abort with bitmaps on several nodes
Date: Wed, 7 Oct 2026 07:22:31 -0500 [thread overview]
Message-ID: <asY5VH_Kb2GXiyM9@redhat.com> (raw)
In-Reply-To: <20261006170738.453977-1-den@openvz.org>
On Tue, Oct 06, 2026 at 07:07:35PM +0200, Denis V. Lunev wrote:
> Postcopy migration of dirty bitmaps kills the destination as soon as
> bitmaps live on more than one node:
>
> qemu-system-x86_64: ../block.c:6400: bdrv_lookup_bs: Assertion
> `qemu_in_main_thread()' failed.
>
> Changes in v2:
> - new patch 1: add QEMU_COUNTED_STRING_SIZE instead of bare 256 (Eric)
> - patch 2: drop the "Error: " prefix from the new error message (Eric)
> - patch 2: move node_alias to the end of LoadBitmapState
> - patch 3: add Eric's Tested-by and Reviewed-by
I'm queueing this series through my NBD tree, and running tests now in
preparation for a pull request.
--
Eric Blake, Principal Software Engineer
Red Hat, Inc.
Virtualization: qemu.org | libguestfs.org
prev parent reply other threads:[~2026-10-07 12:24 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-10-06 17:07 [PATCH v2 0/3] migration/block-dirty-bitmap: fix postcopy abort with bitmaps on several nodes Denis V. Lunev
2026-10-06 17:07 ` [PATCH v2 1/3] migration: add QEMU_COUNTED_STRING_SIZE for counted string buffers Denis V. Lunev
2026-10-06 21:33 ` Eric Blake
2026-10-06 17:07 ` [PATCH v2 2/3] migration/block-dirty-bitmap: fix postcopy abort with bitmaps on several nodes Denis V. Lunev
2026-10-07 12:01 ` Eric Blake
2026-10-06 17:07 ` [PATCH v2 3/3] iotests/migrate-bitmaps-postcopy-test: add a bitmap on a second node Denis V. Lunev
2026-10-07 21:44 ` Eric Blake
2026-10-07 12:22 ` Eric Blake [this message]
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=asY5VH_Kb2GXiyM9@redhat.com \
--to=eblake@redhat.com \
--cc=den@openvz.org \
--cc=farosas@suse.de \
--cc=peterx@redhat.com \
--cc=qemu-block@nongnu.org \
--cc=qemu-devel@nongnu.org \
--cc=vsementsov@yandex-team.ru \
/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.