You can use the Migration wizard to migrate a powered-on virtual machine from one compute resource to another by using vMotion. To relocate only the disks of a powered-on virtual machine, migrate the virtual machine to a new datastore by using Storage vMotion.
Before you begin
Verify that your hosts and virtual machines meet the requirements for migration with vMotion with shared storage.
Verify that your hosts and virtual machines meet the requirements for migration with vMotion. See Host Configuration for vMotion and Virtual Machine Conditions and Limitations for vMotion.
Verify that the storage that contains the virtual machine disks is shared between the source and target hosts. See vMotion Shared Storage Requirements.
For migration across vCenter Server instances verify whether your system meets additional requirements. See Requirements for Migration Between vCenter Server Instances.
- Right-click the virtual machine and select Migrate.
- To locate a virtual machine, select a data center, folder, cluster, resource pool, host, or vApp.
- Click the Related Objects tab and click Virtual Machines.
- Click Change compute resource only and click Next.
- Select a host, cluster, resource pool, or vApp ro run the virtual machine, and click Next.
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 in the same or another vCenter Server system. If your target is a non-automated cluster, select a host within the non-automated cluster.
- Select a destination network for all VM network adapters and click Next.
You can click Advanced to select a new destination network for each VM network adapter.
You can migrate a virtual machine networks to another distributed switch in the same or to another data center or vCenter Server.
- Select the migration priority level and click Next.
Schedule vMotion with high priority
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. if sufficient CPU resources are not immediately available, vMotion is not initiated.
Schedule regular vMotion
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. If there is a lack of CPU resources, the duration of vMotion can be extended.
- Review the page and click Finish.
vCenter Server moves the virtual machine to the new host or storage location.
Event messages appear in the Events tab. The data displayed on the Summary tab shows the status and state throughout the migration. If errors occur during migration, the virtual machines revert to their original states and locations.