You can migrate a VMware VM from a VMware vCenter cluster to UIS without service interruption and without any agents required.
Make sure the VMware VM does not use any independent-persistent or independent-nonpersistent disks.
To migrate the VMware VM while it is online, make sure it is installed with VMware tools.
Data loss might occur during VM migration from VMware ESXi 5.5 or later, or a version between VMware ESXi 6.0 2494585 and 3247720. Upgrade VMware ESXi to ESXi 6.0 3247720 or later before you migrate its VMs to UIS.
Make sure the host to which the VMware VM belongs uses ESX/ESXi 4.0 or higher.
Make sure the hardware version of the VMware VM is 7 or higher.
Make sure the VMware vCenter version is vSphere 6.0, vSphere 6.5, vSphere 6.7, or vSphere 7.0.
Make sure the vCenter is accessible on port 443, and the ESXi host is accessible on port 902.
Make sure the VMware VM does not use an SR-IOV passthrough NIC.
A VM in VMware vCenter 6.0 cannot be migrated to UIS if the VM uses NFS. To migrate such a VM to UIS, you must first change its storage to VMFS on VMware.
If VMware VMs use IPv6 addresses, you must enable VM IPv6 address management in system parameters before migrating the VMware VMs to CAS. If you do not enable VM IPv6 address management, the VMs do not have IPv6 addresses after they are migrated.
A VMware VM cannot be migrated to UIS if it uses an RDM disk in physical compatibility mode. A VMware VM can be migrated to UIS if it uses NFS or uses an RDM disk in virtual compatibility mode. A VMware VM that uses a VMFS disk can be migrated to UIS, regardless of whether the storage resources are provided by SAN or a local disk.
A VM in VMware vCenter 6.0 cannot be migrated to UIS if the VM has snapshots. To resolve this issue, contact the technical support.
A VMware VM cannot be migrated to an ARM host.
To avoid migration failure, make sure the destination storage pool has sufficient space.
You must configure a network IP address for a VMware VM after the VM is migrated to UIS.
When a VMware VM is in sleep mode, its VMware tools stops running and the VM cannot be shut down automatically, which might cause migration failure or data loss. Therefore, do not set a VMware VM to auto sleep or energy saving mode during the migration.
To avoid migration failure, do not operate a VM on VMware while the VM is being migrated to UIS.
If the source VM on VMware fails during the migration, the migration task will fail and cannot be restored.
By default, a VMware VM that uses the Windows server 2003 or Windows XP operating system uses the IDE disk bus type after it is migrated to CAS. After the migration, you must manually install CAStools.
To migrate a VMware VM that uses the Windows server 2003 or Windows XP operating system, make sure the number of disks on the VM does not exceed four (including floppy drives and optical drives).
After a VMware VM that uses the Windows Server 2008 operating system is started (automatically or manually) for the first time after it is migrated to UIS, you must restart the VM to have the drivers run correctly.
If a VMware VM cannot be quiesced during the migration, UIS will prompt snapshot deletion failure and VMware will prompt snapshot saving and VM quiescence failures. In this scenario, quiesce the VM as instructed in the official website of VMware, and then continue the migration.
By default, a VMware VM uses the thin provisioning mode after it is migrated to UIS.
A VMware VM cannot be migrated to an RBD storage pool.
Only vSphere 6.7 and later versions support the simple migration method.
On the top navigation bar, click VMs.
From the left navigation pane, select External VMs > vCenter site > Cluster.
Click the name of an external VM.
Click Migrate.
Configure the parameters as described in "Parameters."
Click Finish.
Destination VM Name: Specify a name for the target VM.
Provisioning: Select a storage volume provision mode. You can edit this parameter for a VM only when the VM is in shutdown state, uses a single-level image file as the disk, and does not have snapshots.
Thin: Allocates only as much storage space as the storage volume needs for its initial operations when the storage volume is created. If the storage volume needs more storage space later, the system allocates as much storage space as the volume would require based on the specified maximum storage size.
Delay Zeroed: Allocates the specified maximum storage size to the storage volume when the storage volume is created. Data remaining on the physical device is not erased during creation, but is zeroed out on first write from the VM. NFS storage pools do not support this mode.
Zeroed: Allocates the specified maximum storage size to the storage volume when the storage volume is created. Data remaining on the physical device is zeroed out during creation. It might take a longer time to create storage volumes in this format than to create storage volumes of other formats.
Select a destination host for the migration.
Dest Disk Size: Configure the disk size for the target VM. It cannot be smaller than the disk size of the source VM.
Target Storage File: Specify the target storage file name.
Target Storage Pool: Select a storage pool for the target VM.
VM MAC: Configure the MAC address of the target VM. It is the MAC address of the source VM by default.
vSwitch: Select a vSwitch for the target VM.
Port Profile/Port Group: Select a port profile/port group for the target VM.
Virtual Firewall: Select a virtual firewall for the target VM.
Automatic Incremental Migration Interval: Specify the interval at which the system performs incremental backup on the source VM when the migration task is to be completed.
Migration Speed Limit: Specify the I/O rate limit in MBps.
Migration Method: Select a migration method. Options include Full and Simple. If you select the simple method, the system will not migrate unassigned blocks. Only vSphere/ESXi 6.7 and later versions support the simple method.
Encrypted Transmission: Select whether to transmit data through an encrypted channel during migration.
Concurrent Acceleration: Enable this feature to increase the transmission rate.
VM Startup/Shutdown:
Forcibly Shutdown: Enable this feature to forcibly shut down the source VM when the VM cannot be shut down normally. Enabling this feature might cause data loss.
Start After Migration: Enable this feature to automatically starts the target VM after the migration is completed.
Automatically Complete Migration Task: Enable this feature to automatically complete the migration task after the incremental migration is completed (the incremental data is less than the threshold). If you do not enable this feature, the migration task will not be automatically completed and the system will migrate the incremental data on the source VM at the specified interval until you manually complete the task.