From: "Lin, Gary (HPS OE-Linux)" <gary.lin@hpe.com>
To: "Yao, Jiewen" <jiewen.yao@intel.com>, Jim Fehlig <jfehlig@suse.com>
Cc: "devel@edk2.groups.io" <devel@edk2.groups.io>
Subject: Re: [edk2-devel] [PATCH v2 0/5] Fix OvmfXen HVM Direct kernel boot failure
Date: Mon, 16 Aug 2021 09:34:05 +0800 [thread overview]
Message-ID: <YRnAjZBsaBF/TkDF@GaryHPELaptop> (raw)
In-Reply-To: <SJ0PR11MB4894601FC24E5F6EDB0067BF8CFA9@SJ0PR11MB4894.namprd11.prod.outlook.com>
On Fri, Aug 13, 2021 at 09:55:48AM +0000, Yao, Jiewen wrote:
> HI Gary
Hi Jiewen,
> Several comment:
>
> 1) According to our process, we need a Bugzilla. Would you please file it?
>
Okay, will create a bugzilla entry to track the issue.
> 2) I do not understand how HVM direct kernel boot is related to S3 enabling.
> It seems 1/3/4/5 are for S3, while 2 is for missing driver.
> Should we split them to 2 patch set?
>
Actually the inconsistency between QemuFwCfgS3Enabled() and
PcdAcpiS3Enable casued the boot failure of HVM direct kernel boot.
S3SaveStateDxe checked PcdAcpiS3Enable(=FALSE) and skipped S3BootScript.
On the other hand, PlatformBootManagerBeforeConsole() invoked
QemuFwCfgS3Enabled()(=TRUE) and tried to locate S3BootScript. Since
S3BootScript wasn't installed, it failed with EFI_NOT_FOUND and stopped
the booting. So Patch 1 and 2 are mainly for the booting issues in
OvmfXen. For Patch 3~5, I just try to eliminate the inconsistency to
avoid the potential problems.
I can split them into 2 or 3 patch sets if necessary.
> 3) Does the S3 issue only happen in direct kernel boot? Or is it a generic issue.
>
> 4) Have you validated non direct kernel boot to ensure it still works?
>
Jim,
Did you encounter any problem with non direct kernel boot VM?
Cheers,
Gary Lin
>
> > -----Original Message-----
> > From: devel@edk2.groups.io <devel@edk2.groups.io> On Behalf Of Lin, Gary
> > (HPS OE-Linux)
> > Sent: Friday, August 13, 2021 2:13 PM
> > To: devel@edk2.groups.io
> > Subject: [edk2-devel] [PATCH v2 0/5] Fix OvmfXen HVM Direct kernel boot
> > failure
> >
> > When using HVM Direct kernel boot with OvmfXen, it could fail at the
> > S3BootScript due to the inconsistency between QemuFwCfgS3Enabled()
> > and PcdAcpiS3Enable. Besides, QemuKernelLoaderFsDxe wasn't included
> > in OvmfXen, so the firmware couldn't fetch kernel/initrd from fw_cfg.
> >
> > This patch series initializes PcdAcpiS3Enable and adds
> > QemuKernelLoaderFsDxe into OvmfXen. Besides, QemuFwCfgS3Enabled() is
> > replaced with PcdAcpiS3Enable in several OVMF libraries to avoid the
> > potential inconsistency.
> >
> > v2:
> > - Amend the description and address "HVM Direct Kernel Boot"
> > - Add the comment for the conditional test of QemuFwCfgS3Enabled()
> > - Remove unused QemuFwCfgLib
> > - Update my email address
> >
> > Gary Lin (5):
> > OvmfPkg/OvmfXen: set PcdAcpiS3Enable at initialization
> > OvmfPkg/OvmfXen: add QemuKernelLoaderFsDxe
> > OvmfPkg/LockBoxLib: use PcdAcpiS3Enable to detect S3 support
> > OvmfPkg/PlatformBootManagerLib: use PcdAcpiS3Enable to detect S3
> > support
> > OvmfPkg/SmmControl2Dxe: use PcdAcpiS3Enable to detect S3 support
> >
> > OvmfPkg/OvmfXen.dsc | 1 +
> > OvmfPkg/OvmfXen.fdf | 1 +
> > OvmfPkg/Library/LockBoxLib/LockBoxDxeLib.inf | 3 +--
> > .../PlatformBootManagerLib.inf | 1 +
> > OvmfPkg/SmmControl2Dxe/SmmControl2Dxe.inf | 2 ++
> > OvmfPkg/XenPlatformPei/XenPlatformPei.inf | 2 ++
> > OvmfPkg/Library/LockBoxLib/LockBoxDxe.c | 4 +---
> > .../Library/PlatformBootManagerLib/BdsPlatform.c | 2 +-
> > OvmfPkg/SmmControl2Dxe/SmmControl2Dxe.c | 4 +---
> > OvmfPkg/XenPlatformPei/Platform.c | 13 +++++++++++++
> > 10 files changed, 24 insertions(+), 9 deletions(-)
> >
> > --
> > 2.31.1
> >
> >
> >
> >
> >
>
next prev parent reply other threads:[~2021-08-16 1:34 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-08-13 6:13 [PATCH v2 0/5] Fix OvmfXen HVM Direct kernel boot failure Lin, Gary (HPS OE-Linux)
2021-08-13 6:13 ` [PATCH v2 1/5] OvmfPkg/OvmfXen: set PcdAcpiS3Enable at initialization Lin, Gary (HPS OE-Linux)
2021-08-16 7:07 ` [edk2-devel] " Ard Biesheuvel
2021-08-16 7:11 ` Lin, Gary (HPS OE-Linux)
2021-08-19 14:33 ` Anthony PERARD
2021-08-13 6:13 ` [PATCH v2 2/5] OvmfPkg/OvmfXen: add QemuKernelLoaderFsDxe Lin, Gary (HPS OE-Linux)
2021-08-19 14:34 ` Anthony PERARD
2021-08-13 6:13 ` [PATCH v2 3/5] OvmfPkg/LockBoxLib: use PcdAcpiS3Enable to detect S3 support Lin, Gary (HPS OE-Linux)
2021-08-13 6:13 ` [PATCH v2 4/5] OvmfPkg/PlatformBootManagerLib: " Lin, Gary (HPS OE-Linux)
2021-08-13 6:13 ` [PATCH v2 5/5] OvmfPkg/SmmControl2Dxe: " Lin, Gary (HPS OE-Linux)
2021-08-13 9:55 ` [edk2-devel] [PATCH v2 0/5] Fix OvmfXen HVM Direct kernel boot failure Yao, Jiewen
2021-08-16 1:34 ` Lin, Gary (HPS OE-Linux) [this message]
2021-08-16 17:14 ` Jim Fehlig
[not found] <169AC8FC9129752E.29477@groups.io>
2021-08-16 7:14 ` Lin, Gary (HPS OE-Linux)
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=YRnAjZBsaBF/TkDF@GaryHPELaptop \
--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