Chapter 1. Migration Toolkit for Virtualization 2.7 You can use the Migration Toolkit for Virtualization (MTV) to migrate virtual machines from the following source providers to OpenShift Virtualization destination providers: VMware vSphere versions 6, 7, and 8 Red Hat Virtualization (RHV) OpenStack Open Virtual Appliances (OVAs) that were created by VMware vSphere Remote OpenShift Virtualization clusters The release notes describe technical changes, new features and enhancements, known issues, and resolved issues. 1.1. Technical changes Migration Toolkit for Virtualization (MTV) 2.7 has the following technical changes: Upgraded virt-v2v to RHEL9 for warm migrations MTV previously used virt-v2v from Red Hat Enterprise Linux (RHEL) 8, which does not include bug fixes and features that are available in virt-v2v in RHEL9. In MTV 2.7.0, components are updated to RHEL 9 in order to improve the functionality of warm migration. (MTV-1152) 1.2. New features and enhancements Migration Toolkit for Virtualization (MTV) 2.7 introduces the following features and enhancements: In MTV 2.7.0, warm migration is now based on RHEL 9 inheriting features and bug fixes. In MTV 2.7.10, you can specify the plan.spec.diskBus which will be on all disks during the creation. Possible options are: SCSI SATA VirtIO Note Virtual machines (VMs) that are migrated in migration plans by using the diskBus:scsi option fail to boot after migration as follows: All Windows VMs fail to boot. Some Linux VMs fail to boot. VMs that use the plan.spec.diskBus:sata and plan.spec.diskBus:virtio options successfully boot after migration. In MTV 2.7.11, you can now migrate shared disks from VMware vSphere by using a new parameter named migrateSharedDisks in Plan CRs. The parameter can be set to true or false : When set to true, MTV migrates all shared disks in the CR. When set to false , MTV does not migrate the shared disks. Note migrateSharedDisks applies only to cold migrations. Warm migration of shared disks is not supported. 1.3. Resolved issues Migration Toolkit for Virtualization (MTV) 2.7 has the following resolved issues: 1.3.1. Resolved issues 2.7.11 Main controller container of forklift controller crashes during VMware migrations In earlier releases of MTV, the main controller container of forklift-container crashed during VMware migrations because users created snapshots of the virtual machines (VMs) during migrations. As a result, some VMs migrated, but others failed to migrate. This issue has been resolved in MTV 2.7.11, but users are cautioned not to create snapshots of VMs during migrations. (MTV-2164) 1.3.2. Resolved issues 2.7.10 OVN secondary network not working with Multus default network override In earlier releases of MTV, the OVN secondary network was not working with Multus default network override. This issue caused the importer pod to become stuck, as the importer pod was created when there were multiple networks and the wrong default network override annotation was configured. This issue has been resolved in MTV 2.7.10. (MTV-1645) Retain IP field description misleading to customers In earlier releases of MTV, it was difficult to understand the user interface relating to the Preserve IPs VM setting in the chosen setting mode. This issue has been resolved in MTV 2.7.10. (MTV-1743) Persistent TPM is always added to the Windows 2022 VM after conversion In earlier releases of MTV, when migrating a Windows Server 2022 VMware virtual machine (VM) to OpenShift Virtualization, the VMI had the Trusted Platform Module (TPM) module configured, even though the module was not configured in the original VM. This issue has been resolved in MTV 2.7.10. (MTV-1939) 1.3.3. Resolved issues 2.7.9 Forklift controller panic in the inventory In earlier releases of MTV, the forklift-contoller inventory container would panic, and the VM would not be migrated. This issue has been resolved in MTV 2.7.9. (MTV-1610) vCenter sessions keep on increasing during migration plan execution In earlier releases of MTV, when migrating virtual machines (VMs) from VMware vSphere 7 to OpenShift Virtualization, vCenter sessions kept increasing. This issue has been resolved in MTV 2.7.9. (MTV-1929) 1.3.4. Resolved issues 2.7.8 MTV not handling OVA NFS URL if it does not contain : char In earlier releases of MTV, the character : in the NFS URL of OVAs was not handled, which created malformed URLs. This issue has been resolved in MTV 2.7.8. (MTV-1856) Changing the host migration network returns an unexpected error In earlier releases of MTV, when changing the network from VMkernel to Management network , the migration network changed. However, an error message was returned that the request could not be completed due to an incorrect user name or password . This issue has been resolved in MTV 2.7.8. (MTV-1862) Migrating RHEL VMs with LUKS disk fail at DiskTransferV2v stage In earlier releases of MTV, migrating Red Hat Enterprise Linux (RHEL) virtual machines (VMs) with disks encrypted with Linux Unified Key Setup (LUKS) enabled from VMWare fails at the DiskTransferV2v stage. This issue has been resolved in MTV 2.7.8. (MTV-1864) Q35 machine type is hard-coded during import from vSphere In earlier releases of MTV, VMs imported from vSphere always had the Q35 machine type set. However, the machine type is floating , and thus the VM application binary interface (ABI) can change between reboots. This issue has been resolved in MTV 2.7.8. (MTV-1865) memory.requests and memory.guest are set during import from VMware In earlier releases of MTV, MTV imported VMs with the requests.memory field and the memory.guest field set. This was problematic as it prevented memory overcommit, memory hot-plug, and caused unnecessary memory pressure on VMs that could lead to out-of-memory (OOM) errors. This issue has been resolved in MTV 2.7.8. (MTV-1866) virt-v2v failure when converting dual-boot VM In earlier releases of MTV, there was an issue when attempting the migration of a VM with two disks with two different operating systems installed in a dual-boot configuration. This issue has been resolved in MTV 2.7.8. (MTV-1877) 1.3.5. Resolved issues 2.7.7 MTV Controller waiting for snapshot creation In earlier releases of MTV, when performing a warm migration using 200 VMs, the MTV Controller could pause the migration during snapshot creation. This issue has been resolved in MTV 2.7.7. (MTV-1775) Extended delay in time taken for VMs to start migration In earlier releases of MTV, in some situations there was an extended delay before all VMs started to migrate. This issue has been resolved in MTV 2.7.7. (MTV-1774) Warm migration plan with multi-VMs from ESXi host provider fails in cutover phase In earlier releases of MTV, the migration plan with multi-VMs from an ESXi host provider failed in the cutover phase. This issue has been resolved in MTV 2.7.7. (MTV-1753) SecureBoot enabled VM in migrated with SecureBoot disabled In earlier releases of MTV, when migrating a virtual machine (VM) with Secure Boot enabled , the VM had Secure Boot disabled after being migrated. This issue has been resolved in MTV 2.7.7. (MTV-1632) VDDK validator fails to launch in environments with quota set In earlier releases of MTV, after creating a migration plan from a VMware provider, the VDDK validation failed due to a LimitRange not being provided to add requests and limits to any container that do not define them. This issue has been resolved in MTV 2.7.7, with MTV setting limits by default to make the migration plan work out of the box. (MTV-1493) 1.3.6. Resolved issues 2.7.6 Warning if preserve static IP is mapped to pod network In earlier releases of MTV, there was no warning message for preserving static IPs while using Pod networking. This issue has been resolved in MTV 2.7.6. (MTV-1503) Schedule the cutover for an archived plan is not allowed In earlier releases of MTV, the option to schedule a cutover for an archived plan was currently available in the UI. This issue has been resolved in MTV 2.7.6 with the cutover action disabled for an archived plan. (MTV-1729) button misplaced in Create new plan wizard In earlier releases of MTV, when creating a new Migration Plan with the Create new plan wizard, after filling in the form, the button was misplaced to the left of the Back option. This issue has been resolved in MTV 2.7.6. (MTV-1732) Static IP address is not preserved for Debian-based VMs that use interfaces In earlier releases of MTV, all Debian-based operating systems could have the network configurations in the /etc/network/interfaces , but information was not fetched from these config files when creating the udev rule to set the interface name. This issue has been resolved in MTV 2.7.6. (MTV-1711) Editing of plan settings is enabled for all plan statuses In earlier releases of MTV, VMS were removed from archived or archiving plans. This issue has been resolved in MTV 2.7.6, and if a plan's status is either archiving or archived, the option to remove VMs for that plan is blocked. (MTV-1713) Warm migration fails to complete In earlier releases of MTV, after the first Disk Transfer step set was completed, the cutover was set. However, during the Image Conversion step, not all data volumes were completed, with some of them being stuck in the import in progress phase and 100% progress . This issue has been resolved in MTV 2.7.6. (MTV-1717) 1.3.7. Resolved issues 2.7.5 XFS filesystem corruption after warm migration of VM from VMware In earlier releases of MTV, virtual machines (VM) were presenting XFS filesystem and other data corruption after the warm migration from VMware to OpenShift Virtualization using MTV. This issue has been resolved in MTV 2.7.5. (MTV-1679) Missing VM network-ID in the inventory In earlier releases of MTV, after creating a migration plan for VMs with a NSX-T network attached from vSphere, the VM network mapping was missing, and also adding network mapping could not list NSX-T networks as source networks. This issue has been resolved in MTV 2.7.5. (MTV-1695) and (MTV-1140) Failure to create Windows 2019 VM during Cold Migration In earlier releases of MTV, cold migrating Windows Server 2019 VM from Red Hat Virtualization (RHV) to a remote cluster returned a firmware.bootloader setting error of admission webhook "virtualmachine-validator.kubevirt.io" denied the request during the VirtualMachineCreation phase. This issue has been resolved in MTV 2.7.5. (MTV-1613) PreferredEfi applied when BIOS already enabled within VirtualMachineInstanceSpec In earlier releases of MTV, PreferredUseEfi was applied when the BIOS was already enabled within the VirtualMachineInstanceSpec . In MTV 2.7.5, PreferredEfi is only applied when a user has not provided their own EFI configuration and the BIOS is additionally not enabled. (CNV-49381) 1.3.8. Resolved issues 2.7.4 XFS filesystem corruption after warm migration of VM from VMware In earlier releases of MTV, in some cases, the destination VMware virtual machine (VM) was observed to have XFS filesystem corruption after being migrated to OpenShift Virtualization using MTV. This issue has been resolved in MTV 2.7.4. (MTV-1656) Error Did not find CDI importer pod for DataVolume is recorded in the forklift-controller logs during the CopyDisks phase In earlier releases of MTV, the forklift-controller incorrectly logged an error Did not find CDI importer pod for DataVolume during the CopyDisks phase. This issue has been resolved in MTV 2.7.4. (MTV-1627) 1.3.9. Resolved issues 2.7.3 Migration plan does not fail when conversion pod fails In earlier releases of MTV, when running the virt-v2v guest conversion, the migration plan did not fail if the conversion pod failed, as expected. This issue has been resolved in MTV 2.7.3. (MTV-1569) Large number of VMs in the inventory can cause the inventory controller to panic In earlier releases of MTV, having a large number of virtual machines (VMs) in the inventory could cause the inventory controller to panic and return a concurrent write to websocket connection warning. This issue was caused by the concurrent write to the WebSocket connection and has been addressed by the addition of a lock, so the Go routine waits before sending the response from the server. This issue has been resolved in MTV 2.7.3. (MTV-1220) VM selection disappears when selecting multiple VMs in the Migration Plan In earlier releases of MTV, the VM selection checkbox disappeared after selecting multiple VMs in the Migration Plan. This issue has been resolved in MTV 2.7.3. (MTV-1546) forklift-controller crashing during OVA plan migration In earlier releases of MTV, the forklift-controller would crash during an OVA plan migration, returning a runtime error: invalid memory address or nil pointer dereference panic. This issue has been resolved in MTV 2.7.3. (MTV-1577) 1.3.10. Resolved issues 2.7.2 VMNetworksNotMapped error occurs after creating a plan from the UI with the source provider set to OpenShift Virtualization In earlier releases of MTV, after creating a plan with an OpenShift Virtualization source provider, the Migration Plan failed with the error The plan is not ready - VMNetworksNotMapped . This issue has been resolved in MTV 2.7.2. (MTV-1201) Migration Plan for OpenShift Virtualization to OpenShift Virtualization missing the source namespace causing VMNetworkNotMapped error In earlier releases of MTV, when creating a Migration Plan for an OpenShift Virtualization to OpenShift Virtualization migration using the Plan Creation Form, the network map generated was missing the source namespace, which caused a VMNetworkNotMapped error on the plan. This issue has been resolved in MTV 2.7.2. (MTV-1297) DV, PVC, and PV are not cleaned up and removed if the migration plan is Archived and Deleted In earlier releases of MTV, the DataVolume (DV), PersistentVolumeClaim (PVC), and PersistentVolume (PV) continued to exist after the migration plan was archived and deleted. This issue has been resolved in MTV 2.7.2. (MTV-1477) Other migrations are halted from starting as the scheduler is waiting for the complete VM to get transferred In earlier releases of MTV, when warm migrating a virtual machine (VM) that has several disks, you had to wait for the complete VM to get migrated, and the scheduler was halted until all the disks finished before the migration would be started. This issue has been resolved in MTV 2.7.2. (MTV-1537) Warm migration is not functioning as expected In earlier releases of MTV, warm migration did not function as expected. When running the warm migration with VMs larger than the MaxInFlight disks, the VMs over this number did not start the migration until the cutover. This issue has been resolved in MTV 2.7.2. (MTV-1543) Migration hanging due to error: virt-v2v: error: -i libvirt: expecting a libvirt guest name In earlier releases of MTV, when attempting to migrate a VMware VM with a non-compliant Kubernetes name, the Openshift console returned a warning that the VM would be renamed. However, after starting the Migration Plan, it hangs since the migration pod is in an Error state. This issue has been resolved in MTV 2.7.2. This issue has been resolved in MTV 2.7.2. (MTV-1555) VMs are not migrated if they have more disks than MAX_VM_INFLIGHT In earlier releases of MTV, when migrating the VM using the warm migration, if there were more disks than the MAX_VM_INFLIGHT the VM was not scheduled and the migration was not started. This issue has been resolved in MTV 2.7.2. (MTV-1573) Migration Plan returns an error even when Changed Block Tracking (CBT) is enabled In earlier releases of MTV, when running a VM in VMware, if the CBT flag was enabled while the VM was running by adding both ctkEnabled=TRUE and scsi0:0.ctkEnabled=TRUE parameters, an error message Danger alert:The plan is not ready - VMMissingChangedBlockTracking was returned, and the migration plan was prevented from working. This issue has been resolved in MTV 2.7.2. (MTV-1576) 1.3.11. Resolved issues 2.7.0 Change . to - in the names of VMs that are migrated In earlier releases of MTV, if the name of the virtual machines (VMs) contained . , this was changed to - when they were migrated. This issue has been resolved in MTV 2.7.0. (MTV-1292) Status condition indicating a failed mapping resource in a plan is not added to the plan In earlier releases of MTV, a status condition indicating a failed mapping resource of a plan was not added to the plan. This issue has been resolved in MTV 2.7.0, with a status condition indicating the failed mapping being added. (MTV-1461) ifcfg files with HWaddr cause the NIC name to change In earlier releases of MTV, interface configuration (ifcfg) files with a hardware address (HWaddr) of the Ethernet interface caused the name of the network interface controller (NIC) to change. This issue has been resolved in MTV 2.7.0. (MTV-1463) Import fails with special characters in VMX file In earlier releases of MTV, imports failed when there were special characters in the parameters of the VMX file. This issue has been resolved in MTV 2.7.0. (MTV-1472) Observed invalid memory address or nil pointer dereference panic In earlier releases of MTV, an invalid memory address or nil pointer dereference panic was observed, which was caused by a refactor and could be triggered when there was a problem with the inventory pod. This issue has been resolved in MTV 2.7.0. (MTV-1482) Static IPv4 changed after warm migrating win2022/2019 VMs In earlier releases of MTV, the static Internet Protocol version 4 (IPv4) address was changed after a warm migration of Windows Server 2022 and Windows Server 2019 VMs. This issue has been resolved in MTV 2.7.0. (MTV-1491) Warm migration is missing arguments In earlier releases of MTV, virt-v2v-in-place for the warm migration was missing arguments that were available in virt-v2v for the cold migration. This issue has been resolved in MTV 2.7.0. (MTV-1495) Default gateway settings changed after migrating Windows Server 2022 VMs with preserve static IPs In earlier releases of MTV, the default gateway settings were changed after migrating Windows Server 2022 VMs with the preserve static IPs setting. This issue has been resolved in MTV 2.7.0. (MTV-1497) 1.4. Known issues Migration Toolkit for Virtualization (MTV) 2.7 has the following known issues: Select Migration Network from the endpoint type ESXi displays multiple incorrect networks When you choose Select Migration Network , from the endpoint type of ESXi , multiple incorrect networks are displayed. (MTV-1291) VMs with Secure Boot enabled might not be migrated automatically Virtual machines (VMs) with Secure Boot enabled currently might not be migrated automatically. This is because Secure Boot, a security standard developed by members of the PC industry to ensure that a device boots using only software that is trusted by the Original Equipment Manufacturer (OEM), would prevent the VMs from booting on the destination provider. Workaround: The current workaround is to disable Secure Boot on the destination. For more details, see Disabling Secure Boot . (MTV-1548) Windows VMs which are using Measured Boot cannot be migrated Microsoft Windows virtual machines (VMs), which are using the Measured Boot feature, cannot be migrated because Measured Boot is a mechanism to prevent any kind of device changes, by checking each start-up component, including the firmware, all the way to the boot driver. The alternative to migration is to re-create the Windows VM directly on OpenShift Virtualization. Migration of a VM with Secure Boot enabled VM migration results in a VM with Secure Boot disabled When migrating a virtual machine (VM) with Secure Boot enabled, the VM has Secure Boot as disabled after being migrated. This issue has been resolved in MTV 2.7.7. (MTV-1632) OVN secondary network is not functioning as expected with the Multus default network override The secondary network of Open Virtual Network (OVN) does not function as expected with the Multus default network override. (MTV-1645) Network and Storage maps in the UI are not correct when created from the command line When creating Network and Storage maps from the UI, the correct names are not shown in the UI. (MTV-1421) Migration fails with module network-legacy configured in RHEL guests Migration fails if the module configuration file is available in the guest and the dhcp-client package is not installed, returning a dracut module 'network-legacy' will not be installed, because command 'dhclient' could not be found error. (MTV-1615) Harden grub2-mkconfig to avoid overwriting /boot/efi/EFI/redhat/grub.cfg In Red Hat Enterprise Linux (RHEL) 9, there has been a significant change in how GRUB is handled on UEFI systems. Previously, the GRUB configuration file, /boot/efi/EFI/redhat/grub.cfg , was used on UEFI systems. However, in RHEL 9, this file now serves as a stub that dynamically redirects to the GRUB configuration, located at /boot/grub2/grub.cfg . This behavior is expected in RHEL 9.4, but has been resolved in RHEL 9.5. (RHEL-32099) Migration fails for VMs backed by vSAN without VDDK Migrations for virtual machines (VMs) that are backed by VMware vSAN must use a Virtual Disk Development Kit (VDDK) image. Without a VDDK image, these migrations fail. (MTV-2203) Migrated VMs that use the diskBus:scsi option fail to boot VMs that are migrated in migration plans by using the plan.spec.diskBus:scsi option fail to boot after migration as follows: All Windows VMs fail to boot. Some Linux VMs fail to boot. VMs that use the plan.spec.diskBus:sata and plan.spec.diskBus:virtio options successfully boot after migration. (MTV-2199)

Commands: