diff options
author | Vladimir Sementsov-Ogievskiy <vsementsov@yandex-team.ru> | 2023-04-28 22:49:21 +0300 |
---|---|---|
committer | Juan Quintela <quintela@redhat.com> | 2023-05-10 18:48:11 +0200 |
commit | 51e47cf8600dab5beedd7fa369ffd645868672ec (patch) | |
tree | 52208e5730399377b8cb2f247a7fe129da691515 /trace/qmp.c | |
parent | 4332ffcd7b21f7391fef1d916e1e3cd5b4bdd268 (diff) | |
download | qemu-51e47cf8600dab5beedd7fa369ffd645868672ec.zip qemu-51e47cf8600dab5beedd7fa369ffd645868672ec.tar.gz qemu-51e47cf8600dab5beedd7fa369ffd645868672ec.tar.bz2 |
build: move COLO under CONFIG_REPLICATION
We don't allow to use x-colo capability when replication is not
configured. So, no reason to build COLO when replication is disabled,
it's unusable in this case.
Note also that the check in migrate_caps_check() is not the only
restriction: some functions in migration/colo.c will just abort if
called with not defined CONFIG_REPLICATION, for example:
migration_iteration_finish()
case MIGRATION_STATUS_COLO:
migrate_start_colo_process()
colo_process_checkpoint()
abort()
It could probably make sense to have possibility to enable COLO without
REPLICATION, but this requires deeper audit of colo & replication code,
which may be done later if needed.
Signed-off-by: Vladimir Sementsov-Ogievskiy <vsementsov@yandex-team.ru>
Acked-by: Dr. David Alan Gilbert <dave@treblig.org>
Reviewed-by: Juan Quintela <quintela@redhat.com>
Message-Id: <20230428194928.1426370-4-vsementsov@yandex-team.ru>
Signed-off-by: Juan Quintela <quintela@redhat.com>
Diffstat (limited to 'trace/qmp.c')
0 files changed, 0 insertions, 0 deletions