public inbox for devel@edk2.groups.io
 help / color / mirror / Atom feed
From: "Christoph Willing" <chris.willing@linux.com>
To: devel@edk2.groups.io
Cc: Christoph Willing <chris.willing@linux.com>
Subject: [PATCH 0/1] OvmfPkg PlatformBootManagerLib: Move TryRunningQemuKernel()
Date: Wed, 28 Jul 2021 12:02:32 +1000	[thread overview]
Message-ID: <20210728020232.127332-1-chris.willing@linux.com> (raw)

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


             reply	other threads:[~2021-07-28  2:18 UTC|newest]

Thread overview: 19+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-07-28  2:02 Christoph Willing [this message]
2021-07-28  2:02 ` [PATCH 1/1] OvmfPkg PlatformBootManagerLib: Move TryRunningQemuKernel() Christoph Willing
2021-08-09 13:08   ` [edk2-devel] " Ard Biesheuvel
     [not found] ` <1695D2E15A92C8E7.3876@groups.io>
2021-08-09 12:53   ` Christoph Willing
2021-08-09 14:52     ` James Bottomley
2021-08-10  0:10       ` Christoph Willing
2021-08-10  6:01         ` Gerd Hoffmann
2021-08-10 12:10           ` Christoph Willing
2021-08-10 14:26         ` James Bottomley
2021-08-10 23:04           ` Christoph Willing
2021-08-10 23:24             ` James Bottomley
2021-08-11  0:34               ` Christoph Willing
2021-08-11  6:12                 ` Gerd Hoffmann
2021-08-11  9:55                   ` Christoph Willing
2021-08-11 10:30                     ` Ard Biesheuvel
2021-08-12 12:41                       ` Christoph Willing
2021-08-12 13:36                         ` Gerd Hoffmann
2021-08-12 14:07                           ` Christoph Willing
2021-08-11  6:08           ` Gerd Hoffmann

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-list from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=20210728020232.127332-1-chris.willing@linux.com \
    --to=devel@edk2.groups.io \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox