Ce contenu n'est pas disponible dans la langue sélectionnée.
Chapter 4. Migration Toolkit for Virtualization 2.3
You can migrate virtual machines (VMs) from VMware vSphere or Red Hat Virtualization to OpenShift Virtualization with the Migration Toolkit for Virtualization (MTV).
The release notes describe technical changes, new features and enhancements, and known issues.
4.1. Technical changes
This release has the following technical changes:
Setting the VddkInitImage path is part of the procedure of adding VMware provider.
In the web console, you enter the VddkInitImage path when adding a VMware provider. Alternatively, from the CLI, you add the VddkInitImage path to the Provider CR for VMware migrations.
The StorageProfile resource needs to be updated for a non-provisioner storage class
You must update the StorageProfile resource with accessModes and volumeMode for non-provisioner storage classes such as NFS. The documentation includes a link to the relevant procedure.
4.2. New features and enhancements
This release has the following features and improvements:
MTV 2.6 supports warm migration from RHV
You can use warm migration to migrate VMs from both VMware and RHV.
The minimal sufficient set of privileges for VMware users is established
VMware users do not have to have full cluster-admin privileges to perform a VM migration. The minimal sufficient set of user’s privileges is established and documented.
MTV documentation is updated with instructions on using hooks
MTV documentation includes instructions on adding hooks to migration plans and running hooks on VMs.
4.3. Known issues
This release has the following known issues:
Some warm migrations from RHV might fail
When you run a migration plan for warm migration of multiple VMs from RHV, the migrations of some VMs might fail during the cutover stage. In that case, restart the migration plan and set the cutover time for the VM migrations that failed in the first run. (BZ#2063531)
Snapshots are not deleted after warm migration
The Migration Controller service does not delete snapshots automatically after a successful warm migration of a RHV VM. You can delete the snapshots manually. (BZ#22053183)
Warm migration from RHV fails if a snapshot operation is performed on the source VM
If the user performs a snapshot operation on the source VM at the time when a migration snapshot is scheduled, the migration fails instead of waiting for the user’s snapshot operation to finish. (BZ#2057459)
QEMU guest agent is not installed on migrated VMs
The QEMU guest agent is not installed on migrated VMs. Workaround: Install the QEMU guest agent with a post-migration hook. (BZ#2018062)
Deleting migration plan does not remove temporary resources.
Deleting a migration plan does not remove temporary resources such as importer pods, conversion pods, config maps, secrets, failed VMs and data volumes. (BZ#2018974) You must archive a migration plan before deleting it in order to clean up the temporary resources.
Unclear error status message for VM with no operating system
The error status message for a VM with no operating system on the Migration plan details page of the web console does not describe the reason for the failure. (BZ#2008846)
Log archive file includes logs of a deleted migration plan or VM
If you delete a migration plan and then run a new migration plan with the same name or if you delete a migrated VM and then remigrate the source VM, the log archive file created by the MTV web console might include the logs of the deleted migration plan or VM. (BZ#2023764)
Migration of virtual machines with encrypted partitions fails during conversion
The problem occurs for both vSphere and RHV migrations.
MTV 2.3.4 only: When the source provider is RHV, duplicating a migration plan fails in either the network mapping stage or the storage mapping stage.
Possible workaround: Delete cache in the browser or restart the browser. (BZ#2143191)
