Knowledge Base

Overview

CPU compatibility messages

• Unable to migrate from <source server> to <destination server>: The CPU of the host is incompatible with the CPU feature requirements of the virtual machine; problem detected at CPUID level 0x80000001 register 'edx' . For more information on this error, see Troubleshooting VMotion CPU feature requirement error messages (1003718) .
  
  
• Unable to migrate from <source server> to <destination server>: The CPU of the host is incompatible with the CPU feature requirements of the virtual machine; problem detected at CPUID level 0x80000001 register 'ecx' . For more information on this error, see Troubleshooting VMotion CPU feature requirement error messages (1003718) .
  
  
• Unable to migrate from <source server> to <destination server>: The CPU of the host is incompatible with the CPU feature requirements of the virtual machine; problem detected at CPUID level 0x1 register 'ecx' . For more information on this error, see Troubleshooting VMotion CPU feature requirement error messages (1003718) .
  
  
• Unable to migrate from <source server> to <destination server>: The CPU of the host is incompatible with the CPU feature requirements of the virtual machine; problem detected at CPUID level 0x1 register 'edx' . For more information on this error, see Troubleshooting VMotion CPU feature requirement error messages (1003718) .
  
  
• Unable to migrate from <source server> to <destination server>: Virtual Machine has 2 virtual CPUs, but the host software only supports 1 . For more information on this error, see Troubleshooting migration compatibility error: Virtual machine has 2 virtual CPUs but the host software only supports 1 (1003741) .
  
  
• Migration from <source server> to <destination server>: Migration will cause the virtual machine's configuration to be modified, to preserve the feature requirements for its guest OS . For more information on this error, see Troubleshooting migration compatibility warning: Migration will cause the virtual machine's configuration to be modified, to preserve the feature requirements for its guest OS (1003770) .
  

Device configuration messages

• Unable to migrate from <source server> to <destination server>: Virtual Machine is configured to use a device that prevents migration: Device '<device>' is a connected device with a remote backing. For more information on this error, see Troubleshooting migration compatibility error: Device is a connected device with a remote backing (1003780) .
  
  
• Unable to migrate from <source server> to <destination server>: Currently connected device '<device>' uses backing '<device>', which is not accessible . For more information on this error, see Troubleshooting migration compatibility error: Currently connected device uses backing which is not accessible (1003787) .
  
  
   
• Unable to migrate from <source server> to <destination server>: Device '<device>' uses backing '<device>', which is not accessible . For more information on this error, see Troubleshooting migration compatibility warning: Device uses backing which is not accessible (1003794) .
  

Disk configuration

• Unable to migrate from <source server> to <destination server>: Unable to access the virtual machine configuration: Unable to access file. [<datastore>] <file>. For more information on this error, see Troubleshooting migration compatibility error: Unable to access the virtual machine configuration: Unable to access file (1003795) .
  
  
• Unable to migrate from <source server> to <destination server>: Virtual machine is configured to use a device that prevents migration: Device '<device>' is a SCSI controller engaged in bus-sharing . For more information on this error, see Troubleshooting migration compatibility error: Device is a SCSI controller engaged in bus-sharing (1003797) .
  
  
• Migration from <source server> to <destination server>: Reverting to snapshot would generate error (warnings) on the destination host . For more information on this error, see Troubleshooting migration compatibility warning: Reverting to snapshot would generate error (warnings) on the destination host (1003800) .
  

General ESX Server configuration messages

• Migration from <source server>: No guest OS heartbeats are being received. Either the guest OS is not responding or VMware tools is not configured properly . For more information on this error, see Troubleshooting Migration compatibility warning: No guest OS heartbeats are being received (1003805) .
  
  
• Unable to migrate from <source server> to <destination server>: The VMotion interface is not configured (or is misconfigured) on the destination host '<destination server>' . For more information on this error, see Troubleshooting Migration compatibility error: The VMotion interface is not configured (or is misconfigured) on the destination host (1003827) .
  
  
• Unable to migrate from <source server> to <destination server>: VMotion from source host to destination host is unsupported because of VMotion protocol differences . For more information on this error, see Troubleshooting Migration compatibility error: VMotion from source host to destination host is unsupported because of VMotion protocol differences (1003828) .
  
  
• Unable to migrate from <source server> to <destination server>: The operation is not allowed in the current state . For more information on this error, see Troubleshooting Migration compatibility error: The operation is not allowed in the current state (1003829) .
  

Networking configuration messages

• Unable to migrate from <source server> to <destination server>: Currently connected network interface '<device>' uses network '<network>', which is not accessible . For more information on this error, see Troubleshooting Migration compatibility error: Currently connected network interface uses network, which is not accessible (1003830) .
  
  
• Unable to migrate from <source server> to <destination server>: Currently connected network interface '<device>' uses network '<network>', which is a 'virtual intranet'. For more information on this error, see Troubleshooting Migration compatibility error: Currently connected network interface uses network, which is a virtual intranet (1003832) .
  
  
• Unable to migrate from <source server> to <destination server>: Currently connected network interface '<device>' uses network '<network>', which is configured for different offload or security policies on the destination host than on the source host . For more information on this error, see Troubleshooting Migration compatibility error: Currently connected network interface uses network, which is configured for different offload or security policies (1003834) .
  
  
• Migration from <source server> to <destination server>: The VMotion interface of the destination host uses network '<network 0>', which differs from the network '<network 1>' used by the VMotion interface of the source host . For more information on this error, see Troubleshooting migration compatibility warning: The VMotion interface of the destination host uses network, which differs from the network used by the VMotion interface of the source host (1003841) .
  

Resource configuration messages

• Unable to migrate from <source server> to <destination server>: Virtual machine has CPU and/or memory affinities configured, preventing VMotion . For more information on this error, see Troubleshooting Migration compatibility error: Virtual machine has CPU and/or memory affinities configured, preventing VMotion (1003842) .
  
  
• Unable to migrate from <source server> to <destination server> and pool <Resource Pool>: Insufficient memory resources . For more information on this error, see Troubleshooting Migration compatibility error: Unable to migrate: Insufficient memory resources (1003855) .