On esxi hosts with iscsi only we persistently get xcopyused=1, on esxi hosts with iscsi+fc we get inconsistent xcopyused 1/0 results. Attempted to migrate same VM on mixed hosts (iscsi+fc) xcopyused=0, same Vm on an iSCSI hosts only xcopyused=1. Attached populator logs, granted the VM had two disks but it doesn't matter we see the issue without adding two populator logs from each host. 

ocp 4.20
cnv 2.10
mtv:211

We're not sure yet, 

1. Set up copy-offload for NetApp ONTAP with iSCSI protocol
2. Migrate a VM from ESXi host that has both FC and iSCSI HBAs
3. Observer populator log may repot xcopyUsed=0, migrations may resort to fallback method.
4. vmware migrate the VM to an ESXi host with only iSCSI (no FC HBAs)Migrate again - observe that xcopyUsed=true.

Host with FC+iSCSI: xcopyUsed=0 (or 1) XCOPY isn't used consistently.
While on host with iSCSI only: xcopyUsed=true (XCOPY works more consistently)

XCOPY should work regardless of whether the ESXi host has FC HBAs in addition to iSCSI adaptors.

Evidence, attached logs showing:

Failed case (host-12642 with FC+iSCSI):
HBA UIDs found: [fc.2000f4e9d45532b6:2100f4e9d45532b6 fc.2000f4e9d45532b7:2100f4e9d45532b7 iqn.1998-01...]failed adding host to igroup [409] - conflicts with FC initiatorsxcopyUsed: false (throughout entire migration)

Success case (host-64 with iSCSI only):
HBA UIDs found: [iqn.1998-01.com.vmware:ecoesxi01...]xcopyUsed: false initially, then changes to true at 54% progress

Suspected Root Cause:When ESXi has both FC and iSCSI adapters, the populator code collects ALL adapter UIDs (FC WWNs + iSCSI IQNs) and attempts to add them to the xcopy initiator group. NetApp returns 409 errors when adding FC WWNs (likely already mapped in different igroups). This may cause the LUN mapping to the xcopy initiator group to fail or be inconsistent, resulting in XCOPY not being available for the vmkfstools operation.