All of lore.kernel.org
 help / color / mirror / Atom feed
From: Peter Xu <peterx@redhat.com>
To: Zhang Chen <zhangckid@gmail.com>
Cc: Lukas Straub <lukasstraub2@web.de>,
	qemu-devel@nongnu.org, Fabiano Rosas <farosas@suse.de>,
	Laurent Vivier <lvivier@redhat.com>,
	Paolo Bonzini <pbonzini@redhat.com>,
	Juan Quintela <quintela@trasno.org>,
	Hailiang Zhang <zhanghailiang@xfusion.com>
Subject: Re: [PATCH 0/3] migration: Add COLO multifd support and COLO migration unit test
Date: Tue, 6 Jan 2026 14:48:14 -0500	[thread overview]
Message-ID: <aV1m_vneDzI_5WDV@x1.local> (raw)
In-Reply-To: <CAK3tnv+f8b9fd_n9_6Od3f__ZuNUtuT2Q_MXszam_k=ooRPqyQ@mail.gmail.com>

On Sun, Jan 04, 2026 at 01:44:52PM +0800, Zhang Chen wrote:
> On Tue, Dec 30, 2025 at 11:02 PM Peter Xu <peterx@redhat.com> wrote:
> >
> > 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,
> >
> 
> Hi Lukas and Peter,

Hi, Chen,

> 
> Thanks for this series, I will support for background info if Peter
> have any questions.

Thanks, I believe my major question so far was, whether we should deprecate
COLO in migration framework. :)

The netfilters and rest can be discussed separately.

Now looking back at my initial ask in Zhijian's fix, I still agree with
Zhijian on these two points mentioned:

https://lore.kernel.org/all/b2eadde7-57e9-426c-8487-e500ba06410e@fujitsu.com/

That is:

        - Active users who depend on it.
        - A unit test for the COLO framework.

Meanwhile, I can't see how COLO would win if to be compared with some
app-level HA infrastructure.. considering the overhead it requires on
running two VMs and compare every packet.

Lukas, thanks for trying to fix the 2nd.  I apologize that I still
requested you to send these patches, without further raising the attention
that I still want to discuss deprecation.  I don't think anyone yet proved
we should keep COLO.  I do plan to send one patch adding COLO framework to
deprecation, if nobody would stop me in a week justifying question 1 above.

We kind of proved almost nobody is actively using COLO anymore in the past
few releases.  If nobody is using COLO, we should simply drop it.

> And CC Hailiang Zhang, although he hasn't replied to emails for a long time.
> If no one objects, I think Lukas can replease Hailiang for COLO Framework.
> 
> COLO Framework
> M: Hailiang Zhang <zhanghailiang@xfusion.com>
> S: Maintained
> F: migration/colo*
> F: include/migration/colo.h
> F: include/migration/failover.h
> F: docs/COLO-FT.txt

Right, this is also another reason why I think we may want to deprecate
COLO framework.

Since I requested this series (sorry again, Lukas), I'll review it today no
matter if we decide to merge this series at last, or deprecate COLO
framework.

Thanks,

> 
> Thanks
> Chen
> 
> > >
> > > 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
> >
> 

-- 
Peter Xu



  parent reply	other threads:[~2026-01-06 19:49 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 ` [PATCH 0/3] migration: Add COLO multifd support and " Peter Xu
2026-01-04  5:44   ` Zhang Chen
2026-01-04  5:48     ` Zhang Chen
2026-01-06 19:48     ` Peter Xu [this message]
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=aV1m_vneDzI_5WDV@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 \
    --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.