On 12/13/22 14:26, Christian Borntraeger wrote:
Am 08.12.22 um 10:44 schrieb Pierre Morel:
The migration can only take place if both source and destination
of the migration both use or both do not use the CPU topology
facility.
We indicate a change in topology during migration postload for the
case the topology changed between source and destination.
I dont get why we need this? If the target QEMU has topology it should
already create this according to the configuration. WHy do we need a
trigger?
We do not.
The first idea was to migrate the topology with a dedicated object but
after today discussion, it will be recreated by the admin on the target
and the MTCR will not be migrated but simply set to 1 on target start.
So next spin will not get migration included.
Regards,
Pierre
--
Pierre Morel
IBM Lab Boeblingen
