Testing supermin, it looks to be doing the right thing WRT to picking up the host kernel/initrd when running on a systemd-boot machine when those items are found in /boot/efi/$MACHINEID/$KERNELVER/kernel.

That appears to be because its actually symlinking the kernel from /lib/modules/$KERNELVER.

That said, at least on aarch64 machines, it seems the resulting example images won't boot, and it appears the problem is because qemu doesn't yet understand the ZBOOT (PE wrapped compressed kernel image) format being used in fedora when passed as a -kernel, because there isn't a direct entry point unless something decompresses the image (AKA a UEFI compliant firmware running in the guest as well).

So, this might just be a qemu bug, but per the fedora-dev mailing list, i'm going to open it here as a placeholder since I can't seem to validate a full supermin sequence at the moment.




Reproducible: Always

Steps to Reproduce:
1. Install a systemd-boot machine with inst.sdboot/etc.
2. Install supermin
3. Follow the examples frp, https://libguestfs.org/supermin.1.html to create an image
4. Attempt to boot image, tweaking parms for aarch64
Actual Results:  
No response from qemu when passed the supermin kernel with -kernel, which looks like it could be a problem with the -serial device, but it behaves the same when -kernel is just garbage too.


Expected Results:  
The image boots per the instructions.