VMware Cloud Community

vCenter does not support hosts of this type ( ). when attempting to import vm from another vcenter.

Getting "vCenter does not support hosts of this type ( )." when attempting to import vm from another vcenter.

Unsure what is causing this. Anyone have any ideas?

More info...

Destination vCenter ( does not support hosts of this type ( ). when attempting to import vm from another vcenter (

Destination ESXi, 7.0.3, 20036589

Source ESXi, 7.0.2, 19290878


0 Kudos
3 Replies

Solution 1. Check the license for vMotion

Although vMotion is integrated with vSphere, it still needs a license. If there is no corresponding license, you might see the error message: vMotion is not licensed on this host.

To make sure ESXi is licensed for vMotion, you could check the license status:

Log into vCenter via vSphere client > select the ESXi host > click Configuration > click Licensed Features > check whether vMotion is supported

Solution 2. Run the same version of ESXi on both hosts

The hosts must be running ESXi 5.1 or later. If the VM is created on an ESXi host of the latest version, and you would like to migrate it to a host of the previous ESXi, the migration might fail.

To exclude this cause, it is suggested to upgrade the old ESXi to a higher ESXi on the host. It would be best to have the same version of ESXi on both hosts.

Solution 3. Keep the same CPU on both ESXi hosts

Hardware configuration would be checked during the vMotion process. If the target host has a different CPU configuration from the source host, or the CPU of the target host is not as good as the source host's, the migration process might be influenced.

Therefore, you should check the CPU of both hosts. If they are different configurations, at least make sure the target hosts is better, or you need to find another target host in the cluster.

Solution 4. Check the VM belongs to which cluster

Normal vMotion just supports migrating VM on the same vCenter. If the destination host is on another vCenter, you need to perform cross vCenter vMotion (vSphere 6.0 or later versions) or Advanced Cross vCenter vMotion (vSphere 7.0 or later versions) to migrate VM.

You need to upgrade vSphere and have the Enterprise Plus license to perform cross-vCenter migration. Check the license as in solution 1.

The process of Cross vCenter vMotions is like the process of normal vMotion. Just select the VM in vCenter and then select Cross vCenter Server export. You would be guided to complete the following steps by the wizard.

If you don't have a license, you must perform a normal cold migration or use another way in the last section of this passage.

Solution 5. Check the network configuration

If there are network issues, you might see the error messages like "Currently connected network interface 'Network adapter 1' uses network 'VM Network'."

You need to check the network configuration by reviewing the configuration in VM Network Properties. Users have reported that they fix the issue by unticking Promiscuous Mode in VM Network Properties.

The possible causes of failed vMotion might be related to the license, ESXi version, hardware resources, VM position, network configuration, etc. 


One more thing from me, mark my reply as a solution. Thx 🙂

0 Kudos

use vc ip, not FQDN.
0 Kudos