> -----Original Message-----
> From: Fabiano Rosas <faro...@suse.de>
> Sent: Thursday, April 11, 2024 10:40 PM
> To: Zhang, Hailiang <zhanghaili...@xfusion.com>; Zhang, Chen
> <chen.zh...@intel.com>; Li Zhijian <lizhij...@fujitsu.com>
> Cc: qemu-devel@nongnu.org; Peter Xu <pet...@redhat.com>
> Subject: COLO state?
>
> Hi COLO maintainers,
>
> Would you please take a look at this issue?
>
> https://gitlab.com/qemu-project/qemu/-/issues/2277
>
Sure, please share more details in gitlab of your test. For example the
primary/secondary VM boot scripts and the backtrace...etc...
> The reporter claims it affects from 9.0-rc2 all the way back to QEMU 7.2. I
> don't have any kind of setup for COLO, so it will take me a while to be able
> to
> verify this.
>
> Could you also provide clarification on what is the state of COLO these days?
> Are any of you looking at it? Do we know of active users of the feature?
Currently, all the COLO code already merged by QEMU. But there is no support
for libvirt (Need to passthrough QMP command to QEMU for enable COLO).
Any users can use the WIKI page(https://wiki.qemu.org/Features/COLO) to setup
COLO based on upstream code.(Maybe have issues? I will double check it... ).
As we know, many cloud services provider build there HA/FT system or products
based on COLO project.
>
> Also, is the MAINTAINERS file reflecting the actual maintenance state
> according to you?
I will check w/ Hailiang/Zhijian/Congyang/Changlong(Block replication) to see
if he will keep working on COLO or not.
Thanks
Chen
>
> COLO Framework
> M: Hailiang Zhang <zhanghaili...@xfusion.com>
> S: Maintained
> F: migration/colo*
> F: include/migration/colo.h
> F: include/migration/failover.h
> F: docs/COLO-FT.txt
>
> COLO Proxy
> M: Zhang Chen <chen.zh...@intel.com>
> M: Li Zhijian <lizhij...@fujitsu.com>
> S: Supported
> F: docs/colo-proxy.txt
> F: net/colo*
> F: net/filter-rewriter.c
> F: net/filter-mirror.c
> F: tests/qtest/test-filter*
>
> Thanks
