After you configure your vSphere environment for vMotion, you can use the vSphere Web Client to migrate powered-on virtual machines between the hosts ESXi-A and ESXi-B. In a production environment, vMotion guarantees minimal downtime of critical tasks that run in virtual machines.

Before migration, you can open a console to the virtual machine and start a continuous task, such as running the ping command in a command-line window or playing streaming video from the Internet. During the vMotion process, the machine is migrated to another host while the task continues with only minimal interruption. This is a useful way to monitor the migration process if you are migrating running virtual machines for the first time.


In the vSphere Web Client, select a powered-on virtual machine that is running on host ESXi-A.


Right-click the virtual machine and select Migrate from the pop-up menu.

If you have compatibility problems with your vMotion environment, messages appear in the Migrate wizard that describe the problems.


Click Change host and click Next.


Select the My EVC Cluster object that you created for your vMotion environment and click Next.


Select ESXi-B as the destination host to which to migrate the virtual machine and click Next.


Select Reserve CPU for optimal vMotion performance and click Next.

vCenter Server reserves resources on both the source and destination hosts to be shared among all concurrent migration with vMotion. vCenter Server grants a smaller share of host CPU resources to standard priority migrations than to high priority migrations. Migrations proceed regardless of the resources that have been reserved.


Review your settings and click Finish.

vCenter Server migrates the virtual machine to another host without service interruption. You can track the progress of the migration in the Recent Tasks panel.

You can enable, on the cluster level, advanced vSphere features such as vSphere FT and vSphere DRS.