All of lore.kernel.org
 help / color / mirror / Atom feed
From: Peter Xu <peterx@redhat.com>
To: Lukas Straub <lukasstraub2@web.de>
Cc: qemu-devel@nongnu.org, Fabiano Rosas <farosas@suse.de>,
	Laurent Vivier <lvivier@redhat.com>,
	Paolo Bonzini <pbonzini@redhat.com>,
	Zhang Chen <zhangckid@gmail.com>,
	Juan Quintela <quintela@trasno.org>
Subject: Re: [PATCH 0/3] migration: Add COLO multifd support and COLO migration unit test
Date: Tue, 30 Dec 2025 10:02:27 -0500	[thread overview]
Message-ID: <aVPpg_LwlGFIPfen@x1.local> (raw)
In-Reply-To: <20251230-colo_unit_test_multifd-v1-0-f9734bc74c71@web.de>

On Tue, Dec 30, 2025 at 03:05:43PM +0100, Lukas Straub wrote:
> Hello everyone,
> This adds COLO multifd support and migration unit tests for COLO migration
> and failover.

Hi, Lukas,

I'll review the series after the new year.

Could you still introduce some background on how you're deploying COLO?  Do
you use it in production, or for fun?

COLO is still a nice and interesting feature, said that, COLO has quite a
lot of code plugged into migration core.  I wished it's like a multifd
compressor which was much more self-contained, but it's not.  I wished we
can simplify the code in QEMU migration.

We've talked it through before with current COLO maintainers, it looks to
me there aren't really much users using it in production, meanwhile COLO
doesn't look like a feature to benefit individual QEMU users either.

I want to study the use case of COLO in status quo, and evaluate how much
effort we should put on it in the future.  Note that if it's for fun we can
always use a stable branch which will be there forever.  We'll need to
think about QEMU evolving in the future, and what's best for QEMU.

Thanks,

> 
> Regards,
> Lukas
> 
> Signed-off-by: Lukas Straub <lukasstraub2@web.de>
> ---
> Lukas Straub (3):
>       multifd: Add colo support
>       migration-test: Add -snapshot option for COLO
>       migration-test: Add COLO migration unit test
> 
>  migration/meson.build              |   2 +-
>  migration/multifd-colo.c           |  57 ++++++++++++++++++
>  migration/multifd-colo.h           |  26 +++++++++
>  migration/multifd.c                |  14 ++++-
>  tests/qtest/meson.build            |   7 ++-
>  tests/qtest/migration-test.c       |   1 +
>  tests/qtest/migration/colo-tests.c | 115 +++++++++++++++++++++++++++++++++++++
>  tests/qtest/migration/framework.c  |  69 +++++++++++++++++++++-
>  tests/qtest/migration/framework.h  |  10 ++++
>  9 files changed, 294 insertions(+), 7 deletions(-)
> ---
> base-commit: 942b0d378a1de9649085ad6db5306d5b8cef3591
> change-id: 20251230-colo_unit_test_multifd-8bf58dcebd46
> 
> Best regards,
> -- 
> Lukas Straub <lukasstraub2@web.de>
> 

-- 
Peter Xu



  parent reply	other threads:[~2025-12-30 15:03 UTC|newest]

Thread overview: 17+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-12-30 14:05 [PATCH 0/3] migration: Add COLO multifd support and COLO migration unit test Lukas Straub
2025-12-30 14:05 ` [PATCH 1/3] multifd: Add colo support Lukas Straub
2026-01-06 19:54   ` Peter Xu
2026-01-15 22:43     ` Lukas Straub
2025-12-30 14:05 ` [PATCH 2/3] migration-test: Add -snapshot option for COLO Lukas Straub
2026-01-06 19:55   ` Peter Xu
2026-01-15 22:37     ` Lukas Straub
2025-12-30 14:05 ` [PATCH 3/3] migration-test: Add COLO migration unit test Lukas Straub
2026-01-06 20:03   ` Peter Xu
2026-01-15 22:35     ` Lukas Straub
2026-01-15 22:42       ` Peter Xu
2025-12-30 15:02 ` Peter Xu [this message]
2026-01-04  5:44   ` [PATCH 0/3] migration: Add COLO multifd support and " Zhang Chen
2026-01-04  5:48     ` Zhang Chen
2026-01-06 19:48     ` Peter Xu
2026-01-15 21:45       ` Lukas Straub
2026-01-06 20:05 ` 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=aVPpg_LwlGFIPfen@x1.local \
    --to=peterx@redhat.com \
    --cc=farosas@suse.de \
    --cc=lukasstraub2@web.de \
    --cc=lvivier@redhat.com \
    --cc=pbonzini@redhat.com \
    --cc=qemu-devel@nongnu.org \
    --cc=quintela@trasno.org \
    --cc=zhangckid@gmail.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.