Red Hat Summit Red Hat SummitSupportKonsoleEntwicklerDemo startenKontakt

Dieser Inhalt ist in der von Ihnen ausgewählten Sprache nicht verfügbar.

Chapter 1. Migration Toolkit for Virtualization 2.10

The release notes describe technical changes, new features and enhancements, known issues, and resolved issues.

1.1. New features and enhancements
Link kopieren

Migration Toolkit for Virtualization (MTV) 2.10 introduces the following features and enhancements:

  • In the MTV 2.10.0 UI, the Virtual Machines tab on the Plan Details page provides improved visibility of migration progress with a clearer page title label and a display of key events in logical order. You can also hide migration resources for a cleaner UI to assess the progress of your migration.
  • In MTV 2.10.0, you can optimize the asynchronous input/output (AIO) buffer configuration for the VMware disk development kit (VDDK) directly in the MTV UI for cold migrations. AIO buffer configuration is deactivated by default, but you can activate the feature and customize the configuration in YAML to improve storage I/O operations and reduce latency when working with VDDK. (MTV-2188)
  • In MTV 2.10.0, you can create network maps directly in the MTV UI by adding a source and target network on the Create network map page instead of writing a YAML file.
  • In the MTV 2.10.0 UI, the Virtual Machines table in the Create migration plan wizard is enhanced to simplify navigation and provide a clearer view of selected VMs. With this update, you can bulk select VMs from the Virtual Machines table toolbar, switch between views of selected and unselected VMs, filter VMs by location, and manage columns. (MTV-3058)
  • In MTV 2.10.0, you can find the status of cutover dates for warm migrations in the MTV UI. The cutover button is an icon in the UI for your migration plan that changes state when you set the date for a cutover so that you can easily identify if a cutover date is set.
  • In MTV 2.10.0, the Migrations section on the Plan Details page is relabelled as Migration history. The Migration history section contains tooltips to provide contextual information and make the section more useful for migration monitoring and troubleshooting.
  • MTV 2.10.0 introduces a formatting feature for VMware system serial numbers. System administrators can use the formatting feature for consistent and error-free system serial numbers and easier system identification during migrations and configurations.
  • In MTV 2.10.0, you can customize the nodeSelector field and options for importer pods in the MTV UI, enhancing resource allocation, scheduling, and application performance. You can customize pod scheduling policies for importer pods to ensure that importer pods are scheduled on specific nodes for enhanced resource management and stability.
  • MTV 2.10.0 supports the migration of Linux Unified Key Setup (LUKS) encrypted VMs by using Network Bound Disk Encryption (NBDE) with Clevis. With this update, you can migrate LUKS-encrypted VMs without rebooting the VMs to obtain a decryption key from the Clevis server. The Clevis server must be accessible from OpenShift. (MTV-3395)
  • In MTV 2.10.0, the insecureSkipVerify flag is set by default for ESXi hosts in the MTV UI, simplifying migrations in environments with self-signed certificates. With this setting, the migration process bypasses SSL certificate validation, reducing potential errors caused by certificates while maintaining security.
  • In MTV 2.10.0, you can configure VM scheduling preferences for migration plans in the MTV UI or the Plan Custom Resource (CR). You can add custom labels to migrated VMs, apply VM scheduling to specific nodes based on node labels, and implement affinity or anti-affinity rules for VMs against workloads or nodes. With this update, you can use the TargetLabels, TargetNodeSelector, and TargetAffinity fields to manage VM placement during migrations, improving resource utilization and operational compliance. (MTV-2768)
  • In MTV 2.10.0, an inspection during warm migration enables early detection of issues during guest conversion. If an issue is detected, the warm migration fails before VM shutdown, and users can adjust VM settings or skip guest conversion. (MTV-2427)
  • Technology Preview: In MTV 2.10.0, you can import Open Virtual Appliances (OVAs) directly from local machines to OpenShift Virtualization by uploading the OVAs to NFS through the web browser in the MTV UI. (MTV-3371)
  • In MTV 2.10.0, you can set useCompatibilityMode to true or false in the Raw Copy Mode settings in the MTV UI. With this update, you can use compatibility devices when migrating source VMs, such as SATA bus, E1000E NICs, or USB, or you can use pre-installed VirtIO devices on source VMs. (MTV-3006)
  • In MTV 2.10.0, you can migrate VMs to existing user-defined networks (UDNs). With this update, you can create UDNs and map a VM’s source network to the UDN, and you can preserve the static IP addresses of source VMs that have assigned IPs. (MTV-2856)
  • Technology Preview: In MTV 2.10.0, you can live migrate VMs from one OpenShift (OCP) cluster to another, minimizing downtime with the continuous availability of VMs during the migration process. With this update, MTV creates and maps resources from the source to the destination cluster and triggers the live migration, and OpenShift Virtualization CNV migrates the running VM. (MTV-2040)
  • In MTV 2.10.0, the Storage Offload Copy feature is Developer Preview for warm migrations and Technology Preview for cold migrations. Storage Offload Copy accelerates disk transfer in the storage array by bypassing the network. With this update, you can create a snapshot and then copy the base disk while the VM is running. You can copy delta changes from a snapshot over the network after the base disk storage offload copy, minimizing the requirement for VM shutdowns. (MTV-2637)
  • In the MTV 2.10.0 UI, you can automate the creation of VMware Virtual Disk Development Kit (VDDK) images from provided s/tat.gz/tar.gz/ files to accelerate the transfer of virtual disks. (MTV-1616)

1.2. Resolved issues
Link kopieren

Migration Toolkit for Virtualization (MTV) 2.10 has the following resolved issues:

1.2.1. Resolved issues 2.10.0
Link kopieren

User could not rename virtual machines to address naming conflicts before migration

In previous versions of MTV, you could not rename virtual machines (VMs) from the source provider to address naming conflicts before the VMs were migrated to Red Hat OpenShift Virtualization. In this release of MTV, you can modify non-compliant VM names in the MTV UI during the migration process to address naming conflicts and ensure compatibility with OpenShift Virtualization naming conventions. (MTV-2919)

User experience was interrupted when adding a new target project to a migration plan

In previous versions of MTV, you had to close the Create migration plan wizard in the MTV UI to add a new target project to your migration plan. In this release of MTV, the option to create a new project as a target for VMs in your migration plan is available in the Target project dropdown list on the General page of the Create migration plan wizard.

Power state of source VMs was preserved post-migration

In previous versions of MTV, the power state of a source VM was preserved post-migration. In this release of MTV, you can set the power state of a migrated VM to on, off, or auto. For example, if you are migrating a VM that is running in the source environment, you can ensure that the VM is powered off post-migration to preserve startup dependencies between VMs. With this update, you can set the power state for the target VM in the MTV UI or by using the powerState field in the spec.vms section of the Plan Custom Resource (CR). The auto setting preserves the power state of the source VM. (MTV-1312)

1.3. Known issues
Link kopieren

Migration Toolkit for Virtualization (MTV) 2.10 has the following known issues:

Raw Device Mapping files prevent copyoffload migration of NFS-based VMs

If you try to migrate an NFS-based VM by using the copyoffload method, the vmkfstools command-line utility attempts to use the fallback method because NFS is file-based. However, NFS datastores do not support Raw Device Mapping (RDM) pointer files, and vmkfstools creates RDM files as cloning targets.

Workaround: You can use one of the following migration methods to address the limitation:

  • Migrate the NFS-based VM to an iSCSI or FC datastore, and then use the copyoffload method to migrate the VM to OpenShift Virtualization.
  • Migrate the VM to a local ESXi disk datastore, and then use the copyoffload fallback method to migrate the VM to OpenShift Virtualization.
  • Use either the HTTP or VDDK method to migrate the VM to OpenShift Virtualization.

Inaccurate ConnectionTestFailed error messages when creating an OVA provider

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 in-progress status of the connection. (MTV-3613)

VDDK image in openshift-mtv namespace

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)

Leftover PVCs consume resources in OVA migrations

During Open Virtual Appliance (OVA) migrations to OpenShift Virtualization, leftover ova-store-pvc-* Persistent Volume Claims (PVCs) are bound to the target cluster, consuming excess resources.

Workaround: Manually delete the leftover ova-store-pvc-* PVCs after migration by using the oc delete pvc <pvc_name> command. This action removes the excess resources, but data loss might occur if the PVCs contain important data. (MTV-3659)

VM migration from OVA to OpenShift Virtualization cluster causes loss of interface settings in VM YAML file

The migration of VMs with DHCP settings from an Open Virtual Appliance (OVA) provider to a OpenShift Virtualization cluster results in the loss of interface settings in the VM YAML file post-migration.

Workaround: Manually configure interfaces on the VM after migration. (MTV-3654)

Incomplete deployment of MTV 2.10 due to incomplete image mirroring

If you use the oc-mirror command to mirror MTV 2.10 images, not all images are mirrored to the chosen destination because of an incomplete related images section in the operator. Because all of the required images for MTV 2.10 are not mirrored, the deployment is incomplete.

Workaround: Manually copy the missing images to the local file to complete the deployment. (MTV-3679)

Missing check for write permissions on OVA files for upload

When uploading an Open Virtual Appliance (OVA) file, the script does not check the write permissions for the destination directory before the upload, which can result in a permission denied error at the end of the upload process.

Workaround: Check the write permission of the OVA file before initiating the upload to complete the upload process without permissions errors. (MTV-3634)

Nach oben
Red Hat logoGithubredditYoutubeTwitter

Lernen

Testen, kaufen und verkaufen

Communitys

Über Red Hat Dokumentation

Wir helfen Red Hat Benutzern, mit unseren Produkten und Diensten innovativ zu sein und ihre Ziele zu erreichen – mit Inhalten, denen sie vertrauen können. Entdecken Sie unsere neuesten Updates.

Mehr Inklusion in Open Source

Red Hat hat sich verpflichtet, problematische Sprache in unserem Code, unserer Dokumentation und unseren Web-Eigenschaften zu ersetzen. Weitere Einzelheiten finden Sie in Red Hat Blog.

Über Red Hat

Wir liefern gehärtete Lösungen, die es Unternehmen leichter machen, plattform- und umgebungsübergreifend zu arbeiten, vom zentralen Rechenzentrum bis zum Netzwerkrand.

Theme

© 2025 Red Hat