This wraps up our 3-post series on VMware vSphere troubleshooting.
Cannot Migrate a Virtual Machine Using VMotion
Check the ESX(i) hosts to make sure all of the requirements are met. Then check to make sure that the CPU is compatible. CPU compatibility is important in VMware, and, if this is a problem, you might have to enable EVC to allow the feature set of both host CPUs to match. This can solve minor incompatibility issues.
If the virtual machine runs a 64-bit operating system, the problem might be that the source machine has Intel Virtualization Technology (VT) enabled in the BIOS, and the destination host does not have VT enabled in the BIOS. If this is the case then you have to make a change in the BIOS so both hosts match.
Also, both hosts must have a VMkernel port on the same LAN. The IP address and subnet mask should match the network configuration for VMKernel gateway.
You could run from command line:
# vmkping <Destination_IP _address> to test the VMkernel TCP/IP stack.
Any VLAN settings should match the VLAN configuration of the local LAN. VMkernel ports should have the check box VMotion enabled. There should be no router separating the hosts.
- Check the virtual machines to make sure all of the requirements have been met
- Check that there are no local devices connected to the virtual machine
- Check CD-ROM mappings to any ISO file on local storage, Floppy, SCSI, USB, CPU affinity, .vswp files stored on local storage
- Check that the virtual machine has enough CPU and memory resources on the destination host
Another thing to look for is that the virtual machine fully powered on. To check the status of the virtual machine, simply open the console in vSphere to make sure the VM is fully powered on.
Problem Performing Storage VMotion
The first thing to check is does the virtual machine have a snapshot? Since Storage VMotion utilizes snapshots, one of the requirements to perform Storage VMotion is that the virtual machine cannot have a snapshot. Use the vSphere client to check for snapshots.
This post is excerpted and reused with permission from 8 tips for Troubleshooting VMware vSphere