For example when running virt-v2v-inspector it says: "virt-v2v-inspector: error: no bootloader detected" on a valid libvirt/kvm bootable guest using systemd-boot. Reproducible: Always Steps to Reproduce: 1. Boot/install a fedora image utilizing systemd-boot on the ESP 2. Run virt-v2v-inspector -i disk $DISKIMAGE 3. Wait for successful completion. Actual Results: [root@mammon-tx2 jlinton]# virt-v2v-inspector -i disk /var/lib/libvirt/images/fedora-rawhide-systemd-boot.qcow2 [ 0.0] Setting up the source: -i disk /var/lib/libvirt/images/fedora-rawhide-systemd-boot.qcow2 [ 1.1] Opening the source [ 10.7] Inspecting the source [ 17.2] Checking for sufficient free disk space in the guest [ 17.2] Converting Fedora Linux 39 (Server Edition Prerelease) to run on KVM virt-v2v-inspector: error: no bootloader detected If reporting bugs, run virt-v2v-inspector with debugging enabled and include the complete output: virt-v2v-inspector -v -x [...]
Created attachment 1975506 [details] Debug output from virt-v2v-inspector run
Although, even with a grub based rawhide on aarch64 it still displays warnings that might need attention: [root@mammon-tx2 jlinton]# virt-v2v-inspector -i disk /var/lib/libvirt/images/fedora-rawhide-2.qcow2 [ 0.0] Setting up the source: -i disk /var/lib/libvirt/images/fedora-rawhide-2.qcow2 [ 1.1] Opening the source [ 11.1] Inspecting the source [ 17.4] Checking for sufficient free disk space in the guest [ 17.4] Converting Fedora Linux 39 (Server Edition Prerelease) to run on KVM virt-v2v-inspector: The QEMU Guest Agent will be installed for this guest at first boot. virt-v2v-inspector: Can't fix UEFI bootloader. VM may not boot.
This bug appears to have been reported against 'rawhide' during the Fedora Linux 39 development cycle. Changing version to 39.