Nota Técnica: Mensajes de error de VMotion

Todos los hemos sufrido en alguna que otra ocasión, en especial cuando queremos presumir de VMotion, por aquello delefecto demo: Los famosos errores de VMotion. VMotion es la capacidad de VI3 ara mover en vivo una máquina virtual de un host a otro. Como requerimiento tenemos la presencia de un Virtual Center (VMotion NO puede hacerse sin él), la existencia de un Virtual Switch habilitado para el mismo, el almacenamiento compartido, y cumplir unos mínimos requerimientos para evitar situaciones de fallo, esto es:

• Red de vMotion dedicada: No usemos trunks 802.1q para la red de vMotion. Ethernet es un protocolo orientado a pérdidas - usemos o no switches - y cuanto más tráfico, más posibilidades de fallo, así que aislemos el tráfico vMotion.
• Red de almacenamiento adecuada: Usemos lo que usemos, iSCSI, NFS o FC, procuremos que la red sea lo más adecuada posible. Si nos decidimos por iSCSI, el vSwitch debe ser dedicado. Si escogemos NFS, tres cuartos de lo mismo.

El cumplir estos requisitos no evitará que puedan aparecer errores. A continuación cito los remarcados por VMware (quien quiera puede obtener el kb desde aquí)

Mensajes de compatibilidad de CPU.

• Unable to migrate from to : The CPU of the host is incompatible with the CPU feature requirements of the virtual machine; problem detected at CPUID level 0×80000001 register ‘edx’. KB de VMware asociado: Troubleshooting VMotion CPU feature requirement error messages (1003718).
  
• Unable to migrate from to : The CPU of the host is incompatible with the CPU feature requirements of the virtual machine; problem detected at CPUID level 0×80000001 register ‘ecx’. KB de VMware asociado: Troubleshooting VMotion CPU feature requirement error messages (1003718).
  
• Unable to migrate from to : The CPU of the host is incompatible with the CPU feature requirements of the virtual machine; problem detected at CPUID level 0×1 register ‘ecx’. KB de VMware asociado: Troubleshooting VMotion CPU feature requirement error messages (1003718).
  
• Unable to migrate from to : The CPU of the host is incompatible with the CPU feature requirements of the virtual machine; problem detected at CPUID level 0×1 register ‘edx’. KB de VMware asociado: Troubleshooting VMotion CPU feature requirement error messages (1003718).

Respecto a estos errores, mi granito de arena: VMware no virtualiza la CPU, lo que implica que la VM la ve tal y como es: Con sus características específicas. Este tipo de errores aparecen cuando se intenta migrar entra distintas generaciones de CPU de un mismo fabricante, o entre fabricantes distintos. El documento que se indica suministra información de cómo limitar el impacto de las diferencias de arquitectura entre generaciones de procesadores. Yo tengo algún DRS donde conviven 3 generaciones de Opteron: D, E y F, y con pequeños ajustes, hacen VMotion entre ellos sin problemas. No es necesario asustarse. Enmascarar características de las CPU para evitar estos errores es sencillo, aunque laborioso si se desea un ajuste fino.

• Unable to migrate from to : Virtual Machine has 2 virtual CPUs, but the host software only supports 1. KB de VMware asociado: Troubleshooting migration compatibility error: Virtual machine has 2 virtual CPUs but the host software only supports 1 (1003741).
  
• Migration from to : Migration will cause the virtual machine’s configuration to be modified, to preserve the feature requirements for its guest OS. KB de VMware asociado: 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).

Mensajes relacionado con la configuración de dispositivos.

• Unable to migrate from to : Virtual Machine is configured to use a device that prevents migration: Device ‘’ is a connected device with a remote backing. KB de VMware asociado: Troubleshooting migration compatibility error: Device is a connected device with a remote backing (1003780).
  
• Unable to migrate from to : Currently connected device ‘’ uses backing ‘’, which is not accessible. KB de VMware asociado: Troubleshooting migration compatibility error: Currently connected device uses backing which is not accessible (1003787).
  
• Unable to migrate from to : Device ‘’ uses backing ‘’, which is not accessible. KB de VMware asociado: Troubleshooting migration compatibility warning: Device uses backing which is not accessible (1003794).
  

Mensajes relacionados con la configuración del Disco.

• Unable to migrate from to : Unable to access the virtual machine configuration: Unable to access file. [] . KB de VMware asociado: Troubleshooting migration compatibility error: Unable to access the virtual machine configuration: Unable to access file (1003795).
  
• Unable to migrate from to : Virtual machine is configured to use a device that prevents migration: Device ‘’ is a SCSI controller engaged in bus-sharing. KB de VMware asociado: Troubleshooting migration compatibility error: Device is a SCSI controller engaged in bus-sharing (1003797).

Más granito de arena con ejemplo práctico: Un cluster virtual NO MIGRA!!!

• Migration from to : Reverting to snapshot would generate error (warnings) on the destination host. KB de VMware asociado: Troubleshooting migration compatibility warning: Reverting to snapshot would generate error (warnings) on the destination host (1003800).

Este es de los buenos. Básicamente VMware no recomienda hacer vMotion de máquinas con Snapshot, advirtiendo que la máquina puede caerse cuando la migración se completa. Entiéndanse las cursiva/negrita como ironía.

Mensajes relacionados con la configuración del ESX:

• Migration from : No guest OS heartbeats are being received. Either the guest OS is not responding or VMware tools is not configured properly. KB de VMware asociado: Troubleshooting Migration compatibility warning: No guest OS heartbeats are being received (1003805).
  
• Unable to migrate from to : The VMotion interface is not configured (or is misconfigured) on the destination host ‘’. KB de VMware asociado: Troubleshooting Migration compatibility error: The VMotion interface is not configured (or is misconfigured) on the destination host (1003827).
  
• Unable to migrate from to : VMotion from source host to destination host is unsupported because of VMotion protocol differences. KB de VMware asociado: Troubleshooting Migration compatibility error: VMotion from source host to destination host is unsupported because of VMotion protocol differences (1003828).
  
• Unable to migrate from to : The operation is not allowed in the current state. KB de VMware asociado: Troubleshooting Migration compatibility error: The operation is not allowed in the current state (1003829).
  

Mensajes relacionados con la configuración de red de vMotion:

• Unable to migrate from to : Currently connected network interface ‘’ uses network ‘’, which is not accessible. KB de VMware asociado: Troubleshooting Migration compatibility error: Currently connected network interface uses network, which is not accessible (1003830).
  
• Unable to migrate from to : Currently connected network interface ‘’ uses network ‘’, which is a ‘virtual intranet’. KB de VMware asociado: Troubleshooting Migration compatibility error: Currently connected network interface uses network, which is a virtual intranet (1003832).
  
• Unable to migrate from to : Currently connected network interface ‘’ uses network ‘’, which is configured for different offload or security policies on the destination host than on the source host. KB de VMware asociado: Troubleshooting Migration compatibility error: Currently connected network interface uses network, which is configured for different offload or security policies (1003834).
  
• Migration from to : The VMotion interface of the destination host uses network ‘’, which differs from the network ‘’ used by the VMotion interface of the source host. KB de VMware asociado: 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).

Mensajes relacionados con la configuración de los recursos de VMotion.

• Unable to migrate from to : Virtual machine has CPU and/or memory affinities configured, preventing VMotion. KB de VMware asociado: Troubleshooting Migration compatibility error: Virtual machine has CPU and/or memory affinities configured, preventing VMotion (1003842).
  
• Unable to migrate from to and pool : Insufficient memory resources. KB de VMware asociado: Troubleshooting Migration compatibility error: Unable to migrate: Insufficient memory resources (1003855).

Un saludo