"vMotion failed. No target host could be choosen after vMotion compatibility checks. The target host does not support the virtual machine's current hardware requirements. com.vmware.vim.vmfeature.misc.rdcl_no:RDCL_NO is not supported. com.vmware.vim.vmfeature.misc.ibrs_all:IBRS_ALL is not supported. com.vmware.vim.vmfeature.misc.rsba_no:RSBA_NO is not supported. com.vmware.vim.vmfeature.misc.mds_no:MDS_NO is not supported. com.vmware.vim.vpxd.vmcheck.featureRequirementsNotMet.useClusterOrPerVmEvc:Use a cluster with Enhanced vMotion Compatibility (EVC) enabled to create a uniform set of CPU features across the cluster, or use per-VM EVC for a consistent set of CPU features for a virtual machine and allow the virtual machine to be moved to a host capable of supporting that set of CPU features. "
HCX 4.11.0
Source and destination ESXi hosts are using different generations of CPUs.
This behavior is expected as, like vMotion, source and destination ESXi hosts are required to present the same CPU generation feature set.
To perform HCX RAV migration, enable EVC in vCenter or configure EVC mode per VM: