* Re: [edk2-devel] [PATCH v9 0/6] Simplify SMM Relocation Process [not found] <17443983D6ED8995.20300@groups.io> @ 2023-02-20 1:06 ` Wu, Jiaxin 2023-02-20 1:14 ` Ni, Ray 2023-02-20 2:37 ` Michael D Kinney 0 siblings, 2 replies; 16+ messages in thread From: Wu, Jiaxin @ 2023-02-20 1:06 UTC (permalink / raw) To: devel@edk2.groups.io, Wu, Jiaxin Cc: Dong, Eric, Ni, Ray, Zeng, Star, Laszlo Ersek, Gerd Hoffmann, Kumar, Rahul R Any more comments to patch series? If no objection, Ray, please help merge the patches. Thanks, Jiaxin > -----Original Message----- > From: devel@edk2.groups.io <devel@edk2.groups.io> On Behalf Of Wu, Jiaxin > Sent: Thursday, February 16, 2023 2:16 PM > To: devel@edk2.groups.io > Cc: Dong, Eric <eric.dong@intel.com>; Ni, Ray <ray.ni@intel.com>; Zeng, Star > <star.zeng@intel.com>; Laszlo Ersek <lersek@redhat.com>; Gerd Hoffmann > <kraxel@redhat.com>; Kumar, Rahul R <rahul.r.kumar@intel.com> > Subject: [edk2-devel] [PATCH v9 0/6] Simplify SMM Relocation Process > > Existing SMBASE Relocation is in the PiSmmCpuDxeSmm driver, which > will relocate the SMBASE of each processor by setting the SMBASE > field in the saved state map (at offset 7EF8h) to a new value. > The RSM instruction reloads the internal SMBASE register with the > value in SMBASE field when each time it exits SMM. All subsequent > SMI requests will use the new SMBASE to find the starting address > for the SMI handler (at SMBASE + 8000h). > > Due to the default SMBASE for all x86 processors is 0x30000, the > APs' 1st SMI for rebase has to be executed one by one to avoid > the processors over-writing each other's SMM Save State Area (see > existing SmmRelocateBases() function), which means the next AP has > to wait for the previous AP to finish its 1st SMI, then it can call > into its 1st SMI for rebase via Smi Ipi command, thus leading the > existing SMBASE Relocation has to be running in series. Besides, it > needs very complex code to handle the AP exit semaphore > (mRebased[Index]), which will hook return address of SMM Save State > so that semaphore code can be executed immediately after AP exits > SMM for SMBASE relocation (see existing SemaphoreHook() function). > > This series is to add the new SMM Base HOB for any PEI module to do > the SmBase relocation ahead of PiSmmCpuDxeSmm driver and store the > relocated SmBase address in array for each Processors. When the > SMBASE relocation happens in a PEI module, the PEI module shall > produce the SMM_BASE_HOB in HOB database which tells the > PiSmmCpuDxeSmm driver (runs at a later phase) about the new SMBASE > for each CPU thread. PiSmmCpuDxeSmm driver installs the SMI handler > at the SMM_BASE_HOB.SmBase[Index]+0x8000 for processor Index. When > the HOB doesn't exist, PiSmmCpuDxeSmm driver shall relocate and > program the new SMBASE itself (keep existing SMBASE Relocation way). > > With SMM Base Hob support, PiSmmCpuDxeSmm does not need the RSM > instruction to do the SMBASE Relocation. SMBASE Register for each > processors have already been programmed and all SMBASE address have > recorded in SMM Base Hob. So the same default SMBASE Address > (0x30000) will not be used, thus the processors over-writing each > other's SMM Save State Area will not happen in PiSmmCpuDxeSmm driver. > This way makes the first SMI init can be executed in parallel and save > boot time on multi-core system. Besides, Semaphore Hook code logic > is also not required, which will greatly simplify the SMBASE > Relocation flow. > > Note: > This is the new way that firmware can program the SMBASE > independently of the RSM instruction. The PEI code performing > this logic will not be open sourced, similarly to other things > that are kept binary-only in the FSP. Due to the register > difference in different vender, and it has not been documented > in the Intel SDM yet, we need a new binary-only interface for > SMM Base HOB. > > Cc: Eric Dong <eric.dong@intel.com> > Cc: Ray Ni <ray.ni@intel.com> > Cc: Zeng Star <star.zeng@intel.com> > Cc: Laszlo Ersek <lersek@redhat.com> > Cc: Gerd Hoffmann <kraxel@redhat.com> > Cc: Rahul Kumar <rahul1.kumar@intel.com> > Signed-off-by: Jiaxin Wu <jiaxin.wu@intel.com> > > Jiaxin Wu (6): > UefiCpuPkg/PiSmmCpuDxeSmm: Fix invalid InitializeMpSyncData call > UefiCpuPkg/PiSmmCpuDxeSmm: Replace mIsBsp by mBspApicId check > UefiCpuPkg/SmmBaseHob.h: Add SMM Base HOB Data > UefiCpuPkg/PiSmmCpuDxeSmm: Consume SMM Base Hob for SmBase info > UefiCpuPkg/SmmCpuFeaturesLib: Skip SMBASE configuration > OvmfPkg/SmmCpuFeaturesLib: Check SmBase relocation supported or not > > .../Library/SmmCpuFeaturesLib/SmmCpuFeaturesLib.c | 10 +- > .../SmmCpuFeaturesLib/SmmCpuFeaturesLib.inf | 6 +- > UefiCpuPkg/Include/Guid/SmmBaseHob.h | 75 ++++++++ > .../Library/SmmCpuFeaturesLib/CpuFeaturesLib.h | 2 + > .../SmmCpuFeaturesLib/IntelSmmCpuFeaturesLib.c | 25 ++- > .../SmmCpuFeaturesLib/SmmCpuFeaturesLib.inf | 6 +- > .../SmmCpuFeaturesLib/SmmCpuFeaturesLibStm.inf | 3 +- > UefiCpuPkg/Library/SmmCpuFeaturesLib/SmmStm.c | 3 +- > .../StandaloneMmCpuFeaturesLib.inf | 6 +- > UefiCpuPkg/PiSmmCpuDxeSmm/CpuS3.c | 31 +++- > UefiCpuPkg/PiSmmCpuDxeSmm/MpService.c | 25 ++- > UefiCpuPkg/PiSmmCpuDxeSmm/PiSmmCpuDxeSmm.c | 193 > ++++++++++++++++----- > UefiCpuPkg/PiSmmCpuDxeSmm/PiSmmCpuDxeSmm.h | 26 ++- > UefiCpuPkg/PiSmmCpuDxeSmm/PiSmmCpuDxeSmm.inf | 3 +- > UefiCpuPkg/UefiCpuPkg.dec | 5 +- > 15 files changed, 356 insertions(+), 63 deletions(-) > create mode 100644 UefiCpuPkg/Include/Guid/SmmBaseHob.h > > -- > 2.16.2.windows.1 > > > > > ^ permalink raw reply [flat|nested] 16+ messages in thread
* Re: [edk2-devel] [PATCH v9 0/6] Simplify SMM Relocation Process 2023-02-20 1:06 ` [edk2-devel] [PATCH v9 0/6] Simplify SMM Relocation Process Wu, Jiaxin @ 2023-02-20 1:14 ` Ni, Ray 2023-02-21 8:48 ` Gerd Hoffmann 2023-02-20 2:37 ` Michael D Kinney 1 sibling, 1 reply; 16+ messages in thread From: Ni, Ray @ 2023-02-20 1:14 UTC (permalink / raw) To: Wu, Jiaxin, devel@edk2.groups.io Cc: Dong, Eric, Zeng, Star, Laszlo Ersek, Gerd Hoffmann, Kumar, Rahul R I expect Gerd at least acknowledges all patches for UefiCpuPkg. Following three haven't got: * [PATCH v9 3/6] UefiCpuPkg/SmmBaseHob.h: Add SMM Base HOB Data * [PATCH v9 4/6] UefiCpuPkg/PiSmmCpuDxeSmm: Consume SMM Base Hob for SmBase info * [PATCH v9 5/6] UefiCpuPkg/SmmCpuFeaturesLib: Skip SMBASE configuration Thanks, Ray > -----Original Message----- > From: Wu, Jiaxin <jiaxin.wu@intel.com> > Sent: Monday, February 20, 2023 9:07 AM > To: devel@edk2.groups.io; Wu, Jiaxin <jiaxin.wu@intel.com> > Cc: Dong, Eric <eric.dong@intel.com>; Ni, Ray <ray.ni@intel.com>; Zeng, Star > <star.zeng@intel.com>; Laszlo Ersek <lersek@redhat.com>; Gerd Hoffmann > <kraxel@redhat.com>; Kumar, Rahul R <rahul.r.kumar@intel.com> > Subject: RE: [edk2-devel] [PATCH v9 0/6] Simplify SMM Relocation Process > > Any more comments to patch series? If no objection, Ray, please help merge > the patches. > > Thanks, > Jiaxin > > > > > -----Original Message----- > > From: devel@edk2.groups.io <devel@edk2.groups.io> On Behalf Of Wu, > Jiaxin > > Sent: Thursday, February 16, 2023 2:16 PM > > To: devel@edk2.groups.io > > Cc: Dong, Eric <eric.dong@intel.com>; Ni, Ray <ray.ni@intel.com>; Zeng, > Star > > <star.zeng@intel.com>; Laszlo Ersek <lersek@redhat.com>; Gerd > Hoffmann > > <kraxel@redhat.com>; Kumar, Rahul R <rahul.r.kumar@intel.com> > > Subject: [edk2-devel] [PATCH v9 0/6] Simplify SMM Relocation Process > > > > Existing SMBASE Relocation is in the PiSmmCpuDxeSmm driver, which > > will relocate the SMBASE of each processor by setting the SMBASE > > field in the saved state map (at offset 7EF8h) to a new value. > > The RSM instruction reloads the internal SMBASE register with the > > value in SMBASE field when each time it exits SMM. All subsequent > > SMI requests will use the new SMBASE to find the starting address > > for the SMI handler (at SMBASE + 8000h). > > > > Due to the default SMBASE for all x86 processors is 0x30000, the > > APs' 1st SMI for rebase has to be executed one by one to avoid > > the processors over-writing each other's SMM Save State Area (see > > existing SmmRelocateBases() function), which means the next AP has > > to wait for the previous AP to finish its 1st SMI, then it can call > > into its 1st SMI for rebase via Smi Ipi command, thus leading the > > existing SMBASE Relocation has to be running in series. Besides, it > > needs very complex code to handle the AP exit semaphore > > (mRebased[Index]), which will hook return address of SMM Save State > > so that semaphore code can be executed immediately after AP exits > > SMM for SMBASE relocation (see existing SemaphoreHook() function). > > > > This series is to add the new SMM Base HOB for any PEI module to do > > the SmBase relocation ahead of PiSmmCpuDxeSmm driver and store the > > relocated SmBase address in array for each Processors. When the > > SMBASE relocation happens in a PEI module, the PEI module shall > > produce the SMM_BASE_HOB in HOB database which tells the > > PiSmmCpuDxeSmm driver (runs at a later phase) about the new SMBASE > > for each CPU thread. PiSmmCpuDxeSmm driver installs the SMI handler > > at the SMM_BASE_HOB.SmBase[Index]+0x8000 for processor Index. When > > the HOB doesn't exist, PiSmmCpuDxeSmm driver shall relocate and > > program the new SMBASE itself (keep existing SMBASE Relocation way). > > > > With SMM Base Hob support, PiSmmCpuDxeSmm does not need the RSM > > instruction to do the SMBASE Relocation. SMBASE Register for each > > processors have already been programmed and all SMBASE address have > > recorded in SMM Base Hob. So the same default SMBASE Address > > (0x30000) will not be used, thus the processors over-writing each > > other's SMM Save State Area will not happen in PiSmmCpuDxeSmm driver. > > This way makes the first SMI init can be executed in parallel and save > > boot time on multi-core system. Besides, Semaphore Hook code logic > > is also not required, which will greatly simplify the SMBASE > > Relocation flow. > > > > Note: > > This is the new way that firmware can program the SMBASE > > independently of the RSM instruction. The PEI code performing > > this logic will not be open sourced, similarly to other things > > that are kept binary-only in the FSP. Due to the register > > difference in different vender, and it has not been documented > > in the Intel SDM yet, we need a new binary-only interface for > > SMM Base HOB. > > > > Cc: Eric Dong <eric.dong@intel.com> > > Cc: Ray Ni <ray.ni@intel.com> > > Cc: Zeng Star <star.zeng@intel.com> > > Cc: Laszlo Ersek <lersek@redhat.com> > > Cc: Gerd Hoffmann <kraxel@redhat.com> > > Cc: Rahul Kumar <rahul1.kumar@intel.com> > > Signed-off-by: Jiaxin Wu <jiaxin.wu@intel.com> > > > > Jiaxin Wu (6): > > UefiCpuPkg/PiSmmCpuDxeSmm: Fix invalid InitializeMpSyncData call > > UefiCpuPkg/PiSmmCpuDxeSmm: Replace mIsBsp by mBspApicId check > > UefiCpuPkg/SmmBaseHob.h: Add SMM Base HOB Data > > UefiCpuPkg/PiSmmCpuDxeSmm: Consume SMM Base Hob for SmBase > info > > UefiCpuPkg/SmmCpuFeaturesLib: Skip SMBASE configuration > > OvmfPkg/SmmCpuFeaturesLib: Check SmBase relocation supported or > not > > > > .../Library/SmmCpuFeaturesLib/SmmCpuFeaturesLib.c | 10 +- > > .../SmmCpuFeaturesLib/SmmCpuFeaturesLib.inf | 6 +- > > UefiCpuPkg/Include/Guid/SmmBaseHob.h | 75 ++++++++ > > .../Library/SmmCpuFeaturesLib/CpuFeaturesLib.h | 2 + > > .../SmmCpuFeaturesLib/IntelSmmCpuFeaturesLib.c | 25 ++- > > .../SmmCpuFeaturesLib/SmmCpuFeaturesLib.inf | 6 +- > > .../SmmCpuFeaturesLib/SmmCpuFeaturesLibStm.inf | 3 +- > > UefiCpuPkg/Library/SmmCpuFeaturesLib/SmmStm.c | 3 +- > > .../StandaloneMmCpuFeaturesLib.inf | 6 +- > > UefiCpuPkg/PiSmmCpuDxeSmm/CpuS3.c | 31 +++- > > UefiCpuPkg/PiSmmCpuDxeSmm/MpService.c | 25 ++- > > UefiCpuPkg/PiSmmCpuDxeSmm/PiSmmCpuDxeSmm.c | 193 > > ++++++++++++++++----- > > UefiCpuPkg/PiSmmCpuDxeSmm/PiSmmCpuDxeSmm.h | 26 ++- > > UefiCpuPkg/PiSmmCpuDxeSmm/PiSmmCpuDxeSmm.inf | 3 +- > > UefiCpuPkg/UefiCpuPkg.dec | 5 +- > > 15 files changed, 356 insertions(+), 63 deletions(-) > > create mode 100644 UefiCpuPkg/Include/Guid/SmmBaseHob.h > > > > -- > > 2.16.2.windows.1 > > > > > > > > > > ^ permalink raw reply [flat|nested] 16+ messages in thread
* Re: [edk2-devel] [PATCH v9 0/6] Simplify SMM Relocation Process 2023-02-20 1:14 ` Ni, Ray @ 2023-02-21 8:48 ` Gerd Hoffmann 2023-02-21 9:12 ` Ni, Ray 2023-03-06 11:13 ` Gerd Hoffmann 0 siblings, 2 replies; 16+ messages in thread From: Gerd Hoffmann @ 2023-02-21 8:48 UTC (permalink / raw) To: Ni, Ray Cc: Wu, Jiaxin, devel@edk2.groups.io, Dong, Eric, Zeng, Star, Laszlo Ersek, Kumar, Rahul R On Mon, Feb 20, 2023 at 01:14:33AM +0000, Ni, Ray wrote: > I expect Gerd at least acknowledges all patches for UefiCpuPkg. Following three haven't got: > * [PATCH v9 3/6] UefiCpuPkg/SmmBaseHob.h: Add SMM Base HOB Data > * [PATCH v9 4/6] UefiCpuPkg/PiSmmCpuDxeSmm: Consume SMM Base Hob for SmBase info > * [PATCH v9 5/6] UefiCpuPkg/SmmCpuFeaturesLib: Skip SMBASE configuration I still think it is worth cleaning cleaning up and remove both code and comment for i486 and pentium processors from the last century. That should reduce confusion of the already complex code. But if you insist on not touching the existing code, so be it. Series (for post-freeze merge): Acked-by: Gerd Hoffmann <kraxel@redhat.com> take care, Gerd ^ permalink raw reply [flat|nested] 16+ messages in thread
* Re: [edk2-devel] [PATCH v9 0/6] Simplify SMM Relocation Process 2023-02-21 8:48 ` Gerd Hoffmann @ 2023-02-21 9:12 ` Ni, Ray 2023-02-21 9:45 ` Gerd Hoffmann 2023-03-06 11:13 ` Gerd Hoffmann 1 sibling, 1 reply; 16+ messages in thread From: Ni, Ray @ 2023-02-21 9:12 UTC (permalink / raw) To: Gerd Hoffmann, Wu, Jiaxin, Kinney, Michael D Cc: devel@edk2.groups.io, Dong, Eric, Zeng, Star, Laszlo Ersek, Kumar, Rahul R Gerd, I also don't think some Pentium processors still use the latest edk2 code. Can you create a bugzilla for the request? If @Kinney, Michael D doesn't have concern, we can follow up on that old code removal. Thanks, Ray > -----Original Message----- > From: Gerd Hoffmann <kraxel@redhat.com> > Sent: Tuesday, February 21, 2023 4:49 PM > To: Ni, Ray <ray.ni@intel.com> > Cc: Wu, Jiaxin <jiaxin.wu@intel.com>; devel@edk2.groups.io; Dong, Eric > <eric.dong@intel.com>; Zeng, Star <star.zeng@intel.com>; Laszlo Ersek > <lersek@redhat.com>; Kumar, Rahul R <rahul.r.kumar@intel.com> > Subject: Re: [edk2-devel] [PATCH v9 0/6] Simplify SMM Relocation Process > > On Mon, Feb 20, 2023 at 01:14:33AM +0000, Ni, Ray wrote: > > I expect Gerd at least acknowledges all patches for UefiCpuPkg. Following > three haven't got: > > * [PATCH v9 3/6] UefiCpuPkg/SmmBaseHob.h: Add SMM Base HOB Data > > * [PATCH v9 4/6] UefiCpuPkg/PiSmmCpuDxeSmm: Consume SMM Base > Hob for SmBase info > > * [PATCH v9 5/6] UefiCpuPkg/SmmCpuFeaturesLib: Skip SMBASE > configuration > > I still think it is worth cleaning cleaning up and remove both code and > comment for i486 and pentium processors from the last century. That > should reduce confusion of the already complex code. But if you insist > on not touching the existing code, so be it. > > Series (for post-freeze merge): > Acked-by: Gerd Hoffmann <kraxel@redhat.com> > > take care, > Gerd ^ permalink raw reply [flat|nested] 16+ messages in thread
* Re: [edk2-devel] [PATCH v9 0/6] Simplify SMM Relocation Process 2023-02-21 9:12 ` Ni, Ray @ 2023-02-21 9:45 ` Gerd Hoffmann 0 siblings, 0 replies; 16+ messages in thread From: Gerd Hoffmann @ 2023-02-21 9:45 UTC (permalink / raw) To: Ni, Ray Cc: Wu, Jiaxin, Kinney, Michael D, devel@edk2.groups.io, Dong, Eric, Zeng, Star, Laszlo Ersek, Kumar, Rahul R On Tue, Feb 21, 2023 at 09:12:20AM +0000, Ni, Ray wrote: > Gerd, > I also don't think some Pentium processors still use the latest edk2 code. > Can you create a bugzilla for the request? > > If @Kinney, Michael D doesn't have concern, we can follow up on that old code removal. https://bugzilla.tianocore.org/show_bug.cgi?id=4345 take care, Gerd ^ permalink raw reply [flat|nested] 16+ messages in thread
* Re: [edk2-devel] [PATCH v9 0/6] Simplify SMM Relocation Process 2023-02-21 8:48 ` Gerd Hoffmann 2023-02-21 9:12 ` Ni, Ray @ 2023-03-06 11:13 ` Gerd Hoffmann 2023-03-06 11:43 ` Ni, Ray 1 sibling, 1 reply; 16+ messages in thread From: Gerd Hoffmann @ 2023-03-06 11:13 UTC (permalink / raw) To: devel Cc: Ni, Ray, Wu, Jiaxin, Dong, Eric, Zeng, Star, Laszlo Ersek, Kumar, Rahul R On Tue, Feb 21, 2023 at 09:48:54AM +0100, Gerd Hoffmann wrote: > On Mon, Feb 20, 2023 at 01:14:33AM +0000, Ni, Ray wrote: > > I expect Gerd at least acknowledges all patches for UefiCpuPkg. Following three haven't got: > > * [PATCH v9 3/6] UefiCpuPkg/SmmBaseHob.h: Add SMM Base HOB Data > > * [PATCH v9 4/6] UefiCpuPkg/PiSmmCpuDxeSmm: Consume SMM Base Hob for SmBase info > > * [PATCH v9 5/6] UefiCpuPkg/SmmCpuFeaturesLib: Skip SMBASE configuration > > I still think it is worth cleaning cleaning up and remove both code and > comment for i486 and pentium processors from the last century. That > should reduce confusion of the already complex code. But if you insist > on not touching the existing code, so be it. > > Series (for post-freeze merge): > Acked-by: Gerd Hoffmann <kraxel@redhat.com> Damn, should have tested this. The series breaks suspend for OvmfPkg/OvmfPkgIa32X64.dsc (32-bit PEI + 64-bit SMM/DXE). Full log below. Please investigate and fix. OvmfPkg/OvmfPkgX64.dsc suspend works fine (64bit PEI/DXE, no SMM). take care, Gerd ------------------ cut here --------------- SecCoreStartupWithStack(0xFFFCC000, 0x820000) Register PPI Notify: DCD0BE23-9586-40F4-B643-06522CED4EDE Install PPI: 8C8CE578-8A3D-4F1C-9935-896185C32DD3 Install PPI: 5473C07A-3DCB-4DCA-BD6F-1E9689E7349A The 0th FV start address is 0x00000820000, size is 0x000E0000, handle is 0x820000 Register PPI Notify: 49EDB1C1-BF21-4761-BB12-EB0031AABB39 Register PPI Notify: EA7CA24B-DED5-4DAD-A389-BF827E8F9B38 Install PPI: B9E0ABFE-5979-4914-977F-6DEE78C278A6 Install PPI: DBE23AA9-A345-4B97-85B6-B226F1617389 Install PPI: 138F9CF4-F0E7-4721-8F49-F5FFECF42D40 DiscoverPeimsAndOrderWithApriori(): Found 0xF PEI FFS files in the 0th FV Loading PEIM 9B3ADA4F-AE56-4C24-8DEA-F03B7558AE50 Loading PEIM at 0x0000082B180 EntryPoint=0x0000082DC72 PcdPeim.efi Install PPI: 06E81C58-4AD7-44BC-8390-F10265F72480 Install PPI: 01F34D25-4DE2-23AD-3FF3-36353FF323F1 Install PPI: 4D8B155B-C059-4C8F-8926-06FD4331DB8A Install PPI: A60C6B59-E459-425D-9C69-0BCC9CB27D81 Register PPI Notify: 605EA650-C65C-42E1-BA80-91A52AB618C6 Loading PEIM A3610442-E69F-4DF3-82CA-2360C4031A23 Loading PEIM at 0x0000082FA40 EntryPoint=0x00000830B74 ReportStatusCodeRouterPei.efi Install PPI: 0065D394-9951-4144-82A3-0AFC8579C251 Install PPI: 229832D3-7A30-4B36-B827-F40CB7D45436 Loading PEIM 9D225237-FA01-464C-A949-BAABC02D31D0 Loading PEIM at 0x000008318C0 EntryPoint=0x00000832927 StatusCodeHandlerPei.efi Loading PEIM 222C386D-5ABC-4FB4-B124-FBB82488ACF4 Loading PEIM at 0x00000833740 EntryPoint=0x00000839C59 PlatformPei.efi Platform PEIM Loaded CMOS: 00: 21 00 57 00 10 00 02 06 03 23 26 02 00 80 00 00 10: 00 00 00 00 06 80 02 FF FF 00 00 00 00 00 00 00 20: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 30: FF FF 20 00 00 3F 00 20 30 00 00 00 00 12 00 00 40: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 50: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 01 60: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 70: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 QemuFwCfgProbe: Supported 1, DMA 1 Select Item: 0x19 Select Item: 0x2C S3 support was detected on QEMU Install PPI: 7408D748-FC8C-4EE6-9288-C4BEC092A410 Select Item: 0x19 Select Item: 0x19 Select Item: 0x25 Select Item: 0x19 Select Item: 0x19 PlatformAddressWidthFromCpuid: Signature: 'GenuineIntel', PhysBits: 39, QemuQuirk: On, Valid: Yes PlatformDynamicMmioWindow: using dynamic mmio window PlatformDynamicMmioWindow: Addr Space 0x8000000000 (512 GB) PlatformDynamicMmioWindow: MMIO Space 0x1000000000 (64 GB) Select Item: 0x19 Select Item: 0x25 PlatformDynamicMmioWindow: Pci64 Base 0x7000000000 PlatformDynamicMmioWindow: Pci64 Size 0x1000000000 AddressWidthInitialization: Pci64Base=0x7000000000 Pci64Size=0x1000000000 Select Item: 0x5 PlatformMaxCpuCountInitialization: BootCpuCount=2 MaxCpuCount=4 Q35TsegMbytesInitialization: QEMU offers an extended TSEG (16 MB) Q35SmramAtDefaultSmbaseInitialization: SMRAM at default SMBASE found Select Item: 0x19 Select Item: 0x25 PlatformGetLowMemoryCB: LowMemory=0x40000000 PublishPeiMemory: PhysMemAddressWidth=39 PeiMemoryCap=67592 KB PeiInstallPeiMemory MemoryBegin 0x3AD5E000, MemoryLength 0x4202000 Select Item: 0x19 Select Item: 0x25 PlatformQemuInitializeRam called Select Item: 0x19 Select Item: 0x25 Select Item: 0x19 Select Item: 0x25 PlatformAddHobCB: Reserved [0xFEFFC000, 0xFF000000) Select Item: 0x19 Select Item: 0x25 Platform PEI Firmware Volume Initialization Install PPI: 49EDB1C1-BF21-4761-BB12-EB0031AABB39 Notify: PPI Guid: 49EDB1C1-BF21-4761-BB12-EB0031AABB39, Peim notify entry point: 824202 The 1th FV start address is 0x00000900000, size is 0x00D00000, handle is 0x900000 Register PPI Notify: 2AB86EF5-ECB5-4134-B556-3854CA1FE1B4 Select Item: 0x19 Select Item: 0x25 Select Item: 0x19 Register PPI Notify: EE16160A-E8BE-47A6-820A-C6900DB0250A Select Item: 0x19 Select Item: 0x26 Register PPI Notify: EE16160A-E8BE-47A6-820A-C6900DB0250A Temp Stack : BaseAddress=0x818000 Length=0x8000 Temp Heap : BaseAddress=0x810000 Length=0x8000 Total temporary memory: 65536 bytes. temporary memory stack ever used: 28412 bytes. temporary memory heap used for HobList: 5704 bytes. temporary memory heap occupied by memory pages: 0 bytes. Memory Allocation 0x0000000A 0x3EF60000 - 0x3EFFFFFF Memory Allocation 0x0000000A 0x810000 - 0x81FFFF Memory Allocation 0x0000000A 0x807000 - 0x807FFF Memory Allocation 0x00000000 0x3F000000 - 0x3FFFFFFF Memory Allocation 0x00000000 0x30000 - 0x4FFFF Memory Allocation 0x0000000A 0x820000 - 0x8FFFFF Memory Allocation 0x0000000A 0x900000 - 0x15FFFFF Memory Allocation 0x0000000A 0x1600000 - 0x180FFFF Memory Allocation 0x00000000 0xB0000000 - 0xBFFFFFFF Old Stack size 32768, New stack size 131072 Stack Hob: BaseAddress=0x3AD5E000 Length=0x20000 Heap Offset = 0x3A56E000 Stack Offset = 0x3A55E000 TemporaryRamMigration(0x810000, 0x3AD76000, 0x10000) Loading PEIM 52C05B14-0B98-496C-BC3B-04B50211D680 Loading PEIM at 0x0003EF55000 EntryPoint=0x0003EF5C5A3 PeiCore.efi Reinstall PPI: 8C8CE578-8A3D-4F1C-9935-896185C32DD3 Reinstall PPI: 5473C07A-3DCB-4DCA-BD6F-1E9689E7349A Reinstall PPI: B9E0ABFE-5979-4914-977F-6DEE78C278A6 Install PPI: F894643D-C449-42D1-8EA8-85BDD8C65BDE Loading PEIM 9B3ADA4F-AE56-4C24-8DEA-F03B7558AE50 Loading PEIM at 0x0003EF50000 EntryPoint=0x0003EF52AF2 PcdPeim.efi Reinstall PPI: 06E81C58-4AD7-44BC-8390-F10265F72480 Reinstall PPI: 4D8B155B-C059-4C8F-8926-06FD4331DB8A Reinstall PPI: 01F34D25-4DE2-23AD-3FF3-36353FF323F1 Reinstall PPI: A60C6B59-E459-425D-9C69-0BCC9CB27D81 Loading PEIM 86D70125-BAA3-4296-A62F-602BEBBB9081 Loading PEIM at 0x0003EF4B000 EntryPoint=0x0003EF4DE83 DxeIpl.efi Install PPI: 1A36E4E7-FAB6-476A-8E75-695A0576FDD7 Install PPI: 0AE8CE5D-E448-4437-A8D7-EBF5F194F731 Loading PEIM 89E549B0-7CFE-449D-9BA3-10D8B2312D71 Loading PEIM at 0x0003EF46000 EntryPoint=0x0003EF488A2 S3Resume2Pei.efi Install PPI: 6D582DBC-DB85-4514-8FCC-5ADF6227B147 Loading PEIM AAC33064-9ED0-4B89-A5AD-3EA767960B22 Loading PEIM at 0x0003EF43000 EntryPoint=0x0003EF4417F FaultTolerantWritePei.efi Install PPI: 1D3E9CB8-43AF-490B-830A-3516AA532047 Loading PEIM 34C8C28F-B61C-45A2-8F2E-89E46BECC63B Loading PEIM at 0x0003EF40000 EntryPoint=0x0003EF41E96 PeiVariable.efi Install PPI: 2AB86EF5-ECB5-4134-B556-3854CA1FE1B4 Notify: PPI Guid: 2AB86EF5-ECB5-4134-B556-3854CA1FE1B4, Peim notify entry point: 835496 RefreshMemTypeInfo: GetVariable(): Not Found Loading PEIM 6C0E75B4-B0B9-44D1-8210-3377D7B4E066 Loading PEIM at 0x0003EF3D000 EntryPoint=0x0003EF3E371 SmmAccessPei.efi Install PPI: 268F33A9-CCCD-48BE-8817-86053AC32ED6 Loading PEIM EDADEB9D-DDBA-48BD-9D22-C1C169C8C5C6 Loading PEIM at 0x0003EF32000 EntryPoint=0x0003EF37D0D CpuMpPei.efi Register PPI Notify: F894643D-C449-42D1-8EA8-85BDD8C65BDE Notify: PPI Guid: F894643D-C449-42D1-8EA8-85BDD8C65BDE, Peim notify entry point: 3EF367E9 AP Loop Mode is 1 AP Vector: non-16-bit = 3EF08000/DC WakeupBufferStart = 2F000, WakeupBufferSize = 0 AP Vector: 16-bit = 2F000/41, ExchangeInfo = 2F041/5C CpuMpPei: 5-Level Paging = 0 APIC MODE is 1 MpInitLib: Find 2 processors in system. GetMicrocodePatchInfoFromHob: Microcode patch cache HOB is not found. CpuMpPei: 5-Level Paging = 0 CPU[0000]: Microcode revision = 00000000, expected = 00000000 CPU[0001]: Microcode revision = 00000000, expected = 00000000 Register PPI Notify: 8F9D4825-797D-48FC-8471-845025792EF6 Does not find any stored CPU BIST information from PPI! APICID - 0x00000000, BIST - 0x00000000 APICID - 0x00000001, BIST - 0x00000000 Install PPI: 9E9F374B-8F16-4230-9824-5846EE766A97 Install PPI: 5CB9CB3D-31A4-480C-9498-29D269BACFBA Install PPI: EE16160A-E8BE-47A6-820A-C6900DB0250A Notify: PPI Guid: EE16160A-E8BE-47A6-820A-C6900DB0250A, Peim notify entry point: 8351C8 PlatformPei: ClearCacheOnMpServicesAvailable CpuMpPei: 5-Level Paging = 0 Notify: PPI Guid: EE16160A-E8BE-47A6-820A-C6900DB0250A, Peim notify entry point: 836A02 CpuMpPei: 5-Level Paging = 0 Loading PEIM F12F698A-E506-4A1B-B32E-6920E55DA1C4 Loading PEIM at 0x0003EF06000 EntryPoint=0x0003EF06DAB TpmMmioSevDecryptPei.efi TpmMmioSevDecryptPeimEntryPoint Install PPI: 35C84FF2-7BFE-453D-845F-683A492CF7B7 Loading PEIM 8AD3148F-945F-46B4-8ACD-71469EA73945 Loading PEIM at 0x0003EF03000 EntryPoint=0x0003EF04137 Tcg2ConfigPei.efi Tcg2ConfigPeimEntryPoint Tcg2ConfigPeimEntryPoint: no TPM detected Install PPI: A030D115-54DD-447B-9064-F206883D7CCC Install PPI: 7F4158D3-074D-456D-8CB2-01F9C8F79DAA Loading PEIM 2BE1E4A6-6505-43B3-9FFC-A3C8330E0432 Loading PEIM at 0x0003EEFE000 EntryPoint=0x0003EF004AD TcgPei.efi No TPM12 instance required! Loading PEIM A0C98B77-CBA5-4BB8-993B-4AF6CE33ECE4 Loading PEIM at 0x0003EEF1000 EntryPoint=0x0003EEF9AEE Tcg2Pei.efi No TPM2 instance required! Loading PEIM 47727552-A54B-4A84-8CC1-BFF23E239636 Loading PEIM at 0x0003EEED000 EntryPoint=0x0003EEEF11A Tcg2PlatformPei.efi DiscoverPeimsAndOrderWithApriori(): Found 0x0 PEI FFS files in the 1th FV DXE IPL Entry Loading PEIM D6A2CB7F-6A18-4E2F-B43B-9920A733700A Loading PEIM at 0x0003EEC1000 EntryPoint=0x0003EED2946 DxeCore.efi Loading DXE CORE at 0x0003EEC1000 EntryPoint=0x0003EED2946 AddressBits=39 5LevelPaging=0 1GPage=0 Pml5=1 Pml4=1 Pdp=512 TotalPage=514 Install PPI: 605EA650-C65C-42E1-BA80-91A52AB618C6 Notify: PPI Guid: 605EA650-C65C-42E1-BA80-91A52AB618C6, Peim notify entry point: 82CB08 HandOffToDxeCore() Stack Base: 0x3EEA1000, Stack Size: 0x20000 CoreInitializeMemoryServices: BaseAddress - 0x3AD81000 Length - 0x3C7E000 MinimalMemorySizeNeeded - 0x322000 InstallProtocolInterface: 5B1B31A1-9562-11D2-8E3F-00A0C969723B 3EEE3168 ProtectUefiImageCommon - 0x3EEE3168 - 0x000000003EEC1000 - 0x000000000002C000 DxeMain: MemoryBaseAddress=0x3AD81000 MemoryLength=0x3C7E000 HOBLIST address in DXE = 0x3E6E7018 Memory Allocation 0x0000000A 0x3EF60000 - 0x3EFFFFFF Memory Allocation 0x0000000A 0x810000 - 0x81FFFF Memory Allocation 0x0000000A 0x807000 - 0x807FFF Memory Allocation 0x00000000 0x3F000000 - 0x3FFFFFFF Memory Allocation 0x00000000 0x30000 - 0x4FFFF Memory Allocation 0x0000000A 0x820000 - 0x8FFFFF Memory Allocation 0x0000000A 0x900000 - 0x15FFFFF Memory Allocation 0x0000000A 0x1600000 - 0x180FFFF Memory Allocation 0x00000000 0xB0000000 - 0xBFFFFFFF Memory Allocation 0x00000004 0x3EEA1000 - 0x3EEC0FFF Memory Allocation 0x00000003 0x3EF55000 - 0x3EF5FFFF Memory Allocation 0x00000003 0x3EF50000 - 0x3EF54FFF Memory Allocation 0x00000003 0x3EF4B000 - 0x3EF4FFFF Memory Allocation 0x00000003 0x3EF46000 - 0x3EF4AFFF Memory Allocation 0x00000003 0x3EF43000 - 0x3EF45FFF Memory Allocation 0x00000003 0x3EF40000 - 0x3EF42FFF Memory Allocation 0x00000003 0x3EF3D000 - 0x3EF3FFFF Memory Allocation 0x00000003 0x3EF32000 - 0x3EF3CFFF Memory Allocation 0x00000004 0x3EF09000 - 0x3EF31FFF Memory Allocation 0x00000003 0x3EF08000 - 0x3EF08FFF Memory Allocation 0x00000003 0x3EF06000 - 0x3EF07FFF Memory Allocation 0x00000003 0x3EF03000 - 0x3EF05FFF Memory Allocation 0x00000003 0x3EEFE000 - 0x3EF02FFF Memory Allocation 0x00000003 0x3EEF1000 - 0x3EEFDFFF Memory Allocation 0x00000003 0x3EEED000 - 0x3EEF0FFF Memory Allocation 0x00000003 0x3EEC1000 - 0x3EEECFFF Memory Allocation 0x00000003 0x3EEC1000 - 0x3EEECFFF Memory Allocation 0x00000004 0x3EEA1000 - 0x3EEC0FFF Memory Allocation 0x00000004 0x3EA00000 - 0x3EDFFFFF Memory Allocation 0x00000007 0x3EE00000 - 0x3EEA0FFF Memory Allocation 0x00000004 0x3AD5E000 - 0x3AD7DFFF Memory Allocation 0x00000004 0x3E9FF000 - 0x3E9FFFFF FV Hob 0x900000 - 0x15FFFFF InstallProtocolInterface: D8117CFE-94A6-11D4-9A3A-0090273FC14D 3EEE38E0 InstallProtocolInterface: 8F644FA9-E850-4DB1-9CE2-0B44698E8DA4 3E6E38B0 InstallProtocolInterface: 09576E91-6D3F-11D2-8E39-00A0C969723B 3E6E3998 InstallProtocolInterface: 220E73B6-6BDB-4413-8405-B974B108619A 3E6E33B0 InstallProtocolInterface: EE4E5898-3914-4259-9D6E-DC7BD79403CF 3EEE37F8 Loading driver 9B680FCE-AD6B-4F3A-B60B-F59899003443 InstallProtocolInterface: 5B1B31A1-9562-11D2-8E3F-00A0C969723B 3E18B040 Loading driver at 0x0003E17F000 EntryPoint=0x0003E186E1D DevicePathDxe.efi InstallProtocolInterface: BC62157E-3E33-4FEC-9920-2D3B36D750DF 3E18BD98 ProtectUefiImageCommon - 0x3E18B040 - 0x000000003E17F000 - 0x000000000000B400 InstallProtocolInterface: 0379BE4E-D706-437D-B037-EDB82FB772A4 3E189700 InstallProtocolInterface: 8B843E20-8132-4852-90CC-551A4E4A7F1C 3E1896E0 InstallProtocolInterface: 05C99A21-C70F-4AD2-8A5F-35DF3343F51E 3E1896C0 Loading driver 80CF7257-87AB-47F9-A3FE-D50B76D89541 InstallProtocolInterface: 5B1B31A1-9562-11D2-8E3F-00A0C969723B 3E18B3C0 Loading driver at 0x0003E18C000 EntryPoint=0x0003E18F976 PcdDxe.efi InstallProtocolInterface: BC62157E-3E33-4FEC-9920-2D3B36D750DF 3E18B998 ProtectUefiImageCommon - 0x3E18B3C0 - 0x000000003E18C000 - 0x0000000000005D00 InstallProtocolInterface: 11B34006-D85B-4D0A-A290-D5A571310EF7 3E1919C0 InstallProtocolInterface: 13A3F0F6-264A-3EF0-F2E0-DEC512342F34 3E191920 InstallProtocolInterface: 5BE40F57-FA68-4610-BBBF-E9C5FCDAD365 3E1918F0 InstallProtocolInterface: FD0F4478-0EFD-461D-BA2D-E58C45FD5F5E 3E1918D0 Loading driver 2EC9DA37-EE35-4DE9-86C5-6D9A81DC38A7 InstallProtocolInterface: 5B1B31A1-9562-11D2-8E3F-00A0C969723B 3E196BC0 Loading driver at 0x0003E17B000 EntryPoint=0x0003E17D1E6 AmdSevDxe.efi InstallProtocolInterface: BC62157E-3E33-4FEC-9920-2D3B36D750DF 3E196F18 ProtectUefiImageCommon - 0x3E196BC0 - 0x000000003E17B000 - 0x0000000000003D80 Error: Image at 0003E17B000 start failed: Unsupported Loading driver D93CE3D8-A7EB-4730-8C8E-CC466A9ECC3C InstallProtocolInterface: 5B1B31A1-9562-11D2-8E3F-00A0C969723B 3E196BC0 Loading driver at 0x0003E8E6000 EntryPoint=0x0003E8E87D4 ReportStatusCodeRouterRuntimeDxe.efi InstallProtocolInterface: BC62157E-3E33-4FEC-9920-2D3B36D750DF 3E196B18 ProtectUefiImageCommon - 0x3E196BC0 - 0x000000003E8E6000 - 0x0000000000006000 InstallProtocolInterface: 86212936-0E76-41C8-A03A-2AF2FC1C39E2 3E8EA060 InstallProtocolInterface: D2B2B828-0826-48A7-B3DF-983C006024F0 3E8EA040 Loading driver B601F8C4-43B7-4784-95B1-F4226CB40CEE InstallProtocolInterface: 5B1B31A1-9562-11D2-8E3F-00A0C969723B 3E196340 Loading driver at 0x0003E8E0000 EntryPoint=0x0003E8E24FF RuntimeDxe.efi InstallProtocolInterface: BC62157E-3E33-4FEC-9920-2D3B36D750DF 3E193B18 ProtectUefiImageCommon - 0x3E196340 - 0x000000003E8E0000 - 0x0000000000006000 InstallProtocolInterface: B7DFB4E1-052F-449F-87BE-9818FC91B733 3E8E4080 Loading driver F80697E9-7FD6-4665-8646-88E33EF71DFC InstallProtocolInterface: 5B1B31A1-9562-11D2-8E3F-00A0C969723B 3E1931C0 Loading driver at 0x0003E093000 EntryPoint=0x0003E0CFEB6 SecurityStubDxe.efi InstallProtocolInterface: BC62157E-3E33-4FEC-9920-2D3B36D750DF 3E193918 ProtectUefiImageCommon - 0x3E1931C0 - 0x000000003E093000 - 0x0000000000075040 InstallProtocolInterface: 94AB2F58-1438-4EF1-9152-18941A3A0E68 3E104758 InstallProtocolInterface: A46423E3-4617-49F1-B9FF-D1BFA9115839 3E104750 InstallProtocolInterface: 15853D7C-3DDF-43E0-A1CB-EBF85B8F872C 3E104730 Loading driver 13AC6DD0-73D0-11D4-B06B-00AA00BD6DE7 None of Tcg2Protocol/CcMeasurementProtocol is installed. InstallProtocolInterface: 5B1B31A1-9562-11D2-8E3F-00A0C969723B 3E192940 Loading driver at 0x0003E172000 EntryPoint=0x0003E1765BA EbcDxe.efi InstallProtocolInterface: BC62157E-3E33-4FEC-9920-2D3B36D750DF 3E192898 ProtectUefiImageCommon - 0x3E192940 - 0x000000003E172000 - 0x0000000000006000 InstallProtocolInterface: 13AC6DD1-73D0-11D4-B06B-00AA00BD6DE7 3E192818 InstallProtocolInterface: 96F46153-97A7-4793-ACC1-FA19BF78EA97 3E177A20 InstallProtocolInterface: 2755590C-6F3C-42FA-9EA4-A3BA543CDA25 3E17E018 InstallProtocolInterface: AAEACCFD-F27B-4C17-B610-75CA1F2DFB52 3E17EE98 Loading driver A19B1FE7-C1BC-49F8-875F-54A5D542443F None of Tcg2Protocol/CcMeasurementProtocol is installed. InstallProtocolInterface: 5B1B31A1-9562-11D2-8E3F-00A0C969723B 3E17E0C0 Loading driver at 0x0003E178000 EntryPoint=0x0003E179455 CpuIo2Dxe.efi InstallProtocolInterface: BC62157E-3E33-4FEC-9920-2D3B36D750DF 3E192318 ProtectUefiImageCommon - 0x3E17E0C0 - 0x000000003E178000 - 0x00000000000020C0 InstallProtocolInterface: AD61F191-AE5F-4C0E-B9FA-E869D288C64F 3E179F80 Loading driver 1A1E4886-9517-440E-9FDE-3BE44CEE2136 None of Tcg2Protocol/CcMeasurementProtocol is installed. InstallProtocolInterface: 5B1B31A1-9562-11D2-8E3F-00A0C969723B 3E17E540 Loading driver at 0x0003E142000 EntryPoint=0x0003E14B242 CpuDxe.efi InstallProtocolInterface: BC62157E-3E33-4FEC-9920-2D3B36D750DF 3E17D018 ProtectUefiImageCommon - 0x3E17E540 - 0x000000003E142000 - 0x0000000000017580 Paging: added 512 pages to page table pool CurrentPagingContext: MachineType - 0x8664 PageTableBase - 0x3EA01000 Attributes - 0xC0000006 InstallProtocolInterface: 26BACCB1-6F42-11D4-BCE7-0080C73C8881 3E1529E0 MemoryProtectionCpuArchProtocolNotify: ProtectUefiImageCommon - 0x3EEE3168 - 0x000000003EEC1000 - 0x000000000002C000 ProtectUefiImageCommon - 0x3E18B040 - 0x000000003E17F000 - 0x000000000000B400 ProtectUefiImageCommon - 0x3E18B3C0 - 0x000000003E18C000 - 0x0000000000005D00 ProtectUefiImageCommon - 0x3E196BC0 - 0x000000003E8E6000 - 0x0000000000006000 SetUefiImageMemoryAttributes - 0x000000003E8E6000 - 0x0000000000001000 (0x0000000000004000) SetUefiImageMemoryAttributes - 0x000000003E8E7000 - 0x0000000000003000 (0x0000000000020000) SetUefiImageMemoryAttributes - 0x000000003E8EA000 - 0x0000000000002000 (0x0000000000004000) ProtectUefiImageCommon - 0x3E196340 - 0x000000003E8E0000 - 0x0000000000006000 SetUefiImageMemoryAttributes - 0x000000003E8E0000 - 0x0000000000001000 (0x0000000000004000) SetUefiImageMemoryAttributes - 0x000000003E8E1000 - 0x0000000000003000 (0x0000000000020000) SetUefiImageMemoryAttributes - 0x000000003E8E4000 - 0x0000000000002000 (0x0000000000004000) ProtectUefiImageCommon - 0x3E1931C0 - 0x000000003E093000 - 0x0000000000075040 ProtectUefiImageCommon - 0x3E192940 - 0x000000003E172000 - 0x0000000000006000 ProtectUefiImageCommon - 0x3E17E0C0 - 0x000000003E178000 - 0x00000000000020C0 ProtectUefiImageCommon - 0x3E17E540 - 0x000000003E142000 - 0x0000000000017580 ConvertPages: failed to find range 30000 - 4FFFF ConvertPages: failed to find range A0000 - FFFFF ConvertPages: failed to find range 3F000000 - 3FFFFFFF ConvertPages: failed to find range B0000000 - BFFFFFFF ConvertPages: failed to find range C0000000 - FBFFFFFF ConvertPages: failed to find range FEC00000 - FEC00FFF Failed to update capability: [12] 00000000FED00000 - 00000000FED003FF (C700000000000001 -> C700000000026001) ConvertPages: failed to find range FED1C000 - FED1FFFF ConvertPages: failed to find range FEE00000 - FEEFFFFF ConvertPages: failed to find range FEFFC000 - FEFFFFFF AP Loop Mode is 1 AP Vector: non-16-bit = 3E170000/32A GetMicrocodePatchInfoFromHob: MicrocodeBase = 0x0, MicrocodeSize = 0x0 WakeupBufferStart = 87000, WakeupBufferSize = DD AP Vector: 16-bit = 87000/39, ExchangeInfo = 87039/A4 CpuDxe: 5-Level Paging = 0 CPU[0000]: Microcode revision = 00000000, expected = 00000000 CPU[0001]: Microcode revision = 00000000, expected = 00000000 Detect CPU count: 2 InstallProtocolInterface: 3FDDA605-A76E-4F46-AD29-12F4531B3D08 3E152AE0 Loading driver F6697AC4-A776-4EE1-B643-1FEFF2B615BB None of Tcg2Protocol/CcMeasurementProtocol is installed. InstallProtocolInterface: 5B1B31A1-9562-11D2-8E3F-00A0C969723B 3E1716C0 Loading driver at 0x0003E16B000 EntryPoint=0x0003E16C100 IncompatiblePciDeviceSupportDxe.efi InstallProtocolInterface: BC62157E-3E33-4FEC-9920-2D3B36D750DF 3E171298 ProtectUefiImageCommon - 0x3E1716C0 - 0x000000003E16B000 - 0x0000000000002000 InstallProtocolInterface: EB23F55A-7863-4AC2-8D3D-956535DE0375 3E16CF00 Loading driver 11A6EDF6-A9BE-426D-A6CC-B22FE51D9224 None of Tcg2Protocol/CcMeasurementProtocol is installed. InstallProtocolInterface: 5B1B31A1-9562-11D2-8E3F-00A0C969723B 3E16FB40 Loading driver at 0x0003E161000 EntryPoint=0x0003E164408 PciHotPlugInitDxe.efi InstallProtocolInterface: BC62157E-3E33-4FEC-9920-2D3B36D750DF 3E16FE18 ProtectUefiImageCommon - 0x3E16FB40 - 0x000000003E161000 - 0x0000000000004CC0 InstallProtocolInterface: AA0E8BC1-DABC-46B0-A844-37B8169B2BEA 3E165BD0 Loading driver 4B28E4C7-FF36-4E10-93CF-A82159E777C5 None of Tcg2Protocol/CcMeasurementProtocol is installed. InstallProtocolInterface: 5B1B31A1-9562-11D2-8E3F-00A0C969723B 3E16F140 Loading driver at 0x0003E8D9000 EntryPoint=0x0003E8DB995 ResetSystemRuntimeDxe.efi InstallProtocolInterface: BC62157E-3E33-4FEC-9920-2D3B36D750DF 3E16F418 ProtectUefiImageCommon - 0x3E16F140 - 0x000000003E8D9000 - 0x0000000000007000 SetUefiImageMemoryAttributes - 0x000000003E8D9000 - 0x0000000000001000 (0x0000000000004008) SetUefiImageMemoryAttributes - 0x000000003E8DA000 - 0x0000000000004000 (0x0000000000020008) SetUefiImageMemoryAttributes - 0x000000003E8DE000 - 0x0000000000002000 (0x0000000000004008) InstallProtocolInterface: 27CFAC88-46CC-11D4-9A38-0090273FC14D 0 InstallProtocolInterface: 9DA34AE0-EAF9-4BBF-8EC3-FD60226C44BE 3E8DE108 InstallProtocolInterface: 695D7835-8D47-4C11-AB22-FA8ACCE7AE7A 3E8DE148 InstallProtocolInterface: 2DF6BA0B-7092-440D-BD04-FB091EC3F3C1 3E8DE0C8 Loading driver C8339973-A563-4561-B858-D8476F9DEFC4 None of Tcg2Protocol/CcMeasurementProtocol is installed. InstallProtocolInterface: 5B1B31A1-9562-11D2-8E3F-00A0C969723B 3E16E240 Loading driver at 0x0003E15E000 EntryPoint=0x0003E15F108 Metronome.efi InstallProtocolInterface: BC62157E-3E33-4FEC-9920-2D3B36D750DF 3E16E998 ProtectUefiImageCommon - 0x3E16E240 - 0x000000003E15E000 - 0x00000000000023C0 InstallProtocolInterface: 26BACCB2-6F42-11D4-BCE7-0080C73C8881 3E160230 Loading driver 348C4D62-BFBD-4882-9ECE-C80BB1C4783B None of Tcg2Protocol/CcMeasurementProtocol is installed. InstallProtocolInterface: 5B1B31A1-9562-11D2-8E3F-00A0C969723B 3E16D040 Loading driver at 0x0003DC76000 EntryPoint=0x0003DC8E4BF HiiDatabase.efi InstallProtocolInterface: BC62157E-3E33-4FEC-9920-2D3B36D750DF 3E16DD18 ProtectUefiImageCommon - 0x3E16D040 - 0x000000003DC76000 - 0x000000000001CD40 InstallProtocolInterface: E9CA4775-8657-47FC-97E7-7ED65A084324 3DC928E8 InstallProtocolInterface: 0FD96974-23AA-4CDC-B9CB-98D17750322A 3DC92960 InstallProtocolInterface: EF9FC172-A1B2-4693-B327-6D32FC416042 3DC92988 InstallProtocolInterface: 587E72D7-CC50-4F79-8209-CA291FC1A10F 3DC929E0 InstallProtocolInterface: 0A8BADD5-03B8-4D19-B128-7B8F0EDAA596 3DC92A10 InstallProtocolInterface: 31A6406A-6BDF-4E46-B2A2-EBAA89C40920 3DC92908 InstallProtocolInterface: 1A1241E6-8F19-41A9-BC0E-E8EF39E06546 3DC92930 Loading driver 96B5C032-DF4C-4B6E-8232-438DCF448D0E None of Tcg2Protocol/CcMeasurementProtocol is installed. InstallProtocolInterface: 5B1B31A1-9562-11D2-8E3F-00A0C969723B 3E167040 Loading driver at 0x0003E15B000 EntryPoint=0x0003E15C166 NullMemoryTestDxe.efi InstallProtocolInterface: BC62157E-3E33-4FEC-9920-2D3B36D750DF 3E16D398 ProtectUefiImageCommon - 0x3E167040 - 0x000000003E15B000 - 0x00000000000021C0 InstallProtocolInterface: 309DE7F1-7F5E-4ACE-B49C-531BE5AA95EF 3E15D020 Loading driver 9622E42C-8E38-4A08-9E8F-54F784652F6B None of Tcg2Protocol/CcMeasurementProtocol is installed. InstallProtocolInterface: 5B1B31A1-9562-11D2-8E3F-00A0C969723B 3E167440 Loading driver at 0x0003E118000 EntryPoint=0x0003E11C206 AcpiTableDxe.efi InstallProtocolInterface: BC62157E-3E33-4FEC-9920-2D3B36D750DF 3E167B98 ProtectUefiImageCommon - 0x3E167440 - 0x000000003E118000 - 0x0000000000007700 InstallProtocolInterface: FFE06BDD-6107-46A6-7BB2-5A9C7EC5275C 3E16A0A0 InstallProtocolInterface: EB97088E-CFDF-49C6-BE4B-D906A5B20E86 3E16A0B0 Loading driver BDCE85BB-FBAA-4F4E-9264-501A2C249581 None of Tcg2Protocol/CcMeasurementProtocol is installed. InstallProtocolInterface: 5B1B31A1-9562-11D2-8E3F-00A0C969723B 3E16ACC0 Loading driver at 0x0003E111000 EntryPoint=0x0003E1151A8 S3SaveStateDxe.efi InstallProtocolInterface: BC62157E-3E33-4FEC-9920-2D3B36D750DF 3E16AB18 ProtectUefiImageCommon - 0x3E16ACC0 - 0x000000003E111000 - 0x00000000000063C0 InstallProtocolInterface: E857CAF6-C046-45DC-BE3F-EE0765FBA887 3E117100 Loading driver A210F973-229D-4F4D-AA37-9895E6C9EABA None of Tcg2Protocol/CcMeasurementProtocol is installed. InstallProtocolInterface: 5B1B31A1-9562-11D2-8E3F-00A0C969723B 3E16A3C0 Loading driver at 0x0003E122000 EntryPoint=0x0003E123270 DpcDxe.efi InstallProtocolInterface: BC62157E-3E33-4FEC-9920-2D3B36D750DF 3E169F98 ProtectUefiImageCommon - 0x3E16A3C0 - 0x000000003E122000 - 0x0000000000002080 InstallProtocolInterface: 480F8AE9-0C46-4AA9-BC89-DB9FBA619806 3E123D40 Loading driver 22EA234F-E72A-11E4-91F9-28D2447C4829 None of Tcg2Protocol/CcMeasurementProtocol is installed. InstallProtocolInterface: 5B1B31A1-9562-11D2-8E3F-00A0C969723B 3E1697C0 Loading driver at 0x0003E10E000 EntryPoint=0x0003E10FACE HttpUtilitiesDxe.efi InstallProtocolInterface: BC62157E-3E33-4FEC-9920-2D3B36D750DF 3E169118 ProtectUefiImageCommon - 0x3E1697C0 - 0x000000003E10E000 - 0x0000000000002C40 InstallProtocolInterface: 3E35C163-4074-45DD-431E-23989DD86B32 3E110AD0 Loading driver 8657015B-EA43-440D-949A-AF3BE365C0FC None of Tcg2Protocol/CcMeasurementProtocol is installed. InstallProtocolInterface: 5B1B31A1-9562-11D2-8E3F-00A0C969723B 3E168040 Loading driver at 0x0003DC71000 EntryPoint=0x0003DC73E8E IoMmuDxe.efi InstallProtocolInterface: BC62157E-3E33-4FEC-9920-2D3B36D750DF 3E169418 ProtectUefiImageCommon - 0x3E168040 - 0x000000003DC71000 - 0x0000000000004B40 InstallProtocolInterface: F8775D50-8ABD-4ADF-92AC-853E51F6C8DC 0 Loading driver AC95AD3D-4366-44BF-9A62-E4B29D7A2206 None of Tcg2Protocol/CcMeasurementProtocol is installed. InstallProtocolInterface: 5B1B31A1-9562-11D2-8E3F-00A0C969723B 3E1689C0 Loading driver at 0x0003E120000 EntryPoint=0x0003E1213B2 SmmAccess2Dxe.efi InstallProtocolInterface: BC62157E-3E33-4FEC-9920-2D3B36D750DF 3E168798 ProtectUefiImageCommon - 0x3E1689C0 - 0x000000003E120000 - 0x0000000000001EC0 InstallProtocolInterface: C2702B74-800C-4131-8746-8FB5B89CE4AC 3E121D60 Loading driver A5683620-7998-4BB2-A377-1C1E31E1E215 None of Tcg2Protocol/CcMeasurementProtocol is installed. InstallProtocolInterface: 5B1B31A1-9562-11D2-8E3F-00A0C969723B 3E166040 Loading driver at 0x0003DC6C000 EntryPoint=0x0003DC6EA13 TcgDxe.efi InstallProtocolInterface: BC62157E-3E33-4FEC-9920-2D3B36D750DF 3E168518 ProtectUefiImageCommon - 0x3E166040 - 0x000000003DC6C000 - 0x0000000000004BC0 No TPM12 instance required! Error: Image at 0003DC6C000 start failed: Unsupported Loading driver 6C2004EF-4E0E-4BE4-B14C-340EB4AA5891 None of Tcg2Protocol/CcMeasurementProtocol is installed. InstallProtocolInterface: 5B1B31A1-9562-11D2-8E3F-00A0C969723B 3E166040 Loading driver at 0x0003E8D4000 EntryPoint=0x0003E8D6017 StatusCodeHandlerRuntimeDxe.efi InstallProtocolInterface: BC62157E-3E33-4FEC-9920-2D3B36D750DF 3E166E18 ProtectUefiImageCommon - 0x3E166040 - 0x000000003E8D4000 - 0x0000000000005000 SetUefiImageMemoryAttributes - 0x000000003E8D4000 - 0x0000000000001000 (0x0000000000004008) SetUefiImageMemoryAttributes - 0x000000003E8D5000 - 0x0000000000003000 (0x0000000000020008) SetUefiImageMemoryAttributes - 0x000000003E8D8000 - 0x0000000000001000 (0x0000000000004008) Loading driver 52FE8196-F9DE-4D07-B22F-51F77A0E7C41 None of Tcg2Protocol/CcMeasurementProtocol is installed. InstallProtocolInterface: 5B1B31A1-9562-11D2-8E3F-00A0C969723B 3E166540 Loading driver at 0x0003E10B000 EntryPoint=0x0003E10C794 LocalApicTimerDxe.efi InstallProtocolInterface: BC62157E-3E33-4FEC-9920-2D3B36D750DF 3E166898 ProtectUefiImageCommon - 0x3E166540 - 0x000000003E10B000 - 0x0000000000002E00 InstallProtocolInterface: 26BACCB3-6F42-11D4-BCE7-0080C73C8881 3E10DC20 Loading driver 128FB770-5E79-4176-9E51-9BB268A17DD1 None of Tcg2Protocol/CcMeasurementProtocol is installed. InstallProtocolInterface: 5B1B31A1-9562-11D2-8E3F-00A0C969723B 3E15ACC0 Loading driver at 0x0003DC5D000 EntryPoint=0x0003DC63F0D PciHostBridgeDxe.efi InstallProtocolInterface: BC62157E-3E33-4FEC-9920-2D3B36D750DF 3E15AB18 ProtectUefiImageCommon - 0x3E15ACC0 - 0x000000003DC5D000 - 0x0000000000009D80 Select Item: 0x0 FW CFG Signature: 0x554D4551 Select Item: 0x1 FW CFG Revision: 0x3 QemuFwCfg interface (DMA) is supported. Select Item: 0x19 Select Item: 0x19 PciHostBridgeUtilityInitRootBridge: populated root bus 0, with room for 255 subordinate bus(es) RootBridge: PciRoot(0x0) Support/Attr: 70069 / 70069 DmaAbove4G: No NoExtConfSpace: No AllocAttr: 3 (CombineMemPMem Mem64Decode) Bus: 0 - FF Translation=0 Io: 6000 - FFFF Translation=0 Mem: C0000000 - FBFFFFFF Translation=0 MemAbove4G: 7000000000 - 7FFFFFFFFF Translation=0 PMem: FFFFFFFFFFFFFFFF - 0 Translation=0 PMemAbove4G: FFFFFFFFFFFFFFFF - 0 Translation=0 CpuDxe: 5-Level Paging = 0 InstallProtocolInterface: CF8034BE-6768-4D8B-B739-7CCE683A9FBE 3E15A7C0 InstallProtocolInterface: 09576E91-6D3F-11D2-8E39-00A0C969723B 3E15A318 InstallProtocolInterface: 2F707EBB-4A1A-11D4-9A38-0090273FC14D 3E1271F0 Loading driver EBF342FE-B1D3-4EF8-957C-8048606FF671 None of Tcg2Protocol/CcMeasurementProtocol is installed. InstallProtocolInterface: 5B1B31A1-9562-11D2-8E3F-00A0C969723B 3E127B40 Loading driver at 0x0003DC2B000 EntryPoint=0x0003DC3B289 SetupBrowser.efi InstallProtocolInterface: BC62157E-3E33-4FEC-9920-2D3B36D750DF 3E127998 ProtectUefiImageCommon - 0x3E127B40 - 0x000000003DC2B000 - 0x0000000000018AC0 InstallProtocolInterface: B9D4C360-BCFB-4F9B-9298-53C136982258 3DC435B0 InstallProtocolInterface: A770C357-B693-4E6D-A6CF-D21C728E550B 3DC435E0 InstallProtocolInterface: 1F73B18D-4630-43C1-A1DE-6F80855D7DA4 3DC435C0 Loading driver F9D88642-0737-49BC-81B5-6889CD57D9EA None of Tcg2Protocol/CcMeasurementProtocol is installed. InstallProtocolInterface: 5B1B31A1-9562-11D2-8E3F-00A0C969723B 3E1260C0 Loading driver at 0x0003DC57000 EntryPoint=0x0003DC5A332 SmbiosDxe.efi InstallProtocolInterface: BC62157E-3E33-4FEC-9920-2D3B36D750DF 3E126A98 ProtectUefiImageCommon - 0x3E1260C0 - 0x000000003DC57000 - 0x0000000000005980 Select Item: 0x0 FW CFG Signature: 0x554D4551 Select Item: 0x1 FW CFG Revision: 0x3 QemuFwCfg interface (DMA) is supported. Select Item: 0x19 Select Item: 0x19 Select Item: 0x27 DetectSmbiosVersion: SMBIOS version from QEMU: 0x0208 InstallProtocolInterface: 03583FF6-CB36-4940-947E-B9B39F4AFAF7 3DC5C810 Loading driver 17985E6F-E778-4D94-AEFA-C5DD2B77E186 None of Tcg2Protocol/CcMeasurementProtocol is installed. InstallProtocolInterface: 5B1B31A1-9562-11D2-8E3F-00A0C969723B 3E125040 Loading driver at 0x0003DC50000 EntryPoint=0x0003DC546C6 QemuFwCfgAcpiPlatform.efi InstallProtocolInterface: BC62157E-3E33-4FEC-9920-2D3B36D750DF 3E126598 ProtectUefiImageCommon - 0x3E125040 - 0x000000003DC50000 - 0x0000000000006D80 Select Item: 0x0 FW CFG Signature: 0x554D4551 Select Item: 0x1 FW CFG Revision: 0x3 QemuFwCfg interface (DMA) is supported. AcpiPlatformEntryPoint: waiting for root bridges to be connected, registered callback Loading driver A487A478-51EF-48AA-8794-7BEE2A0562F1 None of Tcg2Protocol/CcMeasurementProtocol is installed. InstallProtocolInterface: 5B1B31A1-9562-11D2-8E3F-00A0C969723B 3E125A40 Loading driver at 0x0003DC20000 EntryPoint=0x0003DC26739 tftpDynamicCommand.efi InstallProtocolInterface: BC62157E-3E33-4FEC-9920-2D3B36D750DF 3E125398 InstallProtocolInterface: 6A1EE763-D47A-43B4-AABE-EF1DE2AB56FC 3DC28C70 ProtectUefiImageCommon - 0x3E125A40 - 0x000000003DC20000 - 0x000000000000A7C0 InstallProtocolInterface: 3C7200E9-005F-4EA4-87DE-A3DFAC8A27C3 3DC289A0 Loading driver 19618BCE-55AE-09C6-37E9-4CE04084C7A1 None of Tcg2Protocol/CcMeasurementProtocol is installed. InstallProtocolInterface: 5B1B31A1-9562-11D2-8E3F-00A0C969723B 3E10ABC0 Loading driver at 0x0003DC06000 EntryPoint=0x0003DC0DF8C httpDynamicCommand.efi InstallProtocolInterface: BC62157E-3E33-4FEC-9920-2D3B36D750DF 3E10AA18 InstallProtocolInterface: 6A1EE763-D47A-43B4-AABE-EF1DE2AB56FC 3DC10AF0 ProtectUefiImageCommon - 0x3E10ABC0 - 0x000000003DC06000 - 0x000000000000CD80 InstallProtocolInterface: 3C7200E9-005F-4EA4-87DE-A3DFAC8A27C3 3DC107F0 Loading driver 2F30DA26-F51B-4B6F-85C4-31873C281BCA None of Tcg2Protocol/CcMeasurementProtocol is installed. InstallProtocolInterface: 5B1B31A1-9562-11D2-8E3F-00A0C969723B 3E109040 Loading driver at 0x0003DC18000 EntryPoint=0x0003DC1CFED LinuxInitrdDynamicShellCommand.efi InstallProtocolInterface: BC62157E-3E33-4FEC-9920-2D3B36D750DF 3E10A398 InstallProtocolInterface: 6A1EE763-D47A-43B4-AABE-EF1DE2AB56FC 3DC1F0F0 ProtectUefiImageCommon - 0x3E109040 - 0x000000003DC18000 - 0x0000000000007C00 InstallProtocolInterface: 3C7200E9-005F-4EA4-87DE-A3DFAC8A27C3 3DC1EDA0 Loading driver F74D20EE-37E7-48FC-97F7-9B1047749C69 None of Tcg2Protocol/CcMeasurementProtocol is installed. InstallProtocolInterface: 5B1B31A1-9562-11D2-8E3F-00A0C969723B 3DC6BAC0 Loading driver at 0x0003DC46000 EntryPoint=0x0003DC46F39 LogoDxe.efi InstallProtocolInterface: BC62157E-3E33-4FEC-9920-2D3B36D750DF 3DC6BE18 InstallProtocolInterface: 6A1EE763-D47A-43B4-AABE-EF1DE2AB56FC 3DC47B30 ProtectUefiImageCommon - 0x3DC6BAC0 - 0x000000003DC46000 - 0x0000000000004A80 InstallProtocolInterface: 53CD299F-2BC1-40C0-8C07-23F64FDB30E0 3DC47980 Loading driver DCE1B094-7DC6-45D0-9FDD-D7FC3CC3E4EF None of Tcg2Protocol/CcMeasurementProtocol is installed. InstallProtocolInterface: 5B1B31A1-9562-11D2-8E3F-00A0C969723B 3DC6A440 Loading driver at 0x0003DC13000 EntryPoint=0x0003DC1558E QemuRamfbDxe.efi InstallProtocolInterface: BC62157E-3E33-4FEC-9920-2D3B36D750DF 3DC6AE18 ProtectUefiImageCommon - 0x3DC6A440 - 0x000000003DC13000 - 0x0000000000004500 Select Item: 0x0 FW CFG Signature: 0x554D4551 Select Item: 0x1 FW CFG Revision: 0x3 QemuFwCfg interface (DMA) is supported. Select Item: 0x19 Error: Image at 0003DC13000 start failed: Not Found Loading driver 1206F7CA-A475-4624-A83E-E6FC9BB38E49 None of Tcg2Protocol/CcMeasurementProtocol is installed. InstallProtocolInterface: 5B1B31A1-9562-11D2-8E3F-00A0C969723B 3DC6A440 Loading driver at 0x0003E8CD000 EntryPoint=0x0003E8D00E7 SmmControl2Dxe.efi InstallProtocolInterface: BC62157E-3E33-4FEC-9920-2D3B36D750DF 3DC6AC18 ProtectUefiImageCommon - 0x3DC6A440 - 0x000000003E8CD000 - 0x0000000000007000 SetUefiImageMemoryAttributes - 0x000000003E8CD000 - 0x0000000000001000 (0x0000000000004008) SetUefiImageMemoryAttributes - 0x000000003E8CE000 - 0x0000000000004000 (0x0000000000020008) SetUefiImageMemoryAttributes - 0x000000003E8D2000 - 0x0000000000002000 (0x0000000000004008) Select Item: 0x0 FW CFG Signature: 0x554D4551 Select Item: 0x1 FW CFG Revision: 0x3 QemuFwCfg interface (DMA) is supported. Select Item: 0x19 Select Item: 0x19 Select Item: 0x19 Select Item: 0x2B Select Item: 0x2A Select Item: 0x29 NegotiateSmiFeatures: using SMI broadcast NegotiateSmiFeatures: CPU hotplug with SMI negotiated NegotiateSmiFeatures: CPU hot-unplug with SMI negotiated Select Item: 0x1 SmmControl2Dxe: S3SaveStateInstalledNotify: DmaAccess@0x3E964018 ScratchBuffer@[0x3E964028+0x8] InstallProtocolInterface: 843DC720-AB1E-42CB-9357-8A0078F3561B 3E8D2010 Loading driver 229B7EFD-DA02-46B9-93F4-E20C009F94E9 None of Tcg2Protocol/CcMeasurementProtocol is installed. InstallProtocolInterface: 5B1B31A1-9562-11D2-8E3F-00A0C969723B 3DC4C040 Loading driver at 0x0003DC15000 EntryPoint=0x0003DC16266 CpuS3DataDxe.efi InstallProtocolInterface: BC62157E-3E33-4FEC-9920-2D3B36D750DF 3DC6A718 ProtectUefiImageCommon - 0x3DC4C040 - 0x000000003DC15000 - 0x00000000000023C0 Loading driver F099D67F-71AE-4C36-B2A3-DCEB0EB2B7D8 None of Tcg2Protocol/CcMeasurementProtocol is installed. InstallProtocolInterface: 5B1B31A1-9562-11D2-8E3F-00A0C969723B 3DC4CA40 Loading driver at 0x0003DC13000 EntryPoint=0x0003DC13FF9 WatchdogTimer.efi InstallProtocolInterface: BC62157E-3E33-4FEC-9920-2D3B36D750DF 3DC4C998 ProtectUefiImageCommon - 0x3DC4CA40 - 0x000000003DC13000 - 0x0000000000001EC0 InstallProtocolInterface: 665E3FF5-46CC-11D4-9A38-0090273FC14D 3DC14D10 Loading driver EBF8ED7C-0DD1-4787-84F1-F48D537DCACF None of Tcg2Protocol/CcMeasurementProtocol is installed. InstallProtocolInterface: 5B1B31A1-9562-11D2-8E3F-00A0C969723B 3DC4B040 Loading driver at 0x0003D9FA000 EntryPoint=0x0003D9FDC1D DriverHealthManagerDxe.efi InstallProtocolInterface: BC62157E-3E33-4FEC-9920-2D3B36D750DF 3DC4BF18 ProtectUefiImageCommon - 0x3DC4B040 - 0x000000003D9FA000 - 0x0000000000005F40 InstallProtocolInterface: 09576E91-6D3F-11D2-8E39-00A0C969723B 3D9FF960 InstallProtocolInterface: 330D4706-F2A0-4E4F-A369-B66FA8D54385 3D9FF930 Loading driver 28A03FF4-12B3-4305-A417-BB1A4F94081E None of Tcg2Protocol/CcMeasurementProtocol is installed. InstallProtocolInterface: 5B1B31A1-9562-11D2-8E3F-00A0C969723B 3DC454C0 Loading driver at 0x0003D9E4000 EntryPoint=0x0003D9EAA01 RamDiskDxe.efi InstallProtocolInterface: BC62157E-3E33-4FEC-9920-2D3B36D750DF 3DC4BA18 ProtectUefiImageCommon - 0x3DC454C0 - 0x000000003D9E4000 - 0x000000000000A900 InstallProtocolInterface: 09576E91-6D3F-11D2-8E39-00A0C969723B 3DC4B618 InstallProtocolInterface: 330D4706-F2A0-4E4F-A369-B66FA8D54385 3D9EE5D8 InstallProtocolInterface: 09576E91-6D3F-11D2-8E39-00A0C969723B 3D9EE670 InstallProtocolInterface: 330D4706-F2A0-4E4F-A369-B66FA8D54385 3DC05FB0 InstallProtocolInterface: AB38A0DF-6873-44A9-87E6-D4EB56148449 3D9EE360 InstallProtocolInterface: 28A03FF4-12B3-4305-A417-BB1A4F94081E 3DC05F98 Loading driver E660EA85-058E-4B55-A54B-F02F83A24707 None of Tcg2Protocol/CcMeasurementProtocol is installed. InstallProtocolInterface: 5B1B31A1-9562-11D2-8E3F-00A0C969723B 3DC04740 Loading driver at 0x0003D9BC000 EntryPoint=0x0003D9CA753 DisplayEngine.efi InstallProtocolInterface: BC62157E-3E33-4FEC-9920-2D3B36D750DF 3DC04A18 ProtectUefiImageCommon - 0x3DC04740 - 0x000000003D9BC000 - 0x0000000000013940 InstallProtocolInterface: 9BBE29E9-FDA1-41EC-AD52-452213742D2E 3D9CDDB0 InstallProtocolInterface: 4311EDC0-6054-46D4-9E40-893EA952FCCC 3D9CDDC8 Loading driver 4110465D-5FF3-4F4B-B580-24ED0D06747A None of Tcg2Protocol/CcMeasurementProtocol is installed. InstallProtocolInterface: 5B1B31A1-9562-11D2-8E3F-00A0C969723B 3DC00140 Loading driver at 0x0003D9F0000 EntryPoint=0x0003D9F1C3E SmbiosPlatformDxe.efi InstallProtocolInterface: BC62157E-3E33-4FEC-9920-2D3B36D750DF 3DC44818 ProtectUefiImageCommon - 0x3DC00140 - 0x000000003D9F0000 - 0x0000000000003380 Select Item: 0x0 FW CFG Signature: 0x554D4551 Select Item: 0x1 FW CFG Revision: 0x3 QemuFwCfg interface (DMA) is supported. Select Item: 0x19 Select Item: 0x28 SmbiosAdd: Smbios type 1 with size 0x4B is added to 32-bit table SmbiosCreateTable: Initialize 32-bit entry point structure SmbiosCreateTable() re-allocate SMBIOS 32-bit table SmbiosAdd: Smbios type 3 with size 0x27 is added to 32-bit table SmbiosAdd: Smbios type 4 with size 0x41 is added to 32-bit table SmbiosAdd: Smbios type 16 with size 0x19 is added to 32-bit table SmbiosAdd: Smbios type 17 with size 0x35 is added to 32-bit table SmbiosAdd: Smbios type 19 with size 0x21 is added to 32-bit table SmbiosAdd: Smbios type 32 with size 0xD is added to 32-bit table FirmwareVendor: "EDK II" (6 chars) FirmwareVersionString: "kraxel-devel-build" (18 chars) FirmwareReleaseDateString: "03/06/2023" (10 chars) SmbiosAdd: Smbios type 0 with size 0x40 is added to 32-bit table Loading driver 2FA2A6DA-11D5-4DC3-999A-749648B03C56 None of Tcg2Protocol/CcMeasurementProtocol is installed. InstallProtocolInterface: 5B1B31A1-9562-11D2-8E3F-00A0C969723B 3D9F74C0 Loading driver at 0x0003E8C4000 EntryPoint=0x0003E8C7CF8 PiSmmIpl.efi InstallProtocolInterface: BC62157E-3E33-4FEC-9920-2D3B36D750DF 3D9F7118 ProtectUefiImageCommon - 0x3D9F74C0 - 0x000000003E8C4000 - 0x0000000000009000 SetUefiImageMemoryAttributes - 0x000000003E8C4000 - 0x0000000000001000 (0x0000000000004008) SetUefiImageMemoryAttributes - 0x000000003E8C5000 - 0x0000000000006000 (0x0000000000020008) SetUefiImageMemoryAttributes - 0x000000003E8CB000 - 0x0000000000002000 (0x0000000000004008) SMM IPL opened SMRAM window SMM IPL found SMRAM window 3F001000 - 3FFFFFFF SMRAM attributes: 0000000000000008 SMM IPL loading SMM Core at SMRAM address 3FFEE000 SMM IPL calling SMM Core at SMRAM address 3FFF881C PiSmmCoreImageBase - 0x000000003FFEE000 PiSmmCoreImageSize - 0x0000000000011000 SmmAddMemoryRegion MemBase - 0x3F001000 MemLength - 0xFED000 Type - 0x7 Attributes - 0xA SmmAddMemoryRegion MemBase - 0x3F000000 MemLength - 0x1000 Type - 0x6 Attributes - 0x1A SmmAddMemoryRegion MemBase - 0x3FFEE000 MemLength - 0x12000 Type - 0x6 Attributes - 0x1A mSmmMemLibInternalMaximumSupportAddress = 0x7FFFFFFFFF InstallProtocolInterface: 5B1B31A1-9562-11D2-8E3F-00A0C969723B 3D9F6898 SmmInstallProtocolInterface: 5B1B31A1-9562-11D2-8E3F-00A0C969723B 3FFEC0C0 InstallProtocolInterface: F4CCBFB7-F6E0-47FD-9DD4-10A8F150C191 3E8CB0E0 InstallProtocolInterface: C68ED8E2-9DC6-4CBD-9D94-DB65ACC5C332 3E8CB400 InstallProtocolInterface: 378DAEDC-F06B-4446-8314-40AB933C87A3 3E8CB0B0 None of Tcg2Protocol/CcMeasurementProtocol is installed. InstallProtocolInterface: 5B1B31A1-9562-11D2-8E3F-00A0C969723B 3D9EF798 SmmInstallProtocolInterface: 5B1B31A1-9562-11D2-8E3F-00A0C969723B 3FFEBAC0 Loading SMM driver at 0x0003FFE2000 EntryPoint=0x0003FFE4289 CpuIo2Smm.efi SmmInstallProtocolInterface: 3242A9D8-CE70-4AA0-955D-5E7B140DE4D2 3FFE6020 None of Tcg2Protocol/CcMeasurementProtocol is installed. InstallProtocolInterface: 5B1B31A1-9562-11D2-8E3F-00A0C969723B 3D9EF598 SmmInstallProtocolInterface: 5B1B31A1-9562-11D2-8E3F-00A0C969723B 3FFEB8C0 Loading SMM driver at 0x0003FFD8000 EntryPoint=0x0003FFDB8A9 SmmLockBox.efi SmmLockBoxSmmLib SmmLockBoxMmConstructor - Enter SmmLockBoxSmmLib SmmLockBoxContext - 3FFDE160 SmmLockBoxSmmLib LockBoxDataAddress - 3FFDE060 SmmLockBoxSmmLib SmmLockBoxMmConstructor - Exit mSmmMemLibInternalMaximumSupportAddress = 0x7FFFFFFFFF InstallProtocolInterface: BD445D79-B7AD-4F04-9AD8-29BD2040EB3C 0 None of Tcg2Protocol/CcMeasurementProtocol is installed. InstallProtocolInterface: 5B1B31A1-9562-11D2-8E3F-00A0C969723B 3D9EF298 SmmInstallProtocolInterface: 5B1B31A1-9562-11D2-8E3F-00A0C969723B 3FFEB6C0 Loading SMM driver at 0x0003FFBF000 EntryPoint=0x0003FFCA149 PiSmmCpuDxeSmm.efi SMRR Base: 0x3F000000, SMRR Size: 0x1000000 PcdCpuSmmCodeAccessCheckEnable = 1 mAddressEncMask = 0x0 PcdControlFlowEnforcementPropertyMask = 0 SMRAM TileSize = 0x00002000 (0x00001000, 0x00001000) PiCpuSmmEntry: gSmmBaseHobGuid not found! New Allcoated SMRAM SaveState Buffer (0x3FFB1000, 0x0000E000) CPU[000] APIC ID=0000 SMBASE=3FFA9000 SaveState=3FFB8C00 Size=00000400 CPU[001] APIC ID=0001 SMBASE=3FFAB000 SaveState=3FFBAC00 Size=00000400 Stacks - 0x3FF98000 mSmmStackSize - 0x6000 PcdCpuSmmStackGuard - 0x1 mXdSupported - 0x1 One Semaphore Size = 0x40 Total Semaphores Size = 0x540 PhysicalAddressBits = 39, 5LPageTable = 0. 5LevelPaging Needed - 0 1GPageTable Support - 1 PcdCpuSmmRestrictedMemoryAccess - 1 PhysicalAddressBits - 39 Initialize IDT IST field for SMM Stack Guard InstallProtocolInterface: 26EEB3DE-B689-492E-80F0-BE8BD7DA4BA7 3FFD4170 SMM IPL registered SMM Entry Point address 3FFEFD8C SmmInstallProtocolInterface: EB346B97-975F-4A9F-8B22-F8E92BB3D569 3FFD41B0 SmmInstallProtocolInterface: 69B792EA-39CE-402D-A2A6-F721DE351DFE 3FFD40B0 CpuSmm: SpinLock Size = 0x40, PcdCpuSmmMpTokenCountPerChunk = 0x40 SmmInstallProtocolInterface: 5D5450D7-990C-4180-A803-8E63F0608307 3FFD4240 SmmInstallProtocolInterface: 1D202CAB-C8AB-4D5C-94F7-3CFCC0D3D335 3FFD4040 SmmInstallProtocolInterface: AA00D50B-4911-428F-B91A-A59DDB13E24C 3FFD4020 SMM S3 SMRAM Structure = 3E6E8B00 SMM S3 Structure = 3F000000 SMM CPU Module exit from SMRAM with EFI_SUCCESS SMM IPL closed SMRAM window None of Tcg2Protocol/CcMeasurementProtocol is installed. InstallProtocolInterface: 5B1B31A1-9562-11D2-8E3F-00A0C969723B 3D9D1B98 SmmInstallProtocolInterface: 5B1B31A1-9562-11D2-8E3F-00A0C969723B 3FFEB4C0 Loading SMM driver at 0x0003FF80000 EntryPoint=0x0003FF83956 FvbServicesSmm.efi QEMU Flash: Attempting flash detection at FFC00010 QemuFlashDetected => FD behaves as FLASH QemuFlashDetected => Yes Installing QEMU flash SMM FVB SmmInstallProtocolInterface: D326D041-BD31-4C01-B5A8-628BE87F0653 3FFB0530 SmmInstallProtocolInterface: 09576E91-6D3F-11D2-8E39-00A0C969723B 3FFB0498 None of Tcg2Protocol/CcMeasurementProtocol is installed. InstallProtocolInterface: 5B1B31A1-9562-11D2-8E3F-00A0C969723B 3D9D1A18 SmmInstallProtocolInterface: 5B1B31A1-9562-11D2-8E3F-00A0C969723B 3FFEB0C0 Loading SMM driver at 0x0003FEDB000 EntryPoint=0x0003FF25CBC VariableSmm.efi mSmmMemLibInternalMaximumSupportAddress = 0x7FFFFFFFFF VarCheckLibRegisterSetVariableCheckHandler - 0x3FF1F0AB Success VarCheckLibRegisterSetVariableCheckHandler - 0x3FF1868F Success Variable driver common space: 0x3FF9C 0x3FF9C 0x3FF9C Variable driver will work with auth variable format! SmmInstallProtocolInterface: ED32D533-99E6-4209-9CC0-2D72CDD998A7 3FF400A0 SmmInstallProtocolInterface: B0D8F3C1-B7DE-4C11-BC89-2FB562C8C411 3FF40060 InstallProtocolInterface: ED32D533-99E6-4209-9CC0-2D72CDD998A7 0 None of Tcg2Protocol/CcMeasurementProtocol is installed. InstallProtocolInterface: 5B1B31A1-9562-11D2-8E3F-00A0C969723B 3D9D1598 SmmInstallProtocolInterface: 5B1B31A1-9562-11D2-8E3F-00A0C969723B 3FFEBCC0 Loading SMM driver at 0x0003FD8E000 EntryPoint=0x0003FD91670 CpuHotplugSmm.efi SmbaseAllocatePostSmmPen: Post-SMM Pen at 0x9F000 None of Tcg2Protocol/CcMeasurementProtocol is installed. InstallProtocolInterface: 5B1B31A1-9562-11D2-8E3F-00A0C969723B 3D9D1218 SmmInstallProtocolInterface: 5B1B31A1-9562-11D2-8E3F-00A0C969723B 3FFEB2C0 Loading SMM driver at 0x0003FD83000 EntryPoint=0x0003FD888D7 SmmFaultTolerantWriteDxe.efi mSmmMemLibInternalMaximumSupportAddress = 0x7FFFFFFFFF Ftw: FtwWorkSpaceLba - 0x41, WorkBlockSize - 0x1000, FtwWorkSpaceBase - 0x0 Ftw: FtwSpareLba - 0x42, SpareBlockSize - 0x1000 Ftw: NumberOfWorkBlock - 0x1, FtwWorkBlockLba - 0x41 Ftw: WorkSpaceLbaInSpare - 0x0, WorkSpaceBaseInSpare - 0x0 Ftw: Remaining work space size - FE0 SmmInstallProtocolInterface: 3868FC3B-7E45-43A7-906C-4BA47DE1754D 3FD80028 Variable PK does not exist. Variable SetupMode is 1 Variable SecureBoot is 0 Variable SecureBootEnable is 0 Variable CustomMode is 0 Variable VendorKeys is 1 Variable driver will work with auth variable support! InstallProtocolInterface: 93BA1826-DFFB-45DD-82A7-E7DCAA3BBDF3 0 InstallProtocolInterface: 3868FC3B-7E45-43A7-906C-4BA47DE1754D 0 Loading driver FA20568B-548B-4B2B-81EF-1BA08D4A3CEC None of Tcg2Protocol/CcMeasurementProtocol is installed. InstallProtocolInterface: 5B1B31A1-9562-11D2-8E3F-00A0C969723B 3D9D00C0 Loading driver at 0x0003D8C8000 EntryPoint=0x0003D8CDD35 BootScriptExecutorDxe.efi InstallProtocolInterface: BC62157E-3E33-4FEC-9920-2D3B36D750DF 3D9D0A98 ProtectUefiImageCommon - 0x3D9D00C0 - 0x000000003D8C8000 - 0x0000000000014B40 Loading driver 9F7DCADE-11EA-448A-A46F-76E003657DD1 None of Tcg2Protocol/CcMeasurementProtocol is installed. InstallProtocolInterface: 5B1B31A1-9562-11D2-8E3F-00A0C969723B 3D9D0540 Loading driver at 0x0003E8BC000 EntryPoint=0x0003E8BFD8A VariableSmmRuntimeDxe.efi InstallProtocolInterface: BC62157E-3E33-4FEC-9920-2D3B36D750DF 3D8E8F98 ProtectUefiImageCommon - 0x3D9D0540 - 0x000000003E8BC000 - 0x0000000000008000 SetUefiImageMemoryAttributes - 0x000000003E8BC000 - 0x0000000000001000 (0x0000000000004008) SetUefiImageMemoryAttributes - 0x000000003E8BD000 - 0x0000000000005000 (0x0000000000020008) SetUefiImageMemoryAttributes - 0x000000003E8C2000 - 0x0000000000002000 (0x0000000000004008) Variable driver runtime cache is disabled. InstallProtocolInterface: 1E5668E2-8481-11D4-BCF1-0080C73C8881 0 InstallProtocolInterface: CD3D0A05-9E24-437C-A891-1EE053DB7638 3E8C2288 InstallProtocolInterface: AF23B340-97B4-4685-8D4F-A3F28169B21D 3E8C2270 InstallProtocolInterface: 6441F818-6362-4E44-B570-7DBA31DD2453 0 InstallProtocolInterface: 81D1675C-86F6-48DF-BD95-9A6E4F0925C3 3E8C21E0 Loading driver 378D7B65-8DA9-4773-B6E4-A47826A833E1 None of Tcg2Protocol/CcMeasurementProtocol is installed. InstallProtocolInterface: 5B1B31A1-9562-11D2-8E3F-00A0C969723B 3D8E8340 Loading driver at 0x0003E8B6000 EntryPoint=0x0003E8B9191 PcRtc.efi InstallProtocolInterface: BC62157E-3E33-4FEC-9920-2D3B36D750DF 3D8EAE98 ProtectUefiImageCommon - 0x3D8E8340 - 0x000000003E8B6000 - 0x0000000000006000 SetUefiImageMemoryAttributes - 0x000000003E8B6000 - 0x0000000000001000 (0x0000000000004008) SetUefiImageMemoryAttributes - 0x000000003E8B7000 - 0x0000000000004000 (0x0000000000020008) SetUefiImageMemoryAttributes - 0x000000003E8BB000 - 0x0000000000001000 (0x0000000000004008) InstallProtocolInterface: 27CFAC87-46CC-11D4-9A38-0090273FC14D 0 Loading driver F0E6A44F-7195-41C3-AC64-54F202CD0A21 None of Tcg2Protocol/CcMeasurementProtocol is installed. InstallProtocolInterface: 5B1B31A1-9562-11D2-8E3F-00A0C969723B 3D8EA340 Loading driver at 0x0003D802000 EntryPoint=0x0003D832601 SecureBootConfigDxe.efi InstallProtocolInterface: BC62157E-3E33-4FEC-9920-2D3B36D750DF 3D8EA698 ProtectUefiImageCommon - 0x3D8EA340 - 0x000000003D802000 - 0x0000000000062B40 InstallProtocolInterface: 09576E91-6D3F-11D2-8E39-00A0C969723B 3D8F1C98 InstallProtocolInterface: 330D4706-F2A0-4E4F-A369-B66FA8D54385 3D84E938 InstallProtocolInterface: 09576E91-6D3F-11D2-8E39-00A0C969723B 3D84E9B0 InstallProtocolInterface: 330D4706-F2A0-4E4F-A369-B66FA8D54385 3D8F0220 InstallProtocolInterface: F0E6A44F-7195-41C3-AC64-54F202CD0A21 3D8F0218 Loading driver AD608272-D07F-4964-801E-7BD3B7888652 None of Tcg2Protocol/CcMeasurementProtocol is installed. InstallProtocolInterface: 5B1B31A1-9562-11D2-8E3F-00A0C969723B 3D8EF740 Loading driver at 0x0003E8B2000 EntryPoint=0x0003E8B3DCD MonotonicCounterRuntimeDxe.efi InstallProtocolInterface: BC62157E-3E33-4FEC-9920-2D3B36D750DF 3D8EEF98 ProtectUefiImageCommon - 0x3D8EF740 - 0x000000003E8B2000 - 0x0000000000004000 SetUefiImageMemoryAttributes - 0x000000003E8B2000 - 0x0000000000001000 (0x0000000000004008) SetUefiImageMemoryAttributes - 0x000000003E8B3000 - 0x0000000000002000 (0x0000000000020008) SetUefiImageMemoryAttributes - 0x000000003E8B5000 - 0x0000000000001000 (0x0000000000004008) InstallProtocolInterface: 1DA97072-BDDC-4B30-99F1-72A0B56FFF2A 0 Loading driver 42857F0A-13F2-4B21-8A23-53D3F714B840 None of Tcg2Protocol/CcMeasurementProtocol is installed. InstallProtocolInterface: 5B1B31A1-9562-11D2-8E3F-00A0C969723B 3D8EE1C0 Loading driver at 0x0003E8AE000 EntryPoint=0x0003E8B0094 CapsuleRuntimeDxe.efi InstallProtocolInterface: BC62157E-3E33-4FEC-9920-2D3B36D750DF 3D8EE718 ProtectUefiImageCommon - 0x3D8EE1C0 - 0x000000003E8AE000 - 0x0000000000004000 SetUefiImageMemoryAttributes - 0x000000003E8AE000 - 0x0000000000001000 (0x0000000000004008) SetUefiImageMemoryAttributes - 0x000000003E8AF000 - 0x0000000000002000 (0x0000000000020008) SetUefiImageMemoryAttributes - 0x000000003E8B1000 - 0x0000000000001000 (0x0000000000004008) InstallProtocolInterface: 5053697E-2CBC-4819-90D9-0580DEEE5754 0 Loading driver 6D33944A-EC75-4855-A54D-809C75241F6C None of Tcg2Protocol/CcMeasurementProtocol is installed. InstallProtocolInterface: 5B1B31A1-9562-11D2-8E3F-00A0C969723B 3D8EDCC0 Loading driver at 0x0003D88C000 EntryPoint=0x0003D89F5E9 BdsDxe.efi InstallProtocolInterface: BC62157E-3E33-4FEC-9920-2D3B36D750DF 3D8EDB18 ProtectUefiImageCommon - 0x3D8EDCC0 - 0x000000003D88C000 - 0x000000000001DDC0 Select Item: 0x0 FW CFG Signature: 0x554D4551 Select Item: 0x1 FW CFG Revision: 0x3 QemuFwCfg interface (DMA) is supported. InstallProtocolInterface: 665E3FF6-46CC-11D4-9A38-0090273FC14D 3D8A9AE0 Loading driver 7CA1024F-EB17-11E5-9DBA-28D2447C4829 None of Tcg2Protocol/CcMeasurementProtocol is installed. InstallProtocolInterface: 5B1B31A1-9562-11D2-8E3F-00A0C969723B 3D8ED2C0 Loading driver at 0x0003D8BD000 EntryPoint=0x0003D8C3A00 TlsAuthConfigDxe.efi InstallProtocolInterface: BC62157E-3E33-4FEC-9920-2D3B36D750DF 3D8ED618 ProtectUefiImageCommon - 0x3D8ED2C0 - 0x000000003D8BD000 - 0x000000000000ADC0 Select Item: 0x0 FW CFG Signature: 0x554D4551 Select Item: 0x1 FW CFG Revision: 0x3 QemuFwCfg interface (DMA) is supported. InstallProtocolInterface: 09576E91-6D3F-11D2-8E39-00A0C969723B 3D8E9C98 InstallProtocolInterface: 330D4706-F2A0-4E4F-A369-B66FA8D54385 3D8C79F8 Select Item: 0x19 Select Item: 0x19 InstallProtocolInterface: 09576E91-6D3F-11D2-8E39-00A0C969723B 3D8C7AF0 InstallProtocolInterface: 330D4706-F2A0-4E4F-A369-B66FA8D54385 3D8E6EB0 InstallProtocolInterface: 7CA1024F-EB17-11E5-9DBA-28D2447C4829 3D8E6E98 Loading driver D9DCC5DF-4007-435E-9098-8970935504B2 None of Tcg2Protocol/CcMeasurementProtocol is installed. InstallProtocolInterface: 5B1B31A1-9562-11D2-8E3F-00A0C969723B 3D8E66C0 Loading driver at 0x0003D8B7000 EntryPoint=0x0003D8BA6A7 PlatformDxe.efi InstallProtocolInterface: BC62157E-3E33-4FEC-9920-2D3B36D750DF 3D8E6A18 ProtectUefiImageCommon - 0x3D8E66C0 - 0x000000003D8B7000 - 0x0000000000005BC0 InstallProtocolInterface: 09576E91-6D3F-11D2-8E39-00A0C969723B 3D8BC9C0 InstallProtocolInterface: 330D4706-F2A0-4E4F-A369-B66FA8D54385 3D8BCA90 Loading driver FDFF263D-5F68-4591-87BA-B768F445A9AF None of Tcg2Protocol/CcMeasurementProtocol is installed. InstallProtocolInterface: 5B1B31A1-9562-11D2-8E3F-00A0C969723B 3D8E5B40 Loading driver at 0x0003D86A000 EntryPoint=0x0003D870A23 Tcg2Dxe.efi InstallProtocolInterface: BC62157E-3E33-4FEC-9920-2D3B36D750DF 3D8DF098 ProtectUefiImageCommon - 0x3D8E5B40 - 0x000000003D86A000 - 0x0000000000010AC0 Select Item: 0x0 FW CFG Signature: 0x554D4551 Select Item: 0x1 FW CFG Revision: 0x3 QemuFwCfg interface (DMA) is supported. WARNING: Tpm2RegisterTpm2DeviceLib - does not support 286BF25A-C2C3-408C-B3B4-25E6758B7317 registration No TPM2 instance required! Error: Image at 0003D86A000 start failed: Unsupported Loading driver 93B80004-9FB3-11D4-9A3A-0090273FC14D None of Tcg2Protocol/CcMeasurementProtocol is installed. InstallProtocolInterface: 5B1B31A1-9562-11D2-8E3F-00A0C969723B 3D8E5B40 Loading driver at 0x0003D86E000 EntryPoint=0x0003D879F00 PciBusDxe.efi InstallProtocolInterface: BC62157E-3E33-4FEC-9920-2D3B36D750DF 3D8DF698 ProtectUefiImageCommon - 0x3D8E5B40 - 0x000000003D86E000 - 0x000000000000EEC0 InstallProtocolInterface: 18A031AB-B443-4D1A-A5C0-0C09261E9F71 3D87CA40 InstallProtocolInterface: 107A772C-D5E1-11D4-9A46-0090273FC14D 3D87C920 InstallProtocolInterface: 6A7A5CFF-E8D9-4F70-BADA-75AB3025CE14 3D87CC00 InstallProtocolInterface: 19CB87AB-2CB9-4665-8360-DDCF6054F79D 3D87CBE0 Loading driver 83DD3B39-7CAF-4FAC-A542-E050B767E3A7 None of Tcg2Protocol/CcMeasurementProtocol is installed. InstallProtocolInterface: 5B1B31A1-9562-11D2-8E3F-00A0C969723B 3D8E54C0 Loading driver at 0x0003D8B4000 EntryPoint=0x0003D8B5C3D VirtioPciDeviceDxe.efi InstallProtocolInterface: BC62157E-3E33-4FEC-9920-2D3B36D750DF 3D8E5798 ProtectUefiImageCommon - 0x3D8E54C0 - 0x000000003D8B4000 - 0x0000000000003000 InstallProtocolInterface: 18A031AB-B443-4D1A-A5C0-0C09261E9F71 3D8B6DA0 InstallProtocolInterface: 107A772C-D5E1-11D4-9A46-0090273FC14D 3D8B6E00 InstallProtocolInterface: 6A7A5CFF-E8D9-4F70-BADA-75AB3025CE14 3D8B6D80 Loading driver 0170F60C-1D40-4651-956D-F0BD9879D527 None of Tcg2Protocol/CcMeasurementProtocol is installed. InstallProtocolInterface: 5B1B31A1-9562-11D2-8E3F-00A0C969723B 3D8E00C0 Loading driver at 0x0003D8AA000 EntryPoint=0x0003D8AD399 Virtio10.efi InstallProtocolInterface: BC62157E-3E33-4FEC-9920-2D3B36D750DF 3D8E0B18 ProtectUefiImageCommon - 0x3D8E00C0 - 0x000000003D8AA000 - 0x0000000000004B40 InstallProtocolInterface: 18A031AB-B443-4D1A-A5C0-0C09261E9F71 3D8AE8E0 InstallProtocolInterface: 107A772C-D5E1-11D4-9A46-0090273FC14D 3D8AE940 InstallProtocolInterface: 6A7A5CFF-E8D9-4F70-BADA-75AB3025CE14 3D8AE8C0 Loading driver 11D92DFB-3CA9-4F93-BA2E-4780ED3E03B5 None of Tcg2Protocol/CcMeasurementProtocol is installed. InstallProtocolInterface: 5B1B31A1-9562-11D2-8E3F-00A0C969723B 3D8E0440 Loading driver at 0x0003D8B0000 EntryPoint=0x0003D8B2201 VirtioBlkDxe.efi InstallProtocolInterface: BC62157E-3E33-4FEC-9920-2D3B36D750DF 3D8DEF18 ProtectUefiImageCommon - 0x3D8E0440 - 0x000000003D8B0000 - 0x00000000000035C0 InstallProtocolInterface: 18A031AB-B443-4D1A-A5C0-0C09261E9F71 3D8B33E0 InstallProtocolInterface: 107A772C-D5E1-11D4-9A46-0090273FC14D 3D8B3440 InstallProtocolInterface: 6A7A5CFF-E8D9-4F70-BADA-75AB3025CE14 3D8B33C0 Loading driver FAB5D4F4-83C0-4AAF-8480-442D11DF6CEA None of Tcg2Protocol/CcMeasurementProtocol is installed. InstallProtocolInterface: 5B1B31A1-9562-11D2-8E3F-00A0C969723B 3D8DE0C0 Loading driver at 0x0003D888000 EntryPoint=0x0003D88A731 VirtioScsiDxe.efi InstallProtocolInterface: BC62157E-3E33-4FEC-9920-2D3B36D750DF 3D8DEA98 ProtectUefiImageCommon - 0x3D8DE0C0 - 0x000000003D888000 - 0x0000000000003A80 InstallProtocolInterface: 18A031AB-B443-4D1A-A5C0-0C09261E9F71 3D88B8A0 InstallProtocolInterface: 107A772C-D5E1-11D4-9A46-0090273FC14D 3D88B900 InstallProtocolInterface: 6A7A5CFF-E8D9-4F70-BADA-75AB3025CE14 3D88B880 Loading driver 58E26F0D-CBAC-4BBA-B70F-18221415665A None of Tcg2Protocol/CcMeasurementProtocol is installed. InstallProtocolInterface: 5B1B31A1-9562-11D2-8E3F-00A0C969723B 3D8E1040 Loading driver at 0x0003D885000 EntryPoint=0x0003D886CBF VirtioRngDxe.efi InstallProtocolInterface: BC62157E-3E33-4FEC-9920-2D3B36D750DF 3D8DE598 ProtectUefiImageCommon - 0x3D8E1040 - 0x000000003D885000 - 0x0000000000002F80 InstallProtocolInterface: 18A031AB-B443-4D1A-A5C0-0C09261E9F71 3D887DA0 InstallProtocolInterface: 107A772C-D5E1-11D4-9A46-0090273FC14D 3D887E00 InstallProtocolInterface: 6A7A5CFF-E8D9-4F70-BADA-75AB3025CE14 3D887D80 Loading driver 51CCF399-4FDF-4E55-A45B-E123F84D456A None of Tcg2Protocol/CcMeasurementProtocol is installed. InstallProtocolInterface: 5B1B31A1-9562-11D2-8E3F-00A0C969723B 3D8E19C0 Loading driver at 0x0003D87D000 EntryPoint=0x0003D87F6F9 ConPlatformDxe.efi InstallProtocolInterface: BC62157E-3E33-4FEC-9920-2D3B36D750DF 3D8E1918 ProtectUefiImageCommon - 0x3D8E19C0 - 0x000000003D87D000 - 0x0000000000003FC0 InstallProtocolInterface: 18A031AB-B443-4D1A-A5C0-0C09261E9F71 3D880D20 InstallProtocolInterface: 107A772C-D5E1-11D4-9A46-0090273FC14D 3D880E20 InstallProtocolInterface: 6A7A5CFF-E8D9-4F70-BADA-75AB3025CE14 3D880CF0 InstallProtocolInterface: 18A031AB-B443-4D1A-A5C0-0C09261E9F71 3D880CC0 InstallProtocolInterface: 107A772C-D5E1-11D4-9A46-0090273FC14D 3D880E20 InstallProtocolInterface: 6A7A5CFF-E8D9-4F70-BADA-75AB3025CE14 3D880CF0 Loading driver 408EDCEC-CF6D-477C-A5A8-B4844E3DE281 None of Tcg2Protocol/CcMeasurementProtocol is installed. InstallProtocolInterface: 5B1B31A1-9562-11D2-8E3F-00A0C969723B 3D8E4BC0 Loading driver at 0x0003D7FA000 EntryPoint=0x0003D7FF04F ConSplitterDxe.efi InstallProtocolInterface: BC62157E-3E33-4FEC-9920-2D3B36D750DF 3D8E4098 ProtectUefiImageCommon - 0x3D8E4BC0 - 0x000000003D7FA000 - 0x0000000000007500 InstallProtocolInterface: 18A031AB-B443-4D1A-A5C0-0C09261E9F71 3D8011E0 InstallProtocolInterface: 107A772C-D5E1-11D4-9A46-0090273FC14D 3D8012C0 InstallProtocolInterface: 6A7A5CFF-E8D9-4F70-BADA-75AB3025CE14 3D800AE0 InstallProtocolInterface: 18A031AB-B443-4D1A-A5C0-0C09261E9F71 3D801160 InstallProtocolInterface: 107A772C-D5E1-11D4-9A46-0090273FC14D 3D8012A0 InstallProtocolInterface: 6A7A5CFF-E8D9-4F70-BADA-75AB3025CE14 3D800AC0 InstallProtocolInterface: 18A031AB-B443-4D1A-A5C0-0C09261E9F71 3D8010E0 InstallProtocolInterface: 107A772C-D5E1-11D4-9A46-0090273FC14D 3D801280 InstallProtocolInterface: 6A7A5CFF-E8D9-4F70-BADA-75AB3025CE14 3D800AA0 InstallProtocolInterface: 18A031AB-B443-4D1A-A5C0-0C09261E9F71 3D801060 InstallProtocolInterface: 107A772C-D5E1-11D4-9A46-0090273FC14D 3D801260 InstallProtocolInterface: 6A7A5CFF-E8D9-4F70-BADA-75AB3025CE14 3D800A80 InstallProtocolInterface: 18A031AB-B443-4D1A-A5C0-0C09261E9F71 3D800FE0 InstallProtocolInterface: 107A772C-D5E1-11D4-9A46-0090273FC14D 3D801240 InstallProtocolInterface: 6A7A5CFF-E8D9-4F70-BADA-75AB3025CE14 3D800A60 InstallProtocolInterface: 387477C1-69C7-11D2-8E39-00A0C969723B 3D800E10 InstallProtocolInterface: DD9E7534-7762-4698-8C14-F58517A625AA 3D800E40 InstallProtocolInterface: 31878C87-0B75-11D5-9A4F-0090273FC14D 3D800EB0 InstallProtocolInterface: 8D59D32B-C655-4AE9-9B15-F25904992A43 3D800F08 InstallProtocolInterface: 387477C2-69C7-11D2-8E39-00A0C969723B 3D800CD0 InstallProtocolInterface: 387477C2-69C7-11D2-8E39-00A0C969723B 3D800BB0 Loading driver CCCB0C28-4B24-11D5-9A5A-0090273FC14D None of Tcg2Protocol/CcMeasurementProtocol is installed. InstallProtocolInterface: 5B1B31A1-9562-11D2-8E3F-00A0C969723B 3D8DD8C0 Loading driver at 0x0003D7F4000 EntryPoint=0x0003D7F6F5E GraphicsConsoleDxe.efi InstallProtocolInterface: BC62157E-3E33-4FEC-9920-2D3B36D750DF 3D8DD798 ProtectUefiImageCommon - 0x3D8DD8C0 - 0x000000003D7F4000 - 0x0000000000005E40 InstallProtocolInterface: 18A031AB-B443-4D1A-A5C0-0C09261E9F71 3D7F84E0 InstallProtocolInterface: 107A772C-D5E1-11D4-9A46-0090273FC14D 3D7F9C80 InstallProtocolInterface: 6A7A5CFF-E8D9-4F70-BADA-75AB3025CE14 3D7F84B0 Loading driver 9E863906-A40F-4875-977F-5B93FF237FC6 None of Tcg2Protocol/CcMeasurementProtocol is installed. InstallProtocolInterface: 5B1B31A1-9562-11D2-8E3F-00A0C969723B 3D8AF8C0 Loading driver at 0x0003D7E4000 EntryPoint=0x0003D7E98C7 TerminalDxe.efi InstallProtocolInterface: BC62157E-3E33-4FEC-9920-2D3B36D750DF 3D8AF798 ProtectUefiImageCommon - 0x3D8AF8C0 - 0x000000003D7E4000 - 0x0000000000007C40 InstallProtocolInterface: 18A031AB-B443-4D1A-A5C0-0C09261E9F71 3D7EBA40 InstallProtocolInterface: 107A772C-D5E1-11D4-9A46-0090273FC14D 3D7EBAA0 InstallProtocolInterface: 6A7A5CFF-E8D9-4F70-BADA-75AB3025CE14 3D7EB7D0 Loading driver 806040CA-DAD9-4978-A3B4-2D2AB0C8A48F None of Tcg2Protocol/CcMeasurementProtocol is installed. InstallProtocolInterface: 5B1B31A1-9562-11D2-8E3F-00A0C969723B 3D86B040 Loading driver at 0x0003D867000 EntryPoint=0x0003D86906B QemuKernelLoaderFsDxe.efi InstallProtocolInterface: BC62157E-3E33-4FEC-9920-2D3B36D750DF 3D86BE18 ProtectUefiImageCommon - 0x3D86B040 - 0x000000003D867000 - 0x0000000000003D40 Select Item: 0x0 FW CFG Signature: 0x554D4551 Select Item: 0x1 FW CFG Revision: 0x3 QemuFwCfg interface (DMA) is supported. Select Item: 0x17 Select Item: 0x8 Select Item: 0xB Select Item: 0x14 Error: Image at 0003D867000 start failed: Not Found Loading driver 6B38F7B4-AD98-40E9-9093-ACA2B5A253C4 None of Tcg2Protocol/CcMeasurementProtocol is installed. InstallProtocolInterface: 5B1B31A1-9562-11D2-8E3F-00A0C969723B 3D86B040 Loading driver at 0x0003D7EF000 EntryPoint=0x0003D7F1EC4 DiskIoDxe.efi InstallProtocolInterface: BC62157E-3E33-4FEC-9920-2D3B36D750DF 3D86BC98 ProtectUefiImageCommon - 0x3D86B040 - 0x000000003D7EF000 - 0x0000000000004800 InstallProtocolInterface: 18A031AB-B443-4D1A-A5C0-0C09261E9F71 3D7F35A0 InstallProtocolInterface: 107A772C-D5E1-11D4-9A46-0090273FC14D 3D7F36C0 InstallProtocolInterface: 6A7A5CFF-E8D9-4F70-BADA-75AB3025CE14 3D7F3580 Loading driver 1FA1F39E-FEFF-4AAE-BD7B-38A070A3B609 None of Tcg2Protocol/CcMeasurementProtocol is installed. InstallProtocolInterface: 5B1B31A1-9562-11D2-8E3F-00A0C969723B 3D86B5C0 Loading driver at 0x0003D7D6000 EntryPoint=0x0003D7DAA88 PartitionDxe.efi InstallProtocolInterface: BC62157E-3E33-4FEC-9920-2D3B36D750DF 3D86B818 ProtectUefiImageCommon - 0x3D86B5C0 - 0x000000003D7D6000 - 0x00000000000065C0 InstallProtocolInterface: 18A031AB-B443-4D1A-A5C0-0C09261E9F71 3D7DC360 InstallProtocolInterface: 107A772C-D5E1-11D4-9A46-0090273FC14D 3D7DC460 InstallProtocolInterface: 6A7A5CFF-E8D9-4F70-BADA-75AB3025CE14 3D7DC340 Loading driver CD3BAFB6-50FB-4FE8-8E4E-AB74D2C1A600 None of Tcg2Protocol/CcMeasurementProtocol is installed. InstallProtocolInterface: 5B1B31A1-9562-11D2-8E3F-00A0C969723B 3D884B40 Loading driver at 0x0003D868000 EntryPoint=0x0003D86930D EnglishDxe.efi InstallProtocolInterface: BC62157E-3E33-4FEC-9920-2D3B36D750DF 3D884098 ProtectUefiImageCommon - 0x3D884B40 - 0x000000003D868000 - 0x0000000000002240 InstallProtocolInterface: 1D85CD7F-F43D-11D2-9A0C-0090273FC14D 3D869DA0 InstallProtocolInterface: A4C751FC-23AE-4C3E-92E9-4964CF63F349 3D869D40 Loading driver 0167CCC4-D0F7-4F21-A3EF-9E64B7CDCE8B None of Tcg2Protocol/CcMeasurementProtocol is installed. InstallProtocolInterface: 5B1B31A1-9562-11D2-8E3F-00A0C969723B 3D884340 Loading driver at 0x0003D7D2000 EntryPoint=0x0003D7D4B29 ScsiBus.efi InstallProtocolInterface: BC62157E-3E33-4FEC-9920-2D3B36D750DF 3D884818 ProtectUefiImageCommon - 0x3D884340 - 0x000000003D7D2000 - 0x0000000000004000 InstallProtocolInterface: 18A031AB-B443-4D1A-A5C0-0C09261E9F71 3D7D5E00 InstallProtocolInterface: 107A772C-D5E1-11D4-9A46-0090273FC14D 3D7D5EA0 InstallProtocolInterface: 6A7A5CFF-E8D9-4F70-BADA-75AB3025CE14 3D7D5DE0 Loading driver 0A66E322-3740-4CCE-AD62-BD172CECCA35 None of Tcg2Protocol/CcMeasurementProtocol is installed. InstallProtocolInterface: 5B1B31A1-9562-11D2-8E3F-00A0C969723B 3D883CC0 Loading driver at 0x0003D7BE000 EntryPoint=0x0003D7C60DE ScsiDisk.efi InstallProtocolInterface: BC62157E-3E33-4FEC-9920-2D3B36D750DF 3D883898 ProtectUefiImageCommon - 0x3D883CC0 - 0x000000003D7BE000 - 0x0000000000009C80 InstallProtocolInterface: 18A031AB-B443-4D1A-A5C0-0C09261E9F71 3D7C7AE0 InstallProtocolInterface: 107A772C-D5E1-11D4-9A46-0090273FC14D 3D7C7B40 InstallProtocolInterface: 6A7A5CFF-E8D9-4F70-BADA-75AB3025CE14 3D7C7A60 Loading driver 021722D8-522B-4079-852A-FE44C2C13F49 None of Tcg2Protocol/CcMeasurementProtocol is installed. InstallProtocolInterface: 5B1B31A1-9562-11D2-8E3F-00A0C969723B 3D8833C0 Loading driver at 0x0003D7CE000 EntryPoint=0x0003D7CFD8E SataController.efi InstallProtocolInterface: BC62157E-3E33-4FEC-9920-2D3B36D750DF 3D883718 ProtectUefiImageCommon - 0x3D8833C0 - 0x000000003D7CE000 - 0x0000000000003240 InstallProtocolInterface: 18A031AB-B443-4D1A-A5C0-0C09261E9F71 3D7D1080 InstallProtocolInterface: 107A772C-D5E1-11D4-9A46-0090273FC14D 3D7D10E0 InstallProtocolInterface: 6A7A5CFF-E8D9-4F70-BADA-75AB3025CE14 3D7D1000 Loading driver 5E523CB4-D397-4986-87BD-A6DD8B22F455 None of Tcg2Protocol/CcMeasurementProtocol is installed. InstallProtocolInterface: 5B1B31A1-9562-11D2-8E3F-00A0C969723B 3D882140 Loading driver at 0x0003D7A6000 EntryPoint=0x0003D7AE6A9 AtaAtapiPassThruDxe.efi InstallProtocolInterface: BC62157E-3E33-4FEC-9920-2D3B36D750DF 3D882D98 ProtectUefiImageCommon - 0x3D882140 - 0x000000003D7A6000 - 0x000000000000B200 InstallProtocolInterface: 18A031AB-B443-4D1A-A5C0-0C09261E9F71 3D7B0D80 InstallProtocolInterface: 107A772C-D5E1-11D4-9A46-0090273FC14D 3D7B0DE0 InstallProtocolInterface: 6A7A5CFF-E8D9-4F70-BADA-75AB3025CE14 3D7B0D00 Loading driver 19DF145A-B1D4-453F-8507-38816676D7F6 None of Tcg2Protocol/CcMeasurementProtocol is installed. InstallProtocolInterface: 5B1B31A1-9562-11D2-8E3F-00A0C969723B 3D8825C0 Loading driver at 0x0003D7B7000 EntryPoint=0x0003D7BB3DC AtaBusDxe.efi InstallProtocolInterface: BC62157E-3E33-4FEC-9920-2D3B36D750DF 3D881F98 ProtectUefiImageCommon - 0x3D8825C0 - 0x000000003D7B7000 - 0x0000000000006580 InstallProtocolInterface: 18A031AB-B443-4D1A-A5C0-0C09261E9F71 3D7BD100 InstallProtocolInterface: 107A772C-D5E1-11D4-9A46-0090273FC14D 3D7BD1F0 InstallProtocolInterface: 6A7A5CFF-E8D9-4F70-BADA-75AB3025CE14 3D7BD1D0 Loading driver 5BE3BDF4-53CF-46A3-A6A9-73C34A6E5EE3 None of Tcg2Protocol/CcMeasurementProtocol is installed. InstallProtocolInterface: 5B1B31A1-9562-11D2-8E3F-00A0C969723B 3D881140 Loading driver at 0x0003D792000 EntryPoint=0x0003D799279 NvmExpressDxe.efi InstallProtocolInterface: BC62157E-3E33-4FEC-9920-2D3B36D750DF 3D881398 ProtectUefiImageCommon - 0x3D881140 - 0x000000003D792000 - 0x0000000000009B00 InstallProtocolInterface: 18A031AB-B443-4D1A-A5C0-0C09261E9F71 3D79B940 InstallProtocolInterface: 107A772C-D5E1-11D4-9A46-0090273FC14D 3D79B9A0 InstallProtocolInterface: 6A7A5CFF-E8D9-4F70-BADA-75AB3025CE14 3D79B870 InstallProtocolInterface: 5C198761-16A8-4E69-972C-89D67954F81D 3D79B7E0 Loading driver 864E1CA8-85EB-4D63-9DCC-6E0FC90FFD55 None of Tcg2Protocol/CcMeasurementProtocol is installed. InstallProtocolInterface: 5B1B31A1-9562-11D2-8E3F-00A0C969723B 3D867040 Loading driver at 0x0003D7CA000 EntryPoint=0x0003D7CBD02 SioBusDxe.efi InstallProtocolInterface: BC62157E-3E33-4FEC-9920-2D3B36D750DF 3D867D18 ProtectUefiImageCommon - 0x3D867040 - 0x000000003D7CA000 - 0x0000000000003180 InstallProtocolInterface: 18A031AB-B443-4D1A-A5C0-0C09261E9F71 3D7CCF20 InstallProtocolInterface: 107A772C-D5E1-11D4-9A46-0090273FC14D 3D7CD040 InstallProtocolInterface: 6A7A5CFF-E8D9-4F70-BADA-75AB3025CE14 3D7CCF00 Loading driver E2775B47-D453-4EE3-ADA7-391A1B05AC17 None of Tcg2Protocol/CcMeasurementProtocol is installed. InstallProtocolInterface: 5B1B31A1-9562-11D2-8E3F-00A0C969723B 3D8679C0 Loading driver at 0x0003D79F000 EntryPoint=0x0003D7A35D0 PciSioSerialDxe.efi InstallProtocolInterface: BC62157E-3E33-4FEC-9920-2D3B36D750DF 3D867898 ProtectUefiImageCommon - 0x3D8679C0 - 0x000000003D79F000 - 0x0000000000006100 InstallProtocolInterface: 18A031AB-B443-4D1A-A5C0-0C09261E9F71 3D7A4F40 InstallProtocolInterface: 107A772C-D5E1-11D4-9A46-0090273FC14D 3D7A4FA0 InstallProtocolInterface: 6A7A5CFF-E8D9-4F70-BADA-75AB3025CE14 3D7A4DB0 Loading driver C4D1F932-821F-4744-BF06-6D30F7730F8D None of Tcg2Protocol/CcMeasurementProtocol is installed. InstallProtocolInterface: 5B1B31A1-9562-11D2-8E3F-00A0C969723B 3D866040 Loading driver at 0x0003D78C000 EntryPoint=0x0003D78FC07 Ps2KeyboardDxe.efi InstallProtocolInterface: BC62157E-3E33-4FEC-9920-2D3B36D750DF 3D867598 ProtectUefiImageCommon - 0x3D866040 - 0x000000003D78C000 - 0x0000000000005AC0 InstallProtocolInterface: 18A031AB-B443-4D1A-A5C0-0C09261E9F71 3D7918E0 InstallProtocolInterface: 107A772C-D5E1-11D4-9A46-0090273FC14D 3D791940 InstallProtocolInterface: 6A7A5CFF-E8D9-4F70-BADA-75AB3025CE14 3D791870 Loading driver B8E62775-BB0A-43F0-A843-5BE8B14F8CCD None of Tcg2Protocol/CcMeasurementProtocol is installed. InstallProtocolInterface: 5B1B31A1-9562-11D2-8E3F-00A0C969723B 3D866440 Loading driver at 0x0003D7E1000 EntryPoint=0x0003D7E25A5 BootGraphicsResourceTableDxe.efi InstallProtocolInterface: BC62157E-3E33-4FEC-9920-2D3B36D750DF 3D866698 ProtectUefiImageCommon - 0x3D866440 - 0x000000003D7E1000 - 0x0000000000002900 InstallProtocolInterface: CDEA2BD3-FC25-4C1C-B97C-B31186064990 3D7E36B0 InstallProtocolInterface: 4B5DC1DF-1EAA-48B2-A7E9-EAC489A00B5C 3D7E3730 Loading driver 961578FE-B6B7-44C3-AF35-6BC705CD2B1F None of Tcg2Protocol/CcMeasurementProtocol is installed. InstallProtocolInterface: 5B1B31A1-9562-11D2-8E3F-00A0C969723B 3D8650C0 Loading driver at 0x0003D778000 EntryPoint=0x0003D77FD7C Fat.efi InstallProtocolInterface: BC62157E-3E33-4FEC-9920-2D3B36D750DF 3D865A98 ProtectUefiImageCommon - 0x3D8650C0 - 0x000000003D778000 - 0x0000000000009F40 InstallProtocolInterface: 18A031AB-B443-4D1A-A5C0-0C09261E9F71 3D781DA0 InstallProtocolInterface: 107A772C-D5E1-11D4-9A46-0090273FC14D 3D781E00 InstallProtocolInterface: 6A7A5CFF-E8D9-4F70-BADA-75AB3025CE14 3D781BD0 Loading driver 905F13B0-8F91-4B0A-BD76-E1E78F9422E4 None of Tcg2Protocol/CcMeasurementProtocol is installed. InstallProtocolInterface: 5B1B31A1-9562-11D2-8E3F-00A0C969723B 3D8653C0 Loading driver at 0x0003D771000 EntryPoint=0x0003D775B8A UdfDxe.efi InstallProtocolInterface: BC62157E-3E33-4FEC-9920-2D3B36D750DF 3D865798 ProtectUefiImageCommon - 0x3D8653C0 - 0x000000003D771000 - 0x0000000000006480 InstallProtocolInterface: 18A031AB-B443-4D1A-A5C0-0C09261E9F71 3D7771E0 InstallProtocolInterface: 107A772C-D5E1-11D4-9A46-0090273FC14D 3D777340 InstallProtocolInterface: 6A7A5CFF-E8D9-4F70-BADA-75AB3025CE14 3D7771C0 Loading driver 7BD9DDF7-8B83-488E-AEC9-24C78610289C None of Tcg2Protocol/CcMeasurementProtocol is installed. InstallProtocolInterface: 5B1B31A1-9562-11D2-8E3F-00A0C969723B 3D7EECC0 Loading driver at 0x0003D767000 EntryPoint=0x0003D76E441 VirtioFsDxe.efi InstallProtocolInterface: BC62157E-3E33-4FEC-9920-2D3B36D750DF 3D7EE818 ProtectUefiImageCommon - 0x3D7EECC0 - 0x000000003D767000 - 0x0000000000009740 InstallProtocolInterface: 18A031AB-B443-4D1A-A5C0-0C09261E9F71 3D770620 InstallProtocolInterface: 6A7A5CFF-E8D9-4F70-BADA-75AB3025CE14 3D770600 Loading driver A2F436EA-A127-4EF8-957C-8048606FF670 None of Tcg2Protocol/CcMeasurementProtocol is installed. InstallProtocolInterface: 5B1B31A1-9562-11D2-8E3F-00A0C969723B 3D7EE3C0 Loading driver at 0x0003D75F000 EntryPoint=0x0003D764032 SnpDxe.efi InstallProtocolInterface: BC62157E-3E33-4FEC-9920-2D3B36D750DF 3D7EE218 ProtectUefiImageCommon - 0x3D7EE3C0 - 0x000000003D75F000 - 0x0000000000007240 InstallProtocolInterface: 18A031AB-B443-4D1A-A5C0-0C09261E9F71 3D766040 InstallProtocolInterface: 107A772C-D5E1-11D4-9A46-0090273FC14D 3D7660A0 InstallProtocolInterface: 6A7A5CFF-E8D9-4F70-BADA-75AB3025CE14 3D766010 Loading driver E4F61863-FE2C-4B56-A8F4-08519BC439DF None of Tcg2Protocol/CcMeasurementProtocol is installed. InstallProtocolInterface: 5B1B31A1-9562-11D2-8E3F-00A0C969723B 3D7ED0C0 Loading driver at 0x0003D758000 EntryPoint=0x0003D75C604 VlanConfigDxe.efi InstallProtocolInterface: BC62157E-3E33-4FEC-9920-2D3B36D750DF 3D7ED918 ProtectUefiImageCommon - 0x3D7ED0C0 - 0x000000003D758000 - 0x0000000000006CC0 InstallProtocolInterface: 18A031AB-B443-4D1A-A5C0-0C09261E9F71 3D75E380 InstallProtocolInterface: 107A772C-D5E1-11D4-9A46-0090273FC14D 3D75EB40 InstallProtocolInterface: 6A7A5CFF-E8D9-4F70-BADA-75AB3025CE14 3D75E360 Loading driver 025BBFC7-E6A9-4B8B-82AD-6815A1AEAF4A None of Tcg2Protocol/CcMeasurementProtocol is installed. InstallProtocolInterface: 5B1B31A1-9562-11D2-8E3F-00A0C969723B 3D7ED3C0 Loading driver at 0x0003D742000 EntryPoint=0x0003D7496A7 MnpDxe.efi InstallProtocolInterface: BC62157E-3E33-4FEC-9920-2D3B36D750DF 3D7ED718 ProtectUefiImageCommon - 0x3D7ED3C0 - 0x000000003D742000 - 0x000000000000A4C0 InstallProtocolInterface: 18A031AB-B443-4D1A-A5C0-0C09261E9F71 3D74C2C0 InstallProtocolInterface: 107A772C-D5E1-11D4-9A46-0090273FC14D 3D74C340 InstallProtocolInterface: 6A7A5CFF-E8D9-4F70-BADA-75AB3025CE14 3D74C2F0 Loading driver 529D3F93-E8E9-4E73-B1E1-BDF6A9D50113 None of Tcg2Protocol/CcMeasurementProtocol is installed. InstallProtocolInterface: 5B1B31A1-9562-11D2-8E3F-00A0C969723B 3D7EC0C0 Loading driver at 0x0003D752000 EntryPoint=0x0003D75616E ArpDxe.efi InstallProtocolInterface: BC62157E-3E33-4FEC-9920-2D3B36D750DF 3D7EC898 ProtectUefiImageCommon - 0x3D7EC0C0 - 0x000000003D752000 - 0x0000000000005E40 InstallProtocolInterface: 18A031AB-B443-4D1A-A5C0-0C09261E9F71 3D757C40 InstallProtocolInterface: 107A772C-D5E1-11D4-9A46-0090273FC14D 3D757D00 InstallProtocolInterface: 6A7A5CFF-E8D9-4F70-BADA-75AB3025CE14 3D757BA0 Loading driver 94734718-0BBC-47FB-96A5-EE7A5AE6A2AD None of Tcg2Protocol/CcMeasurementProtocol is installed. InstallProtocolInterface: 5B1B31A1-9562-11D2-8E3F-00A0C969723B 3D7EC540 Loading driver at 0x0003D72C000 EntryPoint=0x0003D73353B Dhcp4Dxe.efi InstallProtocolInterface: BC62157E-3E33-4FEC-9920-2D3B36D750DF 3D7E0F98 ProtectUefiImageCommon - 0x3D7EC540 - 0x000000003D72C000 - 0x000000000000A380 InstallProtocolInterface: 18A031AB-B443-4D1A-A5C0-0C09261E9F71 3D7360C0 InstallProtocolInterface: 107A772C-D5E1-11D4-9A46-0090273FC14D 3D7361C0 InstallProtocolInterface: 6A7A5CFF-E8D9-4F70-BADA-75AB3025CE14 3D736120 Loading driver 9FB1A1F3-3B71-4324-B39A-745CBB015FFF None of Tcg2Protocol/CcMeasurementProtocol is installed. InstallProtocolInterface: 5B1B31A1-9562-11D2-8E3F-00A0C969723B 3D7E01C0 Loading driver at 0x0003D704000 EntryPoint=0x0003D71365D Ip4Dxe.efi InstallProtocolInterface: BC62157E-3E33-4FEC-9920-2D3B36D750DF 3D7E0A18 ProtectUefiImageCommon - 0x3D7E01C0 - 0x000000003D704000 - 0x0000000000013E80 Select Item: 0x0 FW CFG Signature: 0x554D4551 Select Item: 0x1 FW CFG Revision: 0x3 QemuFwCfg interface (DMA) is supported. Select Item: 0x19 InstallProtocolInterface: 18A031AB-B443-4D1A-A5C0-0C09261E9F71 3D717A60 InstallProtocolInterface: 107A772C-D5E1-11D4-9A46-0090273FC14D 3D7179C0 InstallProtocolInterface: 6A7A5CFF-E8D9-4F70-BADA-75AB3025CE14 3D717970 Loading driver 6D6963AB-906D-4A65-A7CA-BD40E5D6AF2B None of Tcg2Protocol/CcMeasurementProtocol is installed. InstallProtocolInterface: 5B1B31A1-9562-11D2-8E3F-00A0C969723B 3D7DFB40 Loading driver at 0x0003D739000 EntryPoint=0x0003D73F5F1 Udp4Dxe.efi InstallProtocolInterface: BC62157E-3E33-4FEC-9920-2D3B36D750DF 3D7DFA98 ProtectUefiImageCommon - 0x3D7DFB40 - 0x000000003D739000 - 0x0000000000008900 InstallProtocolInterface: 18A031AB-B443-4D1A-A5C0-0C09261E9F71 3D7416C0 InstallProtocolInterface: 107A772C-D5E1-11D4-9A46-0090273FC14D 3D7417A0 InstallProtocolInterface: 6A7A5CFF-E8D9-4F70-BADA-75AB3025CE14 3D741730 Loading driver DC3641B8-2FA8-4ED3-BC1F-F9962A03454B None of Tcg2Protocol/CcMeasurementProtocol is installed. InstallProtocolInterface: 5B1B31A1-9562-11D2-8E3F-00A0C969723B 3D7DF240 Loading driver at 0x0003D722000 EntryPoint=0x0003D728E8A Mtftp4Dxe.efi InstallProtocolInterface: BC62157E-3E33-4FEC-9920-2D3B36D750DF 3D7DF718 ProtectUefiImageCommon - 0x3D7DF240 - 0x000000003D722000 - 0x00000000000091C0 InstallProtocolInterface: 18A031AB-B443-4D1A-A5C0-0C09261E9F71 3D72AF80 InstallProtocolInterface: 107A772C-D5E1-11D4-9A46-0090273FC14D 3D72B000 InstallProtocolInterface: 6A7A5CFF-E8D9-4F70-BADA-75AB3025CE14 3D72AFB0 Loading driver 95E3669D-34BE-4775-A651-7EA41B69D89E None of Tcg2Protocol/CcMeasurementProtocol is installed. InstallProtocolInterface: 5B1B31A1-9562-11D2-8E3F-00A0C969723B 3D7DECC0 Loading driver at 0x0003D6EE000 EntryPoint=0x0003D6F69BF Dhcp6Dxe.efi InstallProtocolInterface: BC62157E-3E33-4FEC-9920-2D3B36D750DF 3D7DEB18 ProtectUefiImageCommon - 0x3D7DECC0 - 0x000000003D6EE000 - 0x000000000000AC40 InstallProtocolInterface: 18A031AB-B443-4D1A-A5C0-0C09261E9F71 3D6F89E0 InstallProtocolInterface: 107A772C-D5E1-11D4-9A46-0090273FC14D 3D6F8920 InstallProtocolInterface: 6A7A5CFF-E8D9-4F70-BADA-75AB3025CE14 3D6F8880 Loading driver 5BEDB5CC-D830-4EB2-8742-2D4CC9B54F2C None of Tcg2Protocol/CcMeasurementProtocol is installed. InstallProtocolInterface: 5B1B31A1-9562-11D2-8E3F-00A0C969723B 3D7DE3C0 Loading driver at 0x0003D6B4000 EntryPoint=0x0003D6C4ECF Ip6Dxe.efi InstallProtocolInterface: BC62157E-3E33-4FEC-9920-2D3B36D750DF 3D7DDF18 ProtectUefiImageCommon - 0x3D7DE3C0 - 0x000000003D6B4000 - 0x000000000001C7C0 Select Item: 0x0 FW CFG Signature: 0x554D4551 Select Item: 0x1 FW CFG Revision: 0x3 QemuFwCfg interface (DMA) is supported. Select Item: 0x19 InstallProtocolInterface: 18A031AB-B443-4D1A-A5C0-0C09261E9F71 3D6CF0E0 InstallProtocolInterface: 107A772C-D5E1-11D4-9A46-0090273FC14D 3D6CF060 InstallProtocolInterface: 6A7A5CFF-E8D9-4F70-BADA-75AB3025CE14 3D6CF010 Loading driver D912C7BC-F098-4367-92BA-E911083C7B0E None of Tcg2Protocol/CcMeasurementProtocol is installed. InstallProtocolInterface: 5B1B31A1-9562-11D2-8E3F-00A0C969723B 3D7DD1C0 Loading driver at 0x0003D719000 EntryPoint=0x0003D71F5C5 Udp6Dxe.efi InstallProtocolInterface: BC62157E-3E33-4FEC-9920-2D3B36D750DF 3D7DDA18 ProtectUefiImageCommon - 0x3D7DD1C0 - 0x000000003D719000 - 0x0000000000008A00 InstallProtocolInterface: 18A031AB-B443-4D1A-A5C0-0C09261E9F71 3D7217E0 InstallProtocolInterface: 107A772C-D5E1-11D4-9A46-0090273FC14D 3D721780 InstallProtocolInterface: 6A7A5CFF-E8D9-4F70-BADA-75AB3025CE14 3D721740 Loading driver 99F03B99-98D8-49DD-A8D3-3219D0FFE41E None of Tcg2Protocol/CcMeasurementProtocol is installed. InstallProtocolInterface: 5B1B31A1-9562-11D2-8E3F-00A0C969723B 3D7C9040 Loading driver at 0x0003D6FA000 EntryPoint=0x0003D7016FA Mtftp6Dxe.efi InstallProtocolInterface: BC62157E-3E33-4FEC-9920-2D3B36D750DF 3D7C9E98 ProtectUefiImageCommon - 0x3D7C9040 - 0x000000003D6FA000 - 0x0000000000009A40 InstallProtocolInterface: 18A031AB-B443-4D1A-A5C0-0C09261E9F71 3D7038A0 InstallProtocolInterface: 107A772C-D5E1-11D4-9A46-0090273FC14D 3D703800 InstallProtocolInterface: 6A7A5CFF-E8D9-4F70-BADA-75AB3025CE14 3D7037C0 Loading driver 1A7E4468-2F55-4A56-903C-01265EB7622B None of Tcg2Protocol/CcMeasurementProtocol is installed. InstallProtocolInterface: 5B1B31A1-9562-11D2-8E3F-00A0C969723B 3D7C99C0 Loading driver at 0x0003D6A1000 EntryPoint=0x0003D6AB4F8 TcpDxe.efi InstallProtocolInterface: BC62157E-3E33-4FEC-9920-2D3B36D750DF 3D7C9918 ProtectUefiImageCommon - 0x3D7C99C0 - 0x000000003D6A1000 - 0x0000000000012140 InstallProtocolInterface: 18A031AB-B443-4D1A-A5C0-0C09261E9F71 3D6B2D20 InstallProtocolInterface: 107A772C-D5E1-11D4-9A46-0090273FC14D 3D6B2BE0 InstallProtocolInterface: 6A7A5CFF-E8D9-4F70-BADA-75AB3025CE14 3D6B2BA0 InstallProtocolInterface: 18A031AB-B443-4D1A-A5C0-0C09261E9F71 3D6B2CE0 InstallProtocolInterface: 107A772C-D5E1-11D4-9A46-0090273FC14D 3D6B2BE0 InstallProtocolInterface: 6A7A5CFF-E8D9-4F70-BADA-75AB3025CE14 3D6B2BA0 Loading driver B95E9FDA-26DE-48D2-8807-1F9107AC5E3A None of Tcg2Protocol/CcMeasurementProtocol is installed. InstallProtocolInterface: 5B1B31A1-9562-11D2-8E3F-00A0C969723B 3D7C80C0 Loading driver at 0x0003D68F000 EntryPoint=0x0003D69C4CF UefiPxeBcDxe.efi InstallProtocolInterface: BC62157E-3E33-4FEC-9920-2D3B36D750DF 3D7C8A18 ProtectUefiImageCommon - 0x3D7C80C0 - 0x000000003D68F000 - 0x00000000000110C0 Select Item: 0x0 FW CFG Signature: 0x554D4551 Select Item: 0x1 FW CFG Revision: 0x3 QemuFwCfg interface (DMA) is supported. Select Item: 0x19 Select Item: 0x19 InstallProtocolInterface: 18A031AB-B443-4D1A-A5C0-0C09261E9F71 3D69FE40 InstallProtocolInterface: 107A772C-D5E1-11D4-9A46-0090273FC14D 3D69FD60 InstallProtocolInterface: 6A7A5CFF-E8D9-4F70-BADA-75AB3025CE14 3D69FE10 InstallProtocolInterface: 18A031AB-B443-4D1A-A5C0-0C09261E9F71 3D69FDE0 InstallProtocolInterface: 107A772C-D5E1-11D4-9A46-0090273FC14D 3D69FD60 InstallProtocolInterface: 6A7A5CFF-E8D9-4F70-BADA-75AB3025CE14 3D69FE10 Loading driver 3ACEB0C0-3C72-11E4-9A56-74D435052646 None of Tcg2Protocol/CcMeasurementProtocol is installed. InstallProtocolInterface: 5B1B31A1-9562-11D2-8E3F-00A0C969723B 3D7B6040 Loading driver at 0x0003D549000 EntryPoint=0x0003D5AD4DA TlsDxe.efi InstallProtocolInterface: BC62157E-3E33-4FEC-9920-2D3B36D750DF 3D7B6D18 ProtectUefiImageCommon - 0x3D7B6040 - 0x000000003D549000 - 0x00000000000A2D40 InstallProtocolInterface: 952CB795-FF36-48CF-A249-4DF486D6AB8D 3D7B6EA0 Loading driver B219E140-DFFC-11E3-B956-0022681E6906 None of Tcg2Protocol/CcMeasurementProtocol is installed. InstallProtocolInterface: 5B1B31A1-9562-11D2-8E3F-00A0C969723B 3D788340 Loading driver at 0x0003D6D6000 EntryPoint=0x0003D6DF9BF DnsDxe.efi InstallProtocolInterface: BC62157E-3E33-4FEC-9920-2D3B36D750DF 3D7C8418 ProtectUefiImageCommon - 0x3D788340 - 0x000000003D6D6000 - 0x000000000000BE00 InstallProtocolInterface: 18A031AB-B443-4D1A-A5C0-0C09261E9F71 3D6E1AE0 InstallProtocolInterface: 107A772C-D5E1-11D4-9A46-0090273FC14D 3D6E1C80 InstallProtocolInterface: 6A7A5CFF-E8D9-4F70-BADA-75AB3025CE14 3D6E1C40 InstallProtocolInterface: 18A031AB-B443-4D1A-A5C0-0C09261E9F71 3D6E1AA0 InstallProtocolInterface: 107A772C-D5E1-11D4-9A46-0090273FC14D 3D6E1C80 InstallProtocolInterface: 6A7A5CFF-E8D9-4F70-BADA-75AB3025CE14 3D6E1C40 Loading driver 2366C20F-E15A-11E3-8BF1-E4115B28BC50 None of Tcg2Protocol/CcMeasurementProtocol is installed. InstallProtocolInterface: 5B1B31A1-9562-11D2-8E3F-00A0C969723B 3D786440 Loading driver at 0x0003D673000 EntryPoint=0x0003D67CDFC HttpDxe.efi InstallProtocolInterface: BC62157E-3E33-4FEC-9920-2D3B36D750DF 3D786918 ProtectUefiImageCommon - 0x3D786440 - 0x000000003D673000 - 0x000000000000D880 InstallProtocolInterface: 18A031AB-B443-4D1A-A5C0-0C09261E9F71 3D680540 InstallProtocolInterface: 107A772C-D5E1-11D4-9A46-0090273FC14D 3D680510 InstallProtocolInterface: 6A7A5CFF-E8D9-4F70-BADA-75AB3025CE14 3D680740 InstallProtocolInterface: 18A031AB-B443-4D1A-A5C0-0C09261E9F71 3D6804E0 InstallProtocolInterface: 107A772C-D5E1-11D4-9A46-0090273FC14D 3D680510 InstallProtocolInterface: 6A7A5CFF-E8D9-4F70-BADA-75AB3025CE14 3D680740 Loading driver ECEBCB00-D9C8-11E4-AF3D-8CDCD426C973 None of Tcg2Protocol/CcMeasurementProtocol is installed. InstallProtocolInterface: 5B1B31A1-9562-11D2-8E3F-00A0C969723B 3D7850C0 Loading driver at 0x0003D64F000 EntryPoint=0x0003D6594D7 HttpBootDxe.efi InstallProtocolInterface: BC62157E-3E33-4FEC-9920-2D3B36D750DF 3D785E18 ProtectUefiImageCommon - 0x3D7850C0 - 0x000000003D64F000 - 0x0000000000011580 InstallProtocolInterface: 18A031AB-B443-4D1A-A5C0-0C09261E9F71 3D65FD80 InstallProtocolInterface: 107A772C-D5E1-11D4-9A46-0090273FC14D 3D65FD50 InstallProtocolInterface: 6A7A5CFF-E8D9-4F70-BADA-75AB3025CE14 3D65FF00 InstallProtocolInterface: 18A031AB-B443-4D1A-A5C0-0C09261E9F71 3D65FD20 InstallProtocolInterface: 107A772C-D5E1-11D4-9A46-0090273FC14D 3D65FD50 InstallProtocolInterface: 6A7A5CFF-E8D9-4F70-BADA-75AB3025CE14 3D65FF00 Loading driver 86CDDF93-4872-4597-8AF9-A35AE4D3725F None of Tcg2Protocol/CcMeasurementProtocol is installed. InstallProtocolInterface: 5B1B31A1-9562-11D2-8E3F-00A0C969723B 3D784040 Loading driver at 0x0003D611000 EntryPoint=0x0003D62302A IScsiDxe.efi InstallProtocolInterface: BC62157E-3E33-4FEC-9920-2D3B36D750DF 3D785398 ProtectUefiImageCommon - 0x3D784040 - 0x000000003D611000 - 0x000000000001E880 InstallProtocolInterface: 18A031AB-B443-4D1A-A5C0-0C09261E9F71 3D62F560 InstallProtocolInterface: 107A772C-D5E1-11D4-9A46-0090273FC14D 3D62DC00 InstallProtocolInterface: 6A7A5CFF-E8D9-4F70-BADA-75AB3025CE14 3D62DB70 InstallProtocolInterface: 18A031AB-B443-4D1A-A5C0-0C09261E9F71 3D62F520 InstallProtocolInterface: 107A772C-D5E1-11D4-9A46-0090273FC14D 3D62DC00 InstallProtocolInterface: 6A7A5CFF-E8D9-4F70-BADA-75AB3025CE14 3D62DB70 InstallProtocolInterface: 59324945-EC44-4C0D-B1CD-9DB139DF070C 3D62DB00 InstallProtocolInterface: 09576E91-6D3F-11D2-8E39-00A0C969723B 3D62F4A0 InstallProtocolInterface: 330D4706-F2A0-4E4F-A369-B66FA8D54385 3D784BA8 InstallProtocolInterface: 7671D9D0-53DB-4173-AA69-2327F21F0BC7 3D62F500 Loading driver A92CDB4B-82F1-4E0B-A516-8A655D371524 None of Tcg2Protocol/CcMeasurementProtocol is installed. InstallProtocolInterface: 5B1B31A1-9562-11D2-8E3F-00A0C969723B 3D7518C0 Loading driver at 0x0003D689000 EntryPoint=0x0003D68CA9F VirtioNetDxe.efi InstallProtocolInterface: BC62157E-3E33-4FEC-9920-2D3B36D750DF 3D751418 ProtectUefiImageCommon - 0x3D7518C0 - 0x000000003D689000 - 0x00000000000053C0 InstallProtocolInterface: 18A031AB-B443-4D1A-A5C0-0C09261E9F71 3D68E200 InstallProtocolInterface: 107A772C-D5E1-11D4-9A46-0090273FC14D 3D68E260 InstallProtocolInterface: 6A7A5CFF-E8D9-4F70-BADA-75AB3025CE14 3D68E180 Loading driver 2FB92EFA-2EE0-4BAE-9EB6-7464125E1EF7 None of Tcg2Protocol/CcMeasurementProtocol is installed. InstallProtocolInterface: 5B1B31A1-9562-11D2-8E3F-00A0C969723B 3D783040 Loading driver at 0x0003D682000 EntryPoint=0x0003D6870DF UhciDxe.efi InstallProtocolInterface: BC62157E-3E33-4FEC-9920-2D3B36D750DF 3D751398 ProtectUefiImageCommon - 0x3D783040 - 0x000000003D682000 - 0x0000000000006DC0 InstallProtocolInterface: 18A031AB-B443-4D1A-A5C0-0C09261E9F71 3D688BC0 InstallProtocolInterface: 107A772C-D5E1-11D4-9A46-0090273FC14D 3D688C40 InstallProtocolInterface: 6A7A5CFF-E8D9-4F70-BADA-75AB3025CE14 3D688C20 Loading driver BDFE430E-8F2A-4DB0-9991-6F856594777E None of Tcg2Protocol/CcMeasurementProtocol is installed. InstallProtocolInterface: 5B1B31A1-9562-11D2-8E3F-00A0C969723B 3D783540 Loading driver at 0x0003D661000 EntryPoint=0x0003D6672CA EhciDxe.efi InstallProtocolInterface: BC62157E-3E33-4FEC-9920-2D3B36D750DF 3D783A18 ProtectUefiImageCommon - 0x3D783540 - 0x000000003D661000 - 0x0000000000008800 InstallProtocolInterface: 18A031AB-B443-4D1A-A5C0-0C09261E9F71 3D669660 InstallProtocolInterface: 107A772C-D5E1-11D4-9A46-0090273FC14D 3D6696C0 InstallProtocolInterface: 6A7A5CFF-E8D9-4F70-BADA-75AB3025CE14 3D6695F0 Loading driver B7F50E91-A759-412C-ADE4-DCD03E7F7C28 None of Tcg2Protocol/CcMeasurementProtocol is installed. InstallProtocolInterface: 5B1B31A1-9562-11D2-8E3F-00A0C969723B 3D7837C0 Loading driver at 0x0003D635000 EntryPoint=0x0003D63EA6C XhciDxe.efi InstallProtocolInterface: BC62157E-3E33-4FEC-9920-2D3B36D750DF 3D782C18 ProtectUefiImageCommon - 0x3D7837C0 - 0x000000003D635000 - 0x000000000000CE00 InstallProtocolInterface: 18A031AB-B443-4D1A-A5C0-0C09261E9F71 3D641B80 InstallProtocolInterface: 107A772C-D5E1-11D4-9A46-0090273FC14D 3D641C80 InstallProtocolInterface: 6A7A5CFF-E8D9-4F70-BADA-75AB3025CE14 3D641C60 Loading driver 240612B7-A063-11D4-9A3A-0090273FC14D None of Tcg2Protocol/CcMeasurementProtocol is installed. InstallProtocolInterface: 5B1B31A1-9562-11D2-8E3F-00A0C969723B 3D782540 Loading driver at 0x0003D607000 EntryPoint=0x0003D60D8B0 UsbBusDxe.efi InstallProtocolInterface: BC62157E-3E33-4FEC-9920-2D3B36D750DF 3D782418 ProtectUefiImageCommon - 0x3D782540 - 0x000000003D607000 - 0x00000000000095C0 InstallProtocolInterface: 18A031AB-B443-4D1A-A5C0-0C09261E9F71 3D610320 InstallProtocolInterface: 107A772C-D5E1-11D4-9A46-0090273FC14D 3D610280 InstallProtocolInterface: 6A7A5CFF-E8D9-4F70-BADA-75AB3025CE14 3D610220 Loading driver 2D2E62CF-9ECF-43B7-8219-94E7FC713DFE None of Tcg2Protocol/CcMeasurementProtocol is installed. InstallProtocolInterface: 5B1B31A1-9562-11D2-8E3F-00A0C969723B 3D738D40 Loading driver at 0x0003D66C000 EntryPoint=0x0003D67003E UsbKbDxe.efi InstallProtocolInterface: BC62157E-3E33-4FEC-9920-2D3B36D750DF 3D738C18 ProtectUefiImageCommon - 0x3D738D40 - 0x000000003D66C000 - 0x0000000000006300 InstallProtocolInterface: 18A031AB-B443-4D1A-A5C0-0C09261E9F71 3D6719A0 InstallProtocolInterface: 107A772C-D5E1-11D4-9A46-0090273FC14D 3D672160 InstallProtocolInterface: 6A7A5CFF-E8D9-4F70-BADA-75AB3025CE14 3D672140 Loading driver 9FB4B4A7-42C0-4BCD-8540-9BCC6711F83E None of Tcg2Protocol/CcMeasurementProtocol is installed. InstallProtocolInterface: 5B1B31A1-9562-11D2-8E3F-00A0C969723B 3D7382C0 Loading driver at 0x0003D649000 EntryPoint=0x0003D64CBEE UsbMassStorageDxe.efi InstallProtocolInterface: BC62157E-3E33-4FEC-9920-2D3B36D750DF 3D738A98 ProtectUefiImageCommon - 0x3D7382C0 - 0x000000003D649000 - 0x0000000000005A00 InstallProtocolInterface: 18A031AB-B443-4D1A-A5C0-0C09261E9F71 3D64E7A0 InstallProtocolInterface: 107A772C-D5E1-11D4-9A46-0090273FC14D 3D64E880 InstallProtocolInterface: 6A7A5CFF-E8D9-4F70-BADA-75AB3025CE14 3D64E770 Loading driver E3752948-B9A1-4770-90C4-DF41C38986BE None of Tcg2Protocol/CcMeasurementProtocol is installed. InstallProtocolInterface: 5B1B31A1-9562-11D2-8E3F-00A0C969723B 3D737D40 Loading driver at 0x0003D642000 EntryPoint=0x0003D645F30 QemuVideoDxe.efi InstallProtocolInterface: BC62157E-3E33-4FEC-9920-2D3B36D750DF 3D737B98 ProtectUefiImageCommon - 0x3D737D40 - 0x000000003D642000 - 0x00000000000066C0 InstallProtocolInterface: 18A031AB-B443-4D1A-A5C0-0C09261E9F71 3D648520 InstallProtocolInterface: 107A772C-D5E1-11D4-9A46-0090273FC14D 3D648580 InstallProtocolInterface: 6A7A5CFF-E8D9-4F70-BADA-75AB3025CE14 3D648310 Loading driver D6099B94-CD97-4CC5-8714-7F6312701A8A None of Tcg2Protocol/CcMeasurementProtocol is installed. InstallProtocolInterface: 5B1B31A1-9562-11D2-8E3F-00A0C969723B 3D7377C0 Loading driver at 0x0003D601000 EntryPoint=0x0003D604F76 VirtioGpuDxe.efi InstallProtocolInterface: BC62157E-3E33-4FEC-9920-2D3B36D750DF 3D737A98 ProtectUefiImageCommon - 0x3D7377C0 - 0x000000003D601000 - 0x0000000000005D00 InstallProtocolInterface: 18A031AB-B443-4D1A-A5C0-0C09261E9F71 3D606AE0 InstallProtocolInterface: 6A7A5CFF-E8D9-4F70-BADA-75AB3025CE14 3D606AB0 Driver 5CAB08D5-AD8F-4D8B-B828-D17A8D9FE977 was discovered but not loaded!! Driver 4D9CBEF0-15A0-4D0C-83DB-5213E710C23F was discovered but not loaded!! [Bds] Entry... [BdsDxe] Locate Variable Policy protocol - Success Variable Driver Auto Update Lang, Lang:eng, PlatformLang:en Status: Success PlatformBootManagerBeforeConsole Registered NotifyDevPath Event PCI Bus First Scanning PciBus: Discovered PCI @ [00|00|00] [VID = 0x8086, DID = 0x29C0] PciBus: Discovered PCI @ [00|01|00] [VID = 0x8086, DID = 0x10D3] BAR[0]: Type = Mem32; Alignment = 0x1FFFF; Length = 0x20000; Offset = 0x10 BAR[1]: Type = Mem32; Alignment = 0x1FFFF; Length = 0x20000; Offset = 0x14 BAR[2]: Type = Io32; Alignment = 0x1F; Length = 0x20; Offset = 0x18 BAR[3]: Type = Mem32; Alignment = 0x3FFF; Length = 0x4000; Offset = 0x1C PciBus: Discovered PPB @ [00|08|00] [VID = 0x1B36, DID = 0xC] Padding: Type = PMem64; Alignment = 0xFFFFFFF; Length = 0x10000000 Padding: Type = Mem32; Alignment = 0x1FFFFF; Length = 0x200000 Padding: Type = Io; Alignment = 0x1FF; Length = 0x200 BAR[0]: Type = Mem32; Alignment = 0xFFF; Length = 0x1000; Offset = 0x10 PciBus: Discovered PCI @ [01|00|00] [VID = 0x1AF4, DID = 0x1042] BAR[1]: Type = Mem32; Alignment = 0xFFF; Length = 0x1000; Offset = 0x14 BAR[4]: Type = PMem64; Alignment = 0x3FFF; Length = 0x4000; Offset = 0x20 PciBus: Discovered PCI @ [00|1F|00] [VID = 0x8086, DID = 0x2918] PciBus: Discovered PCI @ [00|1F|02] [VID = 0x8086, DID = 0x2922] BAR[4]: Type = Io32; Alignment = 0x1F; Length = 0x20; Offset = 0x20 BAR[5]: Type = Mem32; Alignment = 0xFFF; Length = 0x1000; Offset = 0x24 PciBus: Discovered PCI @ [00|1F|03] [VID = 0x8086, DID = 0x2930] BAR[4]: Type = Io32; Alignment = 0x3F; Length = 0x40; Offset = 0x20 PCI Bus Second Scanning PciBus: Discovered PCI @ [00|00|00] [VID = 0x8086, DID = 0x29C0] PciBus: Discovered PCI @ [00|01|00] [VID = 0x8086, DID = 0x10D3] BAR[0]: Type = Mem32; Alignment = 0x1FFFF; Length = 0x20000; Offset = 0x10 BAR[1]: Type = Mem32; Alignment = 0x1FFFF; Length = 0x20000; Offset = 0x14 BAR[2]: Type = Io32; Alignment = 0x1F; Length = 0x20; Offset = 0x18 BAR[3]: Type = Mem32; Alignment = 0x3FFF; Length = 0x4000; Offset = 0x1C PciBus: Discovered PPB @ [00|08|00] [VID = 0x1B36, DID = 0xC] Padding: Type = PMem64; Alignment = 0xFFFFFFF; Length = 0x10000000 Padding: Type = Mem32; Alignment = 0x1FFFFF; Length = 0x200000 Padding: Type = Io; Alignment = 0x1FF; Length = 0x200 BAR[0]: Type = Mem32; Alignment = 0xFFF; Length = 0x1000; Offset = 0x10 PciBus: Discovered PCI @ [01|00|00] [VID = 0x1AF4, DID = 0x1042] BAR[1]: Type = Mem32; Alignment = 0xFFF; Length = 0x1000; Offset = 0x14 BAR[4]: Type = PMem64; Alignment = 0x3FFF; Length = 0x4000; Offset = 0x20 PciBus: Discovered PCI @ [00|1F|00] [VID = 0x8086, DID = 0x2918] PciBus: Discovered PCI @ [00|1F|02] [VID = 0x8086, DID = 0x2922] BAR[4]: Type = Io32; Alignment = 0x1F; Length = 0x20; Offset = 0x20 BAR[5]: Type = Mem32; Alignment = 0xFFF; Length = 0x1000; Offset = 0x24 PciBus: Discovered PCI @ [00|1F|03] [VID = 0x8086, DID = 0x2930] BAR[4]: Type = Io32; Alignment = 0x3F; Length = 0x40; Offset = 0x20 PciBus: Discovered PCI @ [00|00|00] [VID = 0x8086, DID = 0x29C0] PciBus: Discovered PCI @ [00|01|00] [VID = 0x8086, DID = 0x10D3] BAR[0]: Type = Mem32; Alignment = 0x1FFFF; Length = 0x20000; Offset = 0x10 BAR[1]: Type = Mem32; Alignment = 0x1FFFF; Length = 0x20000; Offset = 0x14 BAR[2]: Type = Io32; Alignment = 0x1F; Length = 0x20; Offset = 0x18 BAR[3]: Type = Mem32; Alignment = 0x3FFF; Length = 0x4000; Offset = 0x1C PciBus: Discovered PPB @ [00|08|00] [VID = 0x1B36, DID = 0xC] Padding: Type = PMem64; Alignment = 0xFFFFFFF; Length = 0x10000000 Padding: Type = Mem32; Alignment = 0x1FFFFF; Length = 0x200000 Padding: Type = Io; Alignment = 0x1FF; Length = 0x200 BAR[0]: Type = Mem32; Alignment = 0xFFF; Length = 0x1000; Offset = 0x10 PciBus: Discovered PCI @ [01|00|00] [VID = 0x1AF4, DID = 0x1042] BAR[1]: Type = Mem32; Alignment = 0xFFF; Length = 0x1000; Offset = 0x14 BAR[4]: Type = PMem64; Alignment = 0x3FFF; Length = 0x4000; Offset = 0x20 PciBus: Discovered PCI @ [00|1F|00] [VID = 0x8086, DID = 0x2918] PciBus: Discovered PCI @ [00|1F|02] [VID = 0x8086, DID = 0x2922] BAR[4]: Type = Io32; Alignment = 0x1F; Length = 0x20; Offset = 0x20 BAR[5]: Type = Mem32; Alignment = 0xFFF; Length = 0x1000; Offset = 0x24 PciBus: Discovered PCI @ [00|1F|03] [VID = 0x8086, DID = 0x2930] BAR[4]: Type = Io32; Alignment = 0x3F; Length = 0x40; Offset = 0x20 PciHostBridge: SubmitResources for PciRoot(0x0) I/O: Granularity/SpecificFlag = 0 / 01 Length/Alignment = 0x1000 / 0xFFF Mem: Granularity/SpecificFlag = 32 / 00 Length/Alignment = 0x300000 / 0x1FFFFF Mem: Granularity/SpecificFlag = 64 / 00 Length/Alignment = 0x10000000 / 0xFFFFFFF PciBus: HostBridge->SubmitResources() - Success PciHostBridge: NotifyPhase (AllocateResources) RootBridge: PciRoot(0x0) Mem64: Base/Length/Alignment = 7000000000/10000000/FFFFFFF - Success Mem: Base/Length/Alignment = C0000000/300000/1FFFFF - Success I/O: Base/Length/Alignment = 6000/1000/FFF - Success PciBus: HostBridge->NotifyPhase(AllocateResources) - Success Process Option ROM: BAR Base/Length = C0200000/40000 PciBus: Resource Map for Root Bridge PciRoot(0x0) Type = Io16; Base = 0x6000; Length = 0x1000; Alignment = 0xFFF Base = 0x6000; Length = 0x200; Alignment = 0xFFF; Owner = PPB [00|08|00:**] Base = 0x6200; Length = 0x40; Alignment = 0x3F; Owner = PCI [00|1F|03:20] Base = 0x6240; Length = 0x20; Alignment = 0x1F; Owner = PCI [00|1F|02:20] Base = 0x6260; Length = 0x20; Alignment = 0x1F; Owner = PCI [00|01|00:18] Type = Mem32; Base = 0xC0000000; Length = 0x300000; Alignment = 0x1FFFFF Base = 0xC0000000; Length = 0x200000; Alignment = 0x1FFFFF; Owner = PPB [00|08|00:**] Base = 0xC0200000; Length = 0x40000; Alignment = 0x3FFFF; Owner = PCI [00|00|00:00]; Type = OpRom Base = 0xC0240000; Length = 0x20000; Alignment = 0x1FFFF; Owner = PCI [00|01|00:14] Base = 0xC0260000; Length = 0x20000; Alignment = 0x1FFFF; Owner = PCI [00|01|00:10] Base = 0xC0280000; Length = 0x4000; Alignment = 0x3FFF; Owner = PCI [00|01|00:1C] Base = 0xC0284000; Length = 0x1000; Alignment = 0xFFF; Owner = PCI [00|1F|02:24] Base = 0xC0285000; Length = 0x1000; Alignment = 0xFFF; Owner = PPB [00|08|00:10] Type = Mem64; Base = 0x7000000000; Length = 0x10000000; Alignment = 0xFFFFFFF Base = 0x7000000000; Length = 0x10000000; Alignment = 0xFFFFFFF; Owner = PPB [00|08|00:**]; Type = PMem64 PciBus: Resource Map for Bridge [00|08|00] Type = Io16; Base = 0x6000; Length = 0x200; Alignment = 0xFFF Base = Padding; Length = 0x200; Alignment = 0x1FF Type = Mem32; Base = 0xC0000000; Length = 0x200000; Alignment = 0x1FFFFF Base = Padding; Length = 0x200000; Alignment = 0x1FFFFF Base = 0xC0000000; Length = 0x1000; Alignment = 0xFFF; Owner = PCI [01|00|00:14] Type = Mem32; Base = 0xC0285000; Length = 0x1000; Alignment = 0xFFF Type = PMem64; Base = 0x7000000000; Length = 0x10000000; Alignment = 0xFFFFFFF Base = Padding; Length = 0x10000000; Alignment = 0xFFFFFFF Base = 0x7000000000; Length = 0x4000; Alignment = 0x3FFF; Owner = PCI [01|00|00:20] InstallProtocolInterface: 09576E91-6D3F-11D2-8E39-00A0C969723B 3D718698 InstallProtocolInterface: 4CF5B200-68B8-4CA5-9EEC-B23E3F50029A 3D6F9428 InstallProtocolInterface: 09576E91-6D3F-11D2-8E39-00A0C969723B 3D718798 InstallProtocolInterface: 4CF5B200-68B8-4CA5-9EEC-B23E3F50029A 3D6F9828 InstallProtocolInterface: 4006C0C1-FCB3-403E-996D-4A6C8724E06D 3D6F98F0 [Security] 3rd party image[0] is deferred to load before EndOfDxe: PciRoot(0x0)/Pci(0x1,0x0)/Offset(0x15C00,0x353FF). InstallProtocolInterface: 3BC1B285-8A15-4A82-AABF-4D7D13FB3265 3D6F98D8 InstallProtocolInterface: 09576E91-6D3F-11D2-8E39-00A0C969723B 3D718898 InstallProtocolInterface: 4CF5B200-68B8-4CA5-9EEC-B23E3F50029A 3D6E9028 InstallProtocolInterface: 09576E91-6D3F-11D2-8E39-00A0C969723B 3D718818 InstallProtocolInterface: 4CF5B200-68B8-4CA5-9EEC-B23E3F50029A 3D6E95A8 InstallProtocolInterface: 09576E91-6D3F-11D2-8E39-00A0C969723B 3D6E9F18 InstallProtocolInterface: 4CF5B200-68B8-4CA5-9EEC-B23E3F50029A 3D6E8028 InstallProtocolInterface: 09576E91-6D3F-11D2-8E39-00A0C969723B 3D6E9D18 InstallProtocolInterface: 4CF5B200-68B8-4CA5-9EEC-B23E3F50029A 3D6E8428 InstallProtocolInterface: 09576E91-6D3F-11D2-8E39-00A0C969723B 3D6E9B98 InstallProtocolInterface: 4CF5B200-68B8-4CA5-9EEC-B23E3F50029A 3D6E8828 InstallProtocolInterface: 30CFE3E7-3DE1-4586-BE20-DEABA1B3B793 0 OnRootBridgesConnected: root bridges have been connected, installing ACPI tables Select Item: 0x19 Select Item: 0x2D Select Item: 0x19 Select Item: 0x2C Select Item: 0x19 Select Item: 0x22 Select Item: 0x19 Select Item: 0x23 InstallProtocolInterface: 928939B2-4235-462F-9580-F6A2B2C21A4F 0 InstallQemuFwCfgTables: installed 7 tables PcRtc: Write 0x20 to CMOS location 0x32 SmmEndOfDxeHandler SmmInstallProtocolInterface: 24E70042-D5C5-4260-8C39-0AD3AA32E93D 0 [Variable]SMM_END_OF_DXE is signaled Initialize variable error flag (FF) AcpiS3ContextSave! SmmLockBoxDxeLib SaveLockBox - Enter SmmLockBox SmmLockBoxHandler Enter SmmLockBox LockBoxParameterHeader - 3EEC0930 SmmLockBox Command - 1 SmmLockBoxSmmLib SaveLockBox - Enter LockBoxGuid - DEA652B0-D587-4C54-B5B4-C682E7A0AA3D, SmramBuffer - 0x3FD6F000, Length - 0xA SmmLockBoxSmmLib SaveLockBox - Exit (Success) SmmLockBox SmmLockBoxHandler Exit SmmLockBoxDxeLib SaveLockBox - Exit (Success) SmmLockBoxDxeLib SetLockBoxAttributes - Enter SmmLockBox SmmLockBoxHandler Enter SmmLockBox LockBoxParameterHeader - 3EEC0948 SmmLockBox Command - 4 SmmLockBoxSmmLib SetLockBoxAttributes - Enter SmmLockBoxSmmLib SetLockBoxAttributes - Exit (Success) SmmLockBox SmmLockBoxHandler Exit SmmLockBoxDxeLib SetLockBoxAttributes - Exit (Success) AcpiS3ContextSave TotalPageTableSize - 0xE pages AcpiS3Context: AcpiFacsTable is 0x3E9BB000 AcpiS3Context: IdtrProfile is 0x3E962000 AcpiS3Context: S3NvsPageTableAddress is 0x3E953000 AcpiS3Context: S3DebugBufferAddress is 0x3E94A000 AcpiS3Context: BootScriptStackBase is 0x3E94B000 AcpiS3Context: BootScriptStackSize is 0x 8000 SmmLockBoxDxeLib SaveLockBox - Enter SmmLockBox SmmLockBoxHandler Enter SmmLockBox LockBoxParameterHeader - 3EEC0930 SmmLockBox Command - 1 SmmLockBoxSmmLib SaveLockBox - Enter LockBoxGuid - AF9FFD67-EC10-488A-9DFC-6CBF5EE22C2E, SmramBuffer - 0x3FD6E000, Length - 0x8 SmmLockBoxSmmLib SaveLockBox - Exit (Success) SmmLockBox SmmLockBoxHandler Exit SmmLockBoxDxeLib SaveLockBox - Exit (Success) SmmLockBoxDxeLib SaveLockBox - Enter SmmLockBox SmmLockBoxHandler Enter SmmLockBox LockBoxParameterHeader - 3EEC0930 SmmLockBox Command - 1 SmmLockBoxSmmLib SaveLockBox - Enter LockBoxGuid - 0EF98D3A-3E33-497A-A401-77BE3EB74F38, SmramBuffer - 0x3FD6D000, Length - 0x30 SmmLockBoxSmmLib SaveLockBox - Exit (Success) SmmLockBox SmmLockBoxHandler Exit SmmLockBoxDxeLib SaveLockBox - Exit (Success) SmmLockBoxDxeLib SetLockBoxAttributes - Enter SmmLockBox SmmLockBoxHandler Enter SmmLockBox LockBoxParameterHeader - 3EEC0948 SmmLockBox Command - 4 SmmLockBoxSmmLib SetLockBoxAttributes - Enter SmmLockBoxSmmLib SetLockBoxAttributes - Exit (Success) SmmLockBox SmmLockBoxHandler Exit SmmLockBoxDxeLib SetLockBoxAttributes - Exit (Success) Found LPC Bridge device BdsPlatform.c+709: COM1 DevPath: PciRoot(0x0)/Pci(0x1F,0x0)/Serial(0x0)/Uart(115200,8,N,1)/VenMsg(E0C14753-F9BE-11D2-9A0C-0090273FC14D) BdsPlatform.c+747: COM2 DevPath: PciRoot(0x0)/Pci(0x1F,0x0)/Serial(0x1)/Uart(115200,8,N,1)/VenMsg(E0C14753-F9BE-11D2-9A0C-0090273FC14D) Select Item: 0x19 [TPM2PP] no PPI InstallProtocolInterface: 60FF8964-E906-41D0-AFED-F241E974E08E 0 InstallProtocolInterface: FA20568B-548B-4B2B-81EF-1BA08D4A3CEC 0 SmmLockBoxDxeLib SaveLockBox - Enter SmmLockBox SmmLockBoxHandler Enter SmmLockBox LockBoxParameterHeader - 3EEC06E0 SmmLockBox Command - 1 SmmLockBoxSmmLib SaveLockBox - Enter LockBoxGuid - 3079818C-46D4-4A73-AEF3-E3E46CF1EEDB, SmramBuffer - 0x3FD6C000, Length - 0x8 SmmLockBoxSmmLib SaveLockBox - Exit (Success) SmmLockBox SmmLockBoxHandler Exit SmmLockBoxDxeLib SaveLockBox - Exit (Success) SmmLockBoxDxeLib SaveLockBox - Enter SmmLockBox SmmLockBoxHandler Enter SmmLockBox LockBoxParameterHeader - 3EEC06E0 SmmLockBox Command - 1 SmmLockBoxSmmLib SaveLockBox - Enter LockBoxGuid - 79CB58C4-AC51-442F-AFD7-98E47D2E9908, SmramBuffer - 0x3FD6B000, Length - 0x8 SmmLockBoxSmmLib SaveLockBox - Exit (Success) SmmLockBox SmmLockBoxHandler Exit SmmLockBoxDxeLib SaveLockBox - Exit (Success) SmmLockBoxDxeLib SetLockBoxAttributes - Enter SmmLockBox SmmLockBoxHandler Enter SmmLockBox LockBoxParameterHeader - 3EEC06F8 SmmLockBox Command - 4 SmmLockBoxSmmLib SetLockBoxAttributes - Enter SmmLockBoxSmmLib SetLockBoxAttributes - Exit (Success) SmmLockBox SmmLockBoxHandler Exit SmmLockBoxDxeLib SetLockBoxAttributes - Exit (Success) SmmLockBoxDxeLib SaveLockBox - Enter SmmLockBox SmmLockBoxHandler Enter SmmLockBox LockBoxParameterHeader - 3EEC0790 SmmLockBox Command - 1 SmmLockBoxSmmLib SaveLockBox - Enter LockBoxGuid - 9A8D3433-9FE8-42B6-870B-1E31C84EBE3B, SmramBuffer - 0x3FD56000, Length - 0x14B40 SmmLockBoxSmmLib SaveLockBox - Exit (Success) SmmLockBox SmmLockBoxHandler Exit SmmLockBoxDxeLib SaveLockBox - Exit (Success) SmmLockBoxDxeLib SetLockBoxAttributes - Enter SmmLockBox SmmLockBoxHandler Enter SmmLockBox LockBoxParameterHeader - 3EEC07A8 SmmLockBox Command - 4 SmmLockBoxSmmLib SetLockBoxAttributes - Enter SmmLockBoxSmmLib SetLockBoxAttributes - Exit (Success) SmmLockBox SmmLockBoxHandler Exit SmmLockBoxDxeLib SetLockBoxAttributes - Exit (Success) SmmLockBoxDxeLib SaveLockBox - Enter SmmLockBox SmmLockBoxHandler Enter SmmLockBox LockBoxParameterHeader - 3EEC0960 SmmLockBox Command - 1 SmmLockBoxSmmLib SaveLockBox - Enter LockBoxGuid - AEA6B965-DCF5-4311-B4B8-0F12464494D2, SmramBuffer - 0x3FD52000, Length - 0x4000 SmmLockBoxSmmLib SaveLockBox - Exit (Success) SmmLockBox SmmLockBoxHandler Exit SmmLockBoxDxeLib SaveLockBox - Exit (Success) SmmLockBoxDxeLib SetLockBoxAttributes - Enter SmmLockBox SmmLockBoxHandler Enter SmmLockBox LockBoxParameterHeader - 3EEC0978 SmmLockBox Command - 4 SmmLockBoxSmmLib SetLockBoxAttributes - Enter SmmLockBoxSmmLib SetLockBoxAttributes - Exit (Success) SmmLockBox SmmLockBoxHandler Exit SmmLockBoxDxeLib SetLockBoxAttributes - Exit (Success) SmmLockBoxDxeLib SaveLockBox - Enter SmmLockBox SmmLockBoxHandler Enter SmmLockBox LockBoxParameterHeader - 3EEC0960 SmmLockBox Command - 1 SmmLockBoxSmmLib SaveLockBox - Enter LockBoxGuid - 1810AB4A-2314-4DF6-81EB-67C6EC058591, SmramBuffer - 0x3FD51000, Length - 0x8 SmmLockBoxSmmLib SaveLockBox - Exit (Success) SmmLockBox SmmLockBoxHandler Exit SmmLockBoxDxeLib SaveLockBox - Exit (Success) SmmLockBoxDxeLib SetLockBoxAttributes - Enter SmmLockBox SmmLockBoxHandler Enter SmmLockBox LockBoxParameterHeader - 3EEC0978 SmmLockBox Command - 4 SmmLockBoxSmmLib SetLockBoxAttributes - Enter SmmLockBoxSmmLib SetLockBoxAttributes - Exit (Success) SmmLockBox SmmLockBoxHandler Exit SmmLockBoxDxeLib SetLockBoxAttributes - Exit (Success) SmmInstallProtocolInterface: 47B7FA8C-F4BD-4AF6-8200-333086F0D2C8 0 GetUefiMemoryMap Patch page table start ... Patch page table done! MemoryAttributesTable: Version - 0x00000001 NumberOfEntries - 0x00000027 DescriptorSize - 0x00000030 Entry (0x3FD73028) Type - 0x6 PhysicalStart - 0x000000003F000000 VirtualStart - 0x0000000000000000 NumberOfPages - 0x0000000000000001 Attribute - 0x0000000000004000 Entry (0x3FD73058) Type - 0x7 PhysicalStart - 0x000000003F001000 VirtualStart - 0x0000000000000000 NumberOfPages - 0x0000000000000D71 Attribute - 0x0000000000004000 Entry (0x3FD73088) Type - 0x6 PhysicalStart - 0x000000003FD72000 VirtualStart - 0x0000000000000000 NumberOfPages - 0x0000000000000012 Attribute - 0x0000000000004000 Entry (0x3FD730B8) Type - 0x5 PhysicalStart - 0x000000003FD84000 VirtualStart - 0x0000000000000000 NumberOfPages - 0x0000000000000008 Attribute - 0x0000000000020000 Entry (0x3FD730E8) Type - 0x6 PhysicalStart - 0x000000003FD8C000 VirtualStart - 0x0000000000000000 NumberOfPages - 0x0000000000000001 Attribute - 0x0000000000004000 Entry (0x3FD73118) Type - 0x5 PhysicalStart - 0x000000003FD8D000 VirtualStart - 0x0000000000000000 NumberOfPages - 0x0000000000000001 Attribute - 0x0000000000020000 Entry (0x3FD73148) Type - 0x6 PhysicalStart - 0x000000003FD8E000 VirtualStart - 0x0000000000000000 NumberOfPages - 0x0000000000000001 Attribute - 0x0000000000004000 Entry (0x3FD73178) Type - 0x5 PhysicalStart - 0x000000003FD8F000 VirtualStart - 0x0000000000000000 NumberOfPages - 0x0000000000000005 Attribute - 0x0000000000020000 Entry (0x3FD731A8) Type - 0x6 PhysicalStart - 0x000000003FD94000 VirtualStart - 0x0000000000000000 NumberOfPages - 0x0000000000000001 Attribute - 0x0000000000004000 Entry (0x3FD731D8) Type - 0x5 PhysicalStart - 0x000000003FD95000 VirtualStart - 0x0000000000000000 NumberOfPages - 0x0000000000000001 Attribute - 0x0000000000020000 Entry (0x3FD73208) Type - 0x6 PhysicalStart - 0x000000003FD96000 VirtualStart - 0x0000000000000000 NumberOfPages - 0x0000000000000146 Attribute - 0x0000000000004000 Entry (0x3FD73238) Type - 0x5 PhysicalStart - 0x000000003FEDC000 VirtualStart - 0x0000000000000000 NumberOfPages - 0x0000000000000064 Attribute - 0x0000000000020000 Entry (0x3FD73268) Type - 0x6 PhysicalStart - 0x000000003FF40000 VirtualStart - 0x0000000000000000 NumberOfPages - 0x000000000000001F Attribute - 0x0000000000004000 Entry (0x3FD73298) Type - 0x5 PhysicalStart - 0x000000003FF5F000 VirtualStart - 0x0000000000000000 NumberOfPages - 0x0000000000000001 Attribute - 0x0000000000020000 Entry (0x3FD732C8) Type - 0x6 PhysicalStart - 0x000000003FF60000 VirtualStart - 0x0000000000000000 NumberOfPages - 0x0000000000000021 Attribute - 0x0000000000004000 Entry (0x3FD732F8) Type - 0x5 PhysicalStart - 0x000000003FF81000 VirtualStart - 0x0000000000000000 NumberOfPages - 0x0000000000000005 Attribute - 0x0000000000020000 Entry (0x3FD73328) Type - 0x6 PhysicalStart - 0x000000003FF86000 VirtualStart - 0x0000000000000000 NumberOfPages - 0x0000000000000002 Attribute - 0x0000000000004000 Entry (0x3FD73358) Type - 0x5 PhysicalStart - 0x000000003FF88000 VirtualStart - 0x0000000000000000 NumberOfPages - 0x0000000000000001 Attribute - 0x0000000000020000 Entry (0x3FD73388) Type - 0x6 PhysicalStart - 0x000000003FF89000 VirtualStart - 0x0000000000000000 NumberOfPages - 0x000000000000000B Attribute - 0x0000000000004000 Entry (0x3FD733B8) Type - 0x5 PhysicalStart - 0x000000003FF94000 VirtualStart - 0x0000000000000000 NumberOfPages - 0x0000000000000001 Attribute - 0x0000000000020000 Entry (0x3FD733E8) Type - 0x6 PhysicalStart - 0x000000003FF95000 VirtualStart - 0x0000000000000000 NumberOfPages - 0x0000000000000002 Attribute - 0x0000000000004000 Entry (0x3FD73418) Type - 0x5 PhysicalStart - 0x000000003FF97000 VirtualStart - 0x0000000000000000 NumberOfPages - 0x0000000000000001 Attribute - 0x0000000000020000 Entry (0x3FD73448) Type - 0x6 PhysicalStart - 0x000000003FF98000 VirtualStart - 0x0000000000000000 NumberOfPages - 0x0000000000000019 Attribute - 0x0000000000004000 Entry (0x3FD73478) Type - 0x5 PhysicalStart - 0x000000003FFB1000 VirtualStart - 0x0000000000000000 NumberOfPages - 0x000000000000000E Attribute - 0x0000000000020000 Entry (0x3FD734A8) Type - 0x6 PhysicalStart - 0x000000003FFBF000 VirtualStart - 0x0000000000000000 NumberOfPages - 0x0000000000000001 Attribute - 0x0000000000004000 Entry (0x3FD734D8) Type - 0x5 PhysicalStart - 0x000000003FFC0000 VirtualStart - 0x0000000000000000 NumberOfPages - 0x0000000000000014 Attribute - 0x0000000000020000 Entry (0x3FD73508) Type - 0x6 PhysicalStart - 0x000000003FFD4000 VirtualStart - 0x0000000000000000 NumberOfPages - 0x0000000000000003 Attribute - 0x0000000000004000 Entry (0x3FD73538) Type - 0x5 PhysicalStart - 0x000000003FFD7000 VirtualStart - 0x0000000000000000 NumberOfPages - 0x0000000000000001 Attribute - 0x0000000000020000 Entry (0x3FD73568) Type - 0x6 PhysicalStart - 0x000000003FFD8000 VirtualStart - 0x0000000000000000 NumberOfPages - 0x0000000000000001 Attribute - 0x0000000000004000 Entry (0x3FD73598) Type - 0x5 PhysicalStart - 0x000000003FFD9000 VirtualStart - 0x0000000000000000 NumberOfPages - 0x0000000000000005 Attribute - 0x0000000000020000 Entry (0x3FD735C8) Type - 0x6 PhysicalStart - 0x000000003FFDE000 VirtualStart - 0x0000000000000000 NumberOfPages - 0x0000000000000002 Attribute - 0x0000000000004000 Entry (0x3FD735F8) Type - 0x5 PhysicalStart - 0x000000003FFE0000 VirtualStart - 0x0000000000000000 NumberOfPages - 0x0000000000000001 Attribute - 0x0000000000020000 Entry (0x3FD73628) Type - 0x6 PhysicalStart - 0x000000003FFE1000 VirtualStart - 0x0000000000000000 NumberOfPages - 0x0000000000000002 Attribute - 0x0000000000004000 Entry (0x3FD73658) Type - 0x5 PhysicalStart - 0x000000003FFE3000 VirtualStart - 0x0000000000000000 NumberOfPages - 0x0000000000000003 Attribute - 0x0000000000020000 Entry (0x3FD73688) Type - 0x6 PhysicalStart - 0x000000003FFE6000 VirtualStart - 0x0000000000000000 NumberOfPages - 0x0000000000000002 Attribute - 0x0000000000004000 Entry (0x3FD736B8) Type - 0x5 PhysicalStart - 0x000000003FFE8000 VirtualStart - 0x0000000000000000 NumberOfPages - 0x0000000000000001 Attribute - 0x0000000000020000 Entry (0x3FD736E8) Type - 0x6 PhysicalStart - 0x000000003FFE9000 VirtualStart - 0x0000000000000000 NumberOfPages - 0x0000000000000006 Attribute - 0x0000000000004000 Entry (0x3FD73718) Type - 0x5 PhysicalStart - 0x000000003FFEF000 VirtualStart - 0x0000000000000000 NumberOfPages - 0x000000000000000E Attribute - 0x0000000000020000 Entry (0x3FD73748) Type - 0x6 PhysicalStart - 0x000000003FFFD000 VirtualStart - 0x0000000000000000 NumberOfPages - 0x0000000000000003 Attribute - 0x0000000000004000 PatchSmmSaveStateMap: PatchGdtIdtMap - GDT: PatchGdtIdtMap - IDT: SetUefiMemMapAttributes UefiMemory protection: 0x0 - 0x30000 Success UefiMemory protection: 0x50000 - 0x9E000 Success UefiMemory protection: 0x100000 - 0x807000 Success UefiMemory protection: 0x808000 - 0x810000 Success UefiMemory protection: 0x1810000 - 0x3E6EC000 Success UefiMemory protection: 0x3E96C000 - 0x3E97E000 Success UefiMemory protection: 0x3E9FE000 - 0x3EF60000 Success UefiMemoryAttribute protection: 0x3E8AF000 - 0x3E8B1000 Success UefiMemoryAttribute protection: 0x3E8B3000 - 0x3E8B5000 Success UefiMemoryAttribute protection: 0x3E8B7000 - 0x3E8BB000 Success UefiMemoryAttribute protection: 0x3E8BD000 - 0x3E8C2000 Success UefiMemoryAttribute protection: 0x3E8C5000 - 0x3E8CB000 Success UefiMemoryAttribute protection: 0x3E8CE000 - 0x3E8D2000 Success UefiMemoryAttribute protection: 0x3E8D5000 - 0x3E8D8000 Success UefiMemoryAttribute protection: 0x3E8DA000 - 0x3E8DE000 Success UefiMemoryAttribute protection: 0x3E8E1000 - 0x3E8E4000 Success UefiMemoryAttribute protection: 0x3E8E7000 - 0x3E8EA000 Success SetPageTableAttributes Start... SMM IPL locked SMRAM window [Security] 3rd party image[3D6E9E18] can be loaded after EndOfDxe: PciRoot(0x0)/Pci(0x1,0x0)/Offset(0x15C00,0x353FF). None of Tcg2Protocol/CcMeasurementProtocol is installed. InstallProtocolInterface: 5B1B31A1-9562-11D2-8E3F-00A0C969723B 3D6E4040 Loading driver at 0x0003D3FB000 EntryPoint=0x0003D401FE5 808610d3.efi InstallProtocolInterface: BC62157E-3E33-4FEC-9920-2D3B36D750DF 3D6E5698 ProtectUefiImageCommon - 0x3D6E4040 - 0x000000003D3FB000 - 0x00000000000BC000 InstallProtocolInterface: 18A031AB-B443-4D1A-A5C0-0C09261E9F71 3D42EFE0 InstallProtocolInterface: 6A7A5CFF-E8D9-4F70-BADA-75AB3025CE14 3D42EFA0 Found LPC Bridge device BdsPlatform.c+709: COM1 DevPath: PciRoot(0x0)/Pci(0x1F,0x0)/Serial(0x0)/Uart(115200,8,N,1)/VenMsg(E0C14753-F9BE-11D2-9A0C-0090273FC14D) BdsPlatform.c+747: COM2 DevPath: PciRoot(0x0)/Pci(0x1F,0x0)/Serial(0x1)/Uart(115200,8,N,1)/VenMsg(E0C14753-F9BE-11D2-9A0C-0090273FC14D) Select Item: 0xE [Bds]RegisterKeyNotify: 000C/0000 80000000/00 Success [Bds]RegisterKeyNotify: 0017/0000 80000000/00 Success [Bds]RegisterKeyNotify: 0000/000D 80000000/00 Success InstallProtocolInterface: 864E1CA8-85EB-4D63-9DCC-6E0FC90FFD55 3D6E4A18 InstallProtocolInterface: 09576E91-6D3F-11D2-8E39-00A0C969723B 3D6E4518 InstallProtocolInterface: 215FDD18-BD50-4FEB-890B-58CA0B4739E9 3D6E4EB8 InstallProtocolInterface: 09576E91-6D3F-11D2-8E39-00A0C969723B 3D6E3B18 InstallProtocolInterface: 215FDD18-BD50-4FEB-890B-58CA0B4739E9 3D6E3F38 InstallProtocolInterface: 09576E91-6D3F-11D2-8E39-00A0C969723B 3D6E3D18 InstallProtocolInterface: 215FDD18-BD50-4FEB-890B-58CA0B4739E9 3D6E3C38 ClockRate = 1843200 Divisor = 1 BaudRate/Actual (115200/115200) = 100% ClockRate = 1843200 Divisor = 1 BaudRate/Actual (115200/115200) = 100% InstallProtocolInterface: 09576E91-6D3F-11D2-8E39-00A0C969723B 3D6E3598 InstallProtocolInterface: BB25CF6F-F1D4-11D2-9A0C-0090273FC1FD 3D6E47A8 PciSioSerial: Create SIO child serial device - Success ClockRate = 1843200 Divisor = 1 BaudRate/Actual (115200/115200) = 100% Terminal - Mode 0, Column = 80, Row = 25 Terminal - Mode 1, Column = 80, Row = 50 Terminal - Mode 2, Column = 100, Row = 31 ClockRate = 1843200 Divisor = 1 BaudRate/Actual (115200/115200) = 100% InstallProtocolInterface: 387477C1-69C7-11D2-8E39-00A0C969723B 3D6D5440 InstallProtocolInterface: DD9E7534-7762-4698-8C14-F58517A625AA 3D6D5528 InstallProtocolInterface: 387477C2-69C7-11D2-8E39-00A0C969723B 3D6D5458 InstallProtocolInterface: 09576E91-6D3F-11D2-8E39-00A0C969723B 3D6D5818 InstallProtocolInterface: D3B36F2B-D551-11D4-9A46-0090273FC14D 0 InstallProtocolInterface: D3B36F2C-D551-11D4-9A46-0090273FC14D 0 InstallProtocolInterface: D3B36F2D-D551-11D4-9A46-0090273FC14D 0 ClockRate = 1843200 Divisor = 1 BaudRate/Actual (115200/115200) = 100% PciSioSerial: Create SIO child serial device - Device Error InstallProtocolInterface: 387477C1-69C7-11D2-8E39-00A0C969723B 3D633028 InstallProtocolInterface: DD9E7534-7762-4698-8C14-F58517A625AA 3D633040 InstallProtocolInterface: D3B36F2B-D551-11D4-9A46-0090273FC14D 0 ClockRate = 1843200 Divisor = 1 BaudRate/Actual (115200/115200) = 100% PciSioSerial: Create SIO child serial device - Device Error ClockRate = 1843200 Divisor = 1 BaudRate/Actual (115200/115200) = 100% PciSioSerial: Create SIO child serial device - Device Error PlatformBootManagerAfterConsole PlatformBdsPolicyBehavior: not restoring NvVars from disk since flash variables appear to be supported. Boot Mode:0 Select Item: 0x19 Select Item: 0x21 StoreQemuBootOrder: VMMBootOrder0000 = PciRoot(0x0)/Pci(0x8,0x0)/Pci(0x0,0x0) PlatformBdsConnectSequence Select Item: 0x19 Select Item: 0x21 InstallProtocolInterface: FA920010-6785-4941-B6EC-498C579F160A 3D6E43A0 VirtioBlkInit: LbaSize=0x200[B] NumBlocks=0x48028[Lba] VirtioBlkInit: FirstAligned=0x0[Lba] PhysBlkSize=0x1[Lba] VirtioBlkInit: OptimalTransferLengthGranularity=0x0[Lba] InstallProtocolInterface: 964E5B21-6459-11D2-8E39-00A0C969723B 3D632490 InstallProtocolInterface: CE345171-BA0B-11D2-8E4F-00A0C969723B 3D631020 BlockSize : 512 LastBlock : 48027 Valid efi partition table header Valid efi partition table header Valid primary and Valid backup partition table Partition entries read block success Number of partition entries: 128 start check partition entries End check partition entries Index : 0 Start LBA : 40 End LBA : 7FFF Partition size: 7FC0 Start : 8000 End : FFFE00 InstallProtocolInterface: 09576E91-6D3F-11D2-8E39-00A0C969723B 3D631F18 InstallProtocolInterface: 964E5B21-6459-11D2-8E39-00A0C969723B 3D631330 InstallProtocolInterface: 8CF2F62C-BC9B-4821-808D-EC9EC421A1A0 3D6313E8 InstallProtocolInterface: C12A7328-F81F-11D2-BA4B-00A0C93EC93B 0 Index : 1 Start LBA : 8000 End LBA : 47FFF Partition size: 40000 Start : 1000000 End : 8FFFE00 InstallProtocolInterface: 09576E91-6D3F-11D2-8E39-00A0C969723B 3D632A98 InstallProtocolInterface: 964E5B21-6459-11D2-8E39-00A0C969723B 3D630030 InstallProtocolInterface: 8CF2F62C-BC9B-4821-808D-EC9EC421A1A0 3D6300E8 InstallProtocolInterface: 4F68BCE3-E8CD-4DB1-96E7-FBCAF984B709 0 Prepare to Free Pool InstallProtocolInterface: CE345171-BA0B-11D2-8E4F-00A0C969723B 3D631CA0 BlockSize : 512 LastBlock : 7FBF InstallProtocolInterface: 964E5B22-6459-11D2-8E39-00A0C969723B 3D5ED030 Installed Fat filesystem on 3D632798 InstallProtocolInterface: CE345171-BA0B-11D2-8E4F-00A0C969723B 3D631920 BlockSize : 512 LastBlock : 3FFFF ConnectDevicesFromQemu: 1 OpenFirmware device path(s) connected Select Item: 0x19 Select Item: 0x21 SetBootOrderFromQemu: setting BootOrder: success [Bds]OsIndication: 0000000000000000 [Bds]=============Begin Load Options Dumping ...============= Driver Options: SysPrep Options: Boot Options: Boot0001: UEFI Misc Device 0x0001 Boot0000: UiApp 0x0109 Boot0002: EFI Internal Shell 0x0001 PlatformRecovery Options: PlatformRecovery0000: Default PlatformRecovery 0x0001 [Bds]=============End Load Options Dumping============= [Bds]BdsWait ...Zzzzzzzzzzzz... [Bds]Exit the waiting! [Bds]Stop Hotkey Service! [Bds]UnregisterKeyNotify: 000C/0000 Success [Bds]UnregisterKeyNotify: 0017/0000 Success [Bds]UnregisterKeyNotify: 0000/000D Success SmmInstallProtocolInterface: 6E057ECF-FA99-4F39-95BC-59F9921D17E4 0 Memory Previous Current Next Type Pages Pages Pages ====== ======== ======== ======== 0A 00000080 00000043 00000080 09 00000012 0000000A 00000012 00 00000080 00000038 00000080 05 00000100 0000003E 00000100 06 00000100 0000006A 00000100 [Bds]Booting UEFI Misc Device BlockSize : 512 LastBlock : 48027 Valid efi partition table header Valid efi partition table header Valid primary and Valid backup partition table Partition entries read block success Number of partition entries: 128 start check partition entries End check partition entries Index : 0 Start LBA : 40 End LBA : 7FFF Partition size: 7FC0 Start : 8000 End : FFFE00 Index : 1 Start LBA : 8000 End LBA : 47FFF Partition size: 40000 Start : 1000000 End : 8FFFE00 Prepare to Free Pool BlockSize : 512 LastBlock : 3FFFF FatDiskIo: Cache Page OutBound occurred! FSOpen: Open '\EFI\BOOT\BOOTX64.EFI' Success [Bds] Expand PciRoot(0x0)/Pci(0x8,0x0)/Pci(0x0,0x0) -> PciRoot(0x0)/Pci(0x8,0x0)/Pci(0x0,0x0)/HD(1,GPT,EA84E18B-286C-4EAA-966D-5C039D67459A,0x40,0x7FC0)/\EFI\BOOT\BOOTX64.EFI [Security] 3rd party image[0] can be loaded after EndOfDxe: PciRoot(0x0)/Pci(0x8,0x0)/Pci(0x0,0x0)/HD(1,GPT,EA84E18B-286C-4EAA-966D-5C039D67459A,0x40,0x7FC0)/\EFI\BOOT\BOOTX64.EFI. None of Tcg2Protocol/CcMeasurementProtocol is installed. InstallProtocolInterface: 5B1B31A1-9562-11D2-8E3F-00A0C969723B 3D4D4040 Loading driver at 0x0003CD47000 EntryPoint=0x0003CD48000 InstallProtocolInterface: BC62157E-3E33-4FEC-9920-2D3B36D750DF 3D5ECC18 ProtectUefiImageCommon - 0x3D4D4040 - 0x000000003CD47000 - 0x00000000000A6000 SmmInstallProtocolInterface: 296EB418-C4C8-4E05-AB59-39E8AF56F00A 0 CpuDxe: 5-Level Paging = 0 MpInitChangeApLoopCallback() done! SetUefiImageMemoryAttributes - 0x000000003E8E6000 - 0x0000000000006000 (0x0000000000000008) SetUefiImageMemoryAttributes - 0x000000003E8E0000 - 0x0000000000006000 (0x0000000000000008) SetUefiImageMemoryAttributes - 0x000000003E8D9000 - 0x0000000000007000 (0x0000000000000008) SetUefiImageMemoryAttributes - 0x000000003E8D4000 - 0x0000000000005000 (0x0000000000000008) SetUefiImageMemoryAttributes - 0x000000003E8CD000 - 0x0000000000007000 (0x0000000000000008) SetUefiImageMemoryAttributes - 0x000000003E8C4000 - 0x0000000000009000 (0x0000000000000008) SetUefiImageMemoryAttributes - 0x000000003E8BC000 - 0x0000000000008000 (0x0000000000000008) SetUefiImageMemoryAttributes - 0x000000003E8B6000 - 0x0000000000006000 (0x0000000000000008) SetUefiImageMemoryAttributes - 0x000000003E8B2000 - 0x0000000000004000 (0x0000000000000008) SetUefiImageMemoryAttributes - 0x000000003E8AE000 - 0x0000000000004000 (0x0000000000000008) SecCoreStartupWithStack(0xFFFCC000, 0x820000) Register PPI Notify: DCD0BE23-9586-40F4-B643-06522CED4EDE Install PPI: 8C8CE578-8A3D-4F1C-9935-896185C32DD3 Install PPI: 5473C07A-3DCB-4DCA-BD6F-1E9689E7349A The 0th FV start address is 0x00000820000, size is 0x000E0000, handle is 0x820000 Register PPI Notify: 49EDB1C1-BF21-4761-BB12-EB0031AABB39 Register PPI Notify: EA7CA24B-DED5-4DAD-A389-BF827E8F9B38 Install PPI: B9E0ABFE-5979-4914-977F-6DEE78C278A6 Install PPI: DBE23AA9-A345-4B97-85B6-B226F1617389 Install PPI: 138F9CF4-F0E7-4721-8F49-F5FFECF42D40 DiscoverPeimsAndOrderWithApriori(): Found 0xF PEI FFS files in the 0th FV Loading PEIM 9B3ADA4F-AE56-4C24-8DEA-F03B7558AE50 Loading PEIM at 0x0000082B180 EntryPoint=0x0000082DC72 PcdPeim.efi Install PPI: 06E81C58-4AD7-44BC-8390-F10265F72480 Install PPI: 01F34D25-4DE2-23AD-3FF3-36353FF323F1 Install PPI: 4D8B155B-C059-4C8F-8926-06FD4331DB8A Install PPI: A60C6B59-E459-425D-9C69-0BCC9CB27D81 Register PPI Notify: 605EA650-C65C-42E1-BA80-91A52AB618C6 Loading PEIM A3610442-E69F-4DF3-82CA-2360C4031A23 Loading PEIM at 0x0000082FA40 EntryPoint=0x00000830B74 ReportStatusCodeRouterPei.efi Install PPI: 0065D394-9951-4144-82A3-0AFC8579C251 Install PPI: 229832D3-7A30-4B36-B827-F40CB7D45436 Loading PEIM 9D225237-FA01-464C-A949-BAABC02D31D0 Loading PEIM at 0x000008318C0 EntryPoint=0x00000832927 StatusCodeHandlerPei.efi Loading PEIM 222C386D-5ABC-4FB4-B124-FBB82488ACF4 Loading PEIM at 0x00000833740 EntryPoint=0x00000839C59 PlatformPei.efi Platform PEIM Loaded CMOS: 00: 37 00 57 00 10 00 02 06 03 23 26 02 00 80 00 FE 10: 00 00 00 00 06 80 02 FF FF 00 00 00 00 00 00 00 20: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 30: FF FF 20 00 00 3F 00 20 30 00 00 00 00 12 00 00 40: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 50: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 01 60: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 70: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 QemuFwCfgProbe: Supported 1, DMA 1 Select Item: 0x19 Select Item: 0x2C S3 support was detected on QEMU Install PPI: 7408D748-FC8C-4EE6-9288-C4BEC092A410 Select Item: 0x19 Select Item: 0x19 Select Item: 0x25 Select Item: 0x19 Select Item: 0x19 PlatformAddressWidthFromCpuid: Signature: 'GenuineIntel', PhysBits: 39, QemuQuirk: On, Valid: Yes PlatformDynamicMmioWindow: using dynamic mmio window PlatformDynamicMmioWindow: Addr Space 0x8000000000 (512 GB) PlatformDynamicMmioWindow: MMIO Space 0x1000000000 (64 GB) Select Item: 0x19 Select Item: 0x25 PlatformDynamicMmioWindow: Pci64 Base 0x7000000000 PlatformDynamicMmioWindow: Pci64 Size 0x1000000000 Select Item: 0x5 PlatformMaxCpuCountInitialization: BootCpuCount=2 MaxCpuCount=4 Q35TsegMbytesInitialization: QEMU offers an extended TSEG (16 MB) Q35SmramAtDefaultSmbaseInitialization: SMRAM at default SMBASE found Select Item: 0x19 Select Item: 0x25 PlatformGetLowMemoryCB: LowMemory=0x40000000 PeiInstallPeiMemory MemoryBegin 0x3EF60000, MemoryLength 0xA0000 Select Item: 0x19 Select Item: 0x25 PlatformQemuInitializeRam called Select Item: 0x19 Select Item: 0x25 Register PPI Notify: EE16160A-E8BE-47A6-820A-C6900DB0250A Select Item: 0x19 Select Item: 0x26 Register PPI Notify: EE16160A-E8BE-47A6-820A-C6900DB0250A Temp Stack : BaseAddress=0x818000 Length=0x8000 Temp Heap : BaseAddress=0x810000 Length=0x8000 Total temporary memory: 65536 bytes. temporary memory stack ever used: 28412 bytes. temporary memory heap used for HobList: 4656 bytes. temporary memory heap occupied by memory pages: 0 bytes. Old Stack size 32768, New stack size 131072 Stack Hob: BaseAddress=0x3EF60000 Length=0x20000 Heap Offset = 0x3E770000 Stack Offset = 0x3E760000 TemporaryRamMigration(0x810000, 0x3EF78000, 0x10000) Reinstall PPI: 8C8CE578-8A3D-4F1C-9935-896185C32DD3 Reinstall PPI: 5473C07A-3DCB-4DCA-BD6F-1E9689E7349A Reinstall PPI: B9E0ABFE-5979-4914-977F-6DEE78C278A6 Install PPI: F894643D-C449-42D1-8EA8-85BDD8C65BDE Loading PEIM 86D70125-BAA3-4296-A62F-602BEBBB9081 Loading PEIM at 0x0000083F640 EntryPoint=0x000008424C3 DxeIpl.efi Register PPI Notify: F894643D-C449-42D1-8EA8-85BDD8C65BDE Install PPI: 0AE8CE5D-E448-4437-A8D7-EBF5F194F731 Notify: PPI Guid: F894643D-C449-42D1-8EA8-85BDD8C65BDE, Peim notify entry point: 840B93 Install PPI: 1A36E4E7-FAB6-476A-8E75-695A0576FDD7 Loading PEIM 89E549B0-7CFE-449D-9BA3-10D8B2312D71 Loading PEIM at 0x00000843F40 EntryPoint=0x000008467E2 S3Resume2Pei.efi Install PPI: 6D582DBC-DB85-4514-8FCC-5ADF6227B147 Loading PEIM AAC33064-9ED0-4B89-A5AD-3EA767960B22 Loading PEIM at 0x00000848840 EntryPoint=0x000008499BF FaultTolerantWritePei.efi Install PPI: 1D3E9CB8-43AF-490B-830A-3516AA532047 Loading PEIM 34C8C28F-B61C-45A2-8F2E-89E46BECC63B Loading PEIM at 0x0000084AD40 EntryPoint=0x0000084CBD6 PeiVariable.efi Install PPI: 2AB86EF5-ECB5-4134-B556-3854CA1FE1B4 Loading PEIM 6C0E75B4-B0B9-44D1-8210-3377D7B4E066 Loading PEIM at 0x0000084DD40 EntryPoint=0x0000084F0B1 SmmAccessPei.efi Install PPI: 268F33A9-CCCD-48BE-8817-86053AC32ED6 Loading PEIM EDADEB9D-DDBA-48BD-9D22-C1C169C8C5C6 Loading PEIM at 0x000008503C0 EntryPoint=0x000008560CD CpuMpPei.efi Register PPI Notify: F894643D-C449-42D1-8EA8-85BDD8C65BDE Notify: PPI Guid: F894643D-C449-42D1-8EA8-85BDD8C65BDE, Peim notify entry point: 854BA9 AP Loop Mode is 1 AP Vector: non-16-bit = 3EFD6000/DC WakeupBufferStart = 2F000, WakeupBufferSize = 0 AP Vector: 16-bit = 2F000/41, ExchangeInfo = 2F041/5C CpuMpPei: 5-Level Paging = 0 APIC MODE is 1 MpInitLib: Find 2 processors in system. GetMicrocodePatchInfoFromHob: Microcode patch cache HOB is not found. CpuMpPei: 5-Level Paging = 0 CPU[0000]: Microcode revision = 00000000, expected = 00000000 CPU[0001]: Microcode revision = 00000000, expected = 00000000 Register PPI Notify: 8F9D4825-797D-48FC-8471-845025792EF6 Does not find any stored CPU BIST information from PPI! APICID - 0x00000000, BIST - 0x00000000 APICID - 0x00000001, BIST - 0x00000000 Install PPI: 9E9F374B-8F16-4230-9824-5846EE766A97 Install PPI: 5CB9CB3D-31A4-480C-9498-29D269BACFBA Install PPI: EE16160A-E8BE-47A6-820A-C6900DB0250A Notify: PPI Guid: EE16160A-E8BE-47A6-820A-C6900DB0250A, Peim notify entry point: 8351C8 PlatformPei: ClearCacheOnMpServicesAvailable CpuMpPei: 5-Level Paging = 0 Notify: PPI Guid: EE16160A-E8BE-47A6-820A-C6900DB0250A, Peim notify entry point: 836A02 CpuMpPei: 5-Level Paging = 0 Loading PEIM F12F698A-E506-4A1B-B32E-6920E55DA1C4 Loading PEIM at 0x0000085A540 EntryPoint=0x0000085B2EB TpmMmioSevDecryptPei.efi TpmMmioSevDecryptPeimEntryPoint Install PPI: 35C84FF2-7BFE-453D-845F-683A492CF7B7 Loading PEIM 8AD3148F-945F-46B4-8ACD-71469EA73945 Loading PEIM at 0x0000085C040 EntryPoint=0x0000085D177 Tcg2ConfigPei.efi Tcg2ConfigPeimEntryPoint Tcg2ConfigPeimEntryPoint: no TPM detected Install PPI: A030D115-54DD-447B-9064-F206883D7CCC Install PPI: 7F4158D3-074D-456D-8CB2-01F9C8F79DAA Loading PEIM 2BE1E4A6-6505-43B3-9FFC-A3C8330E0432 Loading PEIM at 0x0000085ECC0 EntryPoint=0x0000086116D TcgPei.efi No TPM12 instance required! Loading PEIM A0C98B77-CBA5-4BB8-993B-4AF6CE33ECE4 Loading PEIM at 0x00000863140 EntryPoint=0x0000086BC2E Tcg2Pei.efi No TPM2 instance required! Loading PEIM 47727552-A54B-4A84-8CC1-BFF23E239636 Loading PEIM at 0x0000086F8C0 EntryPoint=0x000008719DA Tcg2PlatformPei.efi Register PPI Notify: 605EA650-C65C-42E1-BA80-91A52AB618C6 DXE IPL Entry Enter S3 PEIM SmmLockBoxPeiLib RestoreLockBox - Enter SmmLockBoxPeiLib LocatePpi - (Not Found) SmmLockBoxPeiLib RestoreLockBox - Exit (Success) SmmLockBoxPeiLib RestoreLockBox - Enter SmmLockBoxPeiLib LocatePpi - (Not Found) SmmLockBoxPeiLib RestoreLockBox - Exit (Success) SmmLockBoxPeiLib RestoreLockBox - Enter SmmLockBoxPeiLib LocatePpi - (Not Found) SmmLockBoxPeiLib RestoreLockBox - Exit (Success) SmmLockBoxPeiLib RestoreLockBox - Enter SmmLockBoxPeiLib LocatePpi - (Not Found) SmmLockBoxPeiLib RestoreLockBox - Exit (Success) AcpiS3Context = 3E963000 Waking Vector = 981D0 AcpiS3Context->AcpiFacsTable = 3E9BB000 AcpiS3Context->IdtrProfile = 3E962000 AcpiS3Context->S3NvsPageTableAddress = 3E953000 AcpiS3Context->S3DebugBufferAddress = 3E94A000 AcpiS3Context->BootScriptStackBase = 3E94B000 AcpiS3Context->BootScriptStackSize = 8000 EfiBootScriptExecutorVariable->BootScriptExecutorEntrypoint = 3E93BE32 SmmLockBoxPeiLib RestoreAllLockBoxInPlace - Enter SmmLockBoxPeiLib LocatePpi - (Not Found) SmmLockBoxPeiLib RestoreAllLockBoxInPlace - Exit (Success) S3NvsPageTableAddress - 3E953000 (1) SMM S3 Signature = 534D4D53 SMM S3 Stack Base = 3FF89000 SMM S3 Stack Size = 8000 SMM S3 Resume Entry Point = 3FFC6330 SMM S3 CR0 = 80010033 SMM S3 CR3 = 3FF6E000 SMM S3 CR4 = 668 SMM S3 Return CS = 10 SMM S3 Return Entry Point = 845ACC SMM S3 Return Context1 = 3E963000 SMM S3 Return Context2 = 3E934000 SMM S3 Return Stack Pointer = 3EF7EF7C SMM S3 Smst = 3FFFD240 SmmRestoreCpu() ^ permalink raw reply [flat|nested] 16+ messages in thread
* Re: [edk2-devel] [PATCH v9 0/6] Simplify SMM Relocation Process 2023-03-06 11:13 ` Gerd Hoffmann @ 2023-03-06 11:43 ` Ni, Ray 2023-03-06 13:20 ` Gerd Hoffmann 0 siblings, 1 reply; 16+ messages in thread From: Ni, Ray @ 2023-03-06 11:43 UTC (permalink / raw) To: devel@edk2.groups.io, kraxel@redhat.com Cc: Wu, Jiaxin, Dong, Eric, Zeng, Star, Laszlo Ersek, Kumar, Rahul R Gerd, Thanks for reporting. Can you kindly share the reproduce steps? Jiaxin, Can you look into this? Thanks, Ray > -----Original Message----- > From: devel@edk2.groups.io <devel@edk2.groups.io> On Behalf Of Gerd > Hoffmann > Sent: Monday, March 6, 2023 7:13 PM > To: devel@edk2.groups.io > Cc: Ni, Ray <ray.ni@intel.com>; Wu, Jiaxin <jiaxin.wu@intel.com>; Dong, Eric > <eric.dong@intel.com>; Zeng, Star <star.zeng@intel.com>; Laszlo Ersek > <lersek@redhat.com>; Kumar, Rahul R <rahul.r.kumar@intel.com> > Subject: Re: [edk2-devel] [PATCH v9 0/6] Simplify SMM Relocation Process > > On Tue, Feb 21, 2023 at 09:48:54AM +0100, Gerd Hoffmann wrote: > > On Mon, Feb 20, 2023 at 01:14:33AM +0000, Ni, Ray wrote: > > > I expect Gerd at least acknowledges all patches for UefiCpuPkg. Following > three haven't got: > > > * [PATCH v9 3/6] UefiCpuPkg/SmmBaseHob.h: Add SMM Base HOB Data > > > * [PATCH v9 4/6] UefiCpuPkg/PiSmmCpuDxeSmm: Consume SMM Base > Hob for SmBase info > > > * [PATCH v9 5/6] UefiCpuPkg/SmmCpuFeaturesLib: Skip SMBASE > configuration > > > > I still think it is worth cleaning cleaning up and remove both code and > > comment for i486 and pentium processors from the last century. That > > should reduce confusion of the already complex code. But if you insist > > on not touching the existing code, so be it. > > > > Series (for post-freeze merge): > > Acked-by: Gerd Hoffmann <kraxel@redhat.com> > > Damn, should have tested this. The series breaks suspend for > OvmfPkg/OvmfPkgIa32X64.dsc (32-bit PEI + 64-bit SMM/DXE). Full log > below. Please investigate and fix. > > OvmfPkg/OvmfPkgX64.dsc suspend works fine (64bit PEI/DXE, no SMM). > > take care, > Gerd > > ------------------ cut here --------------- > SecCoreStartupWithStack(0xFFFCC000, 0x820000) > Register PPI Notify: DCD0BE23-9586-40F4-B643-06522CED4EDE > Install PPI: 8C8CE578-8A3D-4F1C-9935-896185C32DD3 > Install PPI: 5473C07A-3DCB-4DCA-BD6F-1E9689E7349A > The 0th FV start address is 0x00000820000, size is 0x000E0000, handle is > 0x820000 > Register PPI Notify: 49EDB1C1-BF21-4761-BB12-EB0031AABB39 > Register PPI Notify: EA7CA24B-DED5-4DAD-A389-BF827E8F9B38 > Install PPI: B9E0ABFE-5979-4914-977F-6DEE78C278A6 > Install PPI: DBE23AA9-A345-4B97-85B6-B226F1617389 > Install PPI: 138F9CF4-F0E7-4721-8F49-F5FFECF42D40 > DiscoverPeimsAndOrderWithApriori(): Found 0xF PEI FFS files in the 0th FV > Loading PEIM 9B3ADA4F-AE56-4C24-8DEA-F03B7558AE50 > Loading PEIM at 0x0000082B180 EntryPoint=0x0000082DC72 PcdPeim.efi > Install PPI: 06E81C58-4AD7-44BC-8390-F10265F72480 > Install PPI: 01F34D25-4DE2-23AD-3FF3-36353FF323F1 > Install PPI: 4D8B155B-C059-4C8F-8926-06FD4331DB8A > Install PPI: A60C6B59-E459-425D-9C69-0BCC9CB27D81 > Register PPI Notify: 605EA650-C65C-42E1-BA80-91A52AB618C6 > Loading PEIM A3610442-E69F-4DF3-82CA-2360C4031A23 > Loading PEIM at 0x0000082FA40 EntryPoint=0x00000830B74 > ReportStatusCodeRouterPei.efi > Install PPI: 0065D394-9951-4144-82A3-0AFC8579C251 > Install PPI: 229832D3-7A30-4B36-B827-F40CB7D45436 > Loading PEIM 9D225237-FA01-464C-A949-BAABC02D31D0 > Loading PEIM at 0x000008318C0 EntryPoint=0x00000832927 > StatusCodeHandlerPei.efi > Loading PEIM 222C386D-5ABC-4FB4-B124-FBB82488ACF4 > Loading PEIM at 0x00000833740 EntryPoint=0x00000839C59 PlatformPei.efi > Platform PEIM Loaded > CMOS: > 00: 21 00 57 00 10 00 02 06 03 23 26 02 00 80 00 00 > 10: 00 00 00 00 06 80 02 FF FF 00 00 00 00 00 00 00 > 20: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 > 30: FF FF 20 00 00 3F 00 20 30 00 00 00 00 12 00 00 > 40: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 > 50: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 01 > 60: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 > 70: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 > QemuFwCfgProbe: Supported 1, DMA 1 > Select Item: 0x19 > Select Item: 0x2C > S3 support was detected on QEMU > Install PPI: 7408D748-FC8C-4EE6-9288-C4BEC092A410 > Select Item: 0x19 > Select Item: 0x19 > Select Item: 0x25 > Select Item: 0x19 > Select Item: 0x19 > PlatformAddressWidthFromCpuid: Signature: 'GenuineIntel', PhysBits: 39, > QemuQuirk: On, Valid: Yes > PlatformDynamicMmioWindow: using dynamic mmio window > PlatformDynamicMmioWindow: Addr Space 0x8000000000 (512 GB) > PlatformDynamicMmioWindow: MMIO Space 0x1000000000 (64 GB) > Select Item: 0x19 > Select Item: 0x25 > PlatformDynamicMmioWindow: Pci64 Base 0x7000000000 > PlatformDynamicMmioWindow: Pci64 Size 0x1000000000 > AddressWidthInitialization: Pci64Base=0x7000000000 Pci64Size=0x1000000000 > Select Item: 0x5 > PlatformMaxCpuCountInitialization: BootCpuCount=2 MaxCpuCount=4 > Q35TsegMbytesInitialization: QEMU offers an extended TSEG (16 MB) > Q35SmramAtDefaultSmbaseInitialization: SMRAM at default SMBASE found > Select Item: 0x19 > Select Item: 0x25 > PlatformGetLowMemoryCB: LowMemory=0x40000000 > PublishPeiMemory: PhysMemAddressWidth=39 PeiMemoryCap=67592 KB > PeiInstallPeiMemory MemoryBegin 0x3AD5E000, MemoryLength 0x4202000 > Select Item: 0x19 > Select Item: 0x25 > PlatformQemuInitializeRam called > Select Item: 0x19 > Select Item: 0x25 > Select Item: 0x19 > Select Item: 0x25 > PlatformAddHobCB: Reserved [0xFEFFC000, 0xFF000000) > Select Item: 0x19 > Select Item: 0x25 > Platform PEI Firmware Volume Initialization > Install PPI: 49EDB1C1-BF21-4761-BB12-EB0031AABB39 > Notify: PPI Guid: 49EDB1C1-BF21-4761-BB12-EB0031AABB39, Peim notify > entry point: 824202 > The 1th FV start address is 0x00000900000, size is 0x00D00000, handle is > 0x900000 > Register PPI Notify: 2AB86EF5-ECB5-4134-B556-3854CA1FE1B4 > Select Item: 0x19 > Select Item: 0x25 > Select Item: 0x19 > Register PPI Notify: EE16160A-E8BE-47A6-820A-C6900DB0250A > Select Item: 0x19 > Select Item: 0x26 > Register PPI Notify: EE16160A-E8BE-47A6-820A-C6900DB0250A > Temp Stack : BaseAddress=0x818000 Length=0x8000 > Temp Heap : BaseAddress=0x810000 Length=0x8000 > Total temporary memory: 65536 bytes. > temporary memory stack ever used: 28412 bytes. > temporary memory heap used for HobList: 5704 bytes. > temporary memory heap occupied by memory pages: 0 bytes. > Memory Allocation 0x0000000A 0x3EF60000 - 0x3EFFFFFF > Memory Allocation 0x0000000A 0x810000 - 0x81FFFF > Memory Allocation 0x0000000A 0x807000 - 0x807FFF > Memory Allocation 0x00000000 0x3F000000 - 0x3FFFFFFF > Memory Allocation 0x00000000 0x30000 - 0x4FFFF > Memory Allocation 0x0000000A 0x820000 - 0x8FFFFF > Memory Allocation 0x0000000A 0x900000 - 0x15FFFFF > Memory Allocation 0x0000000A 0x1600000 - 0x180FFFF > Memory Allocation 0x00000000 0xB0000000 - 0xBFFFFFFF > Old Stack size 32768, New stack size 131072 > Stack Hob: BaseAddress=0x3AD5E000 Length=0x20000 > Heap Offset = 0x3A56E000 Stack Offset = 0x3A55E000 > TemporaryRamMigration(0x810000, 0x3AD76000, 0x10000) > Loading PEIM 52C05B14-0B98-496C-BC3B-04B50211D680 > Loading PEIM at 0x0003EF55000 EntryPoint=0x0003EF5C5A3 PeiCore.efi > Reinstall PPI: 8C8CE578-8A3D-4F1C-9935-896185C32DD3 > Reinstall PPI: 5473C07A-3DCB-4DCA-BD6F-1E9689E7349A > Reinstall PPI: B9E0ABFE-5979-4914-977F-6DEE78C278A6 > Install PPI: F894643D-C449-42D1-8EA8-85BDD8C65BDE > Loading PEIM 9B3ADA4F-AE56-4C24-8DEA-F03B7558AE50 > Loading PEIM at 0x0003EF50000 EntryPoint=0x0003EF52AF2 PcdPeim.efi > Reinstall PPI: 06E81C58-4AD7-44BC-8390-F10265F72480 > Reinstall PPI: 4D8B155B-C059-4C8F-8926-06FD4331DB8A > Reinstall PPI: 01F34D25-4DE2-23AD-3FF3-36353FF323F1 > Reinstall PPI: A60C6B59-E459-425D-9C69-0BCC9CB27D81 > Loading PEIM 86D70125-BAA3-4296-A62F-602BEBBB9081 > Loading PEIM at 0x0003EF4B000 EntryPoint=0x0003EF4DE83 DxeIpl.efi > Install PPI: 1A36E4E7-FAB6-476A-8E75-695A0576FDD7 > Install PPI: 0AE8CE5D-E448-4437-A8D7-EBF5F194F731 > Loading PEIM 89E549B0-7CFE-449D-9BA3-10D8B2312D71 > Loading PEIM at 0x0003EF46000 EntryPoint=0x0003EF488A2 > S3Resume2Pei.efi > Install PPI: 6D582DBC-DB85-4514-8FCC-5ADF6227B147 > Loading PEIM AAC33064-9ED0-4B89-A5AD-3EA767960B22 > Loading PEIM at 0x0003EF43000 EntryPoint=0x0003EF4417F > FaultTolerantWritePei.efi > Install PPI: 1D3E9CB8-43AF-490B-830A-3516AA532047 > Loading PEIM 34C8C28F-B61C-45A2-8F2E-89E46BECC63B > Loading PEIM at 0x0003EF40000 EntryPoint=0x0003EF41E96 PeiVariable.efi > Install PPI: 2AB86EF5-ECB5-4134-B556-3854CA1FE1B4 > Notify: PPI Guid: 2AB86EF5-ECB5-4134-B556-3854CA1FE1B4, Peim notify > entry point: 835496 > RefreshMemTypeInfo: GetVariable(): Not Found > Loading PEIM 6C0E75B4-B0B9-44D1-8210-3377D7B4E066 > Loading PEIM at 0x0003EF3D000 EntryPoint=0x0003EF3E371 > SmmAccessPei.efi > Install PPI: 268F33A9-CCCD-48BE-8817-86053AC32ED6 > Loading PEIM EDADEB9D-DDBA-48BD-9D22-C1C169C8C5C6 > Loading PEIM at 0x0003EF32000 EntryPoint=0x0003EF37D0D CpuMpPei.efi > Register PPI Notify: F894643D-C449-42D1-8EA8-85BDD8C65BDE > Notify: PPI Guid: F894643D-C449-42D1-8EA8-85BDD8C65BDE, Peim notify > entry point: 3EF367E9 > AP Loop Mode is 1 > AP Vector: non-16-bit = 3EF08000/DC > WakeupBufferStart = 2F000, WakeupBufferSize = 0 > AP Vector: 16-bit = 2F000/41, ExchangeInfo = 2F041/5C > CpuMpPei: 5-Level Paging = 0 > APIC MODE is 1 > MpInitLib: Find 2 processors in system. > GetMicrocodePatchInfoFromHob: Microcode patch cache HOB is not found. > CpuMpPei: 5-Level Paging = 0 > CPU[0000]: Microcode revision = 00000000, expected = 00000000 > CPU[0001]: Microcode revision = 00000000, expected = 00000000 > Register PPI Notify: 8F9D4825-797D-48FC-8471-845025792EF6 > Does not find any stored CPU BIST information from PPI! > APICID - 0x00000000, BIST - 0x00000000 > APICID - 0x00000001, BIST - 0x00000000 > Install PPI: 9E9F374B-8F16-4230-9824-5846EE766A97 > Install PPI: 5CB9CB3D-31A4-480C-9498-29D269BACFBA > Install PPI: EE16160A-E8BE-47A6-820A-C6900DB0250A > Notify: PPI Guid: EE16160A-E8BE-47A6-820A-C6900DB0250A, Peim notify > entry point: 8351C8 > PlatformPei: ClearCacheOnMpServicesAvailable > CpuMpPei: 5-Level Paging = 0 > Notify: PPI Guid: EE16160A-E8BE-47A6-820A-C6900DB0250A, Peim notify > entry point: 836A02 > CpuMpPei: 5-Level Paging = 0 > Loading PEIM F12F698A-E506-4A1B-B32E-6920E55DA1C4 > Loading PEIM at 0x0003EF06000 EntryPoint=0x0003EF06DAB > TpmMmioSevDecryptPei.efi > TpmMmioSevDecryptPeimEntryPoint > Install PPI: 35C84FF2-7BFE-453D-845F-683A492CF7B7 > Loading PEIM 8AD3148F-945F-46B4-8ACD-71469EA73945 > Loading PEIM at 0x0003EF03000 EntryPoint=0x0003EF04137 Tcg2ConfigPei.efi > Tcg2ConfigPeimEntryPoint > Tcg2ConfigPeimEntryPoint: no TPM detected > Install PPI: A030D115-54DD-447B-9064-F206883D7CCC > Install PPI: 7F4158D3-074D-456D-8CB2-01F9C8F79DAA > Loading PEIM 2BE1E4A6-6505-43B3-9FFC-A3C8330E0432 > Loading PEIM at 0x0003EEFE000 EntryPoint=0x0003EF004AD TcgPei.efi > No TPM12 instance required! > Loading PEIM A0C98B77-CBA5-4BB8-993B-4AF6CE33ECE4 > Loading PEIM at 0x0003EEF1000 EntryPoint=0x0003EEF9AEE Tcg2Pei.efi > No TPM2 instance required! > Loading PEIM 47727552-A54B-4A84-8CC1-BFF23E239636 > Loading PEIM at 0x0003EEED000 EntryPoint=0x0003EEEF11A > Tcg2PlatformPei.efi > DiscoverPeimsAndOrderWithApriori(): Found 0x0 PEI FFS files in the 1th FV > DXE IPL Entry > Loading PEIM D6A2CB7F-6A18-4E2F-B43B-9920A733700A > Loading PEIM at 0x0003EEC1000 EntryPoint=0x0003EED2946 DxeCore.efi > Loading DXE CORE at 0x0003EEC1000 EntryPoint=0x0003EED2946 > AddressBits=39 5LevelPaging=0 1GPage=0 > Pml5=1 Pml4=1 Pdp=512 TotalPage=514 > Install PPI: 605EA650-C65C-42E1-BA80-91A52AB618C6 > Notify: PPI Guid: 605EA650-C65C-42E1-BA80-91A52AB618C6, Peim notify > entry point: 82CB08 > HandOffToDxeCore() Stack Base: 0x3EEA1000, Stack Size: 0x20000 > CoreInitializeMemoryServices: > BaseAddress - 0x3AD81000 Length - 0x3C7E000 MinimalMemorySizeNeeded > - 0x322000 > InstallProtocolInterface: 5B1B31A1-9562-11D2-8E3F-00A0C969723B 3EEE3168 > ProtectUefiImageCommon - 0x3EEE3168 > - 0x000000003EEC1000 - 0x000000000002C000 > DxeMain: MemoryBaseAddress=0x3AD81000 MemoryLength=0x3C7E000 > HOBLIST address in DXE = 0x3E6E7018 > Memory Allocation 0x0000000A 0x3EF60000 - 0x3EFFFFFF > Memory Allocation 0x0000000A 0x810000 - 0x81FFFF > Memory Allocation 0x0000000A 0x807000 - 0x807FFF > Memory Allocation 0x00000000 0x3F000000 - 0x3FFFFFFF > Memory Allocation 0x00000000 0x30000 - 0x4FFFF > Memory Allocation 0x0000000A 0x820000 - 0x8FFFFF > Memory Allocation 0x0000000A 0x900000 - 0x15FFFFF > Memory Allocation 0x0000000A 0x1600000 - 0x180FFFF > Memory Allocation 0x00000000 0xB0000000 - 0xBFFFFFFF > Memory Allocation 0x00000004 0x3EEA1000 - 0x3EEC0FFF > Memory Allocation 0x00000003 0x3EF55000 - 0x3EF5FFFF > Memory Allocation 0x00000003 0x3EF50000 - 0x3EF54FFF > Memory Allocation 0x00000003 0x3EF4B000 - 0x3EF4FFFF > Memory Allocation 0x00000003 0x3EF46000 - 0x3EF4AFFF > Memory Allocation 0x00000003 0x3EF43000 - 0x3EF45FFF > Memory Allocation 0x00000003 0x3EF40000 - 0x3EF42FFF > Memory Allocation 0x00000003 0x3EF3D000 - 0x3EF3FFFF > Memory Allocation 0x00000003 0x3EF32000 - 0x3EF3CFFF > Memory Allocation 0x00000004 0x3EF09000 - 0x3EF31FFF > Memory Allocation 0x00000003 0x3EF08000 - 0x3EF08FFF > Memory Allocation 0x00000003 0x3EF06000 - 0x3EF07FFF > Memory Allocation 0x00000003 0x3EF03000 - 0x3EF05FFF > Memory Allocation 0x00000003 0x3EEFE000 - 0x3EF02FFF > Memory Allocation 0x00000003 0x3EEF1000 - 0x3EEFDFFF > Memory Allocation 0x00000003 0x3EEED000 - 0x3EEF0FFF > Memory Allocation 0x00000003 0x3EEC1000 - 0x3EEECFFF > Memory Allocation 0x00000003 0x3EEC1000 - 0x3EEECFFF > Memory Allocation 0x00000004 0x3EEA1000 - 0x3EEC0FFF > Memory Allocation 0x00000004 0x3EA00000 - 0x3EDFFFFF > Memory Allocation 0x00000007 0x3EE00000 - 0x3EEA0FFF > Memory Allocation 0x00000004 0x3AD5E000 - 0x3AD7DFFF > Memory Allocation 0x00000004 0x3E9FF000 - 0x3E9FFFFF > FV Hob 0x900000 - 0x15FFFFF > InstallProtocolInterface: D8117CFE-94A6-11D4-9A3A-0090273FC14D 3EEE38E0 > InstallProtocolInterface: 8F644FA9-E850-4DB1-9CE2-0B44698E8DA4 3E6E38B0 > InstallProtocolInterface: 09576E91-6D3F-11D2-8E39-00A0C969723B 3E6E3998 > InstallProtocolInterface: 220E73B6-6BDB-4413-8405-B974B108619A 3E6E33B0 > InstallProtocolInterface: EE4E5898-3914-4259-9D6E-DC7BD79403CF 3EEE37F8 > Loading driver 9B680FCE-AD6B-4F3A-B60B-F59899003443 > InstallProtocolInterface: 5B1B31A1-9562-11D2-8E3F-00A0C969723B 3E18B040 > Loading driver at 0x0003E17F000 EntryPoint=0x0003E186E1D > DevicePathDxe.efi > InstallProtocolInterface: BC62157E-3E33-4FEC-9920-2D3B36D750DF 3E18BD98 > ProtectUefiImageCommon - 0x3E18B040 > - 0x000000003E17F000 - 0x000000000000B400 > InstallProtocolInterface: 0379BE4E-D706-437D-B037-EDB82FB772A4 3E189700 > InstallProtocolInterface: 8B843E20-8132-4852-90CC-551A4E4A7F1C 3E1896E0 > InstallProtocolInterface: 05C99A21-C70F-4AD2-8A5F-35DF3343F51E 3E1896C0 > Loading driver 80CF7257-87AB-47F9-A3FE-D50B76D89541 > InstallProtocolInterface: 5B1B31A1-9562-11D2-8E3F-00A0C969723B 3E18B3C0 > Loading driver at 0x0003E18C000 EntryPoint=0x0003E18F976 PcdDxe.efi > InstallProtocolInterface: BC62157E-3E33-4FEC-9920-2D3B36D750DF 3E18B998 > ProtectUefiImageCommon - 0x3E18B3C0 > - 0x000000003E18C000 - 0x0000000000005D00 > InstallProtocolInterface: 11B34006-D85B-4D0A-A290-D5A571310EF7 3E1919C0 > InstallProtocolInterface: 13A3F0F6-264A-3EF0-F2E0-DEC512342F34 3E191920 > InstallProtocolInterface: 5BE40F57-FA68-4610-BBBF-E9C5FCDAD365 3E1918F0 > InstallProtocolInterface: FD0F4478-0EFD-461D-BA2D-E58C45FD5F5E 3E1918D0 > Loading driver 2EC9DA37-EE35-4DE9-86C5-6D9A81DC38A7 > InstallProtocolInterface: 5B1B31A1-9562-11D2-8E3F-00A0C969723B 3E196BC0 > Loading driver at 0x0003E17B000 EntryPoint=0x0003E17D1E6 AmdSevDxe.efi > InstallProtocolInterface: BC62157E-3E33-4FEC-9920-2D3B36D750DF 3E196F18 > ProtectUefiImageCommon - 0x3E196BC0 > - 0x000000003E17B000 - 0x0000000000003D80 > Error: Image at 0003E17B000 start failed: Unsupported > Loading driver D93CE3D8-A7EB-4730-8C8E-CC466A9ECC3C > InstallProtocolInterface: 5B1B31A1-9562-11D2-8E3F-00A0C969723B 3E196BC0 > Loading driver at 0x0003E8E6000 EntryPoint=0x0003E8E87D4 > ReportStatusCodeRouterRuntimeDxe.efi > InstallProtocolInterface: BC62157E-3E33-4FEC-9920-2D3B36D750DF 3E196B18 > ProtectUefiImageCommon - 0x3E196BC0 > - 0x000000003E8E6000 - 0x0000000000006000 > InstallProtocolInterface: 86212936-0E76-41C8-A03A-2AF2FC1C39E2 3E8EA060 > InstallProtocolInterface: D2B2B828-0826-48A7-B3DF-983C006024F0 3E8EA040 > Loading driver B601F8C4-43B7-4784-95B1-F4226CB40CEE > InstallProtocolInterface: 5B1B31A1-9562-11D2-8E3F-00A0C969723B 3E196340 > Loading driver at 0x0003E8E0000 EntryPoint=0x0003E8E24FF RuntimeDxe.efi > InstallProtocolInterface: BC62157E-3E33-4FEC-9920-2D3B36D750DF 3E193B18 > ProtectUefiImageCommon - 0x3E196340 > - 0x000000003E8E0000 - 0x0000000000006000 > InstallProtocolInterface: B7DFB4E1-052F-449F-87BE-9818FC91B733 3E8E4080 > Loading driver F80697E9-7FD6-4665-8646-88E33EF71DFC > InstallProtocolInterface: 5B1B31A1-9562-11D2-8E3F-00A0C969723B 3E1931C0 > Loading driver at 0x0003E093000 EntryPoint=0x0003E0CFEB6 > SecurityStubDxe.efi > InstallProtocolInterface: BC62157E-3E33-4FEC-9920-2D3B36D750DF 3E193918 > ProtectUefiImageCommon - 0x3E1931C0 > - 0x000000003E093000 - 0x0000000000075040 > InstallProtocolInterface: 94AB2F58-1438-4EF1-9152-18941A3A0E68 3E104758 > InstallProtocolInterface: A46423E3-4617-49F1-B9FF-D1BFA9115839 3E104750 > InstallProtocolInterface: 15853D7C-3DDF-43E0-A1CB-EBF85B8F872C 3E104730 > Loading driver 13AC6DD0-73D0-11D4-B06B-00AA00BD6DE7 > None of Tcg2Protocol/CcMeasurementProtocol is installed. > InstallProtocolInterface: 5B1B31A1-9562-11D2-8E3F-00A0C969723B 3E192940 > Loading driver at 0x0003E172000 EntryPoint=0x0003E1765BA EbcDxe.efi > InstallProtocolInterface: BC62157E-3E33-4FEC-9920-2D3B36D750DF 3E192898 > ProtectUefiImageCommon - 0x3E192940 > - 0x000000003E172000 - 0x0000000000006000 > InstallProtocolInterface: 13AC6DD1-73D0-11D4-B06B-00AA00BD6DE7 > 3E192818 > InstallProtocolInterface: 96F46153-97A7-4793-ACC1-FA19BF78EA97 3E177A20 > InstallProtocolInterface: 2755590C-6F3C-42FA-9EA4-A3BA543CDA25 3E17E018 > InstallProtocolInterface: AAEACCFD-F27B-4C17-B610-75CA1F2DFB52 > 3E17EE98 > Loading driver A19B1FE7-C1BC-49F8-875F-54A5D542443F > None of Tcg2Protocol/CcMeasurementProtocol is installed. > InstallProtocolInterface: 5B1B31A1-9562-11D2-8E3F-00A0C969723B 3E17E0C0 > Loading driver at 0x0003E178000 EntryPoint=0x0003E179455 CpuIo2Dxe.efi > InstallProtocolInterface: BC62157E-3E33-4FEC-9920-2D3B36D750DF 3E192318 > ProtectUefiImageCommon - 0x3E17E0C0 > - 0x000000003E178000 - 0x00000000000020C0 > InstallProtocolInterface: AD61F191-AE5F-4C0E-B9FA-E869D288C64F 3E179F80 > Loading driver 1A1E4886-9517-440E-9FDE-3BE44CEE2136 > None of Tcg2Protocol/CcMeasurementProtocol is installed. > InstallProtocolInterface: 5B1B31A1-9562-11D2-8E3F-00A0C969723B 3E17E540 > Loading driver at 0x0003E142000 EntryPoint=0x0003E14B242 CpuDxe.efi > InstallProtocolInterface: BC62157E-3E33-4FEC-9920-2D3B36D750DF 3E17D018 > ProtectUefiImageCommon - 0x3E17E540 > - 0x000000003E142000 - 0x0000000000017580 > Paging: added 512 pages to page table pool > CurrentPagingContext: > MachineType - 0x8664 > PageTableBase - 0x3EA01000 > Attributes - 0xC0000006 > InstallProtocolInterface: 26BACCB1-6F42-11D4-BCE7-0080C73C8881 3E1529E0 > MemoryProtectionCpuArchProtocolNotify: > ProtectUefiImageCommon - 0x3EEE3168 > - 0x000000003EEC1000 - 0x000000000002C000 > ProtectUefiImageCommon - 0x3E18B040 > - 0x000000003E17F000 - 0x000000000000B400 > ProtectUefiImageCommon - 0x3E18B3C0 > - 0x000000003E18C000 - 0x0000000000005D00 > ProtectUefiImageCommon - 0x3E196BC0 > - 0x000000003E8E6000 - 0x0000000000006000 > SetUefiImageMemoryAttributes - 0x000000003E8E6000 - > 0x0000000000001000 (0x0000000000004000) > SetUefiImageMemoryAttributes - 0x000000003E8E7000 - > 0x0000000000003000 (0x0000000000020000) > SetUefiImageMemoryAttributes - 0x000000003E8EA000 - > 0x0000000000002000 (0x0000000000004000) > ProtectUefiImageCommon - 0x3E196340 > - 0x000000003E8E0000 - 0x0000000000006000 > SetUefiImageMemoryAttributes - 0x000000003E8E0000 - > 0x0000000000001000 (0x0000000000004000) > SetUefiImageMemoryAttributes - 0x000000003E8E1000 - > 0x0000000000003000 (0x0000000000020000) > SetUefiImageMemoryAttributes - 0x000000003E8E4000 - > 0x0000000000002000 (0x0000000000004000) > ProtectUefiImageCommon - 0x3E1931C0 > - 0x000000003E093000 - 0x0000000000075040 > ProtectUefiImageCommon - 0x3E192940 > - 0x000000003E172000 - 0x0000000000006000 > ProtectUefiImageCommon - 0x3E17E0C0 > - 0x000000003E178000 - 0x00000000000020C0 > ProtectUefiImageCommon - 0x3E17E540 > - 0x000000003E142000 - 0x0000000000017580 > ConvertPages: failed to find range 30000 - 4FFFF > ConvertPages: failed to find range A0000 - FFFFF > ConvertPages: failed to find range 3F000000 - 3FFFFFFF > ConvertPages: failed to find range B0000000 - BFFFFFFF > ConvertPages: failed to find range C0000000 - FBFFFFFF > ConvertPages: failed to find range FEC00000 - FEC00FFF > Failed to update capability: [12] 00000000FED00000 - 00000000FED003FF > (C700000000000001 -> C700000000026001) > ConvertPages: failed to find range FED1C000 - FED1FFFF > ConvertPages: failed to find range FEE00000 - FEEFFFFF > ConvertPages: failed to find range FEFFC000 - FEFFFFFF > AP Loop Mode is 1 > AP Vector: non-16-bit = 3E170000/32A > GetMicrocodePatchInfoFromHob: MicrocodeBase = 0x0, MicrocodeSize = > 0x0 > WakeupBufferStart = 87000, WakeupBufferSize = DD > AP Vector: 16-bit = 87000/39, ExchangeInfo = 87039/A4 > CpuDxe: 5-Level Paging = 0 > CPU[0000]: Microcode revision = 00000000, expected = 00000000 > CPU[0001]: Microcode revision = 00000000, expected = 00000000 > Detect CPU count: 2 > InstallProtocolInterface: 3FDDA605-A76E-4F46-AD29-12F4531B3D08 3E152AE0 > Loading driver F6697AC4-A776-4EE1-B643-1FEFF2B615BB > None of Tcg2Protocol/CcMeasurementProtocol is installed. > InstallProtocolInterface: 5B1B31A1-9562-11D2-8E3F-00A0C969723B 3E1716C0 > Loading driver at 0x0003E16B000 EntryPoint=0x0003E16C100 > IncompatiblePciDeviceSupportDxe.efi > InstallProtocolInterface: BC62157E-3E33-4FEC-9920-2D3B36D750DF 3E171298 > ProtectUefiImageCommon - 0x3E1716C0 > - 0x000000003E16B000 - 0x0000000000002000 > InstallProtocolInterface: EB23F55A-7863-4AC2-8D3D-956535DE0375 3E16CF00 > Loading driver 11A6EDF6-A9BE-426D-A6CC-B22FE51D9224 > None of Tcg2Protocol/CcMeasurementProtocol is installed. > InstallProtocolInterface: 5B1B31A1-9562-11D2-8E3F-00A0C969723B 3E16FB40 > Loading driver at 0x0003E161000 EntryPoint=0x0003E164408 > PciHotPlugInitDxe.efi > InstallProtocolInterface: BC62157E-3E33-4FEC-9920-2D3B36D750DF 3E16FE18 > ProtectUefiImageCommon - 0x3E16FB40 > - 0x000000003E161000 - 0x0000000000004CC0 > InstallProtocolInterface: AA0E8BC1-DABC-46B0-A844-37B8169B2BEA > 3E165BD0 > Loading driver 4B28E4C7-FF36-4E10-93CF-A82159E777C5 > None of Tcg2Protocol/CcMeasurementProtocol is installed. > InstallProtocolInterface: 5B1B31A1-9562-11D2-8E3F-00A0C969723B 3E16F140 > Loading driver at 0x0003E8D9000 EntryPoint=0x0003E8DB995 > ResetSystemRuntimeDxe.efi > InstallProtocolInterface: BC62157E-3E33-4FEC-9920-2D3B36D750DF 3E16F418 > ProtectUefiImageCommon - 0x3E16F140 > - 0x000000003E8D9000 - 0x0000000000007000 > SetUefiImageMemoryAttributes - 0x000000003E8D9000 - > 0x0000000000001000 (0x0000000000004008) > SetUefiImageMemoryAttributes - 0x000000003E8DA000 - > 0x0000000000004000 (0x0000000000020008) > SetUefiImageMemoryAttributes - 0x000000003E8DE000 - > 0x0000000000002000 (0x0000000000004008) > InstallProtocolInterface: 27CFAC88-46CC-11D4-9A38-0090273FC14D 0 > InstallProtocolInterface: 9DA34AE0-EAF9-4BBF-8EC3-FD60226C44BE 3E8DE108 > InstallProtocolInterface: 695D7835-8D47-4C11-AB22-FA8ACCE7AE7A > 3E8DE148 > InstallProtocolInterface: 2DF6BA0B-7092-440D-BD04-FB091EC3F3C1 3E8DE0C8 > Loading driver C8339973-A563-4561-B858-D8476F9DEFC4 > None of Tcg2Protocol/CcMeasurementProtocol is installed. > InstallProtocolInterface: 5B1B31A1-9562-11D2-8E3F-00A0C969723B 3E16E240 > Loading driver at 0x0003E15E000 EntryPoint=0x0003E15F108 Metronome.efi > InstallProtocolInterface: BC62157E-3E33-4FEC-9920-2D3B36D750DF 3E16E998 > ProtectUefiImageCommon - 0x3E16E240 > - 0x000000003E15E000 - 0x00000000000023C0 > InstallProtocolInterface: 26BACCB2-6F42-11D4-BCE7-0080C73C8881 3E160230 > Loading driver 348C4D62-BFBD-4882-9ECE-C80BB1C4783B > None of Tcg2Protocol/CcMeasurementProtocol is installed. > InstallProtocolInterface: 5B1B31A1-9562-11D2-8E3F-00A0C969723B 3E16D040 > Loading driver at 0x0003DC76000 EntryPoint=0x0003DC8E4BF HiiDatabase.efi > InstallProtocolInterface: BC62157E-3E33-4FEC-9920-2D3B36D750DF 3E16DD18 > ProtectUefiImageCommon - 0x3E16D040 > - 0x000000003DC76000 - 0x000000000001CD40 > InstallProtocolInterface: E9CA4775-8657-47FC-97E7-7ED65A084324 3DC928E8 > InstallProtocolInterface: 0FD96974-23AA-4CDC-B9CB-98D17750322A > 3DC92960 > InstallProtocolInterface: EF9FC172-A1B2-4693-B327-6D32FC416042 3DC92988 > InstallProtocolInterface: 587E72D7-CC50-4F79-8209-CA291FC1A10F 3DC929E0 > InstallProtocolInterface: 0A8BADD5-03B8-4D19-B128-7B8F0EDAA596 > 3DC92A10 > InstallProtocolInterface: 31A6406A-6BDF-4E46-B2A2-EBAA89C40920 > 3DC92908 > InstallProtocolInterface: 1A1241E6-8F19-41A9-BC0E-E8EF39E06546 3DC92930 > Loading driver 96B5C032-DF4C-4B6E-8232-438DCF448D0E > None of Tcg2Protocol/CcMeasurementProtocol is installed. > InstallProtocolInterface: 5B1B31A1-9562-11D2-8E3F-00A0C969723B 3E167040 > Loading driver at 0x0003E15B000 EntryPoint=0x0003E15C166 > NullMemoryTestDxe.efi > InstallProtocolInterface: BC62157E-3E33-4FEC-9920-2D3B36D750DF 3E16D398 > ProtectUefiImageCommon - 0x3E167040 > - 0x000000003E15B000 - 0x00000000000021C0 > InstallProtocolInterface: 309DE7F1-7F5E-4ACE-B49C-531BE5AA95EF 3E15D020 > Loading driver 9622E42C-8E38-4A08-9E8F-54F784652F6B > None of Tcg2Protocol/CcMeasurementProtocol is installed. > InstallProtocolInterface: 5B1B31A1-9562-11D2-8E3F-00A0C969723B 3E167440 > Loading driver at 0x0003E118000 EntryPoint=0x0003E11C206 AcpiTableDxe.efi > InstallProtocolInterface: BC62157E-3E33-4FEC-9920-2D3B36D750DF 3E167B98 > ProtectUefiImageCommon - 0x3E167440 > - 0x000000003E118000 - 0x0000000000007700 > InstallProtocolInterface: FFE06BDD-6107-46A6-7BB2-5A9C7EC5275C > 3E16A0A0 > InstallProtocolInterface: EB97088E-CFDF-49C6-BE4B-D906A5B20E86 3E16A0B0 > Loading driver BDCE85BB-FBAA-4F4E-9264-501A2C249581 > None of Tcg2Protocol/CcMeasurementProtocol is installed. > InstallProtocolInterface: 5B1B31A1-9562-11D2-8E3F-00A0C969723B 3E16ACC0 > Loading driver at 0x0003E111000 EntryPoint=0x0003E1151A8 > S3SaveStateDxe.efi > InstallProtocolInterface: BC62157E-3E33-4FEC-9920-2D3B36D750DF 3E16AB18 > ProtectUefiImageCommon - 0x3E16ACC0 > - 0x000000003E111000 - 0x00000000000063C0 > InstallProtocolInterface: E857CAF6-C046-45DC-BE3F-EE0765FBA887 3E117100 > Loading driver A210F973-229D-4F4D-AA37-9895E6C9EABA > None of Tcg2Protocol/CcMeasurementProtocol is installed. > InstallProtocolInterface: 5B1B31A1-9562-11D2-8E3F-00A0C969723B 3E16A3C0 > Loading driver at 0x0003E122000 EntryPoint=0x0003E123270 DpcDxe.efi > InstallProtocolInterface: BC62157E-3E33-4FEC-9920-2D3B36D750DF 3E169F98 > ProtectUefiImageCommon - 0x3E16A3C0 > - 0x000000003E122000 - 0x0000000000002080 > InstallProtocolInterface: 480F8AE9-0C46-4AA9-BC89-DB9FBA619806 3E123D40 > Loading driver 22EA234F-E72A-11E4-91F9-28D2447C4829 > None of Tcg2Protocol/CcMeasurementProtocol is installed. > InstallProtocolInterface: 5B1B31A1-9562-11D2-8E3F-00A0C969723B 3E1697C0 > Loading driver at 0x0003E10E000 EntryPoint=0x0003E10FACE > HttpUtilitiesDxe.efi > InstallProtocolInterface: BC62157E-3E33-4FEC-9920-2D3B36D750DF 3E169118 > ProtectUefiImageCommon - 0x3E1697C0 > - 0x000000003E10E000 - 0x0000000000002C40 > InstallProtocolInterface: 3E35C163-4074-45DD-431E-23989DD86B32 3E110AD0 > Loading driver 8657015B-EA43-440D-949A-AF3BE365C0FC > None of Tcg2Protocol/CcMeasurementProtocol is installed. > InstallProtocolInterface: 5B1B31A1-9562-11D2-8E3F-00A0C969723B 3E168040 > Loading driver at 0x0003DC71000 EntryPoint=0x0003DC73E8E IoMmuDxe.efi > InstallProtocolInterface: BC62157E-3E33-4FEC-9920-2D3B36D750DF 3E169418 > ProtectUefiImageCommon - 0x3E168040 > - 0x000000003DC71000 - 0x0000000000004B40 > InstallProtocolInterface: F8775D50-8ABD-4ADF-92AC-853E51F6C8DC 0 > Loading driver AC95AD3D-4366-44BF-9A62-E4B29D7A2206 > None of Tcg2Protocol/CcMeasurementProtocol is installed. > InstallProtocolInterface: 5B1B31A1-9562-11D2-8E3F-00A0C969723B 3E1689C0 > Loading driver at 0x0003E120000 EntryPoint=0x0003E1213B2 > SmmAccess2Dxe.efi > InstallProtocolInterface: BC62157E-3E33-4FEC-9920-2D3B36D750DF 3E168798 > ProtectUefiImageCommon - 0x3E1689C0 > - 0x000000003E120000 - 0x0000000000001EC0 > InstallProtocolInterface: C2702B74-800C-4131-8746-8FB5B89CE4AC 3E121D60 > Loading driver A5683620-7998-4BB2-A377-1C1E31E1E215 > None of Tcg2Protocol/CcMeasurementProtocol is installed. > InstallProtocolInterface: 5B1B31A1-9562-11D2-8E3F-00A0C969723B 3E166040 > Loading driver at 0x0003DC6C000 EntryPoint=0x0003DC6EA13 TcgDxe.efi > InstallProtocolInterface: BC62157E-3E33-4FEC-9920-2D3B36D750DF 3E168518 > ProtectUefiImageCommon - 0x3E166040 > - 0x000000003DC6C000 - 0x0000000000004BC0 > No TPM12 instance required! > Error: Image at 0003DC6C000 start failed: Unsupported > Loading driver 6C2004EF-4E0E-4BE4-B14C-340EB4AA5891 > None of Tcg2Protocol/CcMeasurementProtocol is installed. > InstallProtocolInterface: 5B1B31A1-9562-11D2-8E3F-00A0C969723B 3E166040 > Loading driver at 0x0003E8D4000 EntryPoint=0x0003E8D6017 > StatusCodeHandlerRuntimeDxe.efi > InstallProtocolInterface: BC62157E-3E33-4FEC-9920-2D3B36D750DF 3E166E18 > ProtectUefiImageCommon - 0x3E166040 > - 0x000000003E8D4000 - 0x0000000000005000 > SetUefiImageMemoryAttributes - 0x000000003E8D4000 - > 0x0000000000001000 (0x0000000000004008) > SetUefiImageMemoryAttributes - 0x000000003E8D5000 - > 0x0000000000003000 (0x0000000000020008) > SetUefiImageMemoryAttributes - 0x000000003E8D8000 - > 0x0000000000001000 (0x0000000000004008) > Loading driver 52FE8196-F9DE-4D07-B22F-51F77A0E7C41 > None of Tcg2Protocol/CcMeasurementProtocol is installed. > InstallProtocolInterface: 5B1B31A1-9562-11D2-8E3F-00A0C969723B 3E166540 > Loading driver at 0x0003E10B000 EntryPoint=0x0003E10C794 > LocalApicTimerDxe.efi > InstallProtocolInterface: BC62157E-3E33-4FEC-9920-2D3B36D750DF 3E166898 > ProtectUefiImageCommon - 0x3E166540 > - 0x000000003E10B000 - 0x0000000000002E00 > InstallProtocolInterface: 26BACCB3-6F42-11D4-BCE7-0080C73C8881 3E10DC20 > Loading driver 128FB770-5E79-4176-9E51-9BB268A17DD1 > None of Tcg2Protocol/CcMeasurementProtocol is installed. > InstallProtocolInterface: 5B1B31A1-9562-11D2-8E3F-00A0C969723B 3E15ACC0 > Loading driver at 0x0003DC5D000 EntryPoint=0x0003DC63F0D > PciHostBridgeDxe.efi > InstallProtocolInterface: BC62157E-3E33-4FEC-9920-2D3B36D750DF 3E15AB18 > ProtectUefiImageCommon - 0x3E15ACC0 > - 0x000000003DC5D000 - 0x0000000000009D80 > Select Item: 0x0 > FW CFG Signature: 0x554D4551 > Select Item: 0x1 > FW CFG Revision: 0x3 > QemuFwCfg interface (DMA) is supported. > Select Item: 0x19 > Select Item: 0x19 > PciHostBridgeUtilityInitRootBridge: populated root bus 0, with room for 255 > subordinate bus(es) > RootBridge: PciRoot(0x0) > Support/Attr: 70069 / 70069 > DmaAbove4G: No > NoExtConfSpace: No > AllocAttr: 3 (CombineMemPMem Mem64Decode) > Bus: 0 - FF Translation=0 > Io: 6000 - FFFF Translation=0 > Mem: C0000000 - FBFFFFFF Translation=0 > MemAbove4G: 7000000000 - 7FFFFFFFFF Translation=0 > PMem: FFFFFFFFFFFFFFFF - 0 Translation=0 > PMemAbove4G: FFFFFFFFFFFFFFFF - 0 Translation=0 > CpuDxe: 5-Level Paging = 0 > InstallProtocolInterface: CF8034BE-6768-4D8B-B739-7CCE683A9FBE 3E15A7C0 > InstallProtocolInterface: 09576E91-6D3F-11D2-8E39-00A0C969723B 3E15A318 > InstallProtocolInterface: 2F707EBB-4A1A-11D4-9A38-0090273FC14D 3E1271F0 > Loading driver EBF342FE-B1D3-4EF8-957C-8048606FF671 > None of Tcg2Protocol/CcMeasurementProtocol is installed. > InstallProtocolInterface: 5B1B31A1-9562-11D2-8E3F-00A0C969723B 3E127B40 > Loading driver at 0x0003DC2B000 EntryPoint=0x0003DC3B289 > SetupBrowser.efi > InstallProtocolInterface: BC62157E-3E33-4FEC-9920-2D3B36D750DF 3E127998 > ProtectUefiImageCommon - 0x3E127B40 > - 0x000000003DC2B000 - 0x0000000000018AC0 > InstallProtocolInterface: B9D4C360-BCFB-4F9B-9298-53C136982258 3DC435B0 > InstallProtocolInterface: A770C357-B693-4E6D-A6CF-D21C728E550B 3DC435E0 > InstallProtocolInterface: 1F73B18D-4630-43C1-A1DE-6F80855D7DA4 > 3DC435C0 > Loading driver F9D88642-0737-49BC-81B5-6889CD57D9EA > None of Tcg2Protocol/CcMeasurementProtocol is installed. > InstallProtocolInterface: 5B1B31A1-9562-11D2-8E3F-00A0C969723B 3E1260C0 > Loading driver at 0x0003DC57000 EntryPoint=0x0003DC5A332 SmbiosDxe.efi > InstallProtocolInterface: BC62157E-3E33-4FEC-9920-2D3B36D750DF 3E126A98 > ProtectUefiImageCommon - 0x3E1260C0 > - 0x000000003DC57000 - 0x0000000000005980 > Select Item: 0x0 > FW CFG Signature: 0x554D4551 > Select Item: 0x1 > FW CFG Revision: 0x3 > QemuFwCfg interface (DMA) is supported. > Select Item: 0x19 > Select Item: 0x19 > Select Item: 0x27 > DetectSmbiosVersion: SMBIOS version from QEMU: 0x0208 > InstallProtocolInterface: 03583FF6-CB36-4940-947E-B9B39F4AFAF7 3DC5C810 > Loading driver 17985E6F-E778-4D94-AEFA-C5DD2B77E186 > None of Tcg2Protocol/CcMeasurementProtocol is installed. > InstallProtocolInterface: 5B1B31A1-9562-11D2-8E3F-00A0C969723B 3E125040 > Loading driver at 0x0003DC50000 EntryPoint=0x0003DC546C6 > QemuFwCfgAcpiPlatform.efi > InstallProtocolInterface: BC62157E-3E33-4FEC-9920-2D3B36D750DF 3E126598 > ProtectUefiImageCommon - 0x3E125040 > - 0x000000003DC50000 - 0x0000000000006D80 > Select Item: 0x0 > FW CFG Signature: 0x554D4551 > Select Item: 0x1 > FW CFG Revision: 0x3 > QemuFwCfg interface (DMA) is supported. > AcpiPlatformEntryPoint: waiting for root bridges to be connected, registered > callback > Loading driver A487A478-51EF-48AA-8794-7BEE2A0562F1 > None of Tcg2Protocol/CcMeasurementProtocol is installed. > InstallProtocolInterface: 5B1B31A1-9562-11D2-8E3F-00A0C969723B 3E125A40 > Loading driver at 0x0003DC20000 EntryPoint=0x0003DC26739 > tftpDynamicCommand.efi > InstallProtocolInterface: BC62157E-3E33-4FEC-9920-2D3B36D750DF 3E125398 > InstallProtocolInterface: 6A1EE763-D47A-43B4-AABE-EF1DE2AB56FC > 3DC28C70 > ProtectUefiImageCommon - 0x3E125A40 > - 0x000000003DC20000 - 0x000000000000A7C0 > InstallProtocolInterface: 3C7200E9-005F-4EA4-87DE-A3DFAC8A27C3 > 3DC289A0 > Loading driver 19618BCE-55AE-09C6-37E9-4CE04084C7A1 > None of Tcg2Protocol/CcMeasurementProtocol is installed. > InstallProtocolInterface: 5B1B31A1-9562-11D2-8E3F-00A0C969723B 3E10ABC0 > Loading driver at 0x0003DC06000 EntryPoint=0x0003DC0DF8C > httpDynamicCommand.efi > InstallProtocolInterface: BC62157E-3E33-4FEC-9920-2D3B36D750DF 3E10AA18 > InstallProtocolInterface: 6A1EE763-D47A-43B4-AABE-EF1DE2AB56FC > 3DC10AF0 > ProtectUefiImageCommon - 0x3E10ABC0 > - 0x000000003DC06000 - 0x000000000000CD80 > InstallProtocolInterface: 3C7200E9-005F-4EA4-87DE-A3DFAC8A27C3 > 3DC107F0 > Loading driver 2F30DA26-F51B-4B6F-85C4-31873C281BCA > None of Tcg2Protocol/CcMeasurementProtocol is installed. > InstallProtocolInterface: 5B1B31A1-9562-11D2-8E3F-00A0C969723B 3E109040 > Loading driver at 0x0003DC18000 EntryPoint=0x0003DC1CFED > LinuxInitrdDynamicShellCommand.efi > InstallProtocolInterface: BC62157E-3E33-4FEC-9920-2D3B36D750DF 3E10A398 > InstallProtocolInterface: 6A1EE763-D47A-43B4-AABE-EF1DE2AB56FC > 3DC1F0F0 > ProtectUefiImageCommon - 0x3E109040 > - 0x000000003DC18000 - 0x0000000000007C00 > InstallProtocolInterface: 3C7200E9-005F-4EA4-87DE-A3DFAC8A27C3 > 3DC1EDA0 > Loading driver F74D20EE-37E7-48FC-97F7-9B1047749C69 > None of Tcg2Protocol/CcMeasurementProtocol is installed. > InstallProtocolInterface: 5B1B31A1-9562-11D2-8E3F-00A0C969723B 3DC6BAC0 > Loading driver at 0x0003DC46000 EntryPoint=0x0003DC46F39 LogoDxe.efi > InstallProtocolInterface: BC62157E-3E33-4FEC-9920-2D3B36D750DF 3DC6BE18 > InstallProtocolInterface: 6A1EE763-D47A-43B4-AABE-EF1DE2AB56FC > 3DC47B30 > ProtectUefiImageCommon - 0x3DC6BAC0 > - 0x000000003DC46000 - 0x0000000000004A80 > InstallProtocolInterface: 53CD299F-2BC1-40C0-8C07-23F64FDB30E0 3DC47980 > Loading driver DCE1B094-7DC6-45D0-9FDD-D7FC3CC3E4EF > None of Tcg2Protocol/CcMeasurementProtocol is installed. > InstallProtocolInterface: 5B1B31A1-9562-11D2-8E3F-00A0C969723B 3DC6A440 > Loading driver at 0x0003DC13000 EntryPoint=0x0003DC1558E > QemuRamfbDxe.efi > InstallProtocolInterface: BC62157E-3E33-4FEC-9920-2D3B36D750DF 3DC6AE18 > ProtectUefiImageCommon - 0x3DC6A440 > - 0x000000003DC13000 - 0x0000000000004500 > Select Item: 0x0 > FW CFG Signature: 0x554D4551 > Select Item: 0x1 > FW CFG Revision: 0x3 > QemuFwCfg interface (DMA) is supported. > Select Item: 0x19 > Error: Image at 0003DC13000 start failed: Not Found > Loading driver 1206F7CA-A475-4624-A83E-E6FC9BB38E49 > None of Tcg2Protocol/CcMeasurementProtocol is installed. > InstallProtocolInterface: 5B1B31A1-9562-11D2-8E3F-00A0C969723B 3DC6A440 > Loading driver at 0x0003E8CD000 EntryPoint=0x0003E8D00E7 > SmmControl2Dxe.efi > InstallProtocolInterface: BC62157E-3E33-4FEC-9920-2D3B36D750DF 3DC6AC18 > ProtectUefiImageCommon - 0x3DC6A440 > - 0x000000003E8CD000 - 0x0000000000007000 > SetUefiImageMemoryAttributes - 0x000000003E8CD000 - > 0x0000000000001000 (0x0000000000004008) > SetUefiImageMemoryAttributes - 0x000000003E8CE000 - > 0x0000000000004000 (0x0000000000020008) > SetUefiImageMemoryAttributes - 0x000000003E8D2000 - > 0x0000000000002000 (0x0000000000004008) > Select Item: 0x0 > FW CFG Signature: 0x554D4551 > Select Item: 0x1 > FW CFG Revision: 0x3 > QemuFwCfg interface (DMA) is supported. > Select Item: 0x19 > Select Item: 0x19 > Select Item: 0x19 > Select Item: 0x2B > Select Item: 0x2A > Select Item: 0x29 > NegotiateSmiFeatures: using SMI broadcast > NegotiateSmiFeatures: CPU hotplug with SMI negotiated > NegotiateSmiFeatures: CPU hot-unplug with SMI negotiated > Select Item: 0x1 > SmmControl2Dxe: S3SaveStateInstalledNotify: DmaAccess@0x3E964018 > ScratchBuffer@[0x3E964028+0x8] > InstallProtocolInterface: 843DC720-AB1E-42CB-9357-8A0078F3561B 3E8D2010 > Loading driver 229B7EFD-DA02-46B9-93F4-E20C009F94E9 > None of Tcg2Protocol/CcMeasurementProtocol is installed. > InstallProtocolInterface: 5B1B31A1-9562-11D2-8E3F-00A0C969723B 3DC4C040 > Loading driver at 0x0003DC15000 EntryPoint=0x0003DC16266 > CpuS3DataDxe.efi > InstallProtocolInterface: BC62157E-3E33-4FEC-9920-2D3B36D750DF 3DC6A718 > ProtectUefiImageCommon - 0x3DC4C040 > - 0x000000003DC15000 - 0x00000000000023C0 > Loading driver F099D67F-71AE-4C36-B2A3-DCEB0EB2B7D8 > None of Tcg2Protocol/CcMeasurementProtocol is installed. > InstallProtocolInterface: 5B1B31A1-9562-11D2-8E3F-00A0C969723B 3DC4CA40 > Loading driver at 0x0003DC13000 EntryPoint=0x0003DC13FF9 > WatchdogTimer.efi > InstallProtocolInterface: BC62157E-3E33-4FEC-9920-2D3B36D750DF 3DC4C998 > ProtectUefiImageCommon - 0x3DC4CA40 > - 0x000000003DC13000 - 0x0000000000001EC0 > InstallProtocolInterface: 665E3FF5-46CC-11D4-9A38-0090273FC14D 3DC14D10 > Loading driver EBF8ED7C-0DD1-4787-84F1-F48D537DCACF > None of Tcg2Protocol/CcMeasurementProtocol is installed. > InstallProtocolInterface: 5B1B31A1-9562-11D2-8E3F-00A0C969723B 3DC4B040 > Loading driver at 0x0003D9FA000 EntryPoint=0x0003D9FDC1D > DriverHealthManagerDxe.efi > InstallProtocolInterface: BC62157E-3E33-4FEC-9920-2D3B36D750DF 3DC4BF18 > ProtectUefiImageCommon - 0x3DC4B040 > - 0x000000003D9FA000 - 0x0000000000005F40 > InstallProtocolInterface: 09576E91-6D3F-11D2-8E39-00A0C969723B 3D9FF960 > InstallProtocolInterface: 330D4706-F2A0-4E4F-A369-B66FA8D54385 3D9FF930 > Loading driver 28A03FF4-12B3-4305-A417-BB1A4F94081E > None of Tcg2Protocol/CcMeasurementProtocol is installed. > InstallProtocolInterface: 5B1B31A1-9562-11D2-8E3F-00A0C969723B 3DC454C0 > Loading driver at 0x0003D9E4000 EntryPoint=0x0003D9EAA01 RamDiskDxe.efi > InstallProtocolInterface: BC62157E-3E33-4FEC-9920-2D3B36D750DF 3DC4BA18 > ProtectUefiImageCommon - 0x3DC454C0 > - 0x000000003D9E4000 - 0x000000000000A900 > InstallProtocolInterface: 09576E91-6D3F-11D2-8E39-00A0C969723B 3DC4B618 > InstallProtocolInterface: 330D4706-F2A0-4E4F-A369-B66FA8D54385 3D9EE5D8 > InstallProtocolInterface: 09576E91-6D3F-11D2-8E39-00A0C969723B 3D9EE670 > InstallProtocolInterface: 330D4706-F2A0-4E4F-A369-B66FA8D54385 3DC05FB0 > InstallProtocolInterface: AB38A0DF-6873-44A9-87E6-D4EB56148449 3D9EE360 > InstallProtocolInterface: 28A03FF4-12B3-4305-A417-BB1A4F94081E 3DC05F98 > Loading driver E660EA85-058E-4B55-A54B-F02F83A24707 > None of Tcg2Protocol/CcMeasurementProtocol is installed. > InstallProtocolInterface: 5B1B31A1-9562-11D2-8E3F-00A0C969723B 3DC04740 > Loading driver at 0x0003D9BC000 EntryPoint=0x0003D9CA753 > DisplayEngine.efi > InstallProtocolInterface: BC62157E-3E33-4FEC-9920-2D3B36D750DF 3DC04A18 > ProtectUefiImageCommon - 0x3DC04740 > - 0x000000003D9BC000 - 0x0000000000013940 > InstallProtocolInterface: 9BBE29E9-FDA1-41EC-AD52-452213742D2E > 3D9CDDB0 > InstallProtocolInterface: 4311EDC0-6054-46D4-9E40-893EA952FCCC > 3D9CDDC8 > Loading driver 4110465D-5FF3-4F4B-B580-24ED0D06747A > None of Tcg2Protocol/CcMeasurementProtocol is installed. > InstallProtocolInterface: 5B1B31A1-9562-11D2-8E3F-00A0C969723B 3DC00140 > Loading driver at 0x0003D9F0000 EntryPoint=0x0003D9F1C3E > SmbiosPlatformDxe.efi > InstallProtocolInterface: BC62157E-3E33-4FEC-9920-2D3B36D750DF 3DC44818 > ProtectUefiImageCommon - 0x3DC00140 > - 0x000000003D9F0000 - 0x0000000000003380 > Select Item: 0x0 > FW CFG Signature: 0x554D4551 > Select Item: 0x1 > FW CFG Revision: 0x3 > QemuFwCfg interface (DMA) is supported. > Select Item: 0x19 > Select Item: 0x28 > SmbiosAdd: Smbios type 1 with size 0x4B is added to 32-bit table > SmbiosCreateTable: Initialize 32-bit entry point structure > SmbiosCreateTable() re-allocate SMBIOS 32-bit table > SmbiosAdd: Smbios type 3 with size 0x27 is added to 32-bit table > SmbiosAdd: Smbios type 4 with size 0x41 is added to 32-bit table > SmbiosAdd: Smbios type 16 with size 0x19 is added to 32-bit table > SmbiosAdd: Smbios type 17 with size 0x35 is added to 32-bit table > SmbiosAdd: Smbios type 19 with size 0x21 is added to 32-bit table > SmbiosAdd: Smbios type 32 with size 0xD is added to 32-bit table > FirmwareVendor: "EDK II" (6 chars) > FirmwareVersionString: "kraxel-devel-build" (18 chars) > FirmwareReleaseDateString: "03/06/2023" (10 chars) > SmbiosAdd: Smbios type 0 with size 0x40 is added to 32-bit table > Loading driver 2FA2A6DA-11D5-4DC3-999A-749648B03C56 > None of Tcg2Protocol/CcMeasurementProtocol is installed. > InstallProtocolInterface: 5B1B31A1-9562-11D2-8E3F-00A0C969723B 3D9F74C0 > Loading driver at 0x0003E8C4000 EntryPoint=0x0003E8C7CF8 PiSmmIpl.efi > InstallProtocolInterface: BC62157E-3E33-4FEC-9920-2D3B36D750DF 3D9F7118 > ProtectUefiImageCommon - 0x3D9F74C0 > - 0x000000003E8C4000 - 0x0000000000009000 > SetUefiImageMemoryAttributes - 0x000000003E8C4000 - > 0x0000000000001000 (0x0000000000004008) > SetUefiImageMemoryAttributes - 0x000000003E8C5000 - > 0x0000000000006000 (0x0000000000020008) > SetUefiImageMemoryAttributes - 0x000000003E8CB000 - > 0x0000000000002000 (0x0000000000004008) > SMM IPL opened SMRAM window > SMM IPL found SMRAM window 3F001000 - 3FFFFFFF > SMRAM attributes: 0000000000000008 > SMM IPL loading SMM Core at SMRAM address 3FFEE000 > SMM IPL calling SMM Core at SMRAM address 3FFF881C > PiSmmCoreImageBase - 0x000000003FFEE000 > PiSmmCoreImageSize - 0x0000000000011000 > SmmAddMemoryRegion > MemBase - 0x3F001000 > MemLength - 0xFED000 > Type - 0x7 > Attributes - 0xA > SmmAddMemoryRegion > MemBase - 0x3F000000 > MemLength - 0x1000 > Type - 0x6 > Attributes - 0x1A > SmmAddMemoryRegion > MemBase - 0x3FFEE000 > MemLength - 0x12000 > Type - 0x6 > Attributes - 0x1A > mSmmMemLibInternalMaximumSupportAddress = 0x7FFFFFFFFF > InstallProtocolInterface: 5B1B31A1-9562-11D2-8E3F-00A0C969723B 3D9F6898 > SmmInstallProtocolInterface: 5B1B31A1-9562-11D2-8E3F-00A0C969723B > 3FFEC0C0 > InstallProtocolInterface: F4CCBFB7-F6E0-47FD-9DD4-10A8F150C191 3E8CB0E0 > InstallProtocolInterface: C68ED8E2-9DC6-4CBD-9D94-DB65ACC5C332 > 3E8CB400 > InstallProtocolInterface: 378DAEDC-F06B-4446-8314-40AB933C87A3 3E8CB0B0 > None of Tcg2Protocol/CcMeasurementProtocol is installed. > InstallProtocolInterface: 5B1B31A1-9562-11D2-8E3F-00A0C969723B 3D9EF798 > SmmInstallProtocolInterface: 5B1B31A1-9562-11D2-8E3F-00A0C969723B > 3FFEBAC0 > Loading SMM driver at 0x0003FFE2000 EntryPoint=0x0003FFE4289 > CpuIo2Smm.efi > SmmInstallProtocolInterface: 3242A9D8-CE70-4AA0-955D-5E7B140DE4D2 > 3FFE6020 > None of Tcg2Protocol/CcMeasurementProtocol is installed. > InstallProtocolInterface: 5B1B31A1-9562-11D2-8E3F-00A0C969723B 3D9EF598 > SmmInstallProtocolInterface: 5B1B31A1-9562-11D2-8E3F-00A0C969723B > 3FFEB8C0 > Loading SMM driver at 0x0003FFD8000 EntryPoint=0x0003FFDB8A9 > SmmLockBox.efi > SmmLockBoxSmmLib SmmLockBoxMmConstructor - Enter > SmmLockBoxSmmLib SmmLockBoxContext - 3FFDE160 > SmmLockBoxSmmLib LockBoxDataAddress - 3FFDE060 > SmmLockBoxSmmLib SmmLockBoxMmConstructor - Exit > mSmmMemLibInternalMaximumSupportAddress = 0x7FFFFFFFFF > InstallProtocolInterface: BD445D79-B7AD-4F04-9AD8-29BD2040EB3C 0 > None of Tcg2Protocol/CcMeasurementProtocol is installed. > InstallProtocolInterface: 5B1B31A1-9562-11D2-8E3F-00A0C969723B 3D9EF298 > SmmInstallProtocolInterface: 5B1B31A1-9562-11D2-8E3F-00A0C969723B > 3FFEB6C0 > Loading SMM driver at 0x0003FFBF000 EntryPoint=0x0003FFCA149 > PiSmmCpuDxeSmm.efi > SMRR Base: 0x3F000000, SMRR Size: 0x1000000 > PcdCpuSmmCodeAccessCheckEnable = 1 > mAddressEncMask = 0x0 > PcdControlFlowEnforcementPropertyMask = 0 > SMRAM TileSize = 0x00002000 (0x00001000, 0x00001000) > PiCpuSmmEntry: gSmmBaseHobGuid not found! > New Allcoated SMRAM SaveState Buffer (0x3FFB1000, 0x0000E000) > CPU[000] APIC ID=0000 SMBASE=3FFA9000 SaveState=3FFB8C00 > Size=00000400 > CPU[001] APIC ID=0001 SMBASE=3FFAB000 SaveState=3FFBAC00 > Size=00000400 > Stacks - 0x3FF98000 > mSmmStackSize - 0x6000 > PcdCpuSmmStackGuard - 0x1 > mXdSupported - 0x1 > One Semaphore Size = 0x40 > Total Semaphores Size = 0x540 > PhysicalAddressBits = 39, 5LPageTable = 0. > 5LevelPaging Needed - 0 > 1GPageTable Support - 1 > PcdCpuSmmRestrictedMemoryAccess - 1 > PhysicalAddressBits - 39 > Initialize IDT IST field for SMM Stack Guard > InstallProtocolInterface: 26EEB3DE-B689-492E-80F0-BE8BD7DA4BA7 3FFD4170 > SMM IPL registered SMM Entry Point address 3FFEFD8C > SmmInstallProtocolInterface: EB346B97-975F-4A9F-8B22-F8E92BB3D569 > 3FFD41B0 > SmmInstallProtocolInterface: 69B792EA-39CE-402D-A2A6-F721DE351DFE > 3FFD40B0 > CpuSmm: SpinLock Size = 0x40, PcdCpuSmmMpTokenCountPerChunk = 0x40 > SmmInstallProtocolInterface: 5D5450D7-990C-4180-A803-8E63F0608307 > 3FFD4240 > SmmInstallProtocolInterface: 1D202CAB-C8AB-4D5C-94F7-3CFCC0D3D335 > 3FFD4040 > SmmInstallProtocolInterface: AA00D50B-4911-428F-B91A-A59DDB13E24C > 3FFD4020 > SMM S3 SMRAM Structure = 3E6E8B00 > SMM S3 Structure = 3F000000 > SMM CPU Module exit from SMRAM with EFI_SUCCESS > SMM IPL closed SMRAM window > None of Tcg2Protocol/CcMeasurementProtocol is installed. > InstallProtocolInterface: 5B1B31A1-9562-11D2-8E3F-00A0C969723B 3D9D1B98 > SmmInstallProtocolInterface: 5B1B31A1-9562-11D2-8E3F-00A0C969723B > 3FFEB4C0 > Loading SMM driver at 0x0003FF80000 EntryPoint=0x0003FF83956 > FvbServicesSmm.efi > QEMU Flash: Attempting flash detection at FFC00010 > QemuFlashDetected => FD behaves as FLASH > QemuFlashDetected => Yes > Installing QEMU flash SMM FVB > SmmInstallProtocolInterface: D326D041-BD31-4C01-B5A8-628BE87F0653 > 3FFB0530 > SmmInstallProtocolInterface: 09576E91-6D3F-11D2-8E39-00A0C969723B > 3FFB0498 > None of Tcg2Protocol/CcMeasurementProtocol is installed. > InstallProtocolInterface: 5B1B31A1-9562-11D2-8E3F-00A0C969723B 3D9D1A18 > SmmInstallProtocolInterface: 5B1B31A1-9562-11D2-8E3F-00A0C969723B > 3FFEB0C0 > Loading SMM driver at 0x0003FEDB000 EntryPoint=0x0003FF25CBC > VariableSmm.efi > mSmmMemLibInternalMaximumSupportAddress = 0x7FFFFFFFFF > VarCheckLibRegisterSetVariableCheckHandler - 0x3FF1F0AB Success > VarCheckLibRegisterSetVariableCheckHandler - 0x3FF1868F Success > Variable driver common space: 0x3FF9C 0x3FF9C 0x3FF9C > Variable driver will work with auth variable format! > SmmInstallProtocolInterface: ED32D533-99E6-4209-9CC0-2D72CDD998A7 > 3FF400A0 > SmmInstallProtocolInterface: B0D8F3C1-B7DE-4C11-BC89-2FB562C8C411 > 3FF40060 > InstallProtocolInterface: ED32D533-99E6-4209-9CC0-2D72CDD998A7 0 > None of Tcg2Protocol/CcMeasurementProtocol is installed. > InstallProtocolInterface: 5B1B31A1-9562-11D2-8E3F-00A0C969723B 3D9D1598 > SmmInstallProtocolInterface: 5B1B31A1-9562-11D2-8E3F-00A0C969723B > 3FFEBCC0 > Loading SMM driver at 0x0003FD8E000 EntryPoint=0x0003FD91670 > CpuHotplugSmm.efi > SmbaseAllocatePostSmmPen: Post-SMM Pen at 0x9F000 > None of Tcg2Protocol/CcMeasurementProtocol is installed. > InstallProtocolInterface: 5B1B31A1-9562-11D2-8E3F-00A0C969723B 3D9D1218 > SmmInstallProtocolInterface: 5B1B31A1-9562-11D2-8E3F-00A0C969723B > 3FFEB2C0 > Loading SMM driver at 0x0003FD83000 EntryPoint=0x0003FD888D7 > SmmFaultTolerantWriteDxe.efi > mSmmMemLibInternalMaximumSupportAddress = 0x7FFFFFFFFF > Ftw: FtwWorkSpaceLba - 0x41, WorkBlockSize - 0x1000, FtwWorkSpaceBase - > 0x0 > Ftw: FtwSpareLba - 0x42, SpareBlockSize - 0x1000 > Ftw: NumberOfWorkBlock - 0x1, FtwWorkBlockLba - 0x41 > Ftw: WorkSpaceLbaInSpare - 0x0, WorkSpaceBaseInSpare - 0x0 > Ftw: Remaining work space size - FE0 > SmmInstallProtocolInterface: 3868FC3B-7E45-43A7-906C-4BA47DE1754D > 3FD80028 > Variable PK does not exist. > Variable SetupMode is 1 > Variable SecureBoot is 0 > Variable SecureBootEnable is 0 > Variable CustomMode is 0 > Variable VendorKeys is 1 > Variable driver will work with auth variable support! > InstallProtocolInterface: 93BA1826-DFFB-45DD-82A7-E7DCAA3BBDF3 0 > InstallProtocolInterface: 3868FC3B-7E45-43A7-906C-4BA47DE1754D 0 > Loading driver FA20568B-548B-4B2B-81EF-1BA08D4A3CEC > None of Tcg2Protocol/CcMeasurementProtocol is installed. > InstallProtocolInterface: 5B1B31A1-9562-11D2-8E3F-00A0C969723B 3D9D00C0 > Loading driver at 0x0003D8C8000 EntryPoint=0x0003D8CDD35 > BootScriptExecutorDxe.efi > InstallProtocolInterface: BC62157E-3E33-4FEC-9920-2D3B36D750DF 3D9D0A98 > ProtectUefiImageCommon - 0x3D9D00C0 > - 0x000000003D8C8000 - 0x0000000000014B40 > Loading driver 9F7DCADE-11EA-448A-A46F-76E003657DD1 > None of Tcg2Protocol/CcMeasurementProtocol is installed. > InstallProtocolInterface: 5B1B31A1-9562-11D2-8E3F-00A0C969723B 3D9D0540 > Loading driver at 0x0003E8BC000 EntryPoint=0x0003E8BFD8A > VariableSmmRuntimeDxe.efi > InstallProtocolInterface: BC62157E-3E33-4FEC-9920-2D3B36D750DF 3D8E8F98 > ProtectUefiImageCommon - 0x3D9D0540 > - 0x000000003E8BC000 - 0x0000000000008000 > SetUefiImageMemoryAttributes - 0x000000003E8BC000 - > 0x0000000000001000 (0x0000000000004008) > SetUefiImageMemoryAttributes - 0x000000003E8BD000 - > 0x0000000000005000 (0x0000000000020008) > SetUefiImageMemoryAttributes - 0x000000003E8C2000 - > 0x0000000000002000 (0x0000000000004008) > Variable driver runtime cache is disabled. > InstallProtocolInterface: 1E5668E2-8481-11D4-BCF1-0080C73C8881 0 > InstallProtocolInterface: CD3D0A05-9E24-437C-A891-1EE053DB7638 3E8C2288 > InstallProtocolInterface: AF23B340-97B4-4685-8D4F-A3F28169B21D 3E8C2270 > InstallProtocolInterface: 6441F818-6362-4E44-B570-7DBA31DD2453 0 > InstallProtocolInterface: 81D1675C-86F6-48DF-BD95-9A6E4F0925C3 3E8C21E0 > Loading driver 378D7B65-8DA9-4773-B6E4-A47826A833E1 > None of Tcg2Protocol/CcMeasurementProtocol is installed. > InstallProtocolInterface: 5B1B31A1-9562-11D2-8E3F-00A0C969723B 3D8E8340 > Loading driver at 0x0003E8B6000 EntryPoint=0x0003E8B9191 PcRtc.efi > InstallProtocolInterface: BC62157E-3E33-4FEC-9920-2D3B36D750DF 3D8EAE98 > ProtectUefiImageCommon - 0x3D8E8340 > - 0x000000003E8B6000 - 0x0000000000006000 > SetUefiImageMemoryAttributes - 0x000000003E8B6000 - > 0x0000000000001000 (0x0000000000004008) > SetUefiImageMemoryAttributes - 0x000000003E8B7000 - > 0x0000000000004000 (0x0000000000020008) > SetUefiImageMemoryAttributes - 0x000000003E8BB000 - > 0x0000000000001000 (0x0000000000004008) > InstallProtocolInterface: 27CFAC87-46CC-11D4-9A38-0090273FC14D 0 > Loading driver F0E6A44F-7195-41C3-AC64-54F202CD0A21 > None of Tcg2Protocol/CcMeasurementProtocol is installed. > InstallProtocolInterface: 5B1B31A1-9562-11D2-8E3F-00A0C969723B 3D8EA340 > Loading driver at 0x0003D802000 EntryPoint=0x0003D832601 > SecureBootConfigDxe.efi > InstallProtocolInterface: BC62157E-3E33-4FEC-9920-2D3B36D750DF 3D8EA698 > ProtectUefiImageCommon - 0x3D8EA340 > - 0x000000003D802000 - 0x0000000000062B40 > InstallProtocolInterface: 09576E91-6D3F-11D2-8E39-00A0C969723B 3D8F1C98 > InstallProtocolInterface: 330D4706-F2A0-4E4F-A369-B66FA8D54385 3D84E938 > InstallProtocolInterface: 09576E91-6D3F-11D2-8E39-00A0C969723B 3D84E9B0 > InstallProtocolInterface: 330D4706-F2A0-4E4F-A369-B66FA8D54385 3D8F0220 > InstallProtocolInterface: F0E6A44F-7195-41C3-AC64-54F202CD0A21 3D8F0218 > Loading driver AD608272-D07F-4964-801E-7BD3B7888652 > None of Tcg2Protocol/CcMeasurementProtocol is installed. > InstallProtocolInterface: 5B1B31A1-9562-11D2-8E3F-00A0C969723B 3D8EF740 > Loading driver at 0x0003E8B2000 EntryPoint=0x0003E8B3DCD > MonotonicCounterRuntimeDxe.efi > InstallProtocolInterface: BC62157E-3E33-4FEC-9920-2D3B36D750DF 3D8EEF98 > ProtectUefiImageCommon - 0x3D8EF740 > - 0x000000003E8B2000 - 0x0000000000004000 > SetUefiImageMemoryAttributes - 0x000000003E8B2000 - > 0x0000000000001000 (0x0000000000004008) > SetUefiImageMemoryAttributes - 0x000000003E8B3000 - > 0x0000000000002000 (0x0000000000020008) > SetUefiImageMemoryAttributes - 0x000000003E8B5000 - > 0x0000000000001000 (0x0000000000004008) > InstallProtocolInterface: 1DA97072-BDDC-4B30-99F1-72A0B56FFF2A 0 > Loading driver 42857F0A-13F2-4B21-8A23-53D3F714B840 > None of Tcg2Protocol/CcMeasurementProtocol is installed. > InstallProtocolInterface: 5B1B31A1-9562-11D2-8E3F-00A0C969723B 3D8EE1C0 > Loading driver at 0x0003E8AE000 EntryPoint=0x0003E8B0094 > CapsuleRuntimeDxe.efi > InstallProtocolInterface: BC62157E-3E33-4FEC-9920-2D3B36D750DF 3D8EE718 > ProtectUefiImageCommon - 0x3D8EE1C0 > - 0x000000003E8AE000 - 0x0000000000004000 > SetUefiImageMemoryAttributes - 0x000000003E8AE000 - > 0x0000000000001000 (0x0000000000004008) > SetUefiImageMemoryAttributes - 0x000000003E8AF000 - > 0x0000000000002000 (0x0000000000020008) > SetUefiImageMemoryAttributes - 0x000000003E8B1000 - > 0x0000000000001000 (0x0000000000004008) > InstallProtocolInterface: 5053697E-2CBC-4819-90D9-0580DEEE5754 0 > Loading driver 6D33944A-EC75-4855-A54D-809C75241F6C > None of Tcg2Protocol/CcMeasurementProtocol is installed. > InstallProtocolInterface: 5B1B31A1-9562-11D2-8E3F-00A0C969723B 3D8EDCC0 > Loading driver at 0x0003D88C000 EntryPoint=0x0003D89F5E9 BdsDxe.efi > InstallProtocolInterface: BC62157E-3E33-4FEC-9920-2D3B36D750DF 3D8EDB18 > ProtectUefiImageCommon - 0x3D8EDCC0 > - 0x000000003D88C000 - 0x000000000001DDC0 > Select Item: 0x0 > FW CFG Signature: 0x554D4551 > Select Item: 0x1 > FW CFG Revision: 0x3 > QemuFwCfg interface (DMA) is supported. > InstallProtocolInterface: 665E3FF6-46CC-11D4-9A38-0090273FC14D 3D8A9AE0 > Loading driver 7CA1024F-EB17-11E5-9DBA-28D2447C4829 > None of Tcg2Protocol/CcMeasurementProtocol is installed. > InstallProtocolInterface: 5B1B31A1-9562-11D2-8E3F-00A0C969723B 3D8ED2C0 > Loading driver at 0x0003D8BD000 EntryPoint=0x0003D8C3A00 > TlsAuthConfigDxe.efi > InstallProtocolInterface: BC62157E-3E33-4FEC-9920-2D3B36D750DF 3D8ED618 > ProtectUefiImageCommon - 0x3D8ED2C0 > - 0x000000003D8BD000 - 0x000000000000ADC0 > Select Item: 0x0 > FW CFG Signature: 0x554D4551 > Select Item: 0x1 > FW CFG Revision: 0x3 > QemuFwCfg interface (DMA) is supported. > InstallProtocolInterface: 09576E91-6D3F-11D2-8E39-00A0C969723B 3D8E9C98 > InstallProtocolInterface: 330D4706-F2A0-4E4F-A369-B66FA8D54385 3D8C79F8 > Select Item: 0x19 > Select Item: 0x19 > InstallProtocolInterface: 09576E91-6D3F-11D2-8E39-00A0C969723B 3D8C7AF0 > InstallProtocolInterface: 330D4706-F2A0-4E4F-A369-B66FA8D54385 3D8E6EB0 > InstallProtocolInterface: 7CA1024F-EB17-11E5-9DBA-28D2447C4829 3D8E6E98 > Loading driver D9DCC5DF-4007-435E-9098-8970935504B2 > None of Tcg2Protocol/CcMeasurementProtocol is installed. > InstallProtocolInterface: 5B1B31A1-9562-11D2-8E3F-00A0C969723B 3D8E66C0 > Loading driver at 0x0003D8B7000 EntryPoint=0x0003D8BA6A7 > PlatformDxe.efi > InstallProtocolInterface: BC62157E-3E33-4FEC-9920-2D3B36D750DF 3D8E6A18 > ProtectUefiImageCommon - 0x3D8E66C0 > - 0x000000003D8B7000 - 0x0000000000005BC0 > InstallProtocolInterface: 09576E91-6D3F-11D2-8E39-00A0C969723B 3D8BC9C0 > InstallProtocolInterface: 330D4706-F2A0-4E4F-A369-B66FA8D54385 3D8BCA90 > Loading driver FDFF263D-5F68-4591-87BA-B768F445A9AF > None of Tcg2Protocol/CcMeasurementProtocol is installed. > InstallProtocolInterface: 5B1B31A1-9562-11D2-8E3F-00A0C969723B 3D8E5B40 > Loading driver at 0x0003D86A000 EntryPoint=0x0003D870A23 Tcg2Dxe.efi > InstallProtocolInterface: BC62157E-3E33-4FEC-9920-2D3B36D750DF 3D8DF098 > ProtectUefiImageCommon - 0x3D8E5B40 > - 0x000000003D86A000 - 0x0000000000010AC0 > Select Item: 0x0 > FW CFG Signature: 0x554D4551 > Select Item: 0x1 > FW CFG Revision: 0x3 > QemuFwCfg interface (DMA) is supported. > WARNING: Tpm2RegisterTpm2DeviceLib - does not support 286BF25A-C2C3- > 408C-B3B4-25E6758B7317 registration > No TPM2 instance required! > Error: Image at 0003D86A000 start failed: Unsupported > Loading driver 93B80004-9FB3-11D4-9A3A-0090273FC14D > None of Tcg2Protocol/CcMeasurementProtocol is installed. > InstallProtocolInterface: 5B1B31A1-9562-11D2-8E3F-00A0C969723B 3D8E5B40 > Loading driver at 0x0003D86E000 EntryPoint=0x0003D879F00 PciBusDxe.efi > InstallProtocolInterface: BC62157E-3E33-4FEC-9920-2D3B36D750DF 3D8DF698 > ProtectUefiImageCommon - 0x3D8E5B40 > - 0x000000003D86E000 - 0x000000000000EEC0 > InstallProtocolInterface: 18A031AB-B443-4D1A-A5C0-0C09261E9F71 > 3D87CA40 > InstallProtocolInterface: 107A772C-D5E1-11D4-9A46-0090273FC14D 3D87C920 > InstallProtocolInterface: 6A7A5CFF-E8D9-4F70-BADA-75AB3025CE14 > 3D87CC00 > InstallProtocolInterface: 19CB87AB-2CB9-4665-8360-DDCF6054F79D > 3D87CBE0 > Loading driver 83DD3B39-7CAF-4FAC-A542-E050B767E3A7 > None of Tcg2Protocol/CcMeasurementProtocol is installed. > InstallProtocolInterface: 5B1B31A1-9562-11D2-8E3F-00A0C969723B 3D8E54C0 > Loading driver at 0x0003D8B4000 EntryPoint=0x0003D8B5C3D > VirtioPciDeviceDxe.efi > InstallProtocolInterface: BC62157E-3E33-4FEC-9920-2D3B36D750DF 3D8E5798 > ProtectUefiImageCommon - 0x3D8E54C0 > - 0x000000003D8B4000 - 0x0000000000003000 > InstallProtocolInterface: 18A031AB-B443-4D1A-A5C0-0C09261E9F71 > 3D8B6DA0 > InstallProtocolInterface: 107A772C-D5E1-11D4-9A46-0090273FC14D 3D8B6E00 > InstallProtocolInterface: 6A7A5CFF-E8D9-4F70-BADA-75AB3025CE14 > 3D8B6D80 > Loading driver 0170F60C-1D40-4651-956D-F0BD9879D527 > None of Tcg2Protocol/CcMeasurementProtocol is installed. > InstallProtocolInterface: 5B1B31A1-9562-11D2-8E3F-00A0C969723B 3D8E00C0 > Loading driver at 0x0003D8AA000 EntryPoint=0x0003D8AD399 Virtio10.efi > InstallProtocolInterface: BC62157E-3E33-4FEC-9920-2D3B36D750DF 3D8E0B18 > ProtectUefiImageCommon - 0x3D8E00C0 > - 0x000000003D8AA000 - 0x0000000000004B40 > InstallProtocolInterface: 18A031AB-B443-4D1A-A5C0-0C09261E9F71 > 3D8AE8E0 > InstallProtocolInterface: 107A772C-D5E1-11D4-9A46-0090273FC14D 3D8AE940 > InstallProtocolInterface: 6A7A5CFF-E8D9-4F70-BADA-75AB3025CE14 > 3D8AE8C0 > Loading driver 11D92DFB-3CA9-4F93-BA2E-4780ED3E03B5 > None of Tcg2Protocol/CcMeasurementProtocol is installed. > InstallProtocolInterface: 5B1B31A1-9562-11D2-8E3F-00A0C969723B 3D8E0440 > Loading driver at 0x0003D8B0000 EntryPoint=0x0003D8B2201 VirtioBlkDxe.efi > InstallProtocolInterface: BC62157E-3E33-4FEC-9920-2D3B36D750DF 3D8DEF18 > ProtectUefiImageCommon - 0x3D8E0440 > - 0x000000003D8B0000 - 0x00000000000035C0 > InstallProtocolInterface: 18A031AB-B443-4D1A-A5C0-0C09261E9F71 3D8B33E0 > InstallProtocolInterface: 107A772C-D5E1-11D4-9A46-0090273FC14D 3D8B3440 > InstallProtocolInterface: 6A7A5CFF-E8D9-4F70-BADA-75AB3025CE14 > 3D8B33C0 > Loading driver FAB5D4F4-83C0-4AAF-8480-442D11DF6CEA > None of Tcg2Protocol/CcMeasurementProtocol is installed. > InstallProtocolInterface: 5B1B31A1-9562-11D2-8E3F-00A0C969723B 3D8DE0C0 > Loading driver at 0x0003D888000 EntryPoint=0x0003D88A731 VirtioScsiDxe.efi > InstallProtocolInterface: BC62157E-3E33-4FEC-9920-2D3B36D750DF 3D8DEA98 > ProtectUefiImageCommon - 0x3D8DE0C0 > - 0x000000003D888000 - 0x0000000000003A80 > InstallProtocolInterface: 18A031AB-B443-4D1A-A5C0-0C09261E9F71 > 3D88B8A0 > InstallProtocolInterface: 107A772C-D5E1-11D4-9A46-0090273FC14D 3D88B900 > InstallProtocolInterface: 6A7A5CFF-E8D9-4F70-BADA-75AB3025CE14 > 3D88B880 > Loading driver 58E26F0D-CBAC-4BBA-B70F-18221415665A > None of Tcg2Protocol/CcMeasurementProtocol is installed. > InstallProtocolInterface: 5B1B31A1-9562-11D2-8E3F-00A0C969723B 3D8E1040 > Loading driver at 0x0003D885000 EntryPoint=0x0003D886CBF VirtioRngDxe.efi > InstallProtocolInterface: BC62157E-3E33-4FEC-9920-2D3B36D750DF 3D8DE598 > ProtectUefiImageCommon - 0x3D8E1040 > - 0x000000003D885000 - 0x0000000000002F80 > InstallProtocolInterface: 18A031AB-B443-4D1A-A5C0-0C09261E9F71 > 3D887DA0 > InstallProtocolInterface: 107A772C-D5E1-11D4-9A46-0090273FC14D 3D887E00 > InstallProtocolInterface: 6A7A5CFF-E8D9-4F70-BADA-75AB3025CE14 > 3D887D80 > Loading driver 51CCF399-4FDF-4E55-A45B-E123F84D456A > None of Tcg2Protocol/CcMeasurementProtocol is installed. > InstallProtocolInterface: 5B1B31A1-9562-11D2-8E3F-00A0C969723B 3D8E19C0 > Loading driver at 0x0003D87D000 EntryPoint=0x0003D87F6F9 > ConPlatformDxe.efi > InstallProtocolInterface: BC62157E-3E33-4FEC-9920-2D3B36D750DF 3D8E1918 > ProtectUefiImageCommon - 0x3D8E19C0 > - 0x000000003D87D000 - 0x0000000000003FC0 > InstallProtocolInterface: 18A031AB-B443-4D1A-A5C0-0C09261E9F71 > 3D880D20 > InstallProtocolInterface: 107A772C-D5E1-11D4-9A46-0090273FC14D 3D880E20 > InstallProtocolInterface: 6A7A5CFF-E8D9-4F70-BADA-75AB3025CE14 > 3D880CF0 > InstallProtocolInterface: 18A031AB-B443-4D1A-A5C0-0C09261E9F71 > 3D880CC0 > InstallProtocolInterface: 107A772C-D5E1-11D4-9A46-0090273FC14D 3D880E20 > InstallProtocolInterface: 6A7A5CFF-E8D9-4F70-BADA-75AB3025CE14 > 3D880CF0 > Loading driver 408EDCEC-CF6D-477C-A5A8-B4844E3DE281 > None of Tcg2Protocol/CcMeasurementProtocol is installed. > InstallProtocolInterface: 5B1B31A1-9562-11D2-8E3F-00A0C969723B 3D8E4BC0 > Loading driver at 0x0003D7FA000 EntryPoint=0x0003D7FF04F > ConSplitterDxe.efi > InstallProtocolInterface: BC62157E-3E33-4FEC-9920-2D3B36D750DF 3D8E4098 > ProtectUefiImageCommon - 0x3D8E4BC0 > - 0x000000003D7FA000 - 0x0000000000007500 > InstallProtocolInterface: 18A031AB-B443-4D1A-A5C0-0C09261E9F71 3D8011E0 > InstallProtocolInterface: 107A772C-D5E1-11D4-9A46-0090273FC14D 3D8012C0 > InstallProtocolInterface: 6A7A5CFF-E8D9-4F70-BADA-75AB3025CE14 > 3D800AE0 > InstallProtocolInterface: 18A031AB-B443-4D1A-A5C0-0C09261E9F71 3D801160 > InstallProtocolInterface: 107A772C-D5E1-11D4-9A46-0090273FC14D 3D8012A0 > InstallProtocolInterface: 6A7A5CFF-E8D9-4F70-BADA-75AB3025CE14 > 3D800AC0 > InstallProtocolInterface: 18A031AB-B443-4D1A-A5C0-0C09261E9F71 3D8010E0 > InstallProtocolInterface: 107A772C-D5E1-11D4-9A46-0090273FC14D 3D801280 > InstallProtocolInterface: 6A7A5CFF-E8D9-4F70-BADA-75AB3025CE14 > 3D800AA0 > InstallProtocolInterface: 18A031AB-B443-4D1A-A5C0-0C09261E9F71 3D801060 > InstallProtocolInterface: 107A772C-D5E1-11D4-9A46-0090273FC14D 3D801260 > InstallProtocolInterface: 6A7A5CFF-E8D9-4F70-BADA-75AB3025CE14 > 3D800A80 > InstallProtocolInterface: 18A031AB-B443-4D1A-A5C0-0C09261E9F71 3D800FE0 > InstallProtocolInterface: 107A772C-D5E1-11D4-9A46-0090273FC14D 3D801240 > InstallProtocolInterface: 6A7A5CFF-E8D9-4F70-BADA-75AB3025CE14 > 3D800A60 > InstallProtocolInterface: 387477C1-69C7-11D2-8E39-00A0C969723B 3D800E10 > InstallProtocolInterface: DD9E7534-7762-4698-8C14-F58517A625AA 3D800E40 > InstallProtocolInterface: 31878C87-0B75-11D5-9A4F-0090273FC14D 3D800EB0 > InstallProtocolInterface: 8D59D32B-C655-4AE9-9B15-F25904992A43 3D800F08 > InstallProtocolInterface: 387477C2-69C7-11D2-8E39-00A0C969723B 3D800CD0 > InstallProtocolInterface: 387477C2-69C7-11D2-8E39-00A0C969723B 3D800BB0 > Loading driver CCCB0C28-4B24-11D5-9A5A-0090273FC14D > None of Tcg2Protocol/CcMeasurementProtocol is installed. > InstallProtocolInterface: 5B1B31A1-9562-11D2-8E3F-00A0C969723B 3D8DD8C0 > Loading driver at 0x0003D7F4000 EntryPoint=0x0003D7F6F5E > GraphicsConsoleDxe.efi > InstallProtocolInterface: BC62157E-3E33-4FEC-9920-2D3B36D750DF 3D8DD798 > ProtectUefiImageCommon - 0x3D8DD8C0 > - 0x000000003D7F4000 - 0x0000000000005E40 > InstallProtocolInterface: 18A031AB-B443-4D1A-A5C0-0C09261E9F71 3D7F84E0 > InstallProtocolInterface: 107A772C-D5E1-11D4-9A46-0090273FC14D 3D7F9C80 > InstallProtocolInterface: 6A7A5CFF-E8D9-4F70-BADA-75AB3025CE14 > 3D7F84B0 > Loading driver 9E863906-A40F-4875-977F-5B93FF237FC6 > None of Tcg2Protocol/CcMeasurementProtocol is installed. > InstallProtocolInterface: 5B1B31A1-9562-11D2-8E3F-00A0C969723B 3D8AF8C0 > Loading driver at 0x0003D7E4000 EntryPoint=0x0003D7E98C7 TerminalDxe.efi > InstallProtocolInterface: BC62157E-3E33-4FEC-9920-2D3B36D750DF 3D8AF798 > ProtectUefiImageCommon - 0x3D8AF8C0 > - 0x000000003D7E4000 - 0x0000000000007C40 > InstallProtocolInterface: 18A031AB-B443-4D1A-A5C0-0C09261E9F71 > 3D7EBA40 > InstallProtocolInterface: 107A772C-D5E1-11D4-9A46-0090273FC14D > 3D7EBAA0 > InstallProtocolInterface: 6A7A5CFF-E8D9-4F70-BADA-75AB3025CE14 > 3D7EB7D0 > Loading driver 806040CA-DAD9-4978-A3B4-2D2AB0C8A48F > None of Tcg2Protocol/CcMeasurementProtocol is installed. > InstallProtocolInterface: 5B1B31A1-9562-11D2-8E3F-00A0C969723B 3D86B040 > Loading driver at 0x0003D867000 EntryPoint=0x0003D86906B > QemuKernelLoaderFsDxe.efi > InstallProtocolInterface: BC62157E-3E33-4FEC-9920-2D3B36D750DF 3D86BE18 > ProtectUefiImageCommon - 0x3D86B040 > - 0x000000003D867000 - 0x0000000000003D40 > Select Item: 0x0 > FW CFG Signature: 0x554D4551 > Select Item: 0x1 > FW CFG Revision: 0x3 > QemuFwCfg interface (DMA) is supported. > Select Item: 0x17 > Select Item: 0x8 > Select Item: 0xB > Select Item: 0x14 > Error: Image at 0003D867000 start failed: Not Found > Loading driver 6B38F7B4-AD98-40E9-9093-ACA2B5A253C4 > None of Tcg2Protocol/CcMeasurementProtocol is installed. > InstallProtocolInterface: 5B1B31A1-9562-11D2-8E3F-00A0C969723B 3D86B040 > Loading driver at 0x0003D7EF000 EntryPoint=0x0003D7F1EC4 DiskIoDxe.efi > InstallProtocolInterface: BC62157E-3E33-4FEC-9920-2D3B36D750DF 3D86BC98 > ProtectUefiImageCommon - 0x3D86B040 > - 0x000000003D7EF000 - 0x0000000000004800 > InstallProtocolInterface: 18A031AB-B443-4D1A-A5C0-0C09261E9F71 > 3D7F35A0 > InstallProtocolInterface: 107A772C-D5E1-11D4-9A46-0090273FC14D 3D7F36C0 > InstallProtocolInterface: 6A7A5CFF-E8D9-4F70-BADA-75AB3025CE14 > 3D7F3580 > Loading driver 1FA1F39E-FEFF-4AAE-BD7B-38A070A3B609 > None of Tcg2Protocol/CcMeasurementProtocol is installed. > InstallProtocolInterface: 5B1B31A1-9562-11D2-8E3F-00A0C969723B 3D86B5C0 > Loading driver at 0x0003D7D6000 EntryPoint=0x0003D7DAA88 > PartitionDxe.efi > InstallProtocolInterface: BC62157E-3E33-4FEC-9920-2D3B36D750DF 3D86B818 > ProtectUefiImageCommon - 0x3D86B5C0 > - 0x000000003D7D6000 - 0x00000000000065C0 > InstallProtocolInterface: 18A031AB-B443-4D1A-A5C0-0C09261E9F71 > 3D7DC360 > InstallProtocolInterface: 107A772C-D5E1-11D4-9A46-0090273FC14D 3D7DC460 > InstallProtocolInterface: 6A7A5CFF-E8D9-4F70-BADA-75AB3025CE14 > 3D7DC340 > Loading driver CD3BAFB6-50FB-4FE8-8E4E-AB74D2C1A600 > None of Tcg2Protocol/CcMeasurementProtocol is installed. > InstallProtocolInterface: 5B1B31A1-9562-11D2-8E3F-00A0C969723B 3D884B40 > Loading driver at 0x0003D868000 EntryPoint=0x0003D86930D EnglishDxe.efi > InstallProtocolInterface: BC62157E-3E33-4FEC-9920-2D3B36D750DF 3D884098 > ProtectUefiImageCommon - 0x3D884B40 > - 0x000000003D868000 - 0x0000000000002240 > InstallProtocolInterface: 1D85CD7F-F43D-11D2-9A0C-0090273FC14D > 3D869DA0 > InstallProtocolInterface: A4C751FC-23AE-4C3E-92E9-4964CF63F349 3D869D40 > Loading driver 0167CCC4-D0F7-4F21-A3EF-9E64B7CDCE8B > None of Tcg2Protocol/CcMeasurementProtocol is installed. > InstallProtocolInterface: 5B1B31A1-9562-11D2-8E3F-00A0C969723B 3D884340 > Loading driver at 0x0003D7D2000 EntryPoint=0x0003D7D4B29 ScsiBus.efi > InstallProtocolInterface: BC62157E-3E33-4FEC-9920-2D3B36D750DF 3D884818 > ProtectUefiImageCommon - 0x3D884340 > - 0x000000003D7D2000 - 0x0000000000004000 > InstallProtocolInterface: 18A031AB-B443-4D1A-A5C0-0C09261E9F71 > 3D7D5E00 > InstallProtocolInterface: 107A772C-D5E1-11D4-9A46-0090273FC14D > 3D7D5EA0 > InstallProtocolInterface: 6A7A5CFF-E8D9-4F70-BADA-75AB3025CE14 > 3D7D5DE0 > Loading driver 0A66E322-3740-4CCE-AD62-BD172CECCA35 > None of Tcg2Protocol/CcMeasurementProtocol is installed. > InstallProtocolInterface: 5B1B31A1-9562-11D2-8E3F-00A0C969723B 3D883CC0 > Loading driver at 0x0003D7BE000 EntryPoint=0x0003D7C60DE ScsiDisk.efi > InstallProtocolInterface: BC62157E-3E33-4FEC-9920-2D3B36D750DF 3D883898 > ProtectUefiImageCommon - 0x3D883CC0 > - 0x000000003D7BE000 - 0x0000000000009C80 > InstallProtocolInterface: 18A031AB-B443-4D1A-A5C0-0C09261E9F71 > 3D7C7AE0 > InstallProtocolInterface: 107A772C-D5E1-11D4-9A46-0090273FC14D 3D7C7B40 > InstallProtocolInterface: 6A7A5CFF-E8D9-4F70-BADA-75AB3025CE14 > 3D7C7A60 > Loading driver 021722D8-522B-4079-852A-FE44C2C13F49 > None of Tcg2Protocol/CcMeasurementProtocol is installed. > InstallProtocolInterface: 5B1B31A1-9562-11D2-8E3F-00A0C969723B 3D8833C0 > Loading driver at 0x0003D7CE000 EntryPoint=0x0003D7CFD8E > SataController.efi > InstallProtocolInterface: BC62157E-3E33-4FEC-9920-2D3B36D750DF 3D883718 > ProtectUefiImageCommon - 0x3D8833C0 > - 0x000000003D7CE000 - 0x0000000000003240 > InstallProtocolInterface: 18A031AB-B443-4D1A-A5C0-0C09261E9F71 > 3D7D1080 > InstallProtocolInterface: 107A772C-D5E1-11D4-9A46-0090273FC14D 3D7D10E0 > InstallProtocolInterface: 6A7A5CFF-E8D9-4F70-BADA-75AB3025CE14 > 3D7D1000 > Loading driver 5E523CB4-D397-4986-87BD-A6DD8B22F455 > None of Tcg2Protocol/CcMeasurementProtocol is installed. > InstallProtocolInterface: 5B1B31A1-9562-11D2-8E3F-00A0C969723B 3D882140 > Loading driver at 0x0003D7A6000 EntryPoint=0x0003D7AE6A9 > AtaAtapiPassThruDxe.efi > InstallProtocolInterface: BC62157E-3E33-4FEC-9920-2D3B36D750DF 3D882D98 > ProtectUefiImageCommon - 0x3D882140 > - 0x000000003D7A6000 - 0x000000000000B200 > InstallProtocolInterface: 18A031AB-B443-4D1A-A5C0-0C09261E9F71 > 3D7B0D80 > InstallProtocolInterface: 107A772C-D5E1-11D4-9A46-0090273FC14D 3D7B0DE0 > InstallProtocolInterface: 6A7A5CFF-E8D9-4F70-BADA-75AB3025CE14 > 3D7B0D00 > Loading driver 19DF145A-B1D4-453F-8507-38816676D7F6 > None of Tcg2Protocol/CcMeasurementProtocol is installed. > InstallProtocolInterface: 5B1B31A1-9562-11D2-8E3F-00A0C969723B 3D8825C0 > Loading driver at 0x0003D7B7000 EntryPoint=0x0003D7BB3DC AtaBusDxe.efi > InstallProtocolInterface: BC62157E-3E33-4FEC-9920-2D3B36D750DF 3D881F98 > ProtectUefiImageCommon - 0x3D8825C0 > - 0x000000003D7B7000 - 0x0000000000006580 > InstallProtocolInterface: 18A031AB-B443-4D1A-A5C0-0C09261E9F71 > 3D7BD100 > InstallProtocolInterface: 107A772C-D5E1-11D4-9A46-0090273FC14D 3D7BD1F0 > InstallProtocolInterface: 6A7A5CFF-E8D9-4F70-BADA-75AB3025CE14 > 3D7BD1D0 > Loading driver 5BE3BDF4-53CF-46A3-A6A9-73C34A6E5EE3 > None of Tcg2Protocol/CcMeasurementProtocol is installed. > InstallProtocolInterface: 5B1B31A1-9562-11D2-8E3F-00A0C969723B 3D881140 > Loading driver at 0x0003D792000 EntryPoint=0x0003D799279 > NvmExpressDxe.efi > InstallProtocolInterface: BC62157E-3E33-4FEC-9920-2D3B36D750DF 3D881398 > ProtectUefiImageCommon - 0x3D881140 > - 0x000000003D792000 - 0x0000000000009B00 > InstallProtocolInterface: 18A031AB-B443-4D1A-A5C0-0C09261E9F71 3D79B940 > InstallProtocolInterface: 107A772C-D5E1-11D4-9A46-0090273FC14D 3D79B9A0 > InstallProtocolInterface: 6A7A5CFF-E8D9-4F70-BADA-75AB3025CE14 > 3D79B870 > InstallProtocolInterface: 5C198761-16A8-4E69-972C-89D67954F81D 3D79B7E0 > Loading driver 864E1CA8-85EB-4D63-9DCC-6E0FC90FFD55 > None of Tcg2Protocol/CcMeasurementProtocol is installed. > InstallProtocolInterface: 5B1B31A1-9562-11D2-8E3F-00A0C969723B 3D867040 > Loading driver at 0x0003D7CA000 EntryPoint=0x0003D7CBD02 SioBusDxe.efi > InstallProtocolInterface: BC62157E-3E33-4FEC-9920-2D3B36D750DF 3D867D18 > ProtectUefiImageCommon - 0x3D867040 > - 0x000000003D7CA000 - 0x0000000000003180 > InstallProtocolInterface: 18A031AB-B443-4D1A-A5C0-0C09261E9F71 > 3D7CCF20 > InstallProtocolInterface: 107A772C-D5E1-11D4-9A46-0090273FC14D 3D7CD040 > InstallProtocolInterface: 6A7A5CFF-E8D9-4F70-BADA-75AB3025CE14 > 3D7CCF00 > Loading driver E2775B47-D453-4EE3-ADA7-391A1B05AC17 > None of Tcg2Protocol/CcMeasurementProtocol is installed. > InstallProtocolInterface: 5B1B31A1-9562-11D2-8E3F-00A0C969723B 3D8679C0 > Loading driver at 0x0003D79F000 EntryPoint=0x0003D7A35D0 > PciSioSerialDxe.efi > InstallProtocolInterface: BC62157E-3E33-4FEC-9920-2D3B36D750DF 3D867898 > ProtectUefiImageCommon - 0x3D8679C0 > - 0x000000003D79F000 - 0x0000000000006100 > InstallProtocolInterface: 18A031AB-B443-4D1A-A5C0-0C09261E9F71 > 3D7A4F40 > InstallProtocolInterface: 107A772C-D5E1-11D4-9A46-0090273FC14D > 3D7A4FA0 > InstallProtocolInterface: 6A7A5CFF-E8D9-4F70-BADA-75AB3025CE14 > 3D7A4DB0 > Loading driver C4D1F932-821F-4744-BF06-6D30F7730F8D > None of Tcg2Protocol/CcMeasurementProtocol is installed. > InstallProtocolInterface: 5B1B31A1-9562-11D2-8E3F-00A0C969723B 3D866040 > Loading driver at 0x0003D78C000 EntryPoint=0x0003D78FC07 > Ps2KeyboardDxe.efi > InstallProtocolInterface: BC62157E-3E33-4FEC-9920-2D3B36D750DF 3D867598 > ProtectUefiImageCommon - 0x3D866040 > - 0x000000003D78C000 - 0x0000000000005AC0 > InstallProtocolInterface: 18A031AB-B443-4D1A-A5C0-0C09261E9F71 3D7918E0 > InstallProtocolInterface: 107A772C-D5E1-11D4-9A46-0090273FC14D 3D791940 > InstallProtocolInterface: 6A7A5CFF-E8D9-4F70-BADA-75AB3025CE14 > 3D791870 > Loading driver B8E62775-BB0A-43F0-A843-5BE8B14F8CCD > None of Tcg2Protocol/CcMeasurementProtocol is installed. > InstallProtocolInterface: 5B1B31A1-9562-11D2-8E3F-00A0C969723B 3D866440 > Loading driver at 0x0003D7E1000 EntryPoint=0x0003D7E25A5 > BootGraphicsResourceTableDxe.efi > InstallProtocolInterface: BC62157E-3E33-4FEC-9920-2D3B36D750DF 3D866698 > ProtectUefiImageCommon - 0x3D866440 > - 0x000000003D7E1000 - 0x0000000000002900 > InstallProtocolInterface: CDEA2BD3-FC25-4C1C-B97C-B31186064990 3D7E36B0 > InstallProtocolInterface: 4B5DC1DF-1EAA-48B2-A7E9-EAC489A00B5C > 3D7E3730 > Loading driver 961578FE-B6B7-44C3-AF35-6BC705CD2B1F > None of Tcg2Protocol/CcMeasurementProtocol is installed. > InstallProtocolInterface: 5B1B31A1-9562-11D2-8E3F-00A0C969723B 3D8650C0 > Loading driver at 0x0003D778000 EntryPoint=0x0003D77FD7C Fat.efi > InstallProtocolInterface: BC62157E-3E33-4FEC-9920-2D3B36D750DF 3D865A98 > ProtectUefiImageCommon - 0x3D8650C0 > - 0x000000003D778000 - 0x0000000000009F40 > InstallProtocolInterface: 18A031AB-B443-4D1A-A5C0-0C09261E9F71 > 3D781DA0 > InstallProtocolInterface: 107A772C-D5E1-11D4-9A46-0090273FC14D 3D781E00 > InstallProtocolInterface: 6A7A5CFF-E8D9-4F70-BADA-75AB3025CE14 > 3D781BD0 > Loading driver 905F13B0-8F91-4B0A-BD76-E1E78F9422E4 > None of Tcg2Protocol/CcMeasurementProtocol is installed. > InstallProtocolInterface: 5B1B31A1-9562-11D2-8E3F-00A0C969723B 3D8653C0 > Loading driver at 0x0003D771000 EntryPoint=0x0003D775B8A UdfDxe.efi > InstallProtocolInterface: BC62157E-3E33-4FEC-9920-2D3B36D750DF 3D865798 > ProtectUefiImageCommon - 0x3D8653C0 > - 0x000000003D771000 - 0x0000000000006480 > InstallProtocolInterface: 18A031AB-B443-4D1A-A5C0-0C09261E9F71 3D7771E0 > InstallProtocolInterface: 107A772C-D5E1-11D4-9A46-0090273FC14D 3D777340 > InstallProtocolInterface: 6A7A5CFF-E8D9-4F70-BADA-75AB3025CE14 > 3D7771C0 > Loading driver 7BD9DDF7-8B83-488E-AEC9-24C78610289C > None of Tcg2Protocol/CcMeasurementProtocol is installed. > InstallProtocolInterface: 5B1B31A1-9562-11D2-8E3F-00A0C969723B 3D7EECC0 > Loading driver at 0x0003D767000 EntryPoint=0x0003D76E441 VirtioFsDxe.efi > InstallProtocolInterface: BC62157E-3E33-4FEC-9920-2D3B36D750DF 3D7EE818 > ProtectUefiImageCommon - 0x3D7EECC0 > - 0x000000003D767000 - 0x0000000000009740 > InstallProtocolInterface: 18A031AB-B443-4D1A-A5C0-0C09261E9F71 3D770620 > InstallProtocolInterface: 6A7A5CFF-E8D9-4F70-BADA-75AB3025CE14 > 3D770600 > Loading driver A2F436EA-A127-4EF8-957C-8048606FF670 > None of Tcg2Protocol/CcMeasurementProtocol is installed. > InstallProtocolInterface: 5B1B31A1-9562-11D2-8E3F-00A0C969723B 3D7EE3C0 > Loading driver at 0x0003D75F000 EntryPoint=0x0003D764032 SnpDxe.efi > InstallProtocolInterface: BC62157E-3E33-4FEC-9920-2D3B36D750DF 3D7EE218 > ProtectUefiImageCommon - 0x3D7EE3C0 > - 0x000000003D75F000 - 0x0000000000007240 > InstallProtocolInterface: 18A031AB-B443-4D1A-A5C0-0C09261E9F71 3D766040 > InstallProtocolInterface: 107A772C-D5E1-11D4-9A46-0090273FC14D 3D7660A0 > InstallProtocolInterface: 6A7A5CFF-E8D9-4F70-BADA-75AB3025CE14 > 3D766010 > Loading driver E4F61863-FE2C-4B56-A8F4-08519BC439DF > None of Tcg2Protocol/CcMeasurementProtocol is installed. > InstallProtocolInterface: 5B1B31A1-9562-11D2-8E3F-00A0C969723B 3D7ED0C0 > Loading driver at 0x0003D758000 EntryPoint=0x0003D75C604 > VlanConfigDxe.efi > InstallProtocolInterface: BC62157E-3E33-4FEC-9920-2D3B36D750DF 3D7ED918 > ProtectUefiImageCommon - 0x3D7ED0C0 > - 0x000000003D758000 - 0x0000000000006CC0 > InstallProtocolInterface: 18A031AB-B443-4D1A-A5C0-0C09261E9F71 3D75E380 > InstallProtocolInterface: 107A772C-D5E1-11D4-9A46-0090273FC14D 3D75EB40 > InstallProtocolInterface: 6A7A5CFF-E8D9-4F70-BADA-75AB3025CE14 > 3D75E360 > Loading driver 025BBFC7-E6A9-4B8B-82AD-6815A1AEAF4A > None of Tcg2Protocol/CcMeasurementProtocol is installed. > InstallProtocolInterface: 5B1B31A1-9562-11D2-8E3F-00A0C969723B 3D7ED3C0 > Loading driver at 0x0003D742000 EntryPoint=0x0003D7496A7 MnpDxe.efi > InstallProtocolInterface: BC62157E-3E33-4FEC-9920-2D3B36D750DF 3D7ED718 > ProtectUefiImageCommon - 0x3D7ED3C0 > - 0x000000003D742000 - 0x000000000000A4C0 > InstallProtocolInterface: 18A031AB-B443-4D1A-A5C0-0C09261E9F71 > 3D74C2C0 > InstallProtocolInterface: 107A772C-D5E1-11D4-9A46-0090273FC14D 3D74C340 > InstallProtocolInterface: 6A7A5CFF-E8D9-4F70-BADA-75AB3025CE14 > 3D74C2F0 > Loading driver 529D3F93-E8E9-4E73-B1E1-BDF6A9D50113 > None of Tcg2Protocol/CcMeasurementProtocol is installed. > InstallProtocolInterface: 5B1B31A1-9562-11D2-8E3F-00A0C969723B 3D7EC0C0 > Loading driver at 0x0003D752000 EntryPoint=0x0003D75616E ArpDxe.efi > InstallProtocolInterface: BC62157E-3E33-4FEC-9920-2D3B36D750DF 3D7EC898 > ProtectUefiImageCommon - 0x3D7EC0C0 > - 0x000000003D752000 - 0x0000000000005E40 > InstallProtocolInterface: 18A031AB-B443-4D1A-A5C0-0C09261E9F71 3D757C40 > InstallProtocolInterface: 107A772C-D5E1-11D4-9A46-0090273FC14D 3D757D00 > InstallProtocolInterface: 6A7A5CFF-E8D9-4F70-BADA-75AB3025CE14 > 3D757BA0 > Loading driver 94734718-0BBC-47FB-96A5-EE7A5AE6A2AD > None of Tcg2Protocol/CcMeasurementProtocol is installed. > InstallProtocolInterface: 5B1B31A1-9562-11D2-8E3F-00A0C969723B 3D7EC540 > Loading driver at 0x0003D72C000 EntryPoint=0x0003D73353B Dhcp4Dxe.efi > InstallProtocolInterface: BC62157E-3E33-4FEC-9920-2D3B36D750DF 3D7E0F98 > ProtectUefiImageCommon - 0x3D7EC540 > - 0x000000003D72C000 - 0x000000000000A380 > InstallProtocolInterface: 18A031AB-B443-4D1A-A5C0-0C09261E9F71 3D7360C0 > InstallProtocolInterface: 107A772C-D5E1-11D4-9A46-0090273FC14D 3D7361C0 > InstallProtocolInterface: 6A7A5CFF-E8D9-4F70-BADA-75AB3025CE14 > 3D736120 > Loading driver 9FB1A1F3-3B71-4324-B39A-745CBB015FFF > None of Tcg2Protocol/CcMeasurementProtocol is installed. > InstallProtocolInterface: 5B1B31A1-9562-11D2-8E3F-00A0C969723B 3D7E01C0 > Loading driver at 0x0003D704000 EntryPoint=0x0003D71365D Ip4Dxe.efi > InstallProtocolInterface: BC62157E-3E33-4FEC-9920-2D3B36D750DF 3D7E0A18 > ProtectUefiImageCommon - 0x3D7E01C0 > - 0x000000003D704000 - 0x0000000000013E80 > Select Item: 0x0 > FW CFG Signature: 0x554D4551 > Select Item: 0x1 > FW CFG Revision: 0x3 > QemuFwCfg interface (DMA) is supported. > Select Item: 0x19 > InstallProtocolInterface: 18A031AB-B443-4D1A-A5C0-0C09261E9F71 > 3D717A60 > InstallProtocolInterface: 107A772C-D5E1-11D4-9A46-0090273FC14D 3D7179C0 > InstallProtocolInterface: 6A7A5CFF-E8D9-4F70-BADA-75AB3025CE14 > 3D717970 > Loading driver 6D6963AB-906D-4A65-A7CA-BD40E5D6AF2B > None of Tcg2Protocol/CcMeasurementProtocol is installed. > InstallProtocolInterface: 5B1B31A1-9562-11D2-8E3F-00A0C969723B 3D7DFB40 > Loading driver at 0x0003D739000 EntryPoint=0x0003D73F5F1 Udp4Dxe.efi > InstallProtocolInterface: BC62157E-3E33-4FEC-9920-2D3B36D750DF 3D7DFA98 > ProtectUefiImageCommon - 0x3D7DFB40 > - 0x000000003D739000 - 0x0000000000008900 > InstallProtocolInterface: 18A031AB-B443-4D1A-A5C0-0C09261E9F71 3D7416C0 > InstallProtocolInterface: 107A772C-D5E1-11D4-9A46-0090273FC14D 3D7417A0 > InstallProtocolInterface: 6A7A5CFF-E8D9-4F70-BADA-75AB3025CE14 > 3D741730 > Loading driver DC3641B8-2FA8-4ED3-BC1F-F9962A03454B > None of Tcg2Protocol/CcMeasurementProtocol is installed. > InstallProtocolInterface: 5B1B31A1-9562-11D2-8E3F-00A0C969723B 3D7DF240 > Loading driver at 0x0003D722000 EntryPoint=0x0003D728E8A Mtftp4Dxe.efi > InstallProtocolInterface: BC62157E-3E33-4FEC-9920-2D3B36D750DF 3D7DF718 > ProtectUefiImageCommon - 0x3D7DF240 > - 0x000000003D722000 - 0x00000000000091C0 > InstallProtocolInterface: 18A031AB-B443-4D1A-A5C0-0C09261E9F71 > 3D72AF80 > InstallProtocolInterface: 107A772C-D5E1-11D4-9A46-0090273FC14D 3D72B000 > InstallProtocolInterface: 6A7A5CFF-E8D9-4F70-BADA-75AB3025CE14 > 3D72AFB0 > Loading driver 95E3669D-34BE-4775-A651-7EA41B69D89E > None of Tcg2Protocol/CcMeasurementProtocol is installed. > InstallProtocolInterface: 5B1B31A1-9562-11D2-8E3F-00A0C969723B 3D7DECC0 > Loading driver at 0x0003D6EE000 EntryPoint=0x0003D6F69BF Dhcp6Dxe.efi > InstallProtocolInterface: BC62157E-3E33-4FEC-9920-2D3B36D750DF 3D7DEB18 > ProtectUefiImageCommon - 0x3D7DECC0 > - 0x000000003D6EE000 - 0x000000000000AC40 > InstallProtocolInterface: 18A031AB-B443-4D1A-A5C0-0C09261E9F71 3D6F89E0 > InstallProtocolInterface: 107A772C-D5E1-11D4-9A46-0090273FC14D 3D6F8920 > InstallProtocolInterface: 6A7A5CFF-E8D9-4F70-BADA-75AB3025CE14 > 3D6F8880 > Loading driver 5BEDB5CC-D830-4EB2-8742-2D4CC9B54F2C > None of Tcg2Protocol/CcMeasurementProtocol is installed. > InstallProtocolInterface: 5B1B31A1-9562-11D2-8E3F-00A0C969723B 3D7DE3C0 > Loading driver at 0x0003D6B4000 EntryPoint=0x0003D6C4ECF Ip6Dxe.efi > InstallProtocolInterface: BC62157E-3E33-4FEC-9920-2D3B36D750DF 3D7DDF18 > ProtectUefiImageCommon - 0x3D7DE3C0 > - 0x000000003D6B4000 - 0x000000000001C7C0 > Select Item: 0x0 > FW CFG Signature: 0x554D4551 > Select Item: 0x1 > FW CFG Revision: 0x3 > QemuFwCfg interface (DMA) is supported. > Select Item: 0x19 > InstallProtocolInterface: 18A031AB-B443-4D1A-A5C0-0C09261E9F71 3D6CF0E0 > InstallProtocolInterface: 107A772C-D5E1-11D4-9A46-0090273FC14D 3D6CF060 > InstallProtocolInterface: 6A7A5CFF-E8D9-4F70-BADA-75AB3025CE14 > 3D6CF010 > Loading driver D912C7BC-F098-4367-92BA-E911083C7B0E > None of Tcg2Protocol/CcMeasurementProtocol is installed. > InstallProtocolInterface: 5B1B31A1-9562-11D2-8E3F-00A0C969723B 3D7DD1C0 > Loading driver at 0x0003D719000 EntryPoint=0x0003D71F5C5 Udp6Dxe.efi > InstallProtocolInterface: BC62157E-3E33-4FEC-9920-2D3B36D750DF > 3D7DDA18 > ProtectUefiImageCommon - 0x3D7DD1C0 > - 0x000000003D719000 - 0x0000000000008A00 > InstallProtocolInterface: 18A031AB-B443-4D1A-A5C0-0C09261E9F71 3D7217E0 > InstallProtocolInterface: 107A772C-D5E1-11D4-9A46-0090273FC14D 3D721780 > InstallProtocolInterface: 6A7A5CFF-E8D9-4F70-BADA-75AB3025CE14 > 3D721740 > Loading driver 99F03B99-98D8-49DD-A8D3-3219D0FFE41E > None of Tcg2Protocol/CcMeasurementProtocol is installed. > InstallProtocolInterface: 5B1B31A1-9562-11D2-8E3F-00A0C969723B 3D7C9040 > Loading driver at 0x0003D6FA000 EntryPoint=0x0003D7016FA Mtftp6Dxe.efi > InstallProtocolInterface: BC62157E-3E33-4FEC-9920-2D3B36D750DF 3D7C9E98 > ProtectUefiImageCommon - 0x3D7C9040 > - 0x000000003D6FA000 - 0x0000000000009A40 > InstallProtocolInterface: 18A031AB-B443-4D1A-A5C0-0C09261E9F71 > 3D7038A0 > InstallProtocolInterface: 107A772C-D5E1-11D4-9A46-0090273FC14D 3D703800 > InstallProtocolInterface: 6A7A5CFF-E8D9-4F70-BADA-75AB3025CE14 > 3D7037C0 > Loading driver 1A7E4468-2F55-4A56-903C-01265EB7622B > None of Tcg2Protocol/CcMeasurementProtocol is installed. > InstallProtocolInterface: 5B1B31A1-9562-11D2-8E3F-00A0C969723B 3D7C99C0 > Loading driver at 0x0003D6A1000 EntryPoint=0x0003D6AB4F8 TcpDxe.efi > InstallProtocolInterface: BC62157E-3E33-4FEC-9920-2D3B36D750DF 3D7C9918 > ProtectUefiImageCommon - 0x3D7C99C0 > - 0x000000003D6A1000 - 0x0000000000012140 > InstallProtocolInterface: 18A031AB-B443-4D1A-A5C0-0C09261E9F71 > 3D6B2D20 > InstallProtocolInterface: 107A772C-D5E1-11D4-9A46-0090273FC14D 3D6B2BE0 > InstallProtocolInterface: 6A7A5CFF-E8D9-4F70-BADA-75AB3025CE14 > 3D6B2BA0 > InstallProtocolInterface: 18A031AB-B443-4D1A-A5C0-0C09261E9F71 > 3D6B2CE0 > InstallProtocolInterface: 107A772C-D5E1-11D4-9A46-0090273FC14D 3D6B2BE0 > InstallProtocolInterface: 6A7A5CFF-E8D9-4F70-BADA-75AB3025CE14 > 3D6B2BA0 > Loading driver B95E9FDA-26DE-48D2-8807-1F9107AC5E3A > None of Tcg2Protocol/CcMeasurementProtocol is installed. > InstallProtocolInterface: 5B1B31A1-9562-11D2-8E3F-00A0C969723B 3D7C80C0 > Loading driver at 0x0003D68F000 EntryPoint=0x0003D69C4CF > UefiPxeBcDxe.efi > InstallProtocolInterface: BC62157E-3E33-4FEC-9920-2D3B36D750DF 3D7C8A18 > ProtectUefiImageCommon - 0x3D7C80C0 > - 0x000000003D68F000 - 0x00000000000110C0 > Select Item: 0x0 > FW CFG Signature: 0x554D4551 > Select Item: 0x1 > FW CFG Revision: 0x3 > QemuFwCfg interface (DMA) is supported. > Select Item: 0x19 > Select Item: 0x19 > InstallProtocolInterface: 18A031AB-B443-4D1A-A5C0-0C09261E9F71 3D69FE40 > InstallProtocolInterface: 107A772C-D5E1-11D4-9A46-0090273FC14D 3D69FD60 > InstallProtocolInterface: 6A7A5CFF-E8D9-4F70-BADA-75AB3025CE14 > 3D69FE10 > InstallProtocolInterface: 18A031AB-B443-4D1A-A5C0-0C09261E9F71 > 3D69FDE0 > InstallProtocolInterface: 107A772C-D5E1-11D4-9A46-0090273FC14D 3D69FD60 > InstallProtocolInterface: 6A7A5CFF-E8D9-4F70-BADA-75AB3025CE14 > 3D69FE10 > Loading driver 3ACEB0C0-3C72-11E4-9A56-74D435052646 > None of Tcg2Protocol/CcMeasurementProtocol is installed. > InstallProtocolInterface: 5B1B31A1-9562-11D2-8E3F-00A0C969723B 3D7B6040 > Loading driver at 0x0003D549000 EntryPoint=0x0003D5AD4DA TlsDxe.efi > InstallProtocolInterface: BC62157E-3E33-4FEC-9920-2D3B36D750DF 3D7B6D18 > ProtectUefiImageCommon - 0x3D7B6040 > - 0x000000003D549000 - 0x00000000000A2D40 > InstallProtocolInterface: 952CB795-FF36-48CF-A249-4DF486D6AB8D > 3D7B6EA0 > Loading driver B219E140-DFFC-11E3-B956-0022681E6906 > None of Tcg2Protocol/CcMeasurementProtocol is installed. > InstallProtocolInterface: 5B1B31A1-9562-11D2-8E3F-00A0C969723B 3D788340 > Loading driver at 0x0003D6D6000 EntryPoint=0x0003D6DF9BF DnsDxe.efi > InstallProtocolInterface: BC62157E-3E33-4FEC-9920-2D3B36D750DF 3D7C8418 > ProtectUefiImageCommon - 0x3D788340 > - 0x000000003D6D6000 - 0x000000000000BE00 > InstallProtocolInterface: 18A031AB-B443-4D1A-A5C0-0C09261E9F71 > 3D6E1AE0 > InstallProtocolInterface: 107A772C-D5E1-11D4-9A46-0090273FC14D 3D6E1C80 > InstallProtocolInterface: 6A7A5CFF-E8D9-4F70-BADA-75AB3025CE14 > 3D6E1C40 > InstallProtocolInterface: 18A031AB-B443-4D1A-A5C0-0C09261E9F71 > 3D6E1AA0 > InstallProtocolInterface: 107A772C-D5E1-11D4-9A46-0090273FC14D 3D6E1C80 > InstallProtocolInterface: 6A7A5CFF-E8D9-4F70-BADA-75AB3025CE14 > 3D6E1C40 > Loading driver 2366C20F-E15A-11E3-8BF1-E4115B28BC50 > None of Tcg2Protocol/CcMeasurementProtocol is installed. > InstallProtocolInterface: 5B1B31A1-9562-11D2-8E3F-00A0C969723B 3D786440 > Loading driver at 0x0003D673000 EntryPoint=0x0003D67CDFC HttpDxe.efi > InstallProtocolInterface: BC62157E-3E33-4FEC-9920-2D3B36D750DF 3D786918 > ProtectUefiImageCommon - 0x3D786440 > - 0x000000003D673000 - 0x000000000000D880 > InstallProtocolInterface: 18A031AB-B443-4D1A-A5C0-0C09261E9F71 3D680540 > InstallProtocolInterface: 107A772C-D5E1-11D4-9A46-0090273FC14D 3D680510 > InstallProtocolInterface: 6A7A5CFF-E8D9-4F70-BADA-75AB3025CE14 > 3D680740 > InstallProtocolInterface: 18A031AB-B443-4D1A-A5C0-0C09261E9F71 3D6804E0 > InstallProtocolInterface: 107A772C-D5E1-11D4-9A46-0090273FC14D 3D680510 > InstallProtocolInterface: 6A7A5CFF-E8D9-4F70-BADA-75AB3025CE14 > 3D680740 > Loading driver ECEBCB00-D9C8-11E4-AF3D-8CDCD426C973 > None of Tcg2Protocol/CcMeasurementProtocol is installed. > InstallProtocolInterface: 5B1B31A1-9562-11D2-8E3F-00A0C969723B 3D7850C0 > Loading driver at 0x0003D64F000 EntryPoint=0x0003D6594D7 HttpBootDxe.efi > InstallProtocolInterface: BC62157E-3E33-4FEC-9920-2D3B36D750DF 3D785E18 > ProtectUefiImageCommon - 0x3D7850C0 > - 0x000000003D64F000 - 0x0000000000011580 > InstallProtocolInterface: 18A031AB-B443-4D1A-A5C0-0C09261E9F71 > 3D65FD80 > InstallProtocolInterface: 107A772C-D5E1-11D4-9A46-0090273FC14D 3D65FD50 > InstallProtocolInterface: 6A7A5CFF-E8D9-4F70-BADA-75AB3025CE14 > 3D65FF00 > InstallProtocolInterface: 18A031AB-B443-4D1A-A5C0-0C09261E9F71 > 3D65FD20 > InstallProtocolInterface: 107A772C-D5E1-11D4-9A46-0090273FC14D 3D65FD50 > InstallProtocolInterface: 6A7A5CFF-E8D9-4F70-BADA-75AB3025CE14 > 3D65FF00 > Loading driver 86CDDF93-4872-4597-8AF9-A35AE4D3725F > None of Tcg2Protocol/CcMeasurementProtocol is installed. > InstallProtocolInterface: 5B1B31A1-9562-11D2-8E3F-00A0C969723B 3D784040 > Loading driver at 0x0003D611000 EntryPoint=0x0003D62302A IScsiDxe.efi > InstallProtocolInterface: BC62157E-3E33-4FEC-9920-2D3B36D750DF 3D785398 > ProtectUefiImageCommon - 0x3D784040 > - 0x000000003D611000 - 0x000000000001E880 > InstallProtocolInterface: 18A031AB-B443-4D1A-A5C0-0C09261E9F71 3D62F560 > InstallProtocolInterface: 107A772C-D5E1-11D4-9A46-0090273FC14D 3D62DC00 > InstallProtocolInterface: 6A7A5CFF-E8D9-4F70-BADA-75AB3025CE14 > 3D62DB70 > InstallProtocolInterface: 18A031AB-B443-4D1A-A5C0-0C09261E9F71 3D62F520 > InstallProtocolInterface: 107A772C-D5E1-11D4-9A46-0090273FC14D 3D62DC00 > InstallProtocolInterface: 6A7A5CFF-E8D9-4F70-BADA-75AB3025CE14 > 3D62DB70 > InstallProtocolInterface: 59324945-EC44-4C0D-B1CD-9DB139DF070C > 3D62DB00 > InstallProtocolInterface: 09576E91-6D3F-11D2-8E39-00A0C969723B 3D62F4A0 > InstallProtocolInterface: 330D4706-F2A0-4E4F-A369-B66FA8D54385 3D784BA8 > InstallProtocolInterface: 7671D9D0-53DB-4173-AA69-2327F21F0BC7 3D62F500 > Loading driver A92CDB4B-82F1-4E0B-A516-8A655D371524 > None of Tcg2Protocol/CcMeasurementProtocol is installed. > InstallProtocolInterface: 5B1B31A1-9562-11D2-8E3F-00A0C969723B 3D7518C0 > Loading driver at 0x0003D689000 EntryPoint=0x0003D68CA9F > VirtioNetDxe.efi > InstallProtocolInterface: BC62157E-3E33-4FEC-9920-2D3B36D750DF 3D751418 > ProtectUefiImageCommon - 0x3D7518C0 > - 0x000000003D689000 - 0x00000000000053C0 > InstallProtocolInterface: 18A031AB-B443-4D1A-A5C0-0C09261E9F71 3D68E200 > InstallProtocolInterface: 107A772C-D5E1-11D4-9A46-0090273FC14D 3D68E260 > InstallProtocolInterface: 6A7A5CFF-E8D9-4F70-BADA-75AB3025CE14 > 3D68E180 > Loading driver 2FB92EFA-2EE0-4BAE-9EB6-7464125E1EF7 > None of Tcg2Protocol/CcMeasurementProtocol is installed. > InstallProtocolInterface: 5B1B31A1-9562-11D2-8E3F-00A0C969723B 3D783040 > Loading driver at 0x0003D682000 EntryPoint=0x0003D6870DF UhciDxe.efi > InstallProtocolInterface: BC62157E-3E33-4FEC-9920-2D3B36D750DF 3D751398 > ProtectUefiImageCommon - 0x3D783040 > - 0x000000003D682000 - 0x0000000000006DC0 > InstallProtocolInterface: 18A031AB-B443-4D1A-A5C0-0C09261E9F71 > 3D688BC0 > InstallProtocolInterface: 107A772C-D5E1-11D4-9A46-0090273FC14D 3D688C40 > InstallProtocolInterface: 6A7A5CFF-E8D9-4F70-BADA-75AB3025CE14 > 3D688C20 > Loading driver BDFE430E-8F2A-4DB0-9991-6F856594777E > None of Tcg2Protocol/CcMeasurementProtocol is installed. > InstallProtocolInterface: 5B1B31A1-9562-11D2-8E3F-00A0C969723B 3D783540 > Loading driver at 0x0003D661000 EntryPoint=0x0003D6672CA EhciDxe.efi > InstallProtocolInterface: BC62157E-3E33-4FEC-9920-2D3B36D750DF 3D783A18 > ProtectUefiImageCommon - 0x3D783540 > - 0x000000003D661000 - 0x0000000000008800 > InstallProtocolInterface: 18A031AB-B443-4D1A-A5C0-0C09261E9F71 3D669660 > InstallProtocolInterface: 107A772C-D5E1-11D4-9A46-0090273FC14D 3D6696C0 > InstallProtocolInterface: 6A7A5CFF-E8D9-4F70-BADA-75AB3025CE14 > 3D6695F0 > Loading driver B7F50E91-A759-412C-ADE4-DCD03E7F7C28 > None of Tcg2Protocol/CcMeasurementProtocol is installed. > InstallProtocolInterface: 5B1B31A1-9562-11D2-8E3F-00A0C969723B 3D7837C0 > Loading driver at 0x0003D635000 EntryPoint=0x0003D63EA6C XhciDxe.efi > InstallProtocolInterface: BC62157E-3E33-4FEC-9920-2D3B36D750DF 3D782C18 > ProtectUefiImageCommon - 0x3D7837C0 > - 0x000000003D635000 - 0x000000000000CE00 > InstallProtocolInterface: 18A031AB-B443-4D1A-A5C0-0C09261E9F71 3D641B80 > InstallProtocolInterface: 107A772C-D5E1-11D4-9A46-0090273FC14D 3D641C80 > InstallProtocolInterface: 6A7A5CFF-E8D9-4F70-BADA-75AB3025CE14 > 3D641C60 > Loading driver 240612B7-A063-11D4-9A3A-0090273FC14D > None of Tcg2Protocol/CcMeasurementProtocol is installed. > InstallProtocolInterface: 5B1B31A1-9562-11D2-8E3F-00A0C969723B 3D782540 > Loading driver at 0x0003D607000 EntryPoint=0x0003D60D8B0 UsbBusDxe.efi > InstallProtocolInterface: BC62157E-3E33-4FEC-9920-2D3B36D750DF 3D782418 > ProtectUefiImageCommon - 0x3D782540 > - 0x000000003D607000 - 0x00000000000095C0 > InstallProtocolInterface: 18A031AB-B443-4D1A-A5C0-0C09261E9F71 3D610320 > InstallProtocolInterface: 107A772C-D5E1-11D4-9A46-0090273FC14D 3D610280 > InstallProtocolInterface: 6A7A5CFF-E8D9-4F70-BADA-75AB3025CE14 > 3D610220 > Loading driver 2D2E62CF-9ECF-43B7-8219-94E7FC713DFE > None of Tcg2Protocol/CcMeasurementProtocol is installed. > InstallProtocolInterface: 5B1B31A1-9562-11D2-8E3F-00A0C969723B 3D738D40 > Loading driver at 0x0003D66C000 EntryPoint=0x0003D67003E UsbKbDxe.efi > InstallProtocolInterface: BC62157E-3E33-4FEC-9920-2D3B36D750DF 3D738C18 > ProtectUefiImageCommon - 0x3D738D40 > - 0x000000003D66C000 - 0x0000000000006300 > InstallProtocolInterface: 18A031AB-B443-4D1A-A5C0-0C09261E9F71 > 3D6719A0 > InstallProtocolInterface: 107A772C-D5E1-11D4-9A46-0090273FC14D 3D672160 > InstallProtocolInterface: 6A7A5CFF-E8D9-4F70-BADA-75AB3025CE14 > 3D672140 > Loading driver 9FB4B4A7-42C0-4BCD-8540-9BCC6711F83E > None of Tcg2Protocol/CcMeasurementProtocol is installed. > InstallProtocolInterface: 5B1B31A1-9562-11D2-8E3F-00A0C969723B 3D7382C0 > Loading driver at 0x0003D649000 EntryPoint=0x0003D64CBEE > UsbMassStorageDxe.efi > InstallProtocolInterface: BC62157E-3E33-4FEC-9920-2D3B36D750DF 3D738A98 > ProtectUefiImageCommon - 0x3D7382C0 > - 0x000000003D649000 - 0x0000000000005A00 > InstallProtocolInterface: 18A031AB-B443-4D1A-A5C0-0C09261E9F71 > 3D64E7A0 > InstallProtocolInterface: 107A772C-D5E1-11D4-9A46-0090273FC14D 3D64E880 > InstallProtocolInterface: 6A7A5CFF-E8D9-4F70-BADA-75AB3025CE14 > 3D64E770 > Loading driver E3752948-B9A1-4770-90C4-DF41C38986BE > None of Tcg2Protocol/CcMeasurementProtocol is installed. > InstallProtocolInterface: 5B1B31A1-9562-11D2-8E3F-00A0C969723B 3D737D40 > Loading driver at 0x0003D642000 EntryPoint=0x0003D645F30 > QemuVideoDxe.efi > InstallProtocolInterface: BC62157E-3E33-4FEC-9920-2D3B36D750DF 3D737B98 > ProtectUefiImageCommon - 0x3D737D40 > - 0x000000003D642000 - 0x00000000000066C0 > InstallProtocolInterface: 18A031AB-B443-4D1A-A5C0-0C09261E9F71 3D648520 > InstallProtocolInterface: 107A772C-D5E1-11D4-9A46-0090273FC14D 3D648580 > InstallProtocolInterface: 6A7A5CFF-E8D9-4F70-BADA-75AB3025CE14 > 3D648310 > Loading driver D6099B94-CD97-4CC5-8714-7F6312701A8A > None of Tcg2Protocol/CcMeasurementProtocol is installed. > InstallProtocolInterface: 5B1B31A1-9562-11D2-8E3F-00A0C969723B 3D7377C0 > Loading driver at 0x0003D601000 EntryPoint=0x0003D604F76 > VirtioGpuDxe.efi > InstallProtocolInterface: BC62157E-3E33-4FEC-9920-2D3B36D750DF 3D737A98 > ProtectUefiImageCommon - 0x3D7377C0 > - 0x000000003D601000 - 0x0000000000005D00 > InstallProtocolInterface: 18A031AB-B443-4D1A-A5C0-0C09261E9F71 > 3D606AE0 > InstallProtocolInterface: 6A7A5CFF-E8D9-4F70-BADA-75AB3025CE14 > 3D606AB0 > Driver 5CAB08D5-AD8F-4D8B-B828-D17A8D9FE977 was discovered but not > loaded!! > Driver 4D9CBEF0-15A0-4D0C-83DB-5213E710C23F was discovered but not > loaded!! > [Bds] Entry... > [BdsDxe] Locate Variable Policy protocol - Success > Variable Driver Auto Update Lang, Lang:eng, PlatformLang:en Status: Success > PlatformBootManagerBeforeConsole > Registered NotifyDevPath Event > PCI Bus First Scanning > PciBus: Discovered PCI @ [00|00|00] [VID = 0x8086, DID = 0x29C0] > > PciBus: Discovered PCI @ [00|01|00] [VID = 0x8086, DID = 0x10D3] > BAR[0]: Type = Mem32; Alignment = 0x1FFFF; Length = 0x20000; > Offset = 0x10 > BAR[1]: Type = Mem32; Alignment = 0x1FFFF; Length = 0x20000; > Offset = 0x14 > BAR[2]: Type = Io32; Alignment = 0x1F; Length = 0x20; Offset = 0x18 > BAR[3]: Type = Mem32; Alignment = 0x3FFF; Length = 0x4000; > Offset = 0x1C > > PciBus: Discovered PPB @ [00|08|00] [VID = 0x1B36, DID = 0xC] > Padding: Type = PMem64; Alignment = 0xFFFFFFF; Length = 0x10000000 > Padding: Type = Mem32; Alignment = 0x1FFFFF; Length = 0x200000 > Padding: Type = Io; Alignment = 0x1FF; Length = 0x200 > BAR[0]: Type = Mem32; Alignment = 0xFFF; Length = 0x1000; > Offset = 0x10 > > PciBus: Discovered PCI @ [01|00|00] [VID = 0x1AF4, DID = 0x1042] > BAR[1]: Type = Mem32; Alignment = 0xFFF; Length = 0x1000; > Offset = 0x14 > BAR[4]: Type = PMem64; Alignment = 0x3FFF; Length = 0x4000; > Offset = 0x20 > > PciBus: Discovered PCI @ [00|1F|00] [VID = 0x8086, DID = 0x2918] > > PciBus: Discovered PCI @ [00|1F|02] [VID = 0x8086, DID = 0x2922] > BAR[4]: Type = Io32; Alignment = 0x1F; Length = 0x20; Offset = 0x20 > BAR[5]: Type = Mem32; Alignment = 0xFFF; Length = 0x1000; > Offset = 0x24 > > PciBus: Discovered PCI @ [00|1F|03] [VID = 0x8086, DID = 0x2930] > BAR[4]: Type = Io32; Alignment = 0x3F; Length = 0x40; Offset = 0x20 > > PCI Bus Second Scanning > PciBus: Discovered PCI @ [00|00|00] [VID = 0x8086, DID = 0x29C0] > > PciBus: Discovered PCI @ [00|01|00] [VID = 0x8086, DID = 0x10D3] > BAR[0]: Type = Mem32; Alignment = 0x1FFFF; Length = 0x20000; > Offset = 0x10 > BAR[1]: Type = Mem32; Alignment = 0x1FFFF; Length = 0x20000; > Offset = 0x14 > BAR[2]: Type = Io32; Alignment = 0x1F; Length = 0x20; Offset = 0x18 > BAR[3]: Type = Mem32; Alignment = 0x3FFF; Length = 0x4000; > Offset = 0x1C > > PciBus: Discovered PPB @ [00|08|00] [VID = 0x1B36, DID = 0xC] > Padding: Type = PMem64; Alignment = 0xFFFFFFF; Length = 0x10000000 > Padding: Type = Mem32; Alignment = 0x1FFFFF; Length = 0x200000 > Padding: Type = Io; Alignment = 0x1FF; Length = 0x200 > BAR[0]: Type = Mem32; Alignment = 0xFFF; Length = 0x1000; > Offset = 0x10 > > PciBus: Discovered PCI @ [01|00|00] [VID = 0x1AF4, DID = 0x1042] > BAR[1]: Type = Mem32; Alignment = 0xFFF; Length = 0x1000; > Offset = 0x14 > BAR[4]: Type = PMem64; Alignment = 0x3FFF; Length = 0x4000; > Offset = 0x20 > > PciBus: Discovered PCI @ [00|1F|00] [VID = 0x8086, DID = 0x2918] > > PciBus: Discovered PCI @ [00|1F|02] [VID = 0x8086, DID = 0x2922] > BAR[4]: Type = Io32; Alignment = 0x1F; Length = 0x20; Offset = 0x20 > BAR[5]: Type = Mem32; Alignment = 0xFFF; Length = 0x1000; > Offset = 0x24 > > PciBus: Discovered PCI @ [00|1F|03] [VID = 0x8086, DID = 0x2930] > BAR[4]: Type = Io32; Alignment = 0x3F; Length = 0x40; Offset = 0x20 > > PciBus: Discovered PCI @ [00|00|00] [VID = 0x8086, DID = 0x29C0] > > PciBus: Discovered PCI @ [00|01|00] [VID = 0x8086, DID = 0x10D3] > BAR[0]: Type = Mem32; Alignment = 0x1FFFF; Length = 0x20000; > Offset = 0x10 > BAR[1]: Type = Mem32; Alignment = 0x1FFFF; Length = 0x20000; > Offset = 0x14 > BAR[2]: Type = Io32; Alignment = 0x1F; Length = 0x20; Offset = 0x18 > BAR[3]: Type = Mem32; Alignment = 0x3FFF; Length = 0x4000; > Offset = 0x1C > > PciBus: Discovered PPB @ [00|08|00] [VID = 0x1B36, DID = 0xC] > Padding: Type = PMem64; Alignment = 0xFFFFFFF; Length = 0x10000000 > Padding: Type = Mem32; Alignment = 0x1FFFFF; Length = 0x200000 > Padding: Type = Io; Alignment = 0x1FF; Length = 0x200 > BAR[0]: Type = Mem32; Alignment = 0xFFF; Length = 0x1000; > Offset = 0x10 > > PciBus: Discovered PCI @ [01|00|00] [VID = 0x1AF4, DID = 0x1042] > BAR[1]: Type = Mem32; Alignment = 0xFFF; Length = 0x1000; > Offset = 0x14 > BAR[4]: Type = PMem64; Alignment = 0x3FFF; Length = 0x4000; > Offset = 0x20 > > PciBus: Discovered PCI @ [00|1F|00] [VID = 0x8086, DID = 0x2918] > > PciBus: Discovered PCI @ [00|1F|02] [VID = 0x8086, DID = 0x2922] > BAR[4]: Type = Io32; Alignment = 0x1F; Length = 0x20; Offset = 0x20 > BAR[5]: Type = Mem32; Alignment = 0xFFF; Length = 0x1000; > Offset = 0x24 > > PciBus: Discovered PCI @ [00|1F|03] [VID = 0x8086, DID = 0x2930] > BAR[4]: Type = Io32; Alignment = 0x3F; Length = 0x40; Offset = 0x20 > > PciHostBridge: SubmitResources for PciRoot(0x0) > I/O: Granularity/SpecificFlag = 0 / 01 > Length/Alignment = 0x1000 / 0xFFF > Mem: Granularity/SpecificFlag = 32 / 00 > Length/Alignment = 0x300000 / 0x1FFFFF > Mem: Granularity/SpecificFlag = 64 / 00 > Length/Alignment = 0x10000000 / 0xFFFFFFF > PciBus: HostBridge->SubmitResources() - Success > PciHostBridge: NotifyPhase (AllocateResources) > RootBridge: PciRoot(0x0) > Mem64: Base/Length/Alignment = 7000000000/10000000/FFFFFFF - Success > Mem: Base/Length/Alignment = C0000000/300000/1FFFFF - Success > I/O: Base/Length/Alignment = 6000/1000/FFF - Success > PciBus: HostBridge->NotifyPhase(AllocateResources) - Success > Process Option ROM: BAR Base/Length = C0200000/40000 > PciBus: Resource Map for Root Bridge PciRoot(0x0) > Type = Io16; Base = 0x6000; Length = 0x1000; Alignment = 0xFFF > Base = 0x6000; Length = 0x200; Alignment = 0xFFF; > Owner = PPB [00|08|00:**] > Base = 0x6200; Length = 0x40; Alignment = 0x3F; Owner = PCI > [00|1F|03:20] > Base = 0x6240; Length = 0x20; Alignment = 0x1F; Owner = PCI > [00|1F|02:20] > Base = 0x6260; Length = 0x20; Alignment = 0x1F; Owner = PCI > [00|01|00:18] > Type = Mem32; Base = 0xC0000000; Length = 0x300000; Alignment = > 0x1FFFFF > Base = 0xC0000000; Length = 0x200000; Alignment = 0x1FFFFF; > Owner = PPB [00|08|00:**] > Base = 0xC0200000; Length = 0x40000; Alignment = 0x3FFFF; > Owner = PCI [00|00|00:00]; Type = OpRom > Base = 0xC0240000; Length = 0x20000; Alignment = 0x1FFFF; > Owner = PCI [00|01|00:14] > Base = 0xC0260000; Length = 0x20000; Alignment = 0x1FFFF; > Owner = PCI [00|01|00:10] > Base = 0xC0280000; Length = 0x4000; Alignment = 0x3FFF; > Owner = PCI [00|01|00:1C] > Base = 0xC0284000; Length = 0x1000; Alignment = 0xFFF; > Owner = PCI [00|1F|02:24] > Base = 0xC0285000; Length = 0x1000; Alignment = 0xFFF; > Owner = PPB [00|08|00:10] > Type = Mem64; Base = 0x7000000000; Length = 0x10000000; Alignment = > 0xFFFFFFF > Base = 0x7000000000; Length = 0x10000000; Alignment = 0xFFFFFFF; > Owner = PPB [00|08|00:**]; Type = PMem64 > > PciBus: Resource Map for Bridge [00|08|00] > Type = Io16; Base = 0x6000; Length = 0x200; Alignment = 0xFFF > Base = Padding; Length = 0x200; Alignment = 0x1FF > Type = Mem32; Base = 0xC0000000; Length = 0x200000; Alignment = > 0x1FFFFF > Base = Padding; Length = 0x200000; Alignment = 0x1FFFFF > Base = 0xC0000000; Length = 0x1000; Alignment = 0xFFF; > Owner = PCI [01|00|00:14] > Type = Mem32; Base = 0xC0285000; Length = 0x1000; Alignment = > 0xFFF > Type = PMem64; Base = 0x7000000000; Length = 0x10000000; Alignment = > 0xFFFFFFF > Base = Padding; Length = 0x10000000; Alignment = 0xFFFFFFF > Base = 0x7000000000; Length = 0x4000; Alignment = 0x3FFF; > Owner = PCI [01|00|00:20] > > InstallProtocolInterface: 09576E91-6D3F-11D2-8E39-00A0C969723B 3D718698 > InstallProtocolInterface: 4CF5B200-68B8-4CA5-9EEC-B23E3F50029A 3D6F9428 > InstallProtocolInterface: 09576E91-6D3F-11D2-8E39-00A0C969723B 3D718798 > InstallProtocolInterface: 4CF5B200-68B8-4CA5-9EEC-B23E3F50029A 3D6F9828 > InstallProtocolInterface: 4006C0C1-FCB3-403E-996D-4A6C8724E06D 3D6F98F0 > [Security] 3rd party image[0] is deferred to load before EndOfDxe: > PciRoot(0x0)/Pci(0x1,0x0)/Offset(0x15C00,0x353FF). > InstallProtocolInterface: 3BC1B285-8A15-4A82-AABF-4D7D13FB3265 > 3D6F98D8 > InstallProtocolInterface: 09576E91-6D3F-11D2-8E39-00A0C969723B 3D718898 > InstallProtocolInterface: 4CF5B200-68B8-4CA5-9EEC-B23E3F50029A 3D6E9028 > InstallProtocolInterface: 09576E91-6D3F-11D2-8E39-00A0C969723B 3D718818 > InstallProtocolInterface: 4CF5B200-68B8-4CA5-9EEC-B23E3F50029A 3D6E95A8 > InstallProtocolInterface: 09576E91-6D3F-11D2-8E39-00A0C969723B 3D6E9F18 > InstallProtocolInterface: 4CF5B200-68B8-4CA5-9EEC-B23E3F50029A 3D6E8028 > InstallProtocolInterface: 09576E91-6D3F-11D2-8E39-00A0C969723B 3D6E9D18 > InstallProtocolInterface: 4CF5B200-68B8-4CA5-9EEC-B23E3F50029A 3D6E8428 > InstallProtocolInterface: 09576E91-6D3F-11D2-8E39-00A0C969723B 3D6E9B98 > InstallProtocolInterface: 4CF5B200-68B8-4CA5-9EEC-B23E3F50029A 3D6E8828 > InstallProtocolInterface: 30CFE3E7-3DE1-4586-BE20-DEABA1B3B793 0 > OnRootBridgesConnected: root bridges have been connected, installing ACPI > tables > Select Item: 0x19 > Select Item: 0x2D > Select Item: 0x19 > Select Item: 0x2C > Select Item: 0x19 > Select Item: 0x22 > Select Item: 0x19 > Select Item: 0x23 > InstallProtocolInterface: 928939B2-4235-462F-9580-F6A2B2C21A4F 0 > InstallQemuFwCfgTables: installed 7 tables > PcRtc: Write 0x20 to CMOS location 0x32 > SmmEndOfDxeHandler > SmmInstallProtocolInterface: 24E70042-D5C5-4260-8C39-0AD3AA32E93D 0 > [Variable]SMM_END_OF_DXE is signaled > Initialize variable error flag (FF) > AcpiS3ContextSave! > SmmLockBoxDxeLib SaveLockBox - Enter > SmmLockBox SmmLockBoxHandler Enter > SmmLockBox LockBoxParameterHeader - 3EEC0930 > SmmLockBox Command - 1 > SmmLockBoxSmmLib SaveLockBox - Enter > LockBoxGuid - DEA652B0-D587-4C54-B5B4-C682E7A0AA3D, SmramBuffer - > 0x3FD6F000, Length - 0xA > SmmLockBoxSmmLib SaveLockBox - Exit (Success) > SmmLockBox SmmLockBoxHandler Exit > SmmLockBoxDxeLib SaveLockBox - Exit (Success) > SmmLockBoxDxeLib SetLockBoxAttributes - Enter > SmmLockBox SmmLockBoxHandler Enter > SmmLockBox LockBoxParameterHeader - 3EEC0948 > SmmLockBox Command - 4 > SmmLockBoxSmmLib SetLockBoxAttributes - Enter > SmmLockBoxSmmLib SetLockBoxAttributes - Exit (Success) > SmmLockBox SmmLockBoxHandler Exit > SmmLockBoxDxeLib SetLockBoxAttributes - Exit (Success) > AcpiS3ContextSave TotalPageTableSize - 0xE pages > AcpiS3Context: AcpiFacsTable is 0x3E9BB000 > AcpiS3Context: IdtrProfile is 0x3E962000 > AcpiS3Context: S3NvsPageTableAddress is 0x3E953000 > AcpiS3Context: S3DebugBufferAddress is 0x3E94A000 > AcpiS3Context: BootScriptStackBase is 0x3E94B000 > AcpiS3Context: BootScriptStackSize is 0x 8000 > SmmLockBoxDxeLib SaveLockBox - Enter > SmmLockBox SmmLockBoxHandler Enter > SmmLockBox LockBoxParameterHeader - 3EEC0930 > SmmLockBox Command - 1 > SmmLockBoxSmmLib SaveLockBox - Enter > LockBoxGuid - AF9FFD67-EC10-488A-9DFC-6CBF5EE22C2E, SmramBuffer - > 0x3FD6E000, Length - 0x8 > SmmLockBoxSmmLib SaveLockBox - Exit (Success) > SmmLockBox SmmLockBoxHandler Exit > SmmLockBoxDxeLib SaveLockBox - Exit (Success) > SmmLockBoxDxeLib SaveLockBox - Enter > SmmLockBox SmmLockBoxHandler Enter > SmmLockBox LockBoxParameterHeader - 3EEC0930 > SmmLockBox Command - 1 > SmmLockBoxSmmLib SaveLockBox - Enter > LockBoxGuid - 0EF98D3A-3E33-497A-A401-77BE3EB74F38, SmramBuffer - > 0x3FD6D000, Length - 0x30 > SmmLockBoxSmmLib SaveLockBox - Exit (Success) > SmmLockBox SmmLockBoxHandler Exit > SmmLockBoxDxeLib SaveLockBox - Exit (Success) > SmmLockBoxDxeLib SetLockBoxAttributes - Enter > SmmLockBox SmmLockBoxHandler Enter > SmmLockBox LockBoxParameterHeader - 3EEC0948 > SmmLockBox Command - 4 > SmmLockBoxSmmLib SetLockBoxAttributes - Enter > SmmLockBoxSmmLib SetLockBoxAttributes - Exit (Success) > SmmLockBox SmmLockBoxHandler Exit > SmmLockBoxDxeLib SetLockBoxAttributes - Exit (Success) > Found LPC Bridge device > BdsPlatform.c+709: COM1 DevPath: > PciRoot(0x0)/Pci(0x1F,0x0)/Serial(0x0)/Uart(115200,8,N,1)/VenMsg(E0C1475 > 3-F9BE-11D2-9A0C-0090273FC14D) > BdsPlatform.c+747: COM2 DevPath: > PciRoot(0x0)/Pci(0x1F,0x0)/Serial(0x1)/Uart(115200,8,N,1)/VenMsg(E0C1475 > 3-F9BE-11D2-9A0C-0090273FC14D) > Select Item: 0x19 > [TPM2PP] no PPI > InstallProtocolInterface: 60FF8964-E906-41D0-AFED-F241E974E08E 0 > InstallProtocolInterface: FA20568B-548B-4B2B-81EF-1BA08D4A3CEC 0 > SmmLockBoxDxeLib SaveLockBox - Enter > SmmLockBox SmmLockBoxHandler Enter > SmmLockBox LockBoxParameterHeader - 3EEC06E0 > SmmLockBox Command - 1 > SmmLockBoxSmmLib SaveLockBox - Enter > LockBoxGuid - 3079818C-46D4-4A73-AEF3-E3E46CF1EEDB, SmramBuffer - > 0x3FD6C000, Length - 0x8 > SmmLockBoxSmmLib SaveLockBox - Exit (Success) > SmmLockBox SmmLockBoxHandler Exit > SmmLockBoxDxeLib SaveLockBox - Exit (Success) > SmmLockBoxDxeLib SaveLockBox - Enter > SmmLockBox SmmLockBoxHandler Enter > SmmLockBox LockBoxParameterHeader - 3EEC06E0 > SmmLockBox Command - 1 > SmmLockBoxSmmLib SaveLockBox - Enter > LockBoxGuid - 79CB58C4-AC51-442F-AFD7-98E47D2E9908, SmramBuffer - > 0x3FD6B000, Length - 0x8 > SmmLockBoxSmmLib SaveLockBox - Exit (Success) > SmmLockBox SmmLockBoxHandler Exit > SmmLockBoxDxeLib SaveLockBox - Exit (Success) > SmmLockBoxDxeLib SetLockBoxAttributes - Enter > SmmLockBox SmmLockBoxHandler Enter > SmmLockBox LockBoxParameterHeader - 3EEC06F8 > SmmLockBox Command - 4 > SmmLockBoxSmmLib SetLockBoxAttributes - Enter > SmmLockBoxSmmLib SetLockBoxAttributes - Exit (Success) > SmmLockBox SmmLockBoxHandler Exit > SmmLockBoxDxeLib SetLockBoxAttributes - Exit (Success) > SmmLockBoxDxeLib SaveLockBox - Enter > SmmLockBox SmmLockBoxHandler Enter > SmmLockBox LockBoxParameterHeader - 3EEC0790 > SmmLockBox Command - 1 > SmmLockBoxSmmLib SaveLockBox - Enter > LockBoxGuid - 9A8D3433-9FE8-42B6-870B-1E31C84EBE3B, SmramBuffer - > 0x3FD56000, Length - 0x14B40 > SmmLockBoxSmmLib SaveLockBox - Exit (Success) > SmmLockBox SmmLockBoxHandler Exit > SmmLockBoxDxeLib SaveLockBox - Exit (Success) > SmmLockBoxDxeLib SetLockBoxAttributes - Enter > SmmLockBox SmmLockBoxHandler Enter > SmmLockBox LockBoxParameterHeader - 3EEC07A8 > SmmLockBox Command - 4 > SmmLockBoxSmmLib SetLockBoxAttributes - Enter > SmmLockBoxSmmLib SetLockBoxAttributes - Exit (Success) > SmmLockBox SmmLockBoxHandler Exit > SmmLockBoxDxeLib SetLockBoxAttributes - Exit (Success) > SmmLockBoxDxeLib SaveLockBox - Enter > SmmLockBox SmmLockBoxHandler Enter > SmmLockBox LockBoxParameterHeader - 3EEC0960 > SmmLockBox Command - 1 > SmmLockBoxSmmLib SaveLockBox - Enter > LockBoxGuid - AEA6B965-DCF5-4311-B4B8-0F12464494D2, SmramBuffer - > 0x3FD52000, Length - 0x4000 > SmmLockBoxSmmLib SaveLockBox - Exit (Success) > SmmLockBox SmmLockBoxHandler Exit > SmmLockBoxDxeLib SaveLockBox - Exit (Success) > SmmLockBoxDxeLib SetLockBoxAttributes - Enter > SmmLockBox SmmLockBoxHandler Enter > SmmLockBox LockBoxParameterHeader - 3EEC0978 > SmmLockBox Command - 4 > SmmLockBoxSmmLib SetLockBoxAttributes - Enter > SmmLockBoxSmmLib SetLockBoxAttributes - Exit (Success) > SmmLockBox SmmLockBoxHandler Exit > SmmLockBoxDxeLib SetLockBoxAttributes - Exit (Success) > SmmLockBoxDxeLib SaveLockBox - Enter > SmmLockBox SmmLockBoxHandler Enter > SmmLockBox LockBoxParameterHeader - 3EEC0960 > SmmLockBox Command - 1 > SmmLockBoxSmmLib SaveLockBox - Enter > LockBoxGuid - 1810AB4A-2314-4DF6-81EB-67C6EC058591, SmramBuffer - > 0x3FD51000, Length - 0x8 > SmmLockBoxSmmLib SaveLockBox - Exit (Success) > SmmLockBox SmmLockBoxHandler Exit > SmmLockBoxDxeLib SaveLockBox - Exit (Success) > SmmLockBoxDxeLib SetLockBoxAttributes - Enter > SmmLockBox SmmLockBoxHandler Enter > SmmLockBox LockBoxParameterHeader - 3EEC0978 > SmmLockBox Command - 4 > SmmLockBoxSmmLib SetLockBoxAttributes - Enter > SmmLockBoxSmmLib SetLockBoxAttributes - Exit (Success) > SmmLockBox SmmLockBoxHandler Exit > SmmLockBoxDxeLib SetLockBoxAttributes - Exit (Success) > SmmInstallProtocolInterface: 47B7FA8C-F4BD-4AF6-8200-333086F0D2C8 0 > GetUefiMemoryMap > Patch page table start ... > Patch page table done! > MemoryAttributesTable: > Version - 0x00000001 > NumberOfEntries - 0x00000027 > DescriptorSize - 0x00000030 > Entry (0x3FD73028) > Type - 0x6 > PhysicalStart - 0x000000003F000000 > VirtualStart - 0x0000000000000000 > NumberOfPages - 0x0000000000000001 > Attribute - 0x0000000000004000 > Entry (0x3FD73058) > Type - 0x7 > PhysicalStart - 0x000000003F001000 > VirtualStart - 0x0000000000000000 > NumberOfPages - 0x0000000000000D71 > Attribute - 0x0000000000004000 > Entry (0x3FD73088) > Type - 0x6 > PhysicalStart - 0x000000003FD72000 > VirtualStart - 0x0000000000000000 > NumberOfPages - 0x0000000000000012 > Attribute - 0x0000000000004000 > Entry (0x3FD730B8) > Type - 0x5 > PhysicalStart - 0x000000003FD84000 > VirtualStart - 0x0000000000000000 > NumberOfPages - 0x0000000000000008 > Attribute - 0x0000000000020000 > Entry (0x3FD730E8) > Type - 0x6 > PhysicalStart - 0x000000003FD8C000 > VirtualStart - 0x0000000000000000 > NumberOfPages - 0x0000000000000001 > Attribute - 0x0000000000004000 > Entry (0x3FD73118) > Type - 0x5 > PhysicalStart - 0x000000003FD8D000 > VirtualStart - 0x0000000000000000 > NumberOfPages - 0x0000000000000001 > Attribute - 0x0000000000020000 > Entry (0x3FD73148) > Type - 0x6 > PhysicalStart - 0x000000003FD8E000 > VirtualStart - 0x0000000000000000 > NumberOfPages - 0x0000000000000001 > Attribute - 0x0000000000004000 > Entry (0x3FD73178) > Type - 0x5 > PhysicalStart - 0x000000003FD8F000 > VirtualStart - 0x0000000000000000 > NumberOfPages - 0x0000000000000005 > Attribute - 0x0000000000020000 > Entry (0x3FD731A8) > Type - 0x6 > PhysicalStart - 0x000000003FD94000 > VirtualStart - 0x0000000000000000 > NumberOfPages - 0x0000000000000001 > Attribute - 0x0000000000004000 > Entry (0x3FD731D8) > Type - 0x5 > PhysicalStart - 0x000000003FD95000 > VirtualStart - 0x0000000000000000 > NumberOfPages - 0x0000000000000001 > Attribute - 0x0000000000020000 > Entry (0x3FD73208) > Type - 0x6 > PhysicalStart - 0x000000003FD96000 > VirtualStart - 0x0000000000000000 > NumberOfPages - 0x0000000000000146 > Attribute - 0x0000000000004000 > Entry (0x3FD73238) > Type - 0x5 > PhysicalStart - 0x000000003FEDC000 > VirtualStart - 0x0000000000000000 > NumberOfPages - 0x0000000000000064 > Attribute - 0x0000000000020000 > Entry (0x3FD73268) > Type - 0x6 > PhysicalStart - 0x000000003FF40000 > VirtualStart - 0x0000000000000000 > NumberOfPages - 0x000000000000001F > Attribute - 0x0000000000004000 > Entry (0x3FD73298) > Type - 0x5 > PhysicalStart - 0x000000003FF5F000 > VirtualStart - 0x0000000000000000 > NumberOfPages - 0x0000000000000001 > Attribute - 0x0000000000020000 > Entry (0x3FD732C8) > Type - 0x6 > PhysicalStart - 0x000000003FF60000 > VirtualStart - 0x0000000000000000 > NumberOfPages - 0x0000000000000021 > Attribute - 0x0000000000004000 > Entry (0x3FD732F8) > Type - 0x5 > PhysicalStart - 0x000000003FF81000 > VirtualStart - 0x0000000000000000 > NumberOfPages - 0x0000000000000005 > Attribute - 0x0000000000020000 > Entry (0x3FD73328) > Type - 0x6 > PhysicalStart - 0x000000003FF86000 > VirtualStart - 0x0000000000000000 > NumberOfPages - 0x0000000000000002 > Attribute - 0x0000000000004000 > Entry (0x3FD73358) > Type - 0x5 > PhysicalStart - 0x000000003FF88000 > VirtualStart - 0x0000000000000000 > NumberOfPages - 0x0000000000000001 > Attribute - 0x0000000000020000 > Entry (0x3FD73388) > Type - 0x6 > PhysicalStart - 0x000000003FF89000 > VirtualStart - 0x0000000000000000 > NumberOfPages - 0x000000000000000B > Attribute - 0x0000000000004000 > Entry (0x3FD733B8) > Type - 0x5 > PhysicalStart - 0x000000003FF94000 > VirtualStart - 0x0000000000000000 > NumberOfPages - 0x0000000000000001 > Attribute - 0x0000000000020000 > Entry (0x3FD733E8) > Type - 0x6 > PhysicalStart - 0x000000003FF95000 > VirtualStart - 0x0000000000000000 > NumberOfPages - 0x0000000000000002 > Attribute - 0x0000000000004000 > Entry (0x3FD73418) > Type - 0x5 > PhysicalStart - 0x000000003FF97000 > VirtualStart - 0x0000000000000000 > NumberOfPages - 0x0000000000000001 > Attribute - 0x0000000000020000 > Entry (0x3FD73448) > Type - 0x6 > PhysicalStart - 0x000000003FF98000 > VirtualStart - 0x0000000000000000 > NumberOfPages - 0x0000000000000019 > Attribute - 0x0000000000004000 > Entry (0x3FD73478) > Type - 0x5 > PhysicalStart - 0x000000003FFB1000 > VirtualStart - 0x0000000000000000 > NumberOfPages - 0x000000000000000E > Attribute - 0x0000000000020000 > Entry (0x3FD734A8) > Type - 0x6 > PhysicalStart - 0x000000003FFBF000 > VirtualStart - 0x0000000000000000 > NumberOfPages - 0x0000000000000001 > Attribute - 0x0000000000004000 > Entry (0x3FD734D8) > Type - 0x5 > PhysicalStart - 0x000000003FFC0000 > VirtualStart - 0x0000000000000000 > NumberOfPages - 0x0000000000000014 > Attribute - 0x0000000000020000 > Entry (0x3FD73508) > Type - 0x6 > PhysicalStart - 0x000000003FFD4000 > VirtualStart - 0x0000000000000000 > NumberOfPages - 0x0000000000000003 > Attribute - 0x0000000000004000 > Entry (0x3FD73538) > Type - 0x5 > PhysicalStart - 0x000000003FFD7000 > VirtualStart - 0x0000000000000000 > NumberOfPages - 0x0000000000000001 > Attribute - 0x0000000000020000 > Entry (0x3FD73568) > Type - 0x6 > PhysicalStart - 0x000000003FFD8000 > VirtualStart - 0x0000000000000000 > NumberOfPages - 0x0000000000000001 > Attribute - 0x0000000000004000 > Entry (0x3FD73598) > Type - 0x5 > PhysicalStart - 0x000000003FFD9000 > VirtualStart - 0x0000000000000000 > NumberOfPages - 0x0000000000000005 > Attribute - 0x0000000000020000 > Entry (0x3FD735C8) > Type - 0x6 > PhysicalStart - 0x000000003FFDE000 > VirtualStart - 0x0000000000000000 > NumberOfPages - 0x0000000000000002 > Attribute - 0x0000000000004000 > Entry (0x3FD735F8) > Type - 0x5 > PhysicalStart - 0x000000003FFE0000 > VirtualStart - 0x0000000000000000 > NumberOfPages - 0x0000000000000001 > Attribute - 0x0000000000020000 > Entry (0x3FD73628) > Type - 0x6 > PhysicalStart - 0x000000003FFE1000 > VirtualStart - 0x0000000000000000 > NumberOfPages - 0x0000000000000002 > Attribute - 0x0000000000004000 > Entry (0x3FD73658) > Type - 0x5 > PhysicalStart - 0x000000003FFE3000 > VirtualStart - 0x0000000000000000 > NumberOfPages - 0x0000000000000003 > Attribute - 0x0000000000020000 > Entry (0x3FD73688) > Type - 0x6 > PhysicalStart - 0x000000003FFE6000 > VirtualStart - 0x0000000000000000 > NumberOfPages - 0x0000000000000002 > Attribute - 0x0000000000004000 > Entry (0x3FD736B8) > Type - 0x5 > PhysicalStart - 0x000000003FFE8000 > VirtualStart - 0x0000000000000000 > NumberOfPages - 0x0000000000000001 > Attribute - 0x0000000000020000 > Entry (0x3FD736E8) > Type - 0x6 > PhysicalStart - 0x000000003FFE9000 > VirtualStart - 0x0000000000000000 > NumberOfPages - 0x0000000000000006 > Attribute - 0x0000000000004000 > Entry (0x3FD73718) > Type - 0x5 > PhysicalStart - 0x000000003FFEF000 > VirtualStart - 0x0000000000000000 > NumberOfPages - 0x000000000000000E > Attribute - 0x0000000000020000 > Entry (0x3FD73748) > Type - 0x6 > PhysicalStart - 0x000000003FFFD000 > VirtualStart - 0x0000000000000000 > NumberOfPages - 0x0000000000000003 > Attribute - 0x0000000000004000 > PatchSmmSaveStateMap: > PatchGdtIdtMap - GDT: > PatchGdtIdtMap - IDT: > SetUefiMemMapAttributes > UefiMemory protection: 0x0 - 0x30000 Success > UefiMemory protection: 0x50000 - 0x9E000 Success > UefiMemory protection: 0x100000 - 0x807000 Success > UefiMemory protection: 0x808000 - 0x810000 Success > UefiMemory protection: 0x1810000 - 0x3E6EC000 Success > UefiMemory protection: 0x3E96C000 - 0x3E97E000 Success > UefiMemory protection: 0x3E9FE000 - 0x3EF60000 Success > UefiMemoryAttribute protection: 0x3E8AF000 - 0x3E8B1000 Success > UefiMemoryAttribute protection: 0x3E8B3000 - 0x3E8B5000 Success > UefiMemoryAttribute protection: 0x3E8B7000 - 0x3E8BB000 Success > UefiMemoryAttribute protection: 0x3E8BD000 - 0x3E8C2000 Success > UefiMemoryAttribute protection: 0x3E8C5000 - 0x3E8CB000 Success > UefiMemoryAttribute protection: 0x3E8CE000 - 0x3E8D2000 Success > UefiMemoryAttribute protection: 0x3E8D5000 - 0x3E8D8000 Success > UefiMemoryAttribute protection: 0x3E8DA000 - 0x3E8DE000 Success > UefiMemoryAttribute protection: 0x3E8E1000 - 0x3E8E4000 Success > UefiMemoryAttribute protection: 0x3E8E7000 - 0x3E8EA000 Success > SetPageTableAttributes > Start... > SMM IPL locked SMRAM window > [Security] 3rd party image[3D6E9E18] can be loaded after EndOfDxe: > PciRoot(0x0)/Pci(0x1,0x0)/Offset(0x15C00,0x353FF). > None of Tcg2Protocol/CcMeasurementProtocol is installed. > InstallProtocolInterface: 5B1B31A1-9562-11D2-8E3F-00A0C969723B 3D6E4040 > Loading driver at 0x0003D3FB000 EntryPoint=0x0003D401FE5 808610d3.efi > InstallProtocolInterface: BC62157E-3E33-4FEC-9920-2D3B36D750DF 3D6E5698 > ProtectUefiImageCommon - 0x3D6E4040 > - 0x000000003D3FB000 - 0x00000000000BC000 > InstallProtocolInterface: 18A031AB-B443-4D1A-A5C0-0C09261E9F71 3D42EFE0 > InstallProtocolInterface: 6A7A5CFF-E8D9-4F70-BADA-75AB3025CE14 > 3D42EFA0 > Found LPC Bridge device > BdsPlatform.c+709: COM1 DevPath: > PciRoot(0x0)/Pci(0x1F,0x0)/Serial(0x0)/Uart(115200,8,N,1)/VenMsg(E0C1475 > 3-F9BE-11D2-9A0C-0090273FC14D) > BdsPlatform.c+747: COM2 DevPath: > PciRoot(0x0)/Pci(0x1F,0x0)/Serial(0x1)/Uart(115200,8,N,1)/VenMsg(E0C1475 > 3-F9BE-11D2-9A0C-0090273FC14D) > Select Item: 0xE > [Bds]RegisterKeyNotify: 000C/0000 80000000/00 Success > [Bds]RegisterKeyNotify: 0017/0000 80000000/00 Success > [Bds]RegisterKeyNotify: 0000/000D 80000000/00 Success > InstallProtocolInterface: 864E1CA8-85EB-4D63-9DCC-6E0FC90FFD55 3D6E4A18 > InstallProtocolInterface: 09576E91-6D3F-11D2-8E39-00A0C969723B 3D6E4518 > InstallProtocolInterface: 215FDD18-BD50-4FEB-890B-58CA0B4739E9 3D6E4EB8 > InstallProtocolInterface: 09576E91-6D3F-11D2-8E39-00A0C969723B 3D6E3B18 > InstallProtocolInterface: 215FDD18-BD50-4FEB-890B-58CA0B4739E9 3D6E3F38 > InstallProtocolInterface: 09576E91-6D3F-11D2-8E39-00A0C969723B 3D6E3D18 > InstallProtocolInterface: 215FDD18-BD50-4FEB-890B-58CA0B4739E9 3D6E3C38 > ClockRate = 1843200 > Divisor = 1 > BaudRate/Actual (115200/115200) = 100% > ClockRate = 1843200 > Divisor = 1 > BaudRate/Actual (115200/115200) = 100% > InstallProtocolInterface: 09576E91-6D3F-11D2-8E39-00A0C969723B 3D6E3598 > InstallProtocolInterface: BB25CF6F-F1D4-11D2-9A0C-0090273FC1FD 3D6E47A8 > PciSioSerial: Create SIO child serial device - Success > ClockRate = 1843200 > Divisor = 1 > BaudRate/Actual (115200/115200) = 100% > Terminal - Mode 0, Column = 80, Row = 25 > Terminal - Mode 1, Column = 80, Row = 50 > Terminal - Mode 2, Column = 100, Row = 31 > ClockRate = 1843200 > Divisor = 1 > BaudRate/Actual (115200/115200) = 100% > InstallProtocolInterface: 387477C1-69C7-11D2-8E39-00A0C969723B 3D6D5440 > InstallProtocolInterface: DD9E7534-7762-4698-8C14-F58517A625AA 3D6D5528 > InstallProtocolInterface: 387477C2-69C7-11D2-8E39-00A0C969723B 3D6D5458 > InstallProtocolInterface: 09576E91-6D3F-11D2-8E39-00A0C969723B 3D6D5818 > InstallProtocolInterface: D3B36F2B-D551-11D4-9A46-0090273FC14D 0 > InstallProtocolInterface: D3B36F2C-D551-11D4-9A46-0090273FC14D 0 > InstallProtocolInterface: D3B36F2D-D551-11D4-9A46-0090273FC14D 0 > ClockRate = 1843200 > Divisor = 1 > BaudRate/Actual (115200/115200) = 100% > PciSioSerial: Create SIO child serial device - Device Error > InstallProtocolInterface: 387477C1-69C7-11D2-8E39-00A0C969723B 3D633028 > InstallProtocolInterface: DD9E7534-7762-4698-8C14-F58517A625AA 3D633040 > InstallProtocolInterface: D3B36F2B-D551-11D4-9A46-0090273FC14D 0 > ClockRate = 1843200 > Divisor = 1 > BaudRate/Actual (115200/115200) = 100% > PciSioSerial: Create SIO child serial device - Device Error > ClockRate = 1843200 > Divisor = 1 > BaudRate/Actual (115200/115200) = 100% > PciSioSerial: Create SIO child serial device - Device Error > PlatformBootManagerAfterConsole > PlatformBdsPolicyBehavior: not restoring NvVars from disk since flash > variables appear to be supported. > Boot Mode:0 > Select Item: 0x19 > Select Item: 0x21 > StoreQemuBootOrder: VMMBootOrder0000 = > PciRoot(0x0)/Pci(0x8,0x0)/Pci(0x0,0x0) > PlatformBdsConnectSequence > Select Item: 0x19 > Select Item: 0x21 > InstallProtocolInterface: FA920010-6785-4941-B6EC-498C579F160A 3D6E43A0 > VirtioBlkInit: LbaSize=0x200[B] NumBlocks=0x48028[Lba] > VirtioBlkInit: FirstAligned=0x0[Lba] PhysBlkSize=0x1[Lba] > VirtioBlkInit: OptimalTransferLengthGranularity=0x0[Lba] > InstallProtocolInterface: 964E5B21-6459-11D2-8E39-00A0C969723B 3D632490 > InstallProtocolInterface: CE345171-BA0B-11D2-8E4F-00A0C969723B 3D631020 > BlockSize : 512 > LastBlock : 48027 > Valid efi partition table header > Valid efi partition table header > Valid primary and Valid backup partition table > Partition entries read block success > Number of partition entries: 128 > start check partition entries > End check partition entries > Index : 0 > Start LBA : 40 > End LBA : 7FFF > Partition size: 7FC0 > Start : 8000 End : FFFE00 > InstallProtocolInterface: 09576E91-6D3F-11D2-8E39-00A0C969723B 3D631F18 > InstallProtocolInterface: 964E5B21-6459-11D2-8E39-00A0C969723B 3D631330 > InstallProtocolInterface: 8CF2F62C-BC9B-4821-808D-EC9EC421A1A0 3D6313E8 > InstallProtocolInterface: C12A7328-F81F-11D2-BA4B-00A0C93EC93B 0 > Index : 1 > Start LBA : 8000 > End LBA : 47FFF > Partition size: 40000 > Start : 1000000 End : 8FFFE00 > InstallProtocolInterface: 09576E91-6D3F-11D2-8E39-00A0C969723B 3D632A98 > InstallProtocolInterface: 964E5B21-6459-11D2-8E39-00A0C969723B 3D630030 > InstallProtocolInterface: 8CF2F62C-BC9B-4821-808D-EC9EC421A1A0 3D6300E8 > InstallProtocolInterface: 4F68BCE3-E8CD-4DB1-96E7-FBCAF984B709 0 > Prepare to Free Pool > InstallProtocolInterface: CE345171-BA0B-11D2-8E4F-00A0C969723B 3D631CA0 > BlockSize : 512 > LastBlock : 7FBF > InstallProtocolInterface: 964E5B22-6459-11D2-8E39-00A0C969723B 3D5ED030 > Installed Fat filesystem on 3D632798 > InstallProtocolInterface: CE345171-BA0B-11D2-8E4F-00A0C969723B 3D631920 > BlockSize : 512 > LastBlock : 3FFFF > ConnectDevicesFromQemu: 1 OpenFirmware device path(s) connected > Select Item: 0x19 > Select Item: 0x21 > SetBootOrderFromQemu: setting BootOrder: success > [Bds]OsIndication: 0000000000000000 > [Bds]=============Begin Load Options Dumping ...============= > Driver Options: > SysPrep Options: > Boot Options: > Boot0001: UEFI Misc Device 0x0001 > Boot0000: UiApp 0x0109 > Boot0002: EFI Internal Shell 0x0001 > PlatformRecovery Options: > PlatformRecovery0000: Default PlatformRecovery 0x0001 > [Bds]=============End Load Options Dumping============= > [Bds]BdsWait ...Zzzzzzzzzzzz... > [Bds]Exit the waiting! > [Bds]Stop Hotkey Service! > [Bds]UnregisterKeyNotify: 000C/0000 Success > [Bds]UnregisterKeyNotify: 0017/0000 Success > [Bds]UnregisterKeyNotify: 0000/000D Success > SmmInstallProtocolInterface: 6E057ECF-FA99-4F39-95BC-59F9921D17E4 0 > Memory Previous Current Next > Type Pages Pages Pages > ====== ======== ======== ======== > 0A 00000080 00000043 00000080 > 09 00000012 0000000A 00000012 > 00 00000080 00000038 00000080 > 05 00000100 0000003E 00000100 > 06 00000100 0000006A 00000100 > [Bds]Booting UEFI Misc Device > BlockSize : 512 > LastBlock : 48027 > Valid efi partition table header > Valid efi partition table header > Valid primary and Valid backup partition table > Partition entries read block success > Number of partition entries: 128 > start check partition entries > End check partition entries > Index : 0 > Start LBA : 40 > End LBA : 7FFF > Partition size: 7FC0 > Start : 8000 End : FFFE00 > Index : 1 > Start LBA : 8000 > End LBA : 47FFF > Partition size: 40000 > Start : 1000000 End : 8FFFE00 > Prepare to Free Pool > BlockSize : 512 > LastBlock : 3FFFF > FatDiskIo: Cache Page OutBound occurred! > FSOpen: Open '\EFI\BOOT\BOOTX64.EFI' Success > [Bds] Expand PciRoot(0x0)/Pci(0x8,0x0)/Pci(0x0,0x0) -> > PciRoot(0x0)/Pci(0x8,0x0)/Pci(0x0,0x0)/HD(1,GPT,EA84E18B-286C-4EAA- > 966D-5C039D67459A,0x40,0x7FC0)/\EFI\BOOT\BOOTX64.EFI > [Security] 3rd party image[0] can be loaded after EndOfDxe: > PciRoot(0x0)/Pci(0x8,0x0)/Pci(0x0,0x0)/HD(1,GPT,EA84E18B-286C-4EAA- > 966D-5C039D67459A,0x40,0x7FC0)/\EFI\BOOT\BOOTX64.EFI. > None of Tcg2Protocol/CcMeasurementProtocol is installed. > InstallProtocolInterface: 5B1B31A1-9562-11D2-8E3F-00A0C969723B 3D4D4040 > Loading driver at 0x0003CD47000 EntryPoint=0x0003CD48000 > InstallProtocolInterface: BC62157E-3E33-4FEC-9920-2D3B36D750DF 3D5ECC18 > ProtectUefiImageCommon - 0x3D4D4040 > - 0x000000003CD47000 - 0x00000000000A6000 > SmmInstallProtocolInterface: 296EB418-C4C8-4E05-AB59-39E8AF56F00A 0 > CpuDxe: 5-Level Paging = 0 > MpInitChangeApLoopCallback() done! > SetUefiImageMemoryAttributes - 0x000000003E8E6000 - > 0x0000000000006000 (0x0000000000000008) > SetUefiImageMemoryAttributes - 0x000000003E8E0000 - > 0x0000000000006000 (0x0000000000000008) > SetUefiImageMemoryAttributes - 0x000000003E8D9000 - > 0x0000000000007000 (0x0000000000000008) > SetUefiImageMemoryAttributes - 0x000000003E8D4000 - > 0x0000000000005000 (0x0000000000000008) > SetUefiImageMemoryAttributes - 0x000000003E8CD000 - > 0x0000000000007000 (0x0000000000000008) > SetUefiImageMemoryAttributes - 0x000000003E8C4000 - > 0x0000000000009000 (0x0000000000000008) > SetUefiImageMemoryAttributes - 0x000000003E8BC000 - > 0x0000000000008000 (0x0000000000000008) > SetUefiImageMemoryAttributes - 0x000000003E8B6000 - > 0x0000000000006000 (0x0000000000000008) > SetUefiImageMemoryAttributes - 0x000000003E8B2000 - > 0x0000000000004000 (0x0000000000000008) > SetUefiImageMemoryAttributes - 0x000000003E8AE000 - > 0x0000000000004000 (0x0000000000000008) > SecCoreStartupWithStack(0xFFFCC000, 0x820000) > Register PPI Notify: DCD0BE23-9586-40F4-B643-06522CED4EDE > Install PPI: 8C8CE578-8A3D-4F1C-9935-896185C32DD3 > Install PPI: 5473C07A-3DCB-4DCA-BD6F-1E9689E7349A > The 0th FV start address is 0x00000820000, size is 0x000E0000, handle is > 0x820000 > Register PPI Notify: 49EDB1C1-BF21-4761-BB12-EB0031AABB39 > Register PPI Notify: EA7CA24B-DED5-4DAD-A389-BF827E8F9B38 > Install PPI: B9E0ABFE-5979-4914-977F-6DEE78C278A6 > Install PPI: DBE23AA9-A345-4B97-85B6-B226F1617389 > Install PPI: 138F9CF4-F0E7-4721-8F49-F5FFECF42D40 > DiscoverPeimsAndOrderWithApriori(): Found 0xF PEI FFS files in the 0th FV > Loading PEIM 9B3ADA4F-AE56-4C24-8DEA-F03B7558AE50 > Loading PEIM at 0x0000082B180 EntryPoint=0x0000082DC72 PcdPeim.efi > Install PPI: 06E81C58-4AD7-44BC-8390-F10265F72480 > Install PPI: 01F34D25-4DE2-23AD-3FF3-36353FF323F1 > Install PPI: 4D8B155B-C059-4C8F-8926-06FD4331DB8A > Install PPI: A60C6B59-E459-425D-9C69-0BCC9CB27D81 > Register PPI Notify: 605EA650-C65C-42E1-BA80-91A52AB618C6 > Loading PEIM A3610442-E69F-4DF3-82CA-2360C4031A23 > Loading PEIM at 0x0000082FA40 EntryPoint=0x00000830B74 > ReportStatusCodeRouterPei.efi > Install PPI: 0065D394-9951-4144-82A3-0AFC8579C251 > Install PPI: 229832D3-7A30-4B36-B827-F40CB7D45436 > Loading PEIM 9D225237-FA01-464C-A949-BAABC02D31D0 > Loading PEIM at 0x000008318C0 EntryPoint=0x00000832927 > StatusCodeHandlerPei.efi > Loading PEIM 222C386D-5ABC-4FB4-B124-FBB82488ACF4 > Loading PEIM at 0x00000833740 EntryPoint=0x00000839C59 PlatformPei.efi > Platform PEIM Loaded > CMOS: > 00: 37 00 57 00 10 00 02 06 03 23 26 02 00 80 00 FE > 10: 00 00 00 00 06 80 02 FF FF 00 00 00 00 00 00 00 > 20: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 > 30: FF FF 20 00 00 3F 00 20 30 00 00 00 00 12 00 00 > 40: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 > 50: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 01 > 60: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 > 70: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 > QemuFwCfgProbe: Supported 1, DMA 1 > Select Item: 0x19 > Select Item: 0x2C > S3 support was detected on QEMU > Install PPI: 7408D748-FC8C-4EE6-9288-C4BEC092A410 > Select Item: 0x19 > Select Item: 0x19 > Select Item: 0x25 > Select Item: 0x19 > Select Item: 0x19 > PlatformAddressWidthFromCpuid: Signature: 'GenuineIntel', PhysBits: 39, > QemuQuirk: On, Valid: Yes > PlatformDynamicMmioWindow: using dynamic mmio window > PlatformDynamicMmioWindow: Addr Space 0x8000000000 (512 GB) > PlatformDynamicMmioWindow: MMIO Space 0x1000000000 (64 GB) > Select Item: 0x19 > Select Item: 0x25 > PlatformDynamicMmioWindow: Pci64 Base 0x7000000000 > PlatformDynamicMmioWindow: Pci64 Size 0x1000000000 > Select Item: 0x5 > PlatformMaxCpuCountInitialization: BootCpuCount=2 MaxCpuCount=4 > Q35TsegMbytesInitialization: QEMU offers an extended TSEG (16 MB) > Q35SmramAtDefaultSmbaseInitialization: SMRAM at default SMBASE found > Select Item: 0x19 > Select Item: 0x25 > PlatformGetLowMemoryCB: LowMemory=0x40000000 > PeiInstallPeiMemory MemoryBegin 0x3EF60000, MemoryLength 0xA0000 > Select Item: 0x19 > Select Item: 0x25 > PlatformQemuInitializeRam called > Select Item: 0x19 > Select Item: 0x25 > Register PPI Notify: EE16160A-E8BE-47A6-820A-C6900DB0250A > Select Item: 0x19 > Select Item: 0x26 > Register PPI Notify: EE16160A-E8BE-47A6-820A-C6900DB0250A > Temp Stack : BaseAddress=0x818000 Length=0x8000 > Temp Heap : BaseAddress=0x810000 Length=0x8000 > Total temporary memory: 65536 bytes. > temporary memory stack ever used: 28412 bytes. > temporary memory heap used for HobList: 4656 bytes. > temporary memory heap occupied by memory pages: 0 bytes. > Old Stack size 32768, New stack size 131072 > Stack Hob: BaseAddress=0x3EF60000 Length=0x20000 > Heap Offset = 0x3E770000 Stack Offset = 0x3E760000 > TemporaryRamMigration(0x810000, 0x3EF78000, 0x10000) > Reinstall PPI: 8C8CE578-8A3D-4F1C-9935-896185C32DD3 > Reinstall PPI: 5473C07A-3DCB-4DCA-BD6F-1E9689E7349A > Reinstall PPI: B9E0ABFE-5979-4914-977F-6DEE78C278A6 > Install PPI: F894643D-C449-42D1-8EA8-85BDD8C65BDE > Loading PEIM 86D70125-BAA3-4296-A62F-602BEBBB9081 > Loading PEIM at 0x0000083F640 EntryPoint=0x000008424C3 DxeIpl.efi > Register PPI Notify: F894643D-C449-42D1-8EA8-85BDD8C65BDE > Install PPI: 0AE8CE5D-E448-4437-A8D7-EBF5F194F731 > Notify: PPI Guid: F894643D-C449-42D1-8EA8-85BDD8C65BDE, Peim notify > entry point: 840B93 > Install PPI: 1A36E4E7-FAB6-476A-8E75-695A0576FDD7 > Loading PEIM 89E549B0-7CFE-449D-9BA3-10D8B2312D71 > Loading PEIM at 0x00000843F40 EntryPoint=0x000008467E2 S3Resume2Pei.efi > Install PPI: 6D582DBC-DB85-4514-8FCC-5ADF6227B147 > Loading PEIM AAC33064-9ED0-4B89-A5AD-3EA767960B22 > Loading PEIM at 0x00000848840 EntryPoint=0x000008499BF > FaultTolerantWritePei.efi > Install PPI: 1D3E9CB8-43AF-490B-830A-3516AA532047 > Loading PEIM 34C8C28F-B61C-45A2-8F2E-89E46BECC63B > Loading PEIM at 0x0000084AD40 EntryPoint=0x0000084CBD6 PeiVariable.efi > Install PPI: 2AB86EF5-ECB5-4134-B556-3854CA1FE1B4 > Loading PEIM 6C0E75B4-B0B9-44D1-8210-3377D7B4E066 > Loading PEIM at 0x0000084DD40 EntryPoint=0x0000084F0B1 > SmmAccessPei.efi > Install PPI: 268F33A9-CCCD-48BE-8817-86053AC32ED6 > Loading PEIM EDADEB9D-DDBA-48BD-9D22-C1C169C8C5C6 > Loading PEIM at 0x000008503C0 EntryPoint=0x000008560CD CpuMpPei.efi > Register PPI Notify: F894643D-C449-42D1-8EA8-85BDD8C65BDE > Notify: PPI Guid: F894643D-C449-42D1-8EA8-85BDD8C65BDE, Peim notify > entry point: 854BA9 > AP Loop Mode is 1 > AP Vector: non-16-bit = 3EFD6000/DC > WakeupBufferStart = 2F000, WakeupBufferSize = 0 > AP Vector: 16-bit = 2F000/41, ExchangeInfo = 2F041/5C > CpuMpPei: 5-Level Paging = 0 > APIC MODE is 1 > MpInitLib: Find 2 processors in system. > GetMicrocodePatchInfoFromHob: Microcode patch cache HOB is not found. > CpuMpPei: 5-Level Paging = 0 > CPU[0000]: Microcode revision = 00000000, expected = 00000000 > CPU[0001]: Microcode revision = 00000000, expected = 00000000 > Register PPI Notify: 8F9D4825-797D-48FC-8471-845025792EF6 > Does not find any stored CPU BIST information from PPI! > APICID - 0x00000000, BIST - 0x00000000 > APICID - 0x00000001, BIST - 0x00000000 > Install PPI: 9E9F374B-8F16-4230-9824-5846EE766A97 > Install PPI: 5CB9CB3D-31A4-480C-9498-29D269BACFBA > Install PPI: EE16160A-E8BE-47A6-820A-C6900DB0250A > Notify: PPI Guid: EE16160A-E8BE-47A6-820A-C6900DB0250A, Peim notify > entry point: 8351C8 > PlatformPei: ClearCacheOnMpServicesAvailable > CpuMpPei: 5-Level Paging = 0 > Notify: PPI Guid: EE16160A-E8BE-47A6-820A-C6900DB0250A, Peim notify > entry point: 836A02 > CpuMpPei: 5-Level Paging = 0 > Loading PEIM F12F698A-E506-4A1B-B32E-6920E55DA1C4 > Loading PEIM at 0x0000085A540 EntryPoint=0x0000085B2EB > TpmMmioSevDecryptPei.efi > TpmMmioSevDecryptPeimEntryPoint > Install PPI: 35C84FF2-7BFE-453D-845F-683A492CF7B7 > Loading PEIM 8AD3148F-945F-46B4-8ACD-71469EA73945 > Loading PEIM at 0x0000085C040 EntryPoint=0x0000085D177 Tcg2ConfigPei.efi > Tcg2ConfigPeimEntryPoint > Tcg2ConfigPeimEntryPoint: no TPM detected > Install PPI: A030D115-54DD-447B-9064-F206883D7CCC > Install PPI: 7F4158D3-074D-456D-8CB2-01F9C8F79DAA > Loading PEIM 2BE1E4A6-6505-43B3-9FFC-A3C8330E0432 > Loading PEIM at 0x0000085ECC0 EntryPoint=0x0000086116D TcgPei.efi > No TPM12 instance required! > Loading PEIM A0C98B77-CBA5-4BB8-993B-4AF6CE33ECE4 > Loading PEIM at 0x00000863140 EntryPoint=0x0000086BC2E Tcg2Pei.efi > No TPM2 instance required! > Loading PEIM 47727552-A54B-4A84-8CC1-BFF23E239636 > Loading PEIM at 0x0000086F8C0 EntryPoint=0x000008719DA > Tcg2PlatformPei.efi > Register PPI Notify: 605EA650-C65C-42E1-BA80-91A52AB618C6 > DXE IPL Entry > Enter S3 PEIM > SmmLockBoxPeiLib RestoreLockBox - Enter > SmmLockBoxPeiLib LocatePpi - (Not Found) > SmmLockBoxPeiLib RestoreLockBox - Exit (Success) > SmmLockBoxPeiLib RestoreLockBox - Enter > SmmLockBoxPeiLib LocatePpi - (Not Found) > SmmLockBoxPeiLib RestoreLockBox - Exit (Success) > SmmLockBoxPeiLib RestoreLockBox - Enter > SmmLockBoxPeiLib LocatePpi - (Not Found) > SmmLockBoxPeiLib RestoreLockBox - Exit (Success) > SmmLockBoxPeiLib RestoreLockBox - Enter > SmmLockBoxPeiLib LocatePpi - (Not Found) > SmmLockBoxPeiLib RestoreLockBox - Exit (Success) > AcpiS3Context = 3E963000 > Waking Vector = 981D0 > AcpiS3Context->AcpiFacsTable = 3E9BB000 > AcpiS3Context->IdtrProfile = 3E962000 > AcpiS3Context->S3NvsPageTableAddress = 3E953000 > AcpiS3Context->S3DebugBufferAddress = 3E94A000 > AcpiS3Context->BootScriptStackBase = 3E94B000 > AcpiS3Context->BootScriptStackSize = 8000 > EfiBootScriptExecutorVariable->BootScriptExecutorEntrypoint = 3E93BE32 > SmmLockBoxPeiLib RestoreAllLockBoxInPlace - Enter > SmmLockBoxPeiLib LocatePpi - (Not Found) > SmmLockBoxPeiLib RestoreAllLockBoxInPlace - Exit (Success) > S3NvsPageTableAddress - 3E953000 (1) > SMM S3 Signature = 534D4D53 > SMM S3 Stack Base = 3FF89000 > SMM S3 Stack Size = 8000 > SMM S3 Resume Entry Point = 3FFC6330 > SMM S3 CR0 = 80010033 > SMM S3 CR3 = 3FF6E000 > SMM S3 CR4 = 668 > SMM S3 Return CS = 10 > SMM S3 Return Entry Point = 845ACC > SMM S3 Return Context1 = 3E963000 > SMM S3 Return Context2 = 3E934000 > SMM S3 Return Stack Pointer = 3EF7EF7C > SMM S3 Smst = 3FFFD240 > SmmRestoreCpu() > > > > > ^ permalink raw reply [flat|nested] 16+ messages in thread
* Re: [edk2-devel] [PATCH v9 0/6] Simplify SMM Relocation Process 2023-03-06 11:43 ` Ni, Ray @ 2023-03-06 13:20 ` Gerd Hoffmann 2023-03-10 9:19 ` Wu, Jiaxin 0 siblings, 1 reply; 16+ messages in thread From: Gerd Hoffmann @ 2023-03-06 13:20 UTC (permalink / raw) To: Ni, Ray Cc: devel@edk2.groups.io, Wu, Jiaxin, Dong, Eric, Zeng, Star, Laszlo Ersek, Kumar, Rahul R On Mon, Mar 06, 2023 at 11:43:12AM +0000, Ni, Ray wrote: > Gerd, > Thanks for reporting. Can you kindly share the reproduce steps? (1) build OvmfPkgIa32X64.dsc with SMM_REQUIRE=TRUE (2) boot linux guest using the firmware build. (3) suspend: use 'echo mem > /sys/power/state' on linux guest shell prompt. (4) wakeup: use 'system_wakeup' on qemu monitor. take care, Gerd ^ permalink raw reply [flat|nested] 16+ messages in thread
* Re: [edk2-devel] [PATCH v9 0/6] Simplify SMM Relocation Process 2023-03-06 13:20 ` Gerd Hoffmann @ 2023-03-10 9:19 ` Wu, Jiaxin 2023-03-10 10:01 ` Gerd Hoffmann 0 siblings, 1 reply; 16+ messages in thread From: Wu, Jiaxin @ 2023-03-10 9:19 UTC (permalink / raw) To: devel@edk2.groups.io, kraxel@redhat.com, Ni, Ray Cc: Dong, Eric, Zeng, Star, Laszlo Ersek, Kumar, Rahul R Is this regression? I remember I tried the S3 on real silicon with the patch change, don't see the issue in normal boot work flow. The only difference what I did is to trigger S3 in the BIOS shell, but it does covered the SmmRestoreCpu test. Now, I'm trying to reproduce the issue on ovmf, and build the OVMF boot on windows qemu, but I saw below error during boot: SecCoreStartupWithStack(0xFFFCC000, 0x820000) ASSERT [SecMain] c:\dev\code\edk2\MdePkg\Library\BasePcdLibNull\PcdLib.c(95): ((BOOLEAN)(0==1)) Build command is: build -p OvmfPkg\OvmfPkgIa32X64.dsc -a X64 -D SMM_REQUIRE -D DEBUG_ON_SERIAL_PORT -D SOURCE_DEBUG_ENABLE Run qemu command is: qemu-system-x86_64 -bios C:\Dev\Code\edk2\Build\Ovmf3264\DEBUG_VS2015x86\FV\OVMF.fd -hda fat:rw:hda-contents -serial file:log001.log -net none Anything need to be care to build OvmfPkgIa32X64? BTW, how can I boot linux guest in windows qemu? Any bkm for this? Thanks, Jiaxin > -----Original Message----- > From: devel@edk2.groups.io <devel@edk2.groups.io> On Behalf Of Gerd > Hoffmann > Sent: Monday, March 6, 2023 9:21 PM > To: Ni, Ray <ray.ni@intel.com> > Cc: devel@edk2.groups.io; Wu, Jiaxin <jiaxin.wu@intel.com>; Dong, Eric > <eric.dong@intel.com>; Zeng, Star <star.zeng@intel.com>; Laszlo Ersek > <lersek@redhat.com>; Kumar, Rahul R <rahul.r.kumar@intel.com> > Subject: Re: [edk2-devel] [PATCH v9 0/6] Simplify SMM Relocation Process > > On Mon, Mar 06, 2023 at 11:43:12AM +0000, Ni, Ray wrote: > > Gerd, > > Thanks for reporting. Can you kindly share the reproduce steps? > > (1) build OvmfPkgIa32X64.dsc with SMM_REQUIRE=TRUE > (2) boot linux guest using the firmware build. > (3) suspend: use 'echo mem > /sys/power/state' on linux guest > shell prompt. > (4) wakeup: use 'system_wakeup' on qemu monitor. > > take care, > Gerd > > > > > ^ permalink raw reply [flat|nested] 16+ messages in thread
* Re: [edk2-devel] [PATCH v9 0/6] Simplify SMM Relocation Process 2023-03-10 9:19 ` Wu, Jiaxin @ 2023-03-10 10:01 ` Gerd Hoffmann 2023-03-10 10:17 ` Wu, Jiaxin ` (2 more replies) 0 siblings, 3 replies; 16+ messages in thread From: Gerd Hoffmann @ 2023-03-10 10:01 UTC (permalink / raw) To: Wu, Jiaxin Cc: devel@edk2.groups.io, Ni, Ray, Dong, Eric, Zeng, Star, Laszlo Ersek, Kumar, Rahul R On Fri, Mar 10, 2023 at 09:19:04AM +0000, Wu, Jiaxin wrote: > Is this regression? I remember I tried the S3 on real silicon with the patch change, don't see the issue in normal boot work flow. The only difference what I did is to trigger S3 in the BIOS shell, but it does covered the SmmRestoreCpu test. > > Now, I'm trying to reproduce the issue on ovmf, and build the OVMF boot on windows qemu, but I saw below error during boot: > SecCoreStartupWithStack(0xFFFCC000, 0x820000) > ASSERT [SecMain] c:\dev\code\edk2\MdePkg\Library\BasePcdLibNull\PcdLib.c(95): ((BOOLEAN)(0==1)) > > Build command is: > build -p OvmfPkg\OvmfPkgIa32X64.dsc -a X64 -D SMM_REQUIRE -D DEBUG_ON_SERIAL_PORT -D SOURCE_DEBUG_ENABLE > > Run qemu command is: > qemu-system-x86_64 -bios C:\Dev\Code\edk2\Build\Ovmf3264\DEBUG_VS2015x86\FV\OVMF.fd -hda fat:rw:hda-contents -serial file:log001.log -net none Mine is this: qemu-system-x86_64 -enable-kvm -machine q35,smm=on -m 4G -net none \ -drive if=pflash,format=raw,file=Build/Ovmf3264/DEBUG_GCC5/FV/OVMF_CODE.fd,readonly=on \ -drive if=pflash,format=raw,file=Build/Ovmf3264/DEBUG_GCC5/FV/OVMF_VARS.fd,snapshot=on \ -chardev vc,id=fw.log -device isa-debugcon,iobase=0x402,chardev=fw.log \ -cdrom /vmdisk/iso/Fedora-Workstation-Live-x86_64-37-1.7.iso \ -device virtio-tablet-pci \ -display gtk,show-tabs=on > Anything need to be care to build OvmfPkgIa32X64? It must be started with the correct flash configuration, see above. The SMM-enabled builds also require the q35 machine type. I have both SMM_REQUIRE and SECURE_BOOT enabled, that probably doesn't make a difference though. I'm using the isa-debugcon instead of the serial port to get the debug log, that should not matter either. > BTW, how can I boot linux guest in windows qemu? Just grab some live iso. The fedora image used above is available from getfedora.org, but any live image should work. How do you trigger suspend from efi shell? There seems to be no builtin command for that. take care, Gerd ^ permalink raw reply [flat|nested] 16+ messages in thread
* Re: [edk2-devel] [PATCH v9 0/6] Simplify SMM Relocation Process 2023-03-10 10:01 ` Gerd Hoffmann @ 2023-03-10 10:17 ` Wu, Jiaxin 2023-03-10 10:29 ` Wu, Jiaxin 2023-03-13 5:50 ` Wu, Jiaxin 2 siblings, 0 replies; 16+ messages in thread From: Wu, Jiaxin @ 2023-03-10 10:17 UTC (permalink / raw) To: kraxel@redhat.com Cc: devel@edk2.groups.io, Ni, Ray, Dong, Eric, Zeng, Star, Laszlo Ersek, Kumar, Rahul R I will have a try with the command. For BIOS shell trigger S3, it just needs a simple application to provide the ACPI FACS waking vector, then write the power management control address at offset 4. Another way is that shell MM command can achieve the trigger action, for example like: mm -io (xxx+4) 0x3400 -w 4, but I suppose the system will crash since there is no waking vector. Thanks, Jiaxin > -----Original Message----- > From: kraxel@redhat.com <kraxel@redhat.com> > Sent: Friday, March 10, 2023 6:01 PM > To: Wu, Jiaxin <jiaxin.wu@intel.com> > Cc: devel@edk2.groups.io; Ni, Ray <ray.ni@intel.com>; Dong, Eric > <eric.dong@intel.com>; Zeng, Star <star.zeng@intel.com>; Laszlo Ersek > <lersek@redhat.com>; Kumar, Rahul R <rahul.r.kumar@intel.com> > Subject: Re: [edk2-devel] [PATCH v9 0/6] Simplify SMM Relocation Process > > On Fri, Mar 10, 2023 at 09:19:04AM +0000, Wu, Jiaxin wrote: > > Is this regression? I remember I tried the S3 on real silicon with the patch > change, don't see the issue in normal boot work flow. The only difference what > I did is to trigger S3 in the BIOS shell, but it does covered the SmmRestoreCpu > test. > > > > Now, I'm trying to reproduce the issue on ovmf, and build the OVMF boot on > windows qemu, but I saw below error during boot: > > SecCoreStartupWithStack(0xFFFCC000, 0x820000) > > ASSERT [SecMain] > c:\dev\code\edk2\MdePkg\Library\BasePcdLibNull\PcdLib.c(95): > ((BOOLEAN)(0==1)) > > > > Build command is: > > build -p OvmfPkg\OvmfPkgIa32X64.dsc -a X64 -D SMM_REQUIRE -D > DEBUG_ON_SERIAL_PORT -D SOURCE_DEBUG_ENABLE > > > > Run qemu command is: > > qemu-system-x86_64 -bios > C:\Dev\Code\edk2\Build\Ovmf3264\DEBUG_VS2015x86\FV\OVMF.fd -hda > fat:rw:hda-contents -serial file:log001.log -net none > > Mine is this: > > qemu-system-x86_64 -enable-kvm -machine q35,smm=on -m 4G -net none \ > -drive > if=pflash,format=raw,file=Build/Ovmf3264/DEBUG_GCC5/FV/OVMF_CODE.fd,r > eadonly=on \ > -drive > if=pflash,format=raw,file=Build/Ovmf3264/DEBUG_GCC5/FV/OVMF_VARS.fd,s > napshot=on \ > -chardev vc,id=fw.log -device isa- > debugcon,iobase=0x402,chardev=fw.log \ > -cdrom /vmdisk/iso/Fedora-Workstation-Live-x86_64-37-1.7.iso \ > -device virtio-tablet-pci \ > -display gtk,show-tabs=on > > > Anything need to be care to build OvmfPkgIa32X64? > > It must be started with the correct flash configuration, see above. > The SMM-enabled builds also require the q35 machine type. > > I have both SMM_REQUIRE and SECURE_BOOT enabled, that probably doesn't > make a difference though. I'm using the isa-debugcon instead of the > serial port to get the debug log, that should not matter either. > > > BTW, how can I boot linux guest in windows qemu? > > Just grab some live iso. The fedora image used above is available from > getfedora.org, but any live image should work. > > How do you trigger suspend from efi shell? There seems to be no > builtin command for that. > > take care, > Gerd ^ permalink raw reply [flat|nested] 16+ messages in thread
* Re: [edk2-devel] [PATCH v9 0/6] Simplify SMM Relocation Process 2023-03-10 10:01 ` Gerd Hoffmann 2023-03-10 10:17 ` Wu, Jiaxin @ 2023-03-10 10:29 ` Wu, Jiaxin 2023-03-10 11:19 ` Gerd Hoffmann 2023-03-13 5:50 ` Wu, Jiaxin 2 siblings, 1 reply; 16+ messages in thread From: Wu, Jiaxin @ 2023-03-10 10:29 UTC (permalink / raw) To: kraxel@redhat.com Cc: devel@edk2.groups.io, Ni, Ray, Dong, Eric, Zeng, Star, Laszlo Ersek, Kumar, Rahul R Gerd, Could you help confirm whether this is regression in OVMF before I set up the enviroment? Thanks, Jiaxin > -----Original Message----- > From: Wu, Jiaxin > Sent: Friday, March 10, 2023 6:18 PM > To: kraxel@redhat.com > Cc: devel@edk2.groups.io; Ni, Ray <ray.ni@intel.com>; Dong, Eric > <eric.dong@intel.com>; Zeng, Star <star.zeng@intel.com>; Laszlo Ersek > <lersek@redhat.com>; Kumar, Rahul R <rahul.r.kumar@intel.com> > Subject: RE: [edk2-devel] [PATCH v9 0/6] Simplify SMM Relocation Process > > I will have a try with the command. > > For BIOS shell trigger S3, it just needs a simple application to provide the ACPI > FACS waking vector, then write the power management control address at > offset 4. > > Another way is that shell MM command can achieve the trigger action, for > example like: mm -io (xxx+4) 0x3400 -w 4, but I suppose the system will crash > since there is no waking vector. > > Thanks, > Jiaxin > > > -----Original Message----- > > From: kraxel@redhat.com <kraxel@redhat.com> > > Sent: Friday, March 10, 2023 6:01 PM > > To: Wu, Jiaxin <jiaxin.wu@intel.com> > > Cc: devel@edk2.groups.io; Ni, Ray <ray.ni@intel.com>; Dong, Eric > > <eric.dong@intel.com>; Zeng, Star <star.zeng@intel.com>; Laszlo Ersek > > <lersek@redhat.com>; Kumar, Rahul R <rahul.r.kumar@intel.com> > > Subject: Re: [edk2-devel] [PATCH v9 0/6] Simplify SMM Relocation Process > > > > On Fri, Mar 10, 2023 at 09:19:04AM +0000, Wu, Jiaxin wrote: > > > Is this regression? I remember I tried the S3 on real silicon with the patch > > change, don't see the issue in normal boot work flow. The only difference > what > > I did is to trigger S3 in the BIOS shell, but it does covered the SmmRestoreCpu > > test. > > > > > > Now, I'm trying to reproduce the issue on ovmf, and build the OVMF boot > on > > windows qemu, but I saw below error during boot: > > > SecCoreStartupWithStack(0xFFFCC000, 0x820000) > > > ASSERT [SecMain] > > c:\dev\code\edk2\MdePkg\Library\BasePcdLibNull\PcdLib.c(95): > > ((BOOLEAN)(0==1)) > > > > > > Build command is: > > > build -p OvmfPkg\OvmfPkgIa32X64.dsc -a X64 -D SMM_REQUIRE -D > > DEBUG_ON_SERIAL_PORT -D SOURCE_DEBUG_ENABLE > > > > > > Run qemu command is: > > > qemu-system-x86_64 -bios > > C:\Dev\Code\edk2\Build\Ovmf3264\DEBUG_VS2015x86\FV\OVMF.fd -hda > > fat:rw:hda-contents -serial file:log001.log -net none > > > > Mine is this: > > > > qemu-system-x86_64 -enable-kvm -machine q35,smm=on -m 4G -net none \ > > -drive > > > if=pflash,format=raw,file=Build/Ovmf3264/DEBUG_GCC5/FV/OVMF_CODE.fd,r > > eadonly=on \ > > -drive > > > if=pflash,format=raw,file=Build/Ovmf3264/DEBUG_GCC5/FV/OVMF_VARS.fd,s > > napshot=on \ > > -chardev vc,id=fw.log -device isa- > > debugcon,iobase=0x402,chardev=fw.log \ > > -cdrom /vmdisk/iso/Fedora-Workstation-Live-x86_64-37-1.7.iso \ > > -device virtio-tablet-pci \ > > -display gtk,show-tabs=on > > > > > Anything need to be care to build OvmfPkgIa32X64? > > > > It must be started with the correct flash configuration, see above. > > The SMM-enabled builds also require the q35 machine type. > > > > I have both SMM_REQUIRE and SECURE_BOOT enabled, that probably > doesn't > > make a difference though. I'm using the isa-debugcon instead of the > > serial port to get the debug log, that should not matter either. > > > > > BTW, how can I boot linux guest in windows qemu? > > > > Just grab some live iso. The fedora image used above is available from > > getfedora.org, but any live image should work. > > > > How do you trigger suspend from efi shell? There seems to be no > > builtin command for that. > > > > take care, > > Gerd ^ permalink raw reply [flat|nested] 16+ messages in thread
* Re: [edk2-devel] [PATCH v9 0/6] Simplify SMM Relocation Process 2023-03-10 10:29 ` Wu, Jiaxin @ 2023-03-10 11:19 ` Gerd Hoffmann 0 siblings, 0 replies; 16+ messages in thread From: Gerd Hoffmann @ 2023-03-10 11:19 UTC (permalink / raw) To: devel, jiaxin.wu Cc: Ni, Ray, Dong, Eric, Zeng, Star, Laszlo Ersek, Kumar, Rahul R On Fri, Mar 10, 2023 at 10:29:30AM +0000, Wu, Jiaxin wrote: > Gerd, > > Could you help confirm whether this is regression in OVMF before I set up the enviroment? What exactly? > > > > Run qemu command is: > > > > qemu-system-x86_64 -bios > > > C:\Dev\Code\edk2\Build\Ovmf3264\DEBUG_VS2015x86\FV\OVMF.fd -hda > > > fat:rw:hda-contents -serial file:log001.log -net none This not working? No regression. As already mentioned proper flash setup and using q35 are hard requirements for the SMM-enabled builds. take care, Gerd ^ permalink raw reply [flat|nested] 16+ messages in thread
* Re: [edk2-devel] [PATCH v9 0/6] Simplify SMM Relocation Process 2023-03-10 10:01 ` Gerd Hoffmann 2023-03-10 10:17 ` Wu, Jiaxin 2023-03-10 10:29 ` Wu, Jiaxin @ 2023-03-13 5:50 ` Wu, Jiaxin 2 siblings, 0 replies; 16+ messages in thread From: Wu, Jiaxin @ 2023-03-13 5:50 UTC (permalink / raw) To: kraxel@redhat.com Cc: devel@edk2.groups.io, Ni, Ray, Dong, Eric, Zeng, Star, Laszlo Ersek, Kumar, Rahul R I can reproduce the issue and root cause to below code. GetFirstGuidHob() can't be used after exit boot service, that's the reason why I didn't catch the issue during the S3 test in shell. I will remove those check directly, and add debug message for the mSmmRelocated value. ASSERT (mSmmRelocated == (BOOLEAN)(GetFirstGuidHob (&gSmmBaseHobGuid) != NULL)); if (mSmmRelocated != (BOOLEAN)(GetFirstGuidHob (&gSmmBaseHobGuid) != NULL)) { DEBUG (( DEBUG_ERROR, "gSmmBaseHobGuid %a produced in normal boot but %a in S3 boot!", mSmmRelocated ? "is" : "is not", mSmmRelocated ? "is not" : "is" )); CpuDeadLoop (); } Thanks, Jiaxin > -----Original Message----- > From: Wu, Jiaxin > Sent: Friday, March 10, 2023 6:18 PM > To: kraxel@redhat.com > Cc: devel@edk2.groups.io; Ni, Ray <ray.ni@intel.com>; Dong, Eric > <eric.dong@intel.com>; Zeng, Star <star.zeng@intel.com>; Laszlo Ersek > <lersek@redhat.com>; Kumar, Rahul R <rahul.r.kumar@intel.com> > Subject: RE: [edk2-devel] [PATCH v9 0/6] Simplify SMM Relocation Process > > I will have a try with the command. > > For BIOS shell trigger S3, it just needs a simple application to provide the ACPI > FACS waking vector, then write the power management control address at > offset 4. > > Another way is that shell MM command can achieve the trigger action, for > example like: mm -io (xxx+4) 0x3400 -w 4, but I suppose the system will crash > since there is no waking vector. > > Thanks, > Jiaxin > > > -----Original Message----- > > From: kraxel@redhat.com <kraxel@redhat.com> > > Sent: Friday, March 10, 2023 6:01 PM > > To: Wu, Jiaxin <jiaxin.wu@intel.com> > > Cc: devel@edk2.groups.io; Ni, Ray <ray.ni@intel.com>; Dong, Eric > > <eric.dong@intel.com>; Zeng, Star <star.zeng@intel.com>; Laszlo Ersek > > <lersek@redhat.com>; Kumar, Rahul R <rahul.r.kumar@intel.com> > > Subject: Re: [edk2-devel] [PATCH v9 0/6] Simplify SMM Relocation Process > > > > On Fri, Mar 10, 2023 at 09:19:04AM +0000, Wu, Jiaxin wrote: > > > Is this regression? I remember I tried the S3 on real silicon with the patch > > change, don't see the issue in normal boot work flow. The only difference > what > > I did is to trigger S3 in the BIOS shell, but it does covered the SmmRestoreCpu > > test. > > > > > > Now, I'm trying to reproduce the issue on ovmf, and build the OVMF boot > on > > windows qemu, but I saw below error during boot: > > > SecCoreStartupWithStack(0xFFFCC000, 0x820000) > > > ASSERT [SecMain] > > c:\dev\code\edk2\MdePkg\Library\BasePcdLibNull\PcdLib.c(95): > > ((BOOLEAN)(0==1)) > > > > > > Build command is: > > > build -p OvmfPkg\OvmfPkgIa32X64.dsc -a X64 -D SMM_REQUIRE -D > > DEBUG_ON_SERIAL_PORT -D SOURCE_DEBUG_ENABLE > > > > > > Run qemu command is: > > > qemu-system-x86_64 -bios > > C:\Dev\Code\edk2\Build\Ovmf3264\DEBUG_VS2015x86\FV\OVMF.fd -hda > > fat:rw:hda-contents -serial file:log001.log -net none > > > > Mine is this: > > > > qemu-system-x86_64 -enable-kvm -machine q35,smm=on -m 4G -net none \ > > -drive > > > if=pflash,format=raw,file=Build/Ovmf3264/DEBUG_GCC5/FV/OVMF_CODE.fd,r > > eadonly=on \ > > -drive > > > if=pflash,format=raw,file=Build/Ovmf3264/DEBUG_GCC5/FV/OVMF_VARS.fd,s > > napshot=on \ > > -chardev vc,id=fw.log -device isa- > > debugcon,iobase=0x402,chardev=fw.log \ > > -cdrom /vmdisk/iso/Fedora-Workstation-Live-x86_64-37-1.7.iso \ > > -device virtio-tablet-pci \ > > -display gtk,show-tabs=on > > > > > Anything need to be care to build OvmfPkgIa32X64? > > > > It must be started with the correct flash configuration, see above. > > The SMM-enabled builds also require the q35 machine type. > > > > I have both SMM_REQUIRE and SECURE_BOOT enabled, that probably > doesn't > > make a difference though. I'm using the isa-debugcon instead of the > > serial port to get the debug log, that should not matter either. > > > > > BTW, how can I boot linux guest in windows qemu? > > > > Just grab some live iso. The fedora image used above is available from > > getfedora.org, but any live image should work. > > > > How do you trigger suspend from efi shell? There seems to be no > > builtin command for that. > > > > take care, > > Gerd ^ permalink raw reply [flat|nested] 16+ messages in thread
* Re: [edk2-devel] [PATCH v9 0/6] Simplify SMM Relocation Process 2023-02-20 1:06 ` [edk2-devel] [PATCH v9 0/6] Simplify SMM Relocation Process Wu, Jiaxin 2023-02-20 1:14 ` Ni, Ray @ 2023-02-20 2:37 ` Michael D Kinney 2023-02-20 2:57 ` Ni, Ray 1 sibling, 1 reply; 16+ messages in thread From: Michael D Kinney @ 2023-02-20 2:37 UTC (permalink / raw) To: devel@edk2.groups.io, Wu, Jiaxin Cc: Dong, Eric, Ni, Ray, Zeng, Star, Laszlo Ersek, Gerd Hoffmann, Kumar, Rahul R, Kinney, Michael D Is this for the edk2-stable202303? Or can it wait to be merged after the release? Thanks, Mike > -----Original Message----- > From: devel@edk2.groups.io <devel@edk2.groups.io> On Behalf Of Wu, Jiaxin > Sent: Sunday, February 19, 2023 5:07 PM > To: devel@edk2.groups.io; Wu, Jiaxin <jiaxin.wu@intel.com> > Cc: Dong, Eric <eric.dong@intel.com>; Ni, Ray <ray.ni@intel.com>; Zeng, Star <star.zeng@intel.com>; Laszlo Ersek > <lersek@redhat.com>; Gerd Hoffmann <kraxel@redhat.com>; Kumar, Rahul R <rahul.r.kumar@intel.com> > Subject: Re: [edk2-devel] [PATCH v9 0/6] Simplify SMM Relocation Process > > Any more comments to patch series? If no objection, Ray, please help merge the patches. > > Thanks, > Jiaxin > > > > > -----Original Message----- > > From: devel@edk2.groups.io <devel@edk2.groups.io> On Behalf Of Wu, Jiaxin > > Sent: Thursday, February 16, 2023 2:16 PM > > To: devel@edk2.groups.io > > Cc: Dong, Eric <eric.dong@intel.com>; Ni, Ray <ray.ni@intel.com>; Zeng, Star > > <star.zeng@intel.com>; Laszlo Ersek <lersek@redhat.com>; Gerd Hoffmann > > <kraxel@redhat.com>; Kumar, Rahul R <rahul.r.kumar@intel.com> > > Subject: [edk2-devel] [PATCH v9 0/6] Simplify SMM Relocation Process > > > > Existing SMBASE Relocation is in the PiSmmCpuDxeSmm driver, which > > will relocate the SMBASE of each processor by setting the SMBASE > > field in the saved state map (at offset 7EF8h) to a new value. > > The RSM instruction reloads the internal SMBASE register with the > > value in SMBASE field when each time it exits SMM. All subsequent > > SMI requests will use the new SMBASE to find the starting address > > for the SMI handler (at SMBASE + 8000h). > > > > Due to the default SMBASE for all x86 processors is 0x30000, the > > APs' 1st SMI for rebase has to be executed one by one to avoid > > the processors over-writing each other's SMM Save State Area (see > > existing SmmRelocateBases() function), which means the next AP has > > to wait for the previous AP to finish its 1st SMI, then it can call > > into its 1st SMI for rebase via Smi Ipi command, thus leading the > > existing SMBASE Relocation has to be running in series. Besides, it > > needs very complex code to handle the AP exit semaphore > > (mRebased[Index]), which will hook return address of SMM Save State > > so that semaphore code can be executed immediately after AP exits > > SMM for SMBASE relocation (see existing SemaphoreHook() function). > > > > This series is to add the new SMM Base HOB for any PEI module to do > > the SmBase relocation ahead of PiSmmCpuDxeSmm driver and store the > > relocated SmBase address in array for each Processors. When the > > SMBASE relocation happens in a PEI module, the PEI module shall > > produce the SMM_BASE_HOB in HOB database which tells the > > PiSmmCpuDxeSmm driver (runs at a later phase) about the new SMBASE > > for each CPU thread. PiSmmCpuDxeSmm driver installs the SMI handler > > at the SMM_BASE_HOB.SmBase[Index]+0x8000 for processor Index. When > > the HOB doesn't exist, PiSmmCpuDxeSmm driver shall relocate and > > program the new SMBASE itself (keep existing SMBASE Relocation way). > > > > With SMM Base Hob support, PiSmmCpuDxeSmm does not need the RSM > > instruction to do the SMBASE Relocation. SMBASE Register for each > > processors have already been programmed and all SMBASE address have > > recorded in SMM Base Hob. So the same default SMBASE Address > > (0x30000) will not be used, thus the processors over-writing each > > other's SMM Save State Area will not happen in PiSmmCpuDxeSmm driver. > > This way makes the first SMI init can be executed in parallel and save > > boot time on multi-core system. Besides, Semaphore Hook code logic > > is also not required, which will greatly simplify the SMBASE > > Relocation flow. > > > > Note: > > This is the new way that firmware can program the SMBASE > > independently of the RSM instruction. The PEI code performing > > this logic will not be open sourced, similarly to other things > > that are kept binary-only in the FSP. Due to the register > > difference in different vender, and it has not been documented > > in the Intel SDM yet, we need a new binary-only interface for > > SMM Base HOB. > > > > Cc: Eric Dong <eric.dong@intel.com> > > Cc: Ray Ni <ray.ni@intel.com> > > Cc: Zeng Star <star.zeng@intel.com> > > Cc: Laszlo Ersek <lersek@redhat.com> > > Cc: Gerd Hoffmann <kraxel@redhat.com> > > Cc: Rahul Kumar <rahul1.kumar@intel.com> > > Signed-off-by: Jiaxin Wu <jiaxin.wu@intel.com> > > > > Jiaxin Wu (6): > > UefiCpuPkg/PiSmmCpuDxeSmm: Fix invalid InitializeMpSyncData call > > UefiCpuPkg/PiSmmCpuDxeSmm: Replace mIsBsp by mBspApicId check > > UefiCpuPkg/SmmBaseHob.h: Add SMM Base HOB Data > > UefiCpuPkg/PiSmmCpuDxeSmm: Consume SMM Base Hob for SmBase info > > UefiCpuPkg/SmmCpuFeaturesLib: Skip SMBASE configuration > > OvmfPkg/SmmCpuFeaturesLib: Check SmBase relocation supported or not > > > > .../Library/SmmCpuFeaturesLib/SmmCpuFeaturesLib.c | 10 +- > > .../SmmCpuFeaturesLib/SmmCpuFeaturesLib.inf | 6 +- > > UefiCpuPkg/Include/Guid/SmmBaseHob.h | 75 ++++++++ > > .../Library/SmmCpuFeaturesLib/CpuFeaturesLib.h | 2 + > > .../SmmCpuFeaturesLib/IntelSmmCpuFeaturesLib.c | 25 ++- > > .../SmmCpuFeaturesLib/SmmCpuFeaturesLib.inf | 6 +- > > .../SmmCpuFeaturesLib/SmmCpuFeaturesLibStm.inf | 3 +- > > UefiCpuPkg/Library/SmmCpuFeaturesLib/SmmStm.c | 3 +- > > .../StandaloneMmCpuFeaturesLib.inf | 6 +- > > UefiCpuPkg/PiSmmCpuDxeSmm/CpuS3.c | 31 +++- > > UefiCpuPkg/PiSmmCpuDxeSmm/MpService.c | 25 ++- > > UefiCpuPkg/PiSmmCpuDxeSmm/PiSmmCpuDxeSmm.c | 193 > > ++++++++++++++++----- > > UefiCpuPkg/PiSmmCpuDxeSmm/PiSmmCpuDxeSmm.h | 26 ++- > > UefiCpuPkg/PiSmmCpuDxeSmm/PiSmmCpuDxeSmm.inf | 3 +- > > UefiCpuPkg/UefiCpuPkg.dec | 5 +- > > 15 files changed, 356 insertions(+), 63 deletions(-) > > create mode 100644 UefiCpuPkg/Include/Guid/SmmBaseHob.h > > > > -- > > 2.16.2.windows.1 > > > > > > > > > > > > > > > ^ permalink raw reply [flat|nested] 16+ messages in thread
* Re: [edk2-devel] [PATCH v9 0/6] Simplify SMM Relocation Process 2023-02-20 2:37 ` Michael D Kinney @ 2023-02-20 2:57 ` Ni, Ray 0 siblings, 0 replies; 16+ messages in thread From: Ni, Ray @ 2023-02-20 2:57 UTC (permalink / raw) To: Kinney, Michael D, devel@edk2.groups.io, Wu, Jiaxin Cc: Dong, Eric, Zeng, Star, Laszlo Ersek, Gerd Hoffmann, Kumar, Rahul R Mike, it can wait. > -----Original Message----- > From: Kinney, Michael D <michael.d.kinney@intel.com> > Sent: Monday, February 20, 2023 10:37 AM > To: devel@edk2.groups.io; Wu, Jiaxin <jiaxin.wu@intel.com> > Cc: Dong, Eric <eric.dong@intel.com>; Ni, Ray <ray.ni@intel.com>; Zeng, Star > <star.zeng@intel.com>; Laszlo Ersek <lersek@redhat.com>; Gerd Hoffmann > <kraxel@redhat.com>; Kumar, Rahul R <rahul.r.kumar@intel.com>; Kinney, > Michael D <michael.d.kinney@intel.com> > Subject: RE: [edk2-devel] [PATCH v9 0/6] Simplify SMM Relocation Process > > Is this for the edk2-stable202303? Or can it wait to be merged after the > release? > > Thanks, > > Mike > > > -----Original Message----- > > From: devel@edk2.groups.io <devel@edk2.groups.io> On Behalf Of Wu, > Jiaxin > > Sent: Sunday, February 19, 2023 5:07 PM > > To: devel@edk2.groups.io; Wu, Jiaxin <jiaxin.wu@intel.com> > > Cc: Dong, Eric <eric.dong@intel.com>; Ni, Ray <ray.ni@intel.com>; Zeng, > Star <star.zeng@intel.com>; Laszlo Ersek > > <lersek@redhat.com>; Gerd Hoffmann <kraxel@redhat.com>; Kumar, > Rahul R <rahul.r.kumar@intel.com> > > Subject: Re: [edk2-devel] [PATCH v9 0/6] Simplify SMM Relocation Process > > > > Any more comments to patch series? If no objection, Ray, please help > merge the patches. > > > > Thanks, > > Jiaxin > > > > > > > > > -----Original Message----- > > > From: devel@edk2.groups.io <devel@edk2.groups.io> On Behalf Of Wu, > Jiaxin > > > Sent: Thursday, February 16, 2023 2:16 PM > > > To: devel@edk2.groups.io > > > Cc: Dong, Eric <eric.dong@intel.com>; Ni, Ray <ray.ni@intel.com>; Zeng, > Star > > > <star.zeng@intel.com>; Laszlo Ersek <lersek@redhat.com>; Gerd > Hoffmann > > > <kraxel@redhat.com>; Kumar, Rahul R <rahul.r.kumar@intel.com> > > > Subject: [edk2-devel] [PATCH v9 0/6] Simplify SMM Relocation Process > > > > > > Existing SMBASE Relocation is in the PiSmmCpuDxeSmm driver, which > > > will relocate the SMBASE of each processor by setting the SMBASE > > > field in the saved state map (at offset 7EF8h) to a new value. > > > The RSM instruction reloads the internal SMBASE register with the > > > value in SMBASE field when each time it exits SMM. All subsequent > > > SMI requests will use the new SMBASE to find the starting address > > > for the SMI handler (at SMBASE + 8000h). > > > > > > Due to the default SMBASE for all x86 processors is 0x30000, the > > > APs' 1st SMI for rebase has to be executed one by one to avoid > > > the processors over-writing each other's SMM Save State Area (see > > > existing SmmRelocateBases() function), which means the next AP has > > > to wait for the previous AP to finish its 1st SMI, then it can call > > > into its 1st SMI for rebase via Smi Ipi command, thus leading the > > > existing SMBASE Relocation has to be running in series. Besides, it > > > needs very complex code to handle the AP exit semaphore > > > (mRebased[Index]), which will hook return address of SMM Save State > > > so that semaphore code can be executed immediately after AP exits > > > SMM for SMBASE relocation (see existing SemaphoreHook() function). > > > > > > This series is to add the new SMM Base HOB for any PEI module to do > > > the SmBase relocation ahead of PiSmmCpuDxeSmm driver and store the > > > relocated SmBase address in array for each Processors. When the > > > SMBASE relocation happens in a PEI module, the PEI module shall > > > produce the SMM_BASE_HOB in HOB database which tells the > > > PiSmmCpuDxeSmm driver (runs at a later phase) about the new SMBASE > > > for each CPU thread. PiSmmCpuDxeSmm driver installs the SMI handler > > > at the SMM_BASE_HOB.SmBase[Index]+0x8000 for processor Index. > When > > > the HOB doesn't exist, PiSmmCpuDxeSmm driver shall relocate and > > > program the new SMBASE itself (keep existing SMBASE Relocation way). > > > > > > With SMM Base Hob support, PiSmmCpuDxeSmm does not need the > RSM > > > instruction to do the SMBASE Relocation. SMBASE Register for each > > > processors have already been programmed and all SMBASE address have > > > recorded in SMM Base Hob. So the same default SMBASE Address > > > (0x30000) will not be used, thus the processors over-writing each > > > other's SMM Save State Area will not happen in PiSmmCpuDxeSmm > driver. > > > This way makes the first SMI init can be executed in parallel and save > > > boot time on multi-core system. Besides, Semaphore Hook code logic > > > is also not required, which will greatly simplify the SMBASE > > > Relocation flow. > > > > > > Note: > > > This is the new way that firmware can program the SMBASE > > > independently of the RSM instruction. The PEI code performing > > > this logic will not be open sourced, similarly to other things > > > that are kept binary-only in the FSP. Due to the register > > > difference in different vender, and it has not been documented > > > in the Intel SDM yet, we need a new binary-only interface for > > > SMM Base HOB. > > > > > > Cc: Eric Dong <eric.dong@intel.com> > > > Cc: Ray Ni <ray.ni@intel.com> > > > Cc: Zeng Star <star.zeng@intel.com> > > > Cc: Laszlo Ersek <lersek@redhat.com> > > > Cc: Gerd Hoffmann <kraxel@redhat.com> > > > Cc: Rahul Kumar <rahul1.kumar@intel.com> > > > Signed-off-by: Jiaxin Wu <jiaxin.wu@intel.com> > > > > > > Jiaxin Wu (6): > > > UefiCpuPkg/PiSmmCpuDxeSmm: Fix invalid InitializeMpSyncData call > > > UefiCpuPkg/PiSmmCpuDxeSmm: Replace mIsBsp by mBspApicId check > > > UefiCpuPkg/SmmBaseHob.h: Add SMM Base HOB Data > > > UefiCpuPkg/PiSmmCpuDxeSmm: Consume SMM Base Hob for SmBase > info > > > UefiCpuPkg/SmmCpuFeaturesLib: Skip SMBASE configuration > > > OvmfPkg/SmmCpuFeaturesLib: Check SmBase relocation supported or > not > > > > > > .../Library/SmmCpuFeaturesLib/SmmCpuFeaturesLib.c | 10 +- > > > .../SmmCpuFeaturesLib/SmmCpuFeaturesLib.inf | 6 +- > > > UefiCpuPkg/Include/Guid/SmmBaseHob.h | 75 ++++++++ > > > .../Library/SmmCpuFeaturesLib/CpuFeaturesLib.h | 2 + > > > .../SmmCpuFeaturesLib/IntelSmmCpuFeaturesLib.c | 25 ++- > > > .../SmmCpuFeaturesLib/SmmCpuFeaturesLib.inf | 6 +- > > > .../SmmCpuFeaturesLib/SmmCpuFeaturesLibStm.inf | 3 +- > > > UefiCpuPkg/Library/SmmCpuFeaturesLib/SmmStm.c | 3 +- > > > .../StandaloneMmCpuFeaturesLib.inf | 6 +- > > > UefiCpuPkg/PiSmmCpuDxeSmm/CpuS3.c | 31 +++- > > > UefiCpuPkg/PiSmmCpuDxeSmm/MpService.c | 25 ++- > > > UefiCpuPkg/PiSmmCpuDxeSmm/PiSmmCpuDxeSmm.c | 193 > > > ++++++++++++++++----- > > > UefiCpuPkg/PiSmmCpuDxeSmm/PiSmmCpuDxeSmm.h | 26 ++- > > > UefiCpuPkg/PiSmmCpuDxeSmm/PiSmmCpuDxeSmm.inf | 3 +- > > > UefiCpuPkg/UefiCpuPkg.dec | 5 +- > > > 15 files changed, 356 insertions(+), 63 deletions(-) > > > create mode 100644 UefiCpuPkg/Include/Guid/SmmBaseHob.h > > > > > > -- > > > 2.16.2.windows.1 > > > > > > > > > > > > > > > > > > > > > > > > > ^ permalink raw reply [flat|nested] 16+ messages in thread
end of thread, other threads:[~2023-03-13 5:50 UTC | newest]
Thread overview: 16+ messages (download: mbox.gz follow: Atom feed
-- links below jump to the message on this page --
[not found] <17443983D6ED8995.20300@groups.io>
2023-02-20 1:06 ` [edk2-devel] [PATCH v9 0/6] Simplify SMM Relocation Process Wu, Jiaxin
2023-02-20 1:14 ` Ni, Ray
2023-02-21 8:48 ` Gerd Hoffmann
2023-02-21 9:12 ` Ni, Ray
2023-02-21 9:45 ` Gerd Hoffmann
2023-03-06 11:13 ` Gerd Hoffmann
2023-03-06 11:43 ` Ni, Ray
2023-03-06 13:20 ` Gerd Hoffmann
2023-03-10 9:19 ` Wu, Jiaxin
2023-03-10 10:01 ` Gerd Hoffmann
2023-03-10 10:17 ` Wu, Jiaxin
2023-03-10 10:29 ` Wu, Jiaxin
2023-03-10 11:19 ` Gerd Hoffmann
2023-03-13 5:50 ` Wu, Jiaxin
2023-02-20 2:37 ` Michael D Kinney
2023-02-20 2:57 ` Ni, Ray
This is a public inbox, see mirroring instructions for how to clone and mirror all data and code used for this inbox