Chapter 1. Migration Toolkit for Virtualization 5.0

Previously, you had to manually enter LUKS encryption keys in the UI when creating a migration plan. With this update, MTV supports selecting a predefined secret containing LUKS encryption keys during plan creation. As a result, you can select an existing secret instead of manually entering encryption keys for each plan.

MTV-2834

Previously, configuring node selectors for importer pods, also known as virt-v2v Convertor pods, was supported for cold migrations only. With this update, MTV supports configuring node selectors for importer pods during warm migrations from VMware virtual machines (VMs). As a result, you can schedule destination nodes for virt-v2v Convertor pods during warm migrations.

MTV-3208

Previously, MTV extracted migration data directly from the ESXi host where the source virtual machine (VM) was registered. With this update, you can designate specific ESXi hosts as dedicated migration hosts in the StorageMap custom resource (CR). You specify these hosts in the vsphereXcopyPluginConfig section of the storage map. As a result, data extraction tasks run on isolated hosts, protecting production workloads from migration load. This capability is a Technology Preview feature.

MTV-3264

With this release, MTV enables you to define Nutanix as a source provider by using the web console or command-line interface (CLI). You can define Nutanix as a source provider by using the UI or the command-line interface (CLI). This capability is a Technology Preview feature.

MTV-4465

With this release, migrations from Microsoft Hyper-V are fully supported. Previously, this feature was available as a Technology Preview. You can migrate VMs from Microsoft Hyper-V hosts and Windows Server Failover Clusters to OpenShift Virtualization.

MTV-4461

Previously, you had to manually edit YAML files to configure storage access modes. With this update, MTV enables you to select storage access modes directly on the Storage maps page in the web console. You can select ReadWriteOnce, ReadWriteMany, or ReadOnlyMany modes for each storage mapping. In addition, the console displays a warning if you select ReadWriteOnce for a storage type capable of ReadWriteMany.

MTV-5496

If a migration fails during disk conversion after a successful disk copy, you can resume the migration without recopying disks. This feature applies to migrations where disk copy and conversion are separate phases (for example, warm migrations or cold migrations with storage offload). If the source virtual machine (VM) was powered on after the failed migration, the copied disks may be inconsistent. Start a new migration instead. This capability is a Technology Preview feature.

MTV-6993

Previously, you could exclude only shared disks attached to a virtual machine (VM) in a migration. With this update, you can exclude any disk attached to a VM in the Plan settings section of a migration plan and the plan wizard.

MTV-6426

Previously, offline virtual machine (VM) migrations failed in Red Hat OpenShift on IBM Cloud (ROKS) environments. This occurred because MTV configured invalid certificates on intermediate DataVolume resources. As a consequence, users encountered certificate errors that blocked the migrations. With this update, MTV probes the export proxy Transport Layer Security (TLS) endpoint before setting the certificate configuration map. It omits the certificate if the VMExport certificate authority (CA) does not verify but system trust does. As a result, offline migrations in ROKS environments complete successfully despite the unverified certificates.

MTV-6458

Previously, you had to pick a past date as a workaround to start immediate cutover for warm migrations. With this release, the Plan cutover menu includes Cutover as soon as possible (default) and Cutover at a specific time options in the web console. As a result, you do not need to select a past date for an immediate cutover.

MTV-5513

Previously, MTV showed the Completed status even though the Windows virtual machine is performing post-migration tasks. With this update, you can check the post-migration status for Windows VMs when they reboot multiple times to install drivers, guest agents, remove VMware tools, or configure networking.

MTV-5506

Previously, you had to manually check whether the guest operating system (OS) was supported while selecting a virtual machine in a plan. With this update, you can view the supported guest OS for selected VMs in a plan, on the Plan details page, and on the Provider details page. You can also filter the VMs by the supported guest OS before you create a migration plan.

MTV-5502

With this release, MTV performs a two-phase transfer of Virtual Hard Disk (VHD) and Virtual Hard Disk v2 (VHDX) for Hyper-V virtual machines (VMs). When you set preCopySourceDisks:type to true, MTV copies the VHDX files from the Server Message Block (SMB) share and the virt-v2v tool then performs in-place guest operating system customization. This capability is a Developer Preview feature.

MTV-6718

Before this update, migrating Windows and Linux virtual machines (VMs) with IPv6 configurations resulted in errors. With this update, you can migrate Windows VMs with static IPv6 addresses and routing configurations, connect to vCenter servers and ESXi hosts with IPv6-only or dual-stack configurations, and run MTV on IPv6-only Red Hat OpenShift clusters.

MTV-2897

Provider alerts are centralized on the Provider details page. As a result, you can view all relevant provider warnings in one place rather than in the Conditions section.

MTV-6656

With this update, MTV propagates the xcopyUsed indicator from the populator pod to the migration plan status. Previously, this information was only available as a transient Prometheus metric that was lost when the populator pod completed. Each disk transfer task includes an xcopyUsed annotation that shows whether the storage array used hardware-accelerated copy or a software fallback. As a result, you can identify which disks benefited from XCOPY and troubleshoot performance differences across storage configurations.

MTV-5871

Before this update, you had to manually track plan-related alerts in a specific plan. With this release, MTV displays automated alerts for migration failures, stalled migrations, persistent volume claim provisioning issues, and insufficient resources in the target namespace. To make monitoring large-scale migration easier, you can track migration issues on the Overview page or on the Plan details page.

link: MTV-5498

With this release, you can configure the network IP mode for virtual network interface cards (vNICs) of Windows virtual machines (VMs) in the NetworkMap. As a result, you can specify whether vNICs preserve the static IP address from the source network, use a Dynamic Host Configuration Protocol (DHCP)-assigned IP address, or are excluded from the static IP configuration after migration.

MTV-5268

With this release, deep inspection is fully supported. Before this update, this feature was available as a Technology Preview. You can use deep inspection to analyze virtual machine (VM) disk images before migration and find compatibility issues that standard inspection might miss. As a result, you can plan remediation before starting the migration.

MTV-4473

The scsiReservation variable is available to enable or disable reservations on demand for shared Raw Device Mapping (RDM) disks. This variable is disabled by default. You can configure this setting per migration plan for all virtual machines (VMs), and a per-VM override is also available. This enhancement prevents issues that occur when a reservation is not desired or supported for a given workload. As a result, you have explicit control over whether SCSI reservations are enabled for shared RDM disks, which prevents unintended reservation behavior and allows fine-grained configuration per workload.

MTV-6070

Before this update, Windows virtual machines (VMs) had VMware drivers and tools after migration. As a result, service stack failures and compatibility issues with KVM or virtio affected the migrated OpenShift VMs. With this release, the VMware components are automatically removed in the post-migration workflow after you configure feature_vsphere_vmware_driver_removal:true in the ForkliftController custom resource (CR).

MTV-4546

With this release, you must install the MTV Operator in the remote Red Hat OpenShift cluster to migrate virtual machines from supported providers. As a result, if you do not install the MTV Operator in the target cluster, the configured provider cannot detect MTV custom resource definitions in the remote cluster and issues a warning.

MTV-5335

With this release, MTV migrates Microsoft Azure virtual machines (VMs) to Red Hat OpenShift clusters on Azure. As a result, you can create the Azure provider through the oc command-line interface (CLI). You must provide tenantId, subscriptionId, clientId, and clientSecret as credentials when creating the provider. After creating the provider you can create migrating plans targeting Azure VMs. This capability is a Developer Preview feature.

MTV-5924

Previously, MTV always set the KubeVirt Multus networkName as namespace/nad-name for all Network Attachment Definitions (NADs). With this update, when the mapped NAD is in the same namespace as the migrated virtual machine (VM), the controller sets networkName to the NAD name only. NADs in the default namespace still use the qualified default/nad-name form. You can revert to the previous behavior by setting controller_multus_network_name_always_qualified: "true" in the ForkliftController custom resource specification. As a result, downstream tools have better compatibility with the shorter network name format.

MTV-4971

With the new release, there’s an option to control the vmx or svm CPU feature per virtual machine (VM) during migration in OpenShift Virtualization. This feature aims to prevent enabling Virtualization-based Security (VBS) on VMs or nesting in guest operating system (OS) if it’s disabled in the source VMware VM. The setting depends on the VM’s status in VMware.

MTV-4696

After you migrate a Windows Server 2019 virtual machine (VM) from vSphere with feature_vsphere_vmware_driver_removal:true in the ForkliftController custom resource (CR), the VM reboots in an indefinite loop. As a consequence, you are unable to log in to the VM even after the VMware driver is removed without any errors.

No known workaround exists.

MTV-6506

After you migrate a Windows virtual machine (VM) from VMware to Red Hat OpenShift with feature_vsphere_vmware_driver_removal:true in the ForkliftController custom resource (CR), the VMware driver remains in the VM. Consequently, the VM can be affected by unnecessary service failures and error logs.

No known workaround exists.

MTV-6525