Chapter 1. Migration Toolkit for Virtualization 2.11

In MTV 2.11.0, users can set a service account name for pre-plan and post-plan hooks in the Create migration plan pages. This UI setting allows for greater flexibility and control over the service accounts used in these hooks, ensuring they have the necessary permissions to manage cluster resources. The Service account field is a free text field as the service account information is not stored in the inventory for a remote cluster. This enhancement improves the overall security and customization of the user’s deployment.

MTV-3681

MTV 2.11.0 enhances the visibility of pre-migration concerns for individual VMs, providing a clear taxonomy and visual indicators to distinguish between critical issues, VM-specific failures, and ignorable warnings. The updated UI includes new icons, colors, and labels for quick comprehension of validation issue severity. The Conditions column of the VM table now displays all current concerns impacting the plan, with filters for Name, Severity, Type, and Folder. A total of critical alerts is displayed at the top of the page, with a View all alerts button for detailed analysis. This improvement increases the clarity and understanding of pre-migration concerns, simplifying the migration process.

MTV-3712

With this update, the Tips and tricks section in the MTV UI is significantly expanded, offering curated learning paths and improved user guidance. This enhancement simplifies complex workflow steps, integrates with Red Hat OpenShift Virtualization LightSpeed AI for dynamic guidance, and reorganizes content for a better learning process for MTV administrators.

MTV-3718

With this update, MTV provides performance metrics during migration, including network and storage throughput. This enhancement aims to assist users in making informed decisions about system configuration for better performance tuning. Real-time insights into these metrics during migration plans are now available in the MTV UI.

MTV-3636

In MTV 2.11.0, cluster administrators can now add descriptive notes to their migration plans during creation. The new Description field allows easy differentiation and management of various plans within the web console. Users can identify the purpose, scope, and owner of each plan by adding reasons for each migration in the Description field. The added context is visible in the plan table and Plan details page for long-term management and auditing purposes.

MTV-3748

MTV 2.11.0 introduces a unified, consistent interaction model for editing forms and fields across the MTV web console, streamlining tasks for cluster administrators. The new design includes an edit button that opens a modal for inputs, promoting clarity and reducing configuration errors. This update aims to reduce cognitive load and eliminate varying UI behaviors on different pages, making administrative tasks easier and quicker.

MTV-3742

In MTV 2.11.0, the Create provider form in the MTV UI has unique authentication and validation fields for source providers such as OpenShift, OpenStack, Red Hat Virtualization (oVirt), and VMware vSphere. The new form provides a cleaner and more user-friendly experience when creating providers, making it easier for cluster administrators to create plans for migrating their VMs.

MTV-3737

MTV 2.11.0 introduces visible validation checks for warm migration from VMware environments in the web console. Users are alerted if the VMware vSphere Virtual Disk Development Kit (VDDK) is missing or incorrectly configured, preventing silent failures and saving time on migration plans. Updated MTV documentation provides guidance on VDDK installation.

MTV-3805

MTV 2.11.0 enhances data integrity during VM migration by using features introduced in RHEL 10.1. This release introduces filesystem-level consistency checks, improved system error handling, and internal diagnostics. Warm migration and features like storage offload minimize downtime with efficient disk migration and data transfer.

MTV-3906

In MTV 2.11.0, the Storage Offload Copy feature accelerates disk transfer in the storage array by bypassing the network, enabling snapshot creation and base disk copying. Storage Offload Copy results in reduced network usage, improved overall performance, and enhanced migration efficiency.

MTV 2.11.0 introduces native alerting, integrating with OpenShift’s Prometheus-based monitoring stack. Administrators now receive notifications for migration plan failures or critical issues, reducing manual monitoring. Users can configure alerts for email, Slack, or PagerDuty, ensuring timely notifications and minimizing downtime.

MTV-2529

MTV introduces a more accurate conversion assessment before migration by fetching additional information from guest machines. With this enhancement, users can perform a pre-migration check for dual-boot VMs, ensuring a successful conversion before the migration process begins.

MTV-2481

With this update, users can import VMs directly from Amazon EC2, streamlining the process and expanding the platform’s compatibility. This enhancement supports cold migration to ROSA, with storage mapping limited to the same storage. It does not currently support targeting non-ROSA, different accounts, different regions, warm or live migrations.

MTV-2735

MTV 2.11.0 introduces customizable firstboot scripts for VM migrations, enhancing deployment flexibility and personalization. Users can now specify these scripts in their migration plans for per-plan customization. Scripts are executed by virt-customize during the guest conversion process, eliminating the need for SSH keys for VM migration and integrating virt-customize for script injection during VM conversion and startup.

MTV-3638

In MTV 2.11.0, the assignment of a secondary network to Forklift Controller pods is now supported, similar to Importer and Populator pods. This update addresses connectivity issues with the Red Hat OpenShift default node network and VMware or RHV providers, reducing the need for cluster-wide changes. The existing CRD flag is reused for network assignment, simplifying setup for network configuration and communication between the Forklift Controller and external providers.

MTV-3644

In MTV 2.11.0, migration admins can set the default gateway directly in the Network Attachment Definition (NAD) configuration. In cases where the default route annotation is not set, the software now attempts to fetch the default gateway from the NAD configuration.

MTV-3699

In MTV 2.11.0, you can customize ephemeral storage during migration, preventing failures due to insufficient node storage in large-scale migrations, Open Virtualization Format (OVA) imports, and nodes with limited storage. Users can define a storageClass for temporary storage, enabling virt-v2v pods to mount a temporary Persistent Volume Claim (PVC) on the defined storageClass, improving migration stability and success. This update reduces the likelihood of migration failures caused by limited node storage.

MTV-3709

With this update, MTV detects the operating system that VMs are running on automatically. This enhancement optimizes VM performance in MTV and reduces the need for manual adjustments, saving time and reducing potential errors.

MTV-3963

In MTV 2.11.0, IP preservation for VM migration now verifies that IPs are from the correct subnet before assignment. MTV preserves and assigns IPs from the subnet for VMs with explicitly assigned IPs during migration to OpenShift Virtualization, ensuring accurate IP assignment and preventing IP mismatches during migration.

MTV-3130

When MTV 2.9.1 is deployed on an IPv6-only OpenShift cluster, an incorrect API endpoint prevents the forklift-console-plugin from serving a valid plugin manifest, displaying the error Failed to get a valid plugin manifest from /api/plugins/forklift-console-plugins/. While the forklift-ui-plugin pod runs successfully, the console plugin cannot load, preventing access to the MTV user interface in the OpenShift web console. This issue affects all IPv6-only cluster deployments with OpenShift 4.19.7 and CNV 4.19.1.

Workaround: Deploy MTV on dual-stack or IPv4 clusters until this issue is resolved.

MTV-3116

Inactive migration plans are incorrectly labeled as Running when max_vms_inflight exceeds the total number of disks per migration. This label leads to confusion about the actual state of the plans, as all migration plans appear to be Running in the user interface.

Workaround: Currently, there is no workaround for this issue.

MTV-1736

During migration between OpenShift namespaces in a cluster, MAC address collisions result in VM creation failure.

Workaround: Disable the KubeMacPool. For more information, see Managing KubeMacPool by using the CLI in the OpenShift documentation.

MTV-2446

In MTV 2.11.0, an update to Golang 1.25 causes a connection failure on FIPS-enabled clusters with VMware vSphere 6 or 7, due to unsupported TLS 1.2 with Extended Master Secret. As a consequence, users cannot migrate VMware vSphere 6 or 7 VMs to a FIPS-compliant cluster.

Workaround: Disable FIPS mode on the cluster or use a VMware vSphere version that supports TLS 1.2 with Extended Master Secret to migrate VMs.

MTV-4411

When migrating two VMs with shared RDM disks using copyoffload in separate migration plans, the second migration plan fails at the ImageConversion step if shared disk migration is disabled. After successfully migrating the first VM with shared disk migration enabled, creating a second migration plan with shared disk migration disabled incorrectly creates two populate pods—one for the OS disk and one for the shared RDM disk—instead of creating only the OS disk populate pod. This causes the second migration to fail.

Workaround: Currently, there is no workaround for this issue.

MTV-4549

When you upload a VMware Virtual Disk Development Kit (VDDK) init image, the image URL is located in the openshift-mtv namespace. If you create a provider in a different namespace, there is an error when pulling the image.

MTV-3673

When you create an Open Virtual Appliance (OVA) provider in the MTV UI, ConnectionTestFailed error messages are displayed before the provider status changes to Ready. The error messages are misleading and do not accurately reflect the in-progress status of the connection.

MTV-3613

Fibre Channel (FC) protocol VM migration fails to identify existing FC host objects in Infinibox due to incorrect adapter ID comparison. As a consequence, FC protocol VM migration fails to identify existing FC hosts, causing volume creation failure due to incorrect port_name.

Workaround: Currently, there is no workaround for this issue.

MTV-4338

During the migration of VMs to an OpenShift Container Platform (OCP) cluster with Fibre Channel (FC), the migration stalls when attempting to add a transfer network to a target namespace that does not have permissions to the transfer network.

Workaround: Currently, there is no workaround for this issue.

MTV-4547

Deleting network or storage maps causes the forklift-controller to shut down unexpectedly, leaving the migration plan state as Ready and causing pods to continue running.

Workaround: Delete and restart the pods manually.

MTV-4413