This is an expected behavior in a mixed VMware vSphere/vDS version environment as compatibility checks require the source and destination vDS are of the same version.
For cross vDS vMotion to be successful, the source and destination vDS should be on the same version.
To resolve this issue, ensure the source and destination vDS are of the same version.
For example:
- Source vDS version 6.0.0 vMotion to destination vDS version 6.0.0
- Source vDS version 6.5.0 vMotion to destination vDS version 6.5.0
Workaround:
There are 2 available options to work around this issue:
- Workaround 1: When cross migrating VMs from a source vSphere 6 cluster to a destination vSphere 6.5 cluster, a standard vSwitch can be created on the vSphere 6.5 cluster. VMs on the source 6.0 cluster must also be migrated to a standard switch to provide a supported migration path. Afterwards, the VMs can be migrated to the vDS that is on version 6.5.
- Workaround 2: When cross migrating VMs from a source vSphere 6 cluster to a destination vSphere 6.5 cluster, a vDS of the version 6.0.0 can be created on the destination vSphere 6.5 cluster. After a successful VM migration, the vDS version 6.0.0 can be upgraded to version 6.5.0.