Skip to content

Latest commit

 

History

History
51 lines (28 loc) · 3.05 KB

known-issues-2-7.adoc

File metadata and controls

51 lines (28 loc) · 3.05 KB

Known issues

{project-first} 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)

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 {project-short} 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)