RHBA-2023:2313 - Bug Fix Advisory

Topic

An update for virt-v2v is now available for Red Hat Enterprise Linux 9.

Description

For detailed information on changes in this release, see the Red Hat Enterprise Linux 9.2 Release Notes linked from the References section.

Solution

Before applying this update, make sure all previously released errata
relevant to your system have been applied.

For details on how to apply this update, refer to:

https://access.redhat.com/articles/11258

Affected Products

• Red Hat Enterprise Linux for x86_64 9 x86_64
• Red Hat Enterprise Linux for x86_64 - Extended Update Support 9.6 x86_64
• Red Hat Enterprise Linux for x86_64 - Extended Update Support 9.4 x86_64
• Red Hat Enterprise Linux for x86_64 - Extended Update Support 9.2 x86_64
• Red Hat Enterprise Linux Server - AUS 9.6 x86_64
• Red Hat Enterprise Linux Server - AUS 9.4 x86_64
• Red Hat Enterprise Linux Server - AUS 9.2 x86_64
• Red Hat Enterprise Linux for x86_64 - Update Services for SAP Solutions 9.6 x86_64
• Red Hat Enterprise Linux for x86_64 - Update Services for SAP Solutions 9.4 x86_64
• Red Hat Enterprise Linux for x86_64 - Update Services for SAP Solutions 9.2 x86_64
• Red Hat CodeReady Linux Builder for x86_64 9 x86_64
• Red Hat CodeReady Linux Builder for x86_64 - Extended Update Support 9.6 x86_64
• Red Hat CodeReady Linux Builder for x86_64 - Extended Update Support 9.4 x86_64
• Red Hat CodeReady Linux Builder for x86_64 - Extended Update Support 9.2 x86_64

Fixes

• BZ - 2131123 - RHEL7 UEFI guest turns into black after v2v conversion
• BZ - 2135762 - RHEL 9.2: Rebase virt-v2v to 2.2
• BZ - 2149629 - Win 2022 fails to boot after virt-p2v conversion from physical host with nvme disk
• BZ - 2149811 - Copy newer versions of drivers for Win 11/Win 2019/Win 2022 during virt-v2v conversion
• BZ - 2149863 - The version of Win 11/Win 2019/Win 2022 shows incorrect on RHV after virt-v2v conversion
• BZ - 2151752 - qemufwcfg device cannot start or has no driver after v2v converting windows guests
• BZ - 2152465 - v2v should set ovirt:id correctly after coverting windows11/2019/2022 guests to rhv via -o rhv-upload
• BZ - 2162331 - In -o kubevirt mode, 'cpu' field appears at the wrong place in the yaml
• BZ - 2162332 - -o kubevirt mode must rename guest to comply with KubeVirt requirements: metadata.name: Invalid value: "esx8.0-rhel8.8-x86_64": a lowercase RFC 1123 subdomain must consist of lower case alphanumeric characters, '-' or '.', and must start and end with an a
• BZ - 2162441 - Incorrect error info for '-o kubevirt' output
• BZ - 2162444 - Enable '--oo compressed' for -o kubevirt
• BZ - 2166565 - Remove option '-oo qemu-boot' info from v2v man page
• BZ - 2166618 - There is virt-v2v: warning: unknown guest operating system: linux rocky 9.1 x86_64 when convert rocky guests to local libvirt
• BZ - 2166619 - kernel panic when booting into OS with rocky9 guest converted by v2v to local libvirt

CVEs

(none)

References

• https://access.redhat.com/documentation/en-us/red_hat_enterprise_linux/9/html/9.2_release_notes/index