Secure boot with fedora

[SleepInfinity]

Hello,

I installed Fedora 43 in a VHD using VirtualBox, ran the vhdboot.sh script inside Fedora, and then copied the VHD file to Ventoy with the .vtoy suffix.

However, when I try to boot it on my PC in UEFI mode with Secure Boot enabled, I get the following errors:

Loading Linux 6.17.9-300.fc43.×86_64 ...
error:../../grub-core/kern/efi/sb.c:189:shim_lock protocol not found.
Loading initial ramdisk ...
error:../../grub-core/loader/i386/efi/linux.c:260:you need to load the kernel
first.
Press any key to continue....

Disabling Secure Boot fixes the issue, but I want it to support Secure Boot since I need to be able to boot Fedora on school PCs where I don't have access to the BIOS settings.

I found an issue mentioning that I should add the -s argument to the script to enable Secure Boot support, but this doesn’t seem to change anything.

Thank you.

[mrgarbagegamer]

Bumping your issue, though I did find a workaround that works:

Using the VentoyPlugson tool, find and enable the VTOY_LINUX_REMOUNT option. That seems to fix the problem for me (when running with Ubuntu 24.04), though it might increase the startup time by a bit (I'm still trying to test to see if there's an actual difference).

[admirabilis]

Hi! With VTOY_LINUX_REMOUNT, it starts booting, but then I get from the kernel:

device-mapper: reload ioctl on ventoy failed: Invalid argument
Command failed.
Waiting for ventoy device ...
[ 9.943180] device-mapper: table: 253:1: linear: Gap in table
device-mapper: reload ioctl on ventoy failed: Invalid argument
Command failed.
device-mapper: create ioctl on nvme0n1p4 failed: Device or resource busy

Waiting for ventoy device ...
Waiting for ventoy device ...
Waiting for ventoy device ...

Any help would be appreciated.