Simple definition
VMware vMotion moves a powered-on virtual machine from one ESXi host to another without a planned guest shutdown. It supports host maintenance, workload balancing and operational flexibility, usually with an imperceptible or very brief interruption depending on configuration and workload.
Technical definition
During vMotion, the execution state of the VM, including memory and CPU-related state, is transferred to the destination host. Memory pages are commonly copied in passes while the guest continues running, followed by a short switchover to synchronize final changes. CPU compatibility and network connectivity matter. Moving virtual disks is handled by Storage vMotion or supported combined migration scenarios when storage is not shared.
What is it used for?
Evacuate an ESXi host for planned maintenance, balance resource consumption and reorganize workloads while keeping applications online. vMotion is not a guarantee against sudden host failure and is not a replacement for high availability.
Practical example
An administrator must update one ESXi cluster host. After checking capacity, networks and CPU compatibility, the administrator moves the running VMs to other hosts, performs maintenance and later balances workloads. The applications generally remain online while migration completes.
Common issues
- Missing or misconfigured vMotion VMkernel networking and insufficient bandwidth.
- Destination host lacking enough CPU, memory or storage access.
- CPU compatibility or EVC configuration preventing migration.
- Destination unable to access the VM's datastore or intended virtual network.
- Particular devices or high memory-write workloads complicating migration.
How live migration transfers a running VM
vMotion transfers execution state over a host-to-host migration network. Iterative copying of memory pages reduces the time during which the VM must be briefly paused for the final switchover. The destination host then resumes the VM with its intended virtual network connectivity.
Moving a guest's execution state differs from transferring its disk files. Classic vMotion often leaves virtual disks on shared storage; Storage vMotion moves disk files. Certain VMware platform versions and scenarios support combined migrations.
Requirements: CPU compatibility, networking and storage
Hosts need supported migration capabilities, appropriate VMkernel interfaces and sufficient network throughput. CPU compatibility requirements, sometimes addressed using Enhanced vMotion Compatibility (EVC), affect whether a guest can resume on the destination.
The target also needs access to the required virtual networks and storage plus sufficient compute resources. Migration failure does not necessarily mean the VM itself is unhealthy; diagnosis involves vCenter or ESXi events, host settings and network paths.
vMotion vs HA vs replication
vMotion performs planned live migration. VMware High Availability (HA) is designed to restart workloads on surviving hosts after certain failures and may involve downtime. Replication keeps a secondary copy of workloads or storage for different recovery scenarios.
Successful live migration does not remove the need for disaster recovery capacity and verified backups. Each mechanism addresses different failure and maintenance risks.
Related terms
Key takeaway: vMotion performs planned live migration between compatible ESXi hosts. It is neither a backup nor a guarantee of zero downtime, and it is different from VMware HA.