Use of Qemu's -kernel option (thus also -initrd & -append) is currently not working correctly under UEFI boot. The nominated kernel is loaded and the initrd is opened successfully but there is no access to the VM filesystem. Booting without the -kernel option i.e. using the VM's internal kernel & intird works as expected with UEFI.
This behaviour has been observed in all of the four Linux systems tested for verification. The commit at which this behaviour appears has been identified and the patch proposed here just reverses it i.e. we now run TryRunningQemuKernel() after PlatformBdsConnectSequence() instead of before it. When the proposed patch is applied, all four systems are subsequently able to boot correctly under UEFI. Christoph Willing (1): OvmfPkg PlatformBootManagerLib: Move TryRunningQemuKernel() OvmfPkg/Library/PlatformBootManagerLib/BdsPlatform.c | 8 ++++---- 1 file changed, 4 insertions(+), 4 deletions(-) -- 2.32.0 -=-=-=-=-=-=-=-=-=-=-=- Groups.io Links: You receive all messages sent to this group. View/Reply Online (#78260): https://edk2.groups.io/g/devel/message/78260 Mute This Topic: https://groups.io/mt/84497351/21656 Group Owner: devel+ow...@edk2.groups.io Unsubscribe: https://edk2.groups.io/g/devel/unsub [arch...@mail-archive.com] -=-=-=-=-=-=-=-=-=-=-=-