Migration with vMotion, also known as hot migration or live migration, moves a powered-on VM from one host or datastore to another. Migration with vMotion is the best option for migrating small numbers of VMs without incurring any downtime.
To implement migration with vMotion, you can configure hybrid linked mode and use the vSphere client. You can also use command-line (PowerShell) or API automation.
Summary of Supported Configurations
- vSphere 6.7U2 or higher.
- vSphere 6.5P03 or higher.
Restrictions on VMs Migrated with vMotion
The restrictions on migration with vMotion that apply to VMs previously migrated from on-premises data centers are as follows:
- VMs that use standard virtual switches for networking cannot be migrated back to an on-premises data center after being migrated to the cloud SDDC.
- Any VM that has been power-cycled in the cloud SDDC can only be migrated back to an on-premises host or cluster with the Broadwell chipset or EVC mode.
- If your on-premises hosts haven't been patched to address vulnerability to side channel analysis due to speculative execution (also referred to as the Spectre Variant 2 vulnerability), this may affect vMotion compatibility as shown in . To find the correct patch for your on-premises hosts, see https://kb.vmware.com/s/article/52245. All hosts in VMware Cloud on AWS SDDCs have been patched.
|On-premises Host Processor Family and Patch Status||Virtual Machine Hardware Version||Has the VM been power-cycled in VMware Cloud on AWS SDDC?||vMotion from On-premises to VMware Cloud on AWS||vMotion from VMware Cloud on AWS to On-premises|
|Broadwell (SPECTRE patched)||< 9||No||Supported||Supported|
|Broadwell (Not SPECTRE patched)||< 9||No||Supported||Not supported|
|Non-Broadwell||< 9||No||Not supported||Supported|
|Yes||Not supported||Not supported|
These restrictions don't apply to cold migration.