OvmfPkg PlatformBootManagerLib: Move TryRunningQemuKernel()

[edk2-devel] [PATCH 0/1] OvmfPkg PlatformBootManagerLib: Move TryRunningQemuKernel()

Christoph Willing posted 1 patch 2 years, 8 months ago

Download series mbox

Patches applied successfully (tree, apply log)
git fetch https://github.com/patchew-project/edk2 tags/patchew/20210728020232.127332-1-chris.willing@linux.com

OvmfPkg/Library/PlatformBootManagerLib/BdsPlatform.c | 8 ++++----
1 file changed, 4 insertions(+), 4 deletions(-)

Expand all Fold all

[edk2-devel] [PATCH 0/1] OvmfPkg PlatformBootManagerLib: Move TryRunningQemuKernel()

Posted by Christoph Willing 2 years, 8 months ago

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/1787277
Group Owner: devel+owner@edk2.groups.io
Unsubscribe: https://edk2.groups.io/g/devel/unsub [importer@patchew.org]
-=-=-=-=-=-=-=-=-=-=-=-