vMotion has the following requirements, specifically shared storage and cpu compatibility between hosts:
To be configured for VMotion, each host in the cluster must meet the following
Ensure that the managed hosts use shared storage. Shared storage is typically on a
storage area network (SAN), but can also be implemented using iSCSI and NAS shared
storage. See the VMware SAN Configuration Guide for additional information on SAN
and the Server Configuration Guide for information on other shared storage.
Shared VMFS Volume or NAS Storage
Configure all managed hosts to use shared VMFS volumes or to be located on NAS
storage. If using shared VMFS volumes:
– Place the disks of all virtual machines on VMFS volumes that are accessible by both
source and target hosts.
– Ensure that the VMFS volume is sufficiently large to store all virtual disks for your
Make sure that the source and destination hosts have a compatible set of processors.
VMotion transfers the running architectural state of a virtual machine between
underlying VMware ESX Server systems. VMotion compatibility requires that the
processors of the target host be able to resume execution using the equivalent
instructions that the processors of the source host were using when suspended.
Processor clock speeds and cache sizes, and the number of processor cores may vary,
but processors must come from the same vendor class (Intel or AMD) and same
processor family (P3, P4, or Intel core) to be compatible for migration with VMotion.
Processor families such as Intel Xeon and AMD Opteron are defined by the processor
1 VMotion requires a Gigabit Ethernet network to ensure rapid migration:
– A dedicated network is recommended to keep virtual machine memory state
– VMotion requires a private Gigabit Ethernet migration network between all of
the VMotion‐enabled managed hosts. When VMotion is enabled on a
managed host, configure a unique network identity object for the managed
host and connect it to the private migration network.
– Two hosts with cross‐connected GigE cards can be used for demo purposes.
2 Virtual machines must have access to the same subnets on the source and
destination ESX Server hosts.
3 Network labels for each virtual NIC must be created through the ESX Server
– Network labels are global across datacenters.
– VMotion automatically maps virtual machines to appropriate virtual NICs
based on network labels.
– For ESX Server 2.x hosts, network labels can be configured through the
Web‐based VMware Management Interface.
Minimum Network Requirements
– Two NICs with at least one GigE NIC dedicated to VMotion.