6.7

Procedure
1 Right-click the virtual machine and select Migrate.
a To locate a virtual machine, select a data center, folder, cluster, resource pool, host, or vApp.
b Click the Virtual Machines tab.
2 Select Change both compute resource and storage and click Next.
3 Select a destination resource for the virtual machine, and click Next.
Any compatibility problems appear in the Compatibility panel. Fix the problem, or select another host
or cluster.
Possible targets include hosts and fully automated DRS clusters. If your target is a non-automated
cluster, select a host within the non-automated cluster.
If your environment has more than one vCenter Server instances, you can move virtual machines
from one vCenter Server inventory to another.
Important If the virtual machine that you migrate has an NVDIMM device and uses PMem storage,
the destination host or cluster must have available PMem resources. Otherwise, the compatibility
check fails and you cannot proceed further with the migration.
If the virtual machine that you migrate does not have an NVDIMM device but it uses PMem storage,
you must select a host or cluster with available PMem resources, so that all PMem hard disks remain
stored on a PMem datastore. Otherwise, all the hard disks use the storage policy and datastore
selected for the configuration files of the virtual machine.
Important Migrating a virtual machine that has an NVDIMM device or a vPMem disk to a host that
does not have the proper license fails and leaves the virtual machine in an unmanageable state for 90
seconds. You can afterwards retry the migration and select a destination host that is licensed to use
PMem devices.
4 Select the format for the virtual machine's disks.
Option Action
Same format as source Use the same format as the source virtual machine.
Thick Provision Lazy Zeroed Create a virtual disk in a default thick format. Space required for the virtual disk is
allocated during creation. Any data remaining on the physical device is not erased
during creation. Instead, it is zeroed out on demand on first write from the virtual
machine.
Thick Provision Eager Zeroed Create a thick disk that supports clustering features such as Fault Tolerance.
Space required for the virtual disk is allocated at creation time. In contrast to the
thick provision lazy zeroed format, the data remaining on the physical device is
zeroed out during creation. It might take longer to create disks in this format than
to create other types of disks.
Thin Provision Use the thin provisioned format. At first, a thin provisioned disk uses only as much
datastore space as the disk initially needs. If the thin disk needs more space later,
it can expand to the maximum capacity allocated to it.
vSphere Virtual Machine Administration
VMware, Inc. 274