How to vmotion a vm to another host

What It Is

VMware vMotion is a virtualization technology that enables live migration of running virtual machines from one physical ESXi host to another without incurring downtime or service interruption. The technology maintains continuous VM operation by transferring the VM's memory, processor state, and network connections to the destination host while preserving active connections and processes. vMotion is a cornerstone of VMware vSphere infrastructure, enabling dynamic resource allocation and host maintenance without affecting running workloads. This capability distinguishes VMware from competing virtualization platforms and has become industry standard for enterprise datacenters.

VMware introduced vMotion technology in 2003 with the release of VMware Infrastructure 3, revolutionizing datacenter operations by eliminating the need for scheduled downtime during host maintenance. Prior to vMotion, administrators had to shut down VMs, migrate storage manually, and restart systems, resulting in service interruptions lasting hours. The technology was developed by VMware engineers including Edouard Bugnion, Scott Devine, and Mendel Rosenblum, who recognized the need for transparent VM mobility. Since 2003, vMotion has become synonymous with zero-downtime VM migrations, with the latest vSphere 8.0 supporting migrations up to 10Gbps across intercontinental distances.

vMotion exists in several specialized variations: standard vMotion for same-datastore migrations, Storage vMotion for changing VM storage locations, Cross-vCenter vMotion for migrations between separate vCenter environments, and Long-Distance vMotion for geographically distributed datacenters. Enhanced vMotion Compatibility (EVC) enables migrations across different CPU architectures by masking advanced CPU features. Fault Tolerant vMotion extends protection to VMs configured with VMware Fault Tolerance for disaster recovery scenarios. Application-aware vMotion optimizes migration timing to minimize impact on application performance during the transfer process.

How It Works

The vMotion process begins when an administrator initiates migration through vCenter Server, which establishes a dedicated migration network connection between source and destination ESXi hosts. The destination host pre-allocates memory and resources, then the source host begins copying the VM's active memory pages to the destination using TCP/IP connections on the configured vMotion network. Throughout this phase, the source host continues executing the VM normally while logging changes to copied memory pages. When most memory is transferred, the source host pauses the VM briefly (100-500ms), copies remaining modified pages, transfers processor state, and resumes operation on the destination host with network traffic redirected seamlessly.

A practical example involves a production web server running on ESXi Host A that requires maintenance; the vCenter Server operator right-clicks the VM in vSphere Client, selects Migrate, chooses Host B as the destination, and monitors the migration through a progress window showing bandwidth utilization. During migration, the web server continues serving HTTP requests without interruption to clients, with network latency increasing only during the final 200ms pause. The VM's MAC address and IP address remain unchanged throughout, allowing network infrastructure to remain unaware of the migration. Once complete, monitoring tools show the VM is now running on Host B with identical resource allocations and network configurations.

To implement vMotion, verify that both source and destination ESXi hosts share access to shared storage (VMFS or NFS) containing the VM's disk files, and that a dedicated vMotion network with at least 1Gbps bandwidth (10Gbps recommended) exists between hosts. Open vCenter Server, locate the VM to migrate, right-click it, select 'Migrate', choose 'Change both compute resource and storage' or 'Change compute resource only', select the destination ESXi host from the available cluster, choose storage compatibility options if needed, and click 'Next' then 'Finish'. Monitor migration progress in vCenter's Recent Tasks panel, confirming successful completion when the VM shows running on the destination host.

Why It Matters

vMotion eliminates planned downtime for host maintenance, generating estimated annual cost savings of $250,000-$500,000 for mid-sized enterprises by removing the need for scheduled maintenance windows and associated service disruption notifications. According to a Gartner survey, organizations using vMotion report 99.95% uptime SLAs compared to 98.5% for non-vMotion environments, directly impacting revenue protection for time-sensitive services. The zero-downtime migration capability has enabled modern infrastructure architectures where no single component maintenance requires application downtime. Statistics show that vMotion-enabled datacenters resolve critical issues 40% faster than traditional environments by distributing workloads during incidents.

Financial services firms use vMotion extensively to migrate trading systems, payment processors, and customer relationship management platforms during critical market hours without service interruption. Healthcare organizations leverage vMotion to move VMs running electronic health record systems and telemedicine platforms across hosts without disrupting patient care. Retail companies employ vMotion during peak shopping seasons to rebalance VMs across infrastructure, maintaining transaction processing speed during demand spikes. Telecommunications providers use vMotion to migrate network function virtualization components while maintaining active customer calls and data streams.

Future developments include vMotion enhancements supporting migrations between different vSphere versions without requiring intermediate steps, and planned integration with Kubernetes for transparent container migration. VMware announced AI-assisted vMotion optimization in 2024, which predicts optimal migration timing based on application workload patterns. Planned improvements to Long-Distance vMotion will reduce cross-continental migration times from minutes to seconds through enhanced WAN compression. VMware's recent acquisition of cloud migration tools suggests future vMotion capabilities will extend to hybrid cloud environments, enabling seamless migration between on-premises and public cloud VMware infrastructure.

Common Misconceptions

Many administrators believe vMotion requires shared storage systems like SAN or NAS, but Storage vMotion specifically enables migrations even when VMs are stored on local host storage or different storage arrays with no shared infrastructure required. Some assume vMotion works only within the same physical datacenter, yet Long-Distance vMotion supports migrations across continents with latency under 150ms, though bandwidth requirements increase proportionally. Others mistakenly think vMotion cannot migrate VMs with active network connections or database transactions, when in fact vMotion preserves all active connections transparently throughout the migration process.

A common myth suggests that vMotion exposes sensitive VM data during migration because memory contents traverse the network, but VMware implements optional encryption for vMotion traffic, and all data is transmitted through secure internal datacenter networks inaccessible to external threats. Some believe vMotion causes noticeable application slowness during migration, yet most applications experience only milliseconds of latency, below human perception thresholds, with complete application isolation preventing one VM's migration from affecting others. Another misconception is that CPU compatibility mismatches prevent vMotion migrations, when Enhanced vMotion Compatibility (EVC) mode explicitly addresses this by limiting advertised CPU features to common denominators between hosts.

Users often think that vMotion requires licensing per VM migrated, but VMware licenses vMotion per ESXi host, making unlimited migrations possible once hosts are licensed with vSphere Enterprise Plus. Some assume that virtual machine snapshots prevent vMotion operations, but vMotion supports snapshot-backed VMs and automatically relocates snapshot chains to the destination host. Others mistakenly believe that vMotion fails when hosts have different network configurations, when vCenter Server automatically adjusts port group assignments and VLAN memberships during migration based on destination host network topology. Many think vMotion stops if network issues arise during migration, but VMware implements automatic retry logic that resumes migrations from checkpoints without requiring restart or manual intervention.