Descriptionmxie@redhat.com
2021-05-27 04:21:28 UTC
Created attachment 1787470[details]
debian10.9.0-uefi-guest-cannot-boot-os-after-v2v.png
Description of problem:
Virt-v2v has no UEFI fix rule for debian UEFI guest
Version-Release number of selected component (if applicable):
virt-v2v-1.44.0-1.el9.1.x86_64
libguestfs-1.45.5-1.el9.x86_64
nbdkit-1.25.7-1.el9.x86_64
libvirt-client-7.0.0-6.el9.x86_64
qemu-kvm-6.0.0-2.el9.x86_64
How reproducible:
100%
Steps to Reproduce:
1.Convert debian UEFI guest from VMware to rhv4.4 by v2v
# virt-v2v -ic vpx://root.198.169/data/10.73.199.217/?no_verify=1 -it vddk -io vddk-libdir=/home/vddk7.0 -io vddk-thumbprint=B5:52:1F:B4:21:09:45:24:51:32:56:F6:63:6A:93:5D:54:08:2D:78 -ip /home/passwd -o rhv-upload -oo rhv-direct -oc https://dell-per740-22.lab.eng.pek2.redhat.com/ovirt-engine/api -op /home/rhvpasswd -of raw -os nfs_data -b ovirtmgmt esx7.0-debian10.9.0-x64-uefi
[ 1.0] Opening the source -i libvirt -ic vpx://root.198.169/data/10.73.199.217/?no_verify=1 esx7.0-debian10.9.0-x64-uefi -it vddk -io vddk-libdir=/home/vddk7.0 -io vddk-thumbprint=B5:52:1F:B4:21:09:45:24:51:32:56:F6:63:6A:93:5D:54:08:2D:78
[ 2.7] Creating an overlay to protect the source from being modified
[ 3.5] Opening the overlay
[ 10.5] Inspecting the overlay
[ 18.0] Checking for sufficient free disk space in the guest
[ 18.0] Estimating space required on target for each disk
[ 18.1] Converting 10.9 to run on KVM
virt-v2v: warning: could not determine a way to update the configuration of
Grub2
virt-v2v: Fixing UEFI bootloader.
virt-v2v: No UEFI fix rule for debian 10
virt-v2v: Can't fix UEFI bootloader. VM may not boot.
virt-v2v: This guest has virtio drivers installed.
[ 61.6] Mapping filesystem data to avoid copying unused and blank areas
[ 63.6] Closing the overlay
[ 63.9] Assigning disks to buses
[ 63.9] Checking if the guest needs BIOS or UEFI to boot
virt-v2v: This guest requires UEFI on the target to boot.
[ 63.9] Initializing the target -o rhv-upload -oc https://dell-per740-22.lab.eng.pek2.redhat.com/ovirt-engine/api -op /home/rhvpasswd -os nfs_data
[ 65.4] Copying disk 1/1 to qemu URI json:{ "file.driver": "nbd", "file.path": "/tmp/v2vnbdkit.mfej8f/nbdkit4.sock", "file.export": "/" } (raw)
(100.00/100%)
[ 452.1] Creating output metadata
[ 453.2] Finishing off
2.Power on guest on rhv after v2v conversion, guset can't boot into OS, please refer to screenshot'debian10.9.0-uefi-guest-cannot-boot-os-after-v2v.png'
Actual results:
As above description
Expected results:
Debian UEFI can boot into OS normally after v2v conversion
Additional info:
(In reply to Richard W.M. Jones from comment #2)
> Is this a regression over RHEL 8? Assuming it isn't then it is caused
It's not regression bug, already filed bug1965176 to track the issue on rhel8, unlike rhel9 v2v, there is no v2v info about " No UEFI fix rule for debian 10" when convert debian UEFI on rhel8
Comment 8Richard W.M. Jones
2022-11-01 07:49:12 UTC