Bug 2222485 - virt-v2v-inspector (and others) is unaware of systemd-boot based systems with kernel/initrd in ESP
Summary: virt-v2v-inspector (and others) is unaware of systemd-boot based systems with...
Keywords:
Status: NEW
Alias: None
Product: Fedora
Classification: Fedora
Component: virt-v2v
Version: 42
Hardware: aarch64
OS: Linux
unspecified
medium
Target Milestone: ---
Assignee: Richard W.M. Jones
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2023-07-13 00:20 UTC by Jeremy Linton
Modified: 2025-02-26 12:54 UTC (History)
2 users (show)

Fixed In Version:
Clone Of:
Environment:
Last Closed:
Type: ---
Embargoed:


Attachments (Terms of Use)
Debug output from virt-v2v-inspector run (1.09 MB, text/plain)
2023-07-13 00:28 UTC, Jeremy Linton
no flags Details

Description Jeremy Linton 2023-07-13 00:20:38 UTC
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 [...]

Comment 1 Jeremy Linton 2023-07-13 00:28:05 UTC
Created attachment 1975506 [details]
Debug output from virt-v2v-inspector run

Comment 2 Jeremy Linton 2023-07-13 00:28:53 UTC
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.

Comment 3 Fedora Release Engineering 2023-08-16 08:12:45 UTC
This bug appears to have been reported against 'rawhide' during the Fedora Linux 39 development cycle.
Changing version to 39.

Comment 4 Aoife Moloney 2024-11-08 10:55:36 UTC
This message is a reminder that Fedora Linux 39 is nearing its end of life.
Fedora will stop maintaining and issuing updates for Fedora Linux 39 on 2024-11-26.
It is Fedora's policy to close all bug reports from releases that are no longer
maintained. At that time this bug will be closed as EOL if it remains open with a
'version' of '39'.

Package Maintainer: If you wish for this bug to remain open because you
plan to fix it in a currently maintained version, change the 'version' 
to a later Fedora Linux version. Note that the version field may be hidden.
Click the "Show advanced fields" button if you do not see it.

Thank you for reporting this issue and we are sorry that we were not 
able to fix it before Fedora Linux 39 is end of life. If you would still like 
to see this bug fixed and are able to reproduce it against a later version 
of Fedora Linux, you are encouraged to change the 'version' to a later version
prior to this bug being closed.

Comment 5 Aoife Moloney 2025-02-26 12:54:00 UTC
This bug appears to have been reported against 'rawhide' during the Fedora Linux 42 development cycle.
Changing version to 42.


Note You need to log in before you can comment on or make changes to this bug.