From: Peter Xu <peterx@redhat.com>
To: Li Zhijian <lizhijian@fujitsu.com>,
zhangckid@gmail.com, zhanghailiang@xfusion.com
Cc: farosas@suse.de, zhangckid@gmail.com, zhanghailiang@xfusion.com,
qemu-devel@nongnu.org
Subject: Re: [PATCH] migration: Fix transition to COLO state from precopy
Date: Wed, 5 Nov 2025 15:58:20 -0500 [thread overview]
Message-ID: <aQu6bDAA7hnIPg-y@x1.local> (raw)
In-Reply-To: <20251104013606.1937764-1-lizhijian@fujitsu.com>
On Tue, Nov 04, 2025 at 09:36:06AM +0800, Li Zhijian wrote:
> Commit 4881411136 ("migration: Always set DEVICE state") set a new DEVICE
> state before completed during migration, which broke the original transition
> to COLO. The migration flow for precopy has changed to:
> active -> pre-switchover -> device -> completed.
>
> This patch updates the transition state to ensure that the Pre-COLO
> state corresponds to DEVICE state correctly.
>
> Fixes: 4881411136 ("migration: Always set DEVICE state")
> Signed-off-by: Li Zhijian <lizhijian@fujitsu.com>
> ---
> migration/migration.c | 4 ++--
> 1 file changed, 2 insertions(+), 2 deletions(-)
>
> diff --git a/migration/migration.c b/migration/migration.c
> index a63b46bbef..6ec7f3cec8 100644
> --- a/migration/migration.c
> +++ b/migration/migration.c
> @@ -3095,9 +3095,9 @@ static void migration_completion(MigrationState *s)
> goto fail;
> }
>
> - if (migrate_colo() && s->state == MIGRATION_STATUS_ACTIVE) {
> + if (migrate_colo() && s->state == MIGRATION_STATUS_DEVICE) {
> /* COLO does not support postcopy */
> - migrate_set_state(&s->state, MIGRATION_STATUS_ACTIVE,
> + migrate_set_state(&s->state, MIGRATION_STATUS_DEVICE,
> MIGRATION_STATUS_COLO);
> } else {
> migration_completion_end(s);
Thanks a lot for fixing it, Zhijian. It means I broke COLO already for
10.0/10.1..
Hailiang/Chen, do you still know anyone who is using COLO, especially in
enterprise? I don't expect any individual using it.. It definitely
complicates migration logics all over the places. Fabiano and I discussed
a few times on removing legacy code and COLO was always in the list.
We used to discuss RDMA obsoletion too, that's when Huawei developers at
least tried to re-implement the whole RDMA using rsocket, that didn't land
only because of a perf regression. Meanwhile, Zhijian also provided an
unit test, which we rely on recently to not break RDMA at the minimum.
If we do not have known users, I sincerely want to discuss with you on
obsoletion and removal of COLO from qemu codebase. Do you see feasible?
Zhijian, do you have any input here?
Thanks,
--
Peter Xu
next prev parent reply other threads:[~2025-11-05 20:58 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-11-04 1:36 [PATCH] migration: Fix transition to COLO state from precopy Li Zhijian via
2025-11-04 1:49 ` Zhijian Li (Fujitsu)
2025-11-04 2:40 ` Zhang Chen
2025-11-05 20:58 ` Peter Xu [this message]
2025-11-06 1:09 ` Zhijian Li (Fujitsu)
2025-11-06 3:21 ` Zhang Chen
2025-11-06 3:24 ` Zhang Chen
2025-11-06 22:07 ` Peter Xu
2025-11-24 0:35 ` Jason Wang
2025-11-24 1:56 ` Zhang Chen
2025-11-24 8:38 ` Lukas Straub
2025-11-24 19:28 ` Peter Xu
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=aQu6bDAA7hnIPg-y@x1.local \
--to=peterx@redhat.com \
--cc=farosas@suse.de \
--cc=lizhijian@fujitsu.com \
--cc=qemu-devel@nongnu.org \
--cc=zhangckid@gmail.com \
--cc=zhanghailiang@xfusion.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.