When performing bulk cold migrations for powered-off virtual machines using the Advanced Cross vCenter vMotion feature, all VMs are unexpectedly placed on a single destination ESXi host (typically the first host in the cluster's inventory) instead of being distributed across the destination cluster.
VMware vCenter Server 8.0
VMware vCenter 9.x
This issue occurs because the relocation request generated by the Advanced Cross vCenter vMotion UI inadvertently sets the same specific destination host for all powered-off VMs in the batch.
Consequently, the vpxd service processes the request exactly as instructed and migrates all VMs to that single host.
VMware by Broadcom is aware of this issue and is currently working on a resolution.
Workaround:
Manually distribute the workload by selecting different destination hosts for the powered-off VMs during the migration setup, or manually migrate the VMs to other hosts in the cluster after the initial Advanced Cross vCenter vMotion completes.