Chapter 6. Migration Toolkit for Virtualization 2.1
Chapter 6. Migration Toolkit for Virtualization 2.1 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 new features and enhancements, known issues, and technical changes. 6.1. Technical changes VDDK image added to HyperConverged custom resource The VMware Virtual Disk Development Kit (VDDK) SDK image must be added to the HyperConverged custom resource. Before this release, it was referenced in the v2v-vmware config map. 6.2. New features and enhancements This release adds the following features and improvements. Cold migration from Red Hat Virtualization You can perform a cold migration of VMs from Red Hat Virtualization. Migration hooks You can create migration hooks to run Ansible playbooks or custom code before or after migration. Filtered must-gather data collection You can specify options for the must-gather tool that enable you to filter the data by namespace, migration plan, or VMs. SR-IOV network support You can migrate VMs with a single root I/O virtualization (SR-IOV) network interface if the OpenShift Virtualization environment has an SR-IOV network. 6.3. Known issues 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 ) Disk copy stage does not progress The disk copy stage of a RHV VM does not progress and the MTV web console does not display an error message. ( BZ#1990596 ) The cause of this problem might be one of the following conditions: The storage class does not exist on the target cluster. The VDDK image has not been added to the HyperConverged custom resource. The VM does not have a disk. The VM disk is locked. The VM time zone is not set to UTC. The VM is configured for a USB device. To disable USB devices, see Configuring USB Devices in the Red Hat Virtualization documentation. To determine the cause: Click Workloads Virtualization in the Red Hat OpenShift web console. Click the Virtual Machines tab. Select a virtual machine to open the Virtual Machine Overview screen. Click Status to view the status of the virtual machine. VM time zone must be UTC with no offset The time zone of the source VMs must be UTC with no offset. You can set the time zone to GMT Standard Time after first assessing the potential impact on the workload. ( BZ#1993259 ) RHV resource UUID causes a "Provider not found" error If a RHV resource UUID is used in a Host , NetworkMap , StorageMap , or Plan custom resource (CR), a "Provider not found" error is displayed. You must use the resource name. ( BZ#1994037 ) Same RHV resource name in different data centers causes ambiguous reference If a RHV resource name is used in a NetworkMap , StorageMap , or Plan custom resource (CR) and if the same resource name exists in another data center, the Plan CR displays a critical "Ambiguous reference" condition. You must rename the resource or use the resource UUID in the CR. In the web console, the resource name appears twice in the same list without a data center reference to distinguish them. You must rename the resource. ( BZ#1993089 ) Snapshots are not deleted after warm migration Snapshots are not deleted automatically after a successful warm migration of a VMware VM. You must delete the snapshots manually in VMware vSphere. ( BZ#2001270 )