Release notes

With this release, the MTV user interface (UI) integrates Lightspeed AI. As a virtual infrastructure administrator, you can use free-text queries to generate AI-powered results. You can use this AI integration to quickly find specific answers during complex migrations. This feature also aligns Lightspeed across the OpenShift console and the UI. As a result, you can troubleshoot migration issues more efficiently.

With this release, MTV supports migrations from Amazon Web Services (AWS) Elastic Compute Cloud (EC2) as a Technology Preview. You can define AWS EC2 as a source provider by using the user interface (UI) or the command-line interface (CLI). To access this capability, you must enable the associated feature flag. As a result, you can migrate workloads from AWS EC2 to a Red Hat-supported environment.

With this release, storage copy offload for warm migrations is fully supported. Before this update, this feature was available as a Technology Preview. You can use this feature to transfer data during a warm migration. As a result, you can migrate virtual machines (VMs) more efficiently.

With this release, a deep inspection tool assesses the migratability of virtual machines (VMs) as a Technology Preview. The tool inspects the VM file system, which is particularly useful for dual-boot VMs. The user interface (UI) displays this information so you can choose root mounts and assess VM migratability without manual planning. As a result, you reduce conversion failures and the time required to prepare a VM for migration.

With this release, you can add virtual machines (VMs) to existing plans in the MTV user interface (UI). You can use this feature to dynamically scale your infrastructure. As a result, you can optimize your workloads and manage resources more efficiently.

With this release, you can configure the tolerations and nodeSelector fields for importer pods in the user interface (UI). You can use this feature to customize pod placement and manage resource allocation for importer tasks. As a result, you can optimize workloads for specific infrastructure requirements.

With this release, the custom firstboot scripts feature is provided as a Technology Preview. Before this update, this feature was available as a Developer Preview. You can use this feature to customize the initial setup of your virtual machines (VMs). This customization eliminates the need for Secure Shell (SSH) key management. As a result, you streamline the migration process and deploy VMs more efficiently.

With this release, you can use {project-short} to trigger hooks directly in the Ansible Automation Platform (AAP) as a Technology Preview. Before this update, you had to specify a hook inside the hook image or the hook configmap. These methods lacked a connection to AAP. You no longer need to specify hooks manually. As a result, you streamline the migration process and improve automation workflows.

With this release, migration plans support the pvcNameTemplate field for OpenShift Virtualization to OpenShift Virtualization migrations. You can use this feature to customize the names of persistent volume claims (PVCs). As a result, you can match the generated PVC names to your storage naming conventions.

This update introduces comprehensive multilanguage translation and internationalization to the MTV web console user interface. With this enhancement, you can navigate migration plans, view provider status, and manage virtual machine (VM) migrations in your preferred language. As a result, the console plugin matches your language preference in the Red Hat OpenShift Container Platform web console. It supports the following languages:

With this release, real-time monitoring of migration performance is fully supported. Before this update, this feature was available as a Technology Preview. You can monitor network and storage throughput in real time during a migration. You can use these metrics to make informed decisions about performance tuning and configuration. As a result, you can improve the efficiency of your data migrations.

Currently, kubevirt prevents mapping multiple network interface controllers (NICs) to a single network attachment definition (NAD). With this enhancement, you can map a single source network to multiple destination NADs.

spec:
  map:
    - destination:
        name: nad-a
        namespace: mtv-5511-test
        type: multus
      source:
        id: network-21
    - destination:
        name: nad-b
        namespace: mtv-5511-test
        type: multus
      source:
        id: network-21

Before this update, the cleanup process removed only populator pods. It left the original and prime persistent volume claims (PVCs) in the cluster. As a consequence, these orphaned PVCs remained after you archived and deleted a migration plan, so you had to manually remove them. With this release, the cleanup process is updated to handle all associated storage resources. As a result, archiving and deleting a migration plan automatically removes the original and prime PVCs. They no longer remain in the cluster.

Before this update, the DiskTransfer icon failed to turn into a checkmark after a successful warm migration. This issue occurred during storage copy offload migrations. As a consequence, you could not visually confirm a successful migration. With this release, the migration process correctly updates the status. As a result, the icon turns into a checkmark when a warm migration succeeds.

Before this update, leaving the .spec.map.storage field empty in a migration plan YAML file caused an issue. A random storage map name appeared in the user interface (UI). As a consequence, an unrelated name incorrectly appeared for an empty storage map. With this release, the migration process correctly handles empty storage maps. As a result, unrelated storage map names no longer appear in the UI.

Before this update, the user interface (UI) did not display certain Multus NADs in the Target network drop-down list. This issue affected Multus NADs outside the installation namespace. As a consequence, you could not create network maps between the vCenter and the host by using these NADs. With this release, the drop-down list includes Multus NADs from all namespaces. As a result, you can successfully create network maps by using these NADs.

Before this update, archiving a cross-cluster live migration plan failed to remove associated virtual machine instance migrations (VMIMs). As a consequence, these VMIMs persisted after you archived and deleted a plan. This persistence caused in-flight migrations to fail. With this release, the cleanup process is updated to handle all associated resources. As a result, archiving and deleting a cross-cluster live migration plan automatically removes the associated VMIMs.

Before this update, setting spec.rdmAsLun=true in a MigrationPlan custom resource did not convert the interface from virtio to SCSI. As a consequence, you encountered a disk interface mismatch. Logical unit number (LUN) disks retained the virtio interface instead of the required SCSI interface. With this release, setting spec.rdmAsLun=true correctly converts the interface type of Raw Device Mapping (RDM) disks to SCSI. As a result, RDM disks converted to LUNs have the correct interface type.

Before this update, a Red Hat Enterprise Linux (RHEL) virtual machine (VM) migration could fail. This occurred if the Preserve static IPs option was enabled for multiple IPv4 addresses on a single network interface controller (NIC). The post-conversion script incorrectly treated the shared Media Access Control (MAC) address as a duplicate MAC address error. As a consequence, the script generated an empty /etc/udev/rules.d/70-persistent-net.rules file. This file caused the VM to lose network connectivity because NetworkManager failed to activate the profile on boot.

Before this update, XFSv5 on Red Hat Enterprise Linux (RHEL) 7 incorrectly reported file system corruption without actual issues. This false reporting caused migration plans to fail. As a consequence, you might have performed unnecessary repairs.

Before this update, migrating Windows virtual machines (VMs) with PowerShell Constrained Language Mode (CLM) enabled caused firstboot network configuration scripts to fail. This failure occurred because the scripts used .NET methods blocked by CLM. As a consequence, the migration process wrote empty or incorrect subnet masks and network settings to the registry.

Before this update, the migration process failed to clean up persistent volume claims (PVCs) after archiving a failed XCOPY migration. As a consequence, orphaned PVCs remained on the cluster, which caused logical unit number (LUN) utilization issues.

Before this update, the migration process automatically installed a vSphere Installation Bundle (VIB) called vmkfstools-wrapper on each clone. As a consequence, this process caused memory issues on ESXi hosts, and migrations failed.

Before this update, the volume populator pod could not find the VMware Virtual Volume (vVol) during copy offload. This failure occurred on Hewlett Packard Enterprise (HPE) Primera storage because of volume name differences. As a consequence, volume cloning failed and returned an error about a missing volume ID.

Before this update, migrating a Red Hat Enterprise Linux (RHEL) 7.2 virtual machine (VM) caused network configuration changes. This issue occurred when migrating from VMware ESXi to a Red Hat OpenShift Container Platform cluster. The network interface names and static IP address settings changed. As a consequence, the migrated VMs did not retain their original network configuration.

Before this update, upgrading the MTV Operator to version 2.10.2 or 2.10.3 introduced a forklift-cli-download deployment. This deployment had insufficient default memory limits. As a consequence, the pod repeatedly terminated with out-of-memory (OOM) errors. These errors caused the Red Hat OpenShift Container Platform cluster to report the MTV infrastructure as unhealthy.