How to Migrate a Powered-On Virtual Machine with vMotion in the vSphere Client

You can use the Migration wizard to migrate a powered-on virtual machine from one host to another using vMotion technology. To relocate the disks of a powered-on virtual machine, migrate the virtual machine using Storage vMotion.

Prerequisites

Before migrating a virtual machine with vMotion, ensure that your hosts and virtual machines meet the requirements for migration with vMotion.

■	Host Configuration for vMotion
■	Virtual Machine Configuration Requirements for vMotion in the vSphere Client

Procedure

1	Select the virtual machine that you want to migrate in the inventory.
2	Right-click on the virtual machine and select Migrate from the pop-up menu.
3	Select Change host and click Next.
4	Select a destination host or cluster for the virtual machine. Any compatibility problem appears in the Compatibility panel. Fix the problem, or select another host or cluster. Possible targets include hosts and fully automated DRS clusters. You can select a non-automated cluster as a target. You are prompted to select a host within the non-automated cluster.
5	Select a resource pool and click Next.
6	Select the migration priority level and click Next. A. High Priority On hosts running ESX/ESXi version 4.1 or later, vCenter Server attempts to reserve resources on both the source and destination hosts to be shared among all concurrent migrations with vMotion. vCenter Server grants a larger share of host CPU resources to high priority migrations than to standard priority migrations. Migrations always proceed regardless of the resources that have been reserved. On hosts running ESX/ESXi version 4.0 or earlier, vCenter Server attempts to reserve a fixed amount of resources on both the source and destination hosts for each migration. High priority migrations do not proceed if resources are unavailable. B. Standard Priority On hosts running ESX/ESXi version 4.1 or later, 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 always proceed regardless of the resources that have been reserved. On hosts running ESX/ESXi version 4.0 or earlier, vCenter Server attempts to reserve a fixed amount resources on the source and destination hosts for each migration. Standard priority migrations always proceed. However, the migration might proceed more slowly or fail to complete if sufficient resources are not available.

7.     Review the page and click Finish.

A task is created that begins the virtual machine migration process.

Video How to :

Source : https://pubs.vmware.com/vsphere-51/index.jsp?topic=%2Fcom.vmware.vsphere.vcenterhost.doc%2FGUID-0542FCAA-209A-4296-8AA4-0A51C13A6233.html