Created attachment 1941768 [details] rocky9-guest-convert-to-libvirt.log Description of problem: kernel panic when booting into OS with rocky9 guest converted by v2v to local libvirt Version-Release number of selected component (if applicable): virt-v2v-2.2.0-3.el9.x86_64 libosinfo-1.10.0-1.el9.x86_64 osinfo-db-20221130-1.el9.noarch nbdkit-server-1.32.5-3.el9.x86_64 libvirt-libs-9.0.0-2.el9.x86_64 qemu-img-7.2.0-5.el9.x86_64 libguestfs-1.48.4-4.el9.x86_64 How reproducible: 100% Steps to Reproduce: 1.Convert a Rocky9 guest from VMware to local libvirt by v2v # virt-v2v -ic esx://root.212.36/?no_verify=1 -it vddk -io vddk-libdir=/home/vddk8.0.0 -io vddk-thumbprint=11:97:52:B3:B6:5D:C4:DD:05:D9:D0:43:31:0E:98:CB:73:6E:D6:45 -ip /home/esxpwd rocky9 [ 0.2] Setting up the source: -i libvirt -ic esx://root.212.36/?no_verify=1 -it vddk rocky9 [ 1.6] Opening the source [ 6.9] Inspecting the source [ 13.6] Checking for sufficient free disk space in the guest [ 13.6] Converting Rocky Linux 9.1 (Blue Onyx) to run on KVM virt-v2v: This guest has virtio drivers installed. [ 129.0] Mapping filesystem data to avoid copying unused and blank areas [ 130.0] Closing the overlay [ 130.3] Assigning disks to buses [ 130.3] Checking if the guest needs BIOS or UEFI to boot virt-v2v: This guest requires UEFI on the target to boot. [ 130.3] Setting up the destination: -o libvirt [ 139.3] Copying disk 1/1 █ 100% [****************************************] [ 267.8] Creating output metadata virt-v2v: warning: unknown guest operating system: linux rocky 9.1 x86_64 (Rocky Linux 9.1 (Blue Onyx)) [ 267.9] Finishing off 2.Power on guest but found kernel panic during OS booting Actual results: As above description Expected results: Hide virt-v2v warning: unknown guest operating system: linux rocky 9.1 x86_64 when convert rocky guests to local libvirt Additional info: Rocky9 guest can boot into OS successfully when convert to rhv by v2v
Well... what are the details of the panic? My guess is that we're seeing a duplicate of bug 2076013 (note: conversion output is similarly "local libvirt"), and that we need to refine commit f28757c6d100 ("convert_linux: set "gcaps_default_cpu = false" for x86_64 RHEL-9.0+ guests", 2022-04-22). I suspect that we currently don't put "rhel" in i_distro for Rocky, and therefore we don't choose host CPU passthrough, and fail to satisfy the 'x86_64-v2' ABI requirement of the guest. Hm yeah, I can actually confirm that, from the attachment on comment#0: > i_distro = rocky > ... > gcaps_default_cpu = true As I wrote in the commit message of f28757c6d100: (Libosinfo does not track processor support, so in the future we may have to extend the expression added in this patch to other distros.) So I guess I'll fix this... sometime. :/
Fixed upstream: https://github.com/libguestfs/virt-v2v/commit/9f12b95bbe7bc2850ce4ba134c46a3cc5fd1167d
Tried with the versions: libguestfs-1.48.4-4.el9.x86_64 osinfo-db-20221130-1.el9.noarch libosinfo-1.10.0-1.el9.x86_64 libvirt-libs-9.0.0-3.el9.x86_64 nbdkit-server-1.32.5-4.el9.x86_64 qemu-img-7.2.0-7.el9.x86_64 virt-v2v-2.2.0-5.el9.x86_64 Steps: 1. Convert Rocky guests from VMware to local libvirt by v2v # virt-v2v -ic esx://root.212.36/?no_verify=1 -it vddk -io vddk-libdir=/home/vddk8.0.0 -io vddk-thumbprint=11:97:52:B3:B6:5D:C4:DD:05:D9:D0:43:31:0E:98:CB:73:6E:D6:45 -ip /v2v-ops/esx_data_pwd rocky9 [ 0.2] Setting up the source: -i libvirt -ic esx://root.212.36/?no_verify=1 -it vddk rocky9 [ 1.5] Opening the source [ 10.6] Inspecting the source [ 19.2] Checking for sufficient free disk space in the guest [ 19.2] Converting Rocky Linux 9.1 (Blue Onyx) to run on KVM virt-v2v: This guest has virtio drivers installed. [ 171.9] Mapping filesystem data to avoid copying unused and blank areas [ 172.9] Closing the overlay [ 173.2] Assigning disks to buses [ 173.2] Checking if the guest needs BIOS or UEFI to boot virt-v2v: This guest requires UEFI on the target to boot. [ 173.2] Setting up the destination: -o libvirt [ 174.7] Copying disk 1/1 █ 100% [****************************************] [ 303.2] Creating output metadata [ 303.3] Finishing off 2. Start the guests and check The rocky9 guest can be running and start into OS successfully. Marking as Verified:Tested.
Marking as Verified.
Since the problem described in this bug report should be resolved in a recent advisory, it has been closed with a resolution of ERRATA. For information on the advisory (virt-v2v bug fix and enhancement update), and where to find the updated files, follow the link below. If the solution does not work for you, open a new bug report. https://access.redhat.com/errata/RHBA-2023:2313