OSDN -- オープンソース・ソフトウェアの開発とダウンロード
日本語の翻訳状況 translation status for ja

チケット #34769
チケット一覧/検索 新規チケット登録 RSS

VM1で、UEFI環境のOSを起動可能にする

登録: 2014-12-31 23:09 最終更新: 2016-09-19 20:22

報告者:
yuichi_xy
担当者:
yuichi_xy
チケットの種類:
機能リクエスト
状況:
オープン [担当者決定済み]
コンポーネント:
(未割り当て)
マイルストーン:
(未割り当て)
優先度:
5 - 中
重要度:
5 - 中
解決法:
なし
ファイル:
1

詳細

VM1で、UEFI環境のOSを起動可能にしたいと思います。

EDK2に含まれるOVMFをゲストBIOS(ゲストUEFI)のベースにしようと思います。
https://github.com/tianocore/tianocore.github.io/wiki/Using-EDK-II-with-Native-GCC


改造内容は次のとおりです。

  • VMM
    • fw-cfgに次のエントリを追加する
      • index 0x5 2byte cpu count (済)
  • UEFI (OVMF)
    • fw-cfg の signature "VMMV" に対応する (済)
    • fw-cfg の index 0x1 4byte interface version がなくても動作するようにする (済)
    • AcpiTimerLib.c ではなく、X86TimerLib.c を使う ? (済)
    • PCI デバイスに対し割り当て済みのリソースを変更しないようにする (済)
    • VM に割り当てられた PCI デバイスに割り当てられているメモリリソースについて、4GB以上と、4GB未満の範囲それぞれにおける上限と下限を計算し、 PCI ルートブリッジのリソースウィンドウとする
    • ACPI テーブルを次のように変更する
      • VM の割り当てられている論理プロセッサの APIC ID を MADT に格納する(歯抜けに対応する)
      • 物理ディスティネーションモードを使う
      • PCI ホットプラグを無効化する
      • PM REG のアドレスを fw-cfg の etc/acpi_pm_base から取得した値をもとに計算する
      • GPE0 BLK のアドレスを、fw-cfg の etc/acpi_pm_base の値 + 0x0c とする
      • SMI CMD を無効にする
      • fw-cfg の acpi/ 配下のファイルを、ACPI テーブルとして登録する
      • MMCFG 領域をメモリマップに反映する

チケットの履歴 (30 件中 3 件表示)

2014-12-31 23:09 更新者: yuichi_xy
  • 新しいチケット "VM1で、UEFI環境のOSを起動可能にする" が作成されました
2014-12-31 23:58 更新者: yuichi_xy
コメント

SeaBIOSのREADME.CSMによると、SeaBIOSはOVMFのcompatibility support moduleとして使えますが、Flash Volumeに一つのファイルとして保存されるようです。

VM1に擬似的なlash Volumeを見せるのは難しいので、SeaBIOSをOVMFのcompatibility support moduleとして使うことは難しそうです。

2015-01-01 20:13 更新者: yuichi_xy
コメント

次のページを参考に、EDK2のソースをsubversionから取得しビルドしてみたら、UEFIのイメージと思われるOVMF.fdができました。 

$ svn co https://svn.code.sf.net/p/edk2/code/trunk/edk2
$ cd edk2
$ make -C BaseTools
$ export export EDK_TOOLS_PATH="`pwd`/BaseTools"
$ . edksetup.sh BaseTools
$ vi Conf/target.txt

次のパラメータの値を、次の値に設定する。

ACTIVE_PLATFORM       = OvmfPkg/OvmfPkgX64.dsc
TOOL_CHAIN_TAG        = GCC47
TARGET_ARCH           = X64

$ build

$ find -name 'OVMF.fd'
./Build/OvmfX64/DEBUG_GCC47/FV/OVMF.fd

以下のページに含まれるUDK2014 SP1には、OVMFのソースは入っていませんでした。

2015-01-01 22:08 更新者: yuichi_xy
コメント

yuichi_xy への返信

次のページを参考に、EDK2のソースをsubversionから取得しビルドしてみたら、UEFIのイメージと思われるOVMF.fdができました。

nasm と uuid-dev パッケージのインストールが必要でした。

2015-01-01 22:13 更新者: yuichi_xy
コメント

http://tianocore.github.io/ovmf/ によると、15214 がリリースバージョンのようです。

2015-01-01 23:00 更新者: yuichi_xy
コメント

buildコマンドに、「-D DEBUG_ON_SERIAL_PORT」オプションを指定したところ、COM1にデバッグメッセージが表示されました。 

build -D DEBUG_ON_SERIAL_PORT
2015-01-02 23:09 更新者: yuichi_xy
コメント

ソースコードを調査して検討した結果、次の改造が必要になると思います。 ★をつけた項目は、改造が大変そうです。。。

  • VMM
    • fw-cfgに次のエントリを追加する
      • index 0x1 4byte interface version
      • index 0x5 2byte cpu count
  • UEFI (OVMF)
    • fw-cfg の signature "VMMV" に対応する
    • AcpiTimerLib.c ではなく、X86TimerLib.c を使う ?
    • PCI デバイスに対し割り当て済みのリソースを変更しないようにする ★
    • VM に割り当てられた PCI デバイスに割り当てられているメモリリソースについて、4GB以上と、4GB未満の範囲それぞれにおける上限と下限を計算し、 PCI ルートブリッジのリソースウィンドウとする
    • ACPI テーブルを次のように変更する
      • VM の割り当てられている論理プロセッサの APIC ID を MADT に格納する(歯抜けに対応する) ★
      • 物理ディスティネーションモードを使う
      • PCI ホットプラグを無効化する
      • PM REG のアドレスを fw-cfg の etc/acpi_pm_base から取得した値をもとに計算する
      • GPE0 BLK のアドレスを、fw-cfg の etc/acpi_pm_base の値 + 0x0c とする
      • SMI CMD を無効にする
      • fw-cfg の acpi/ 配下のファイルを、ACPI テーブルとして登録する
      • MMCFG 領域をメモリマップに反映する
2015-01-06 10:38 更新者: yuichi_xy
コメント

yuichi_xy への返信

* index 0x1 4byte interface version

これはいらないような気がします。

2015-01-11 17:02 更新者: yuichi_xy
コメント

yuichi_xy への返信

* VM の割り当てられている論理プロセッサの APIC ID を MADT に格納する(歯抜けに対応する) ★

VMMでMADTを生成して、ゲストBIOS(ゲストUEFI)に渡してしまえば簡単に実装できる気がしてきました。

2015-01-17 14:38 更新者: yuichi_xy
コメント

Guest UEFIを0xffffffff以下にロードし、VM1のBSPを次のから開始するようにしてみましたが、シリアルコンソールには何も出力されませんでした。

CS_SEL 0xf000 CS_BASE 0xffff0000 CS_LIMIT 0xffff RIP 0xfff0

VMMをパニックさせてみたところ、VM1のBSP(apic id: 4)は、CS_BASE 0x00000000、CS_LIMIT 0xffffffff で、いわゆるunreal modeの状態でした。 Guest UEFI が多少は実行されているが、どこかでストールしているように見えます。 

panic(CPU0,apic id:0x0): Panic requested by user
CR0 80000033    CR2 00000000    CR3 A07D2000    CR4 000026A8
RFLAGS 00000016  GDTR 40343EA8+000000FF  IDTR 401EB5E0+00001000
stackdump: 0 403441F8 0 4014327A 40143298 5 1 19 0 0 403441F8 40125902 A 40125E25 0 40000000 407E7720 8 407E7728 407E76C8 3FFFE000 0 0 0 40125F60 0 407E7730 407E7778 5 5 5 40125F74
backtrace: 4014327A 40143298 40125902 40125E25 40125F60 40125F74 401286C7 401286EC 40128B7C 40144098 4012847F 4011F42F 4011F42F 401216F3 40120C85 40127E98 401286C7 401286EC 401276F5 40128B7C 40144098 4012847F 4011F42F 4011F42F 4012DFA5 40129CB3 4012EC5F 4011F42F 4012DFA5 4012DFA5 40129CB3
Guest state and registers of cpu 0 (apic id:0x0) ------------
RAX 80000033    RCX 00000000    RDX 00000000    RBX 00000000
RSP 010FEC20    RBP 00000000    RSI 00000000    RDI 00000000
R8  00000000    R9  00000000    R10 00000000    R11 00000000
R12 00000000    R13 00000000    R14 00000000    R15 00000000
CR0 00000010    CR2 00000000    CR3 BE1A7000    CR4 000026A8
ACR   ES 00000093 CS 00000093 SS 00000093 DS 00000093 FS 00000093 GS 00000093
LIMIT ES 0000FFFF CS 0000FFFF SS 0000FFFF DS 0000FFFF FS 0000FFFF GS 0000FFFF
BASE  ES 00000000 CS 0004DF90 SS 00000000 DS 00000000 FS 00000000 GS 00000000
SEL   ES 00000000 CS 00004DF9 SS 00000000 DS 00000000 FS 00000000 GS 00000000
RIP 0000000B  RFLAGS 00000002  GDTR BE180480+00000047  IDTR BE181160+00000FFF
EFER 00000101
Exit reason: 0=0x0 (Exception or NMI)
Exit qualification 00000000  VM exit interrupt information 00000000
VM exit errcode 00000000  VMCS IDTR BE181160+00000FFF   VMCS RFLAGS 00000002
re=0 pg=0 sw:en=0x0 es=0x0 cs=0x0 ss=0x0 ds=0x0 fs=0x0 gs=0x0
------------------------------------------------
CR0 80000039    CR2 00000000    CR3 A0A0E000    CR4 000026A8
RFLAGS 00000016  GDTR 407DE808+0000FFFF  IDTR 401EB5E0+0000FFFF
stackdump: 2 407DEB58 1 4014327A 40143298 0 0 19 1 2 407DEB58 40125902 0 40125E25 401268B0 1407F7E90 0 10 407F7E88 407F7E28 0 4015D4E9 A0A34000 407DE800 0 0 0 FFFFFFFF 4015B008 4 0 40125FBE
backtrace: 4014327A 40143298 40125902 40125E25 401268B0 40125FBE 40134F4E 4014E5EC 4014E60A 4014E662 4012F7C6 4011E5BB 40117EB2
Guest state and registers of cpu 2 (apic id:0x4) ------------
RAX BFBFBFBF    RCX 00000000    RDX 00000000    RBX 0000FF74
RSP 00000000    RBP BFBFBFBF    RSI 00000000    RDI 00005042
R8  00000000    R9  00000000    R10 00000000    R11 00000000
R12 00000000    R13 00000000    R14 00000000    R15 00000000
CR0 40000023    CR2 00000000    CR3 00000000    CR4 00000640
ACR   ES 0000C093 CS 0000C09B SS 0000C093 DS 0000C093 FS 0000C093 GS 0000C093
LIMIT ES FFFFFFFF CS FFFFFFFF SS FFFFFFFF DS FFFFFFFF FS FFFFFFFF GS FFFFFFFF
BASE  ES 00000000 CS 00000000 SS 00000000 DS 00000000 FS 00000000 GS 00000000
SEL   ES 00000008 CS 00000010 SS 00000008 DS 00000008 FS 00000008 GS 00000008
RIP FFFFFDD8  RFLAGS 00000087  GDTR FFFFFF80+0000001F  IDTR 00000000+000003FF
EFER 00000000
Exit reason: 0=0x0 (Exception or NMI)
Exit qualification 00000000  VM exit interrupt information 80000202
VM exit errcode 00000000  VMCS IDTR 00000000+000003FF   VMCS RFLAGS 00000087
re=0 pg=0 sw:en=0x0 es=0x0 cs=0x0 ss=0x0 ds=0x0 fs=0x0 gs=0x0
------------------------------------------------
2015-01-17 21:57 更新者: yuichi_xy
コメント

yuichi_xy への返信

VMMをパニックさせてみたところ、VM1のBSP(apic id: 4)は、CS_BASE 0x00000000、CS_LIMIT 0xffffffff で、いわゆるunreal modeの状態でした。 Guest UEFI が多少は実行されているが、どこかでストールしているように見えます。

よく見てみると、CR0が80000039なので、unreal modeではありませんでした。 ページングが有効なプロテクトモードですね。 

> CR0 80000039    CR2 00000000    CR3 A0A0E000    CR4 000026A8
> RFLAGS 00000016  GDTR 407DE808+0000FFFF  IDTR 401EB5E0+0000FFFF
> stackdump: 2 407DEB58 1 4014327A 40143298 0 0 19 1 2 407DEB58 40125902 0 40125E25 401268B0 1407F7E90 0 10 407F7E88 407F7E28 0 4015D4E9 A0A34000 407DE800 0 0 0 FFFFFFFF 4015B008 4 0 40125FBE
> backtrace: 4014327A 40143298 40125902 40125E25 401268B0 40125FBE 40134F4E 4014E5EC 4014E60A 4014E662 4012F7C6 4011E5BB 40117EB2
> Guest state and registers of cpu 2 (apic id:0x4) ------------
> RAX BFBFBFBF    RCX 00000000    RDX 00000000    RBX 0000FF74
> RSP 00000000    RBP BFBFBFBF    RSI 00000000    RDI 00005042
> R8  00000000    R9  00000000    R10 00000000    R11 00000000
> R12 00000000    R13 00000000    R14 00000000    R15 00000000
> CR0 40000023    CR2 00000000    CR3 00000000    CR4 00000640
> ACR   ES 0000C093 CS 0000C09B SS 0000C093 DS 0000C093 FS 0000C093 GS 0000C093
> LIMIT ES FFFFFFFF CS FFFFFFFF SS FFFFFFFF DS FFFFFFFF FS FFFFFFFF GS FFFFFFFF
> BASE  ES 00000000 CS 00000000 SS 00000000 DS 00000000 FS 00000000 GS 00000000
> SEL   ES 00000008 CS 00000010 SS 00000008 DS 00000008 FS 00000008 GS 00000008
> RIP FFFFFDD8  RFLAGS 00000087  GDTR FFFFFF80+0000001F  IDTR 00000000+000003FF
> EFER 00000000
> Exit reason: 0=0x0 (Exception or NMI)
> Exit qualification 00000000  VM exit interrupt information 80000202
> VM exit errcode 00000000  VMCS IDTR 00000000+000003FF   VMCS RFLAGS 00000087
> re=0 pg=0 sw:en=0x0 es=0x0 cs=0x0 ss=0x0 ds=0x0 fs=0x0 gs=0x0
> ------------------------------------------------
2015-01-25 22:30 更新者: yuichi_xy
コメント

yuichi_xy への返信

yuichi_xy への返信

VMMをパニックさせてみたところ、VM1のBSP(apic id: 4)は、CS_BASE 0x00000000、CS_LIMIT 0xffffffff で、いわゆるunreal modeの状態でした。 Guest UEFI が多少は実行されているが、どこかでストールしているように見えます。

よく見てみると、CR0が80000039なので、unreal modeではありませんでした。 ページングが有効なプロテクトモードですね。

いや、ゲストの CR0 が 40000023 なので、ページングが無効なプロテクトモードですね。

2015-01-25 22:51 更新者: yuichi_xy
コメント

RAX レジスタが BFBFBFBF なので、気になってソースを grep してみたところ、 SearchForBfvBase.asm が見つかった。

fiimware volumeが見つからなかったというエラーらしい。

2015-02-09 23:49 更新者: yuichi_xy
コメント

yuichi_xy への返信

RAX レジスタが BFBFBFBF なので、気になってソースを grep してみたところ、 SearchForBfvBase.asm が見つかった。 fiimware volumeが見つからなかったというエラーらしい。

ゲスト物理アドレス 0xffffffff から下位の領域にメモリが割り当てられていなかったことが原因でした。 r317 でメモリを割り当てるようにしたところ、シリアルコンソールに次のメッセージ(1行のみ)が表示されるようになりました。 

> SecCoreStartupWithStack(0xFFFCC000, 0x818000)
2015-04-19 16:31 更新者: yuichi_xy
コメント

panicさせてみたところ、次のような状態でした。 

> trigger_panic 
panic(CPU0,apic id:0x0): Panic requested by user
CR0 80000033    CR2 00000000    CR3 AC7D2000    CR4 000026A8
RFLAGS 00000016  GDTR 40343EA8+000000FF  IDTR 401EB5E0+00001000
stackdump: 0 403441F8 0 4014343A 40143458 7 1 19 0 0 403441F8 40125AA2 3FFFE000 40125FB5 4011F5CF 1E3348F419DC401B 407E6EB0 8 407E6EB8 407E6E58 3FFFE000 0 0 0 401260F0 0 407E6EC0 407E6F08 7 7 7 40126104 
backtrace: 4014343A 40143458 40125AA2 40125FB5 4011F5CF 401260F0 40126104 40128857 4012887C 40128D0C 40144098 4012860F 4011F5CF 40121893 40120E25 40128028 40128857 4012887C 40128D0C 40144098 4012860F 
Guest state and registers of cpu 0 (apic id:0x0) ------------
RAX 80000033    RCX 00000000    RDX 00000000    RBX 00000000
RSP 010FEC20    RBP 00000000    RSI 00000000    RDI 00000000
R8  00000000    R9  00000000    R10 00000000    R11 00000000
R12 00000000    R13 00000000    R14 00000000    R15 00000000
CR0 00000010    CR2 00000000    CR3 CA1A7000    CR4 000026A8
ACR   ES 00000093 CS 00000093 SS 00000093 DS 00000093 FS 00000093 GS 00000093
LIMIT ES 0000FFFF CS 0000FFFF SS 0000FFFF DS 0000FFFF FS 0000FFFF GS 0000FFFF
BASE  ES 00000000 CS 0004DF90 SS 00000000 DS 00000000 FS 00000000 GS 00000000
SEL   ES 00000000 CS 00004DF9 SS 00000000 DS 00000000 FS 00000000 GS 00000000
RIP 0000000B  RFLAGS 00000002  GDTR CA180480+00000047  IDTR CA181160+00000FFF
EFER 00000101
Exit reason: 0=0x0 (Exception or NMI)  
Exit qualification 00000000  VM exit interrupt information 00000000
VM exit errcode 00000000  VMCS IDTR CA181160+00000FFF   VMCS RFLAGS 00000002
re=0 pg=0 sw:en=0x0 es=0x0 cs=0x0 ss=0x0 ds=0x0 fs=0x0 gs=0x0
------------------------------------------------
CR0 80000039    CR2 00000000    CR3 ACA0E000    CR4 000026A8
RFLAGS 00000016  GDTR 407DE808+0000FFFF  IDTR 401EB5E0+0000FFFF
stackdump: 2 407DEB58 1 4014343A 40143458 0 0 19 1 2 407DEB58 40125AA2 1 40125FB5 0 4014CD2B 1E 10 407F7E88 407F7E28 0 4015D529 ACA36000 0 22F600000 22F600000 4015B048 FFFFFFFF 4015B048 4 0 4012614E 
backtrace: 4014343A 40143458 40125AA2 40125FB5 4014CD2B 4012614E 401350DE 4014E5EC 4014E60A 4014E662 4012F956 4011E75B 40118052 
Guest state and registers of cpu 2 (apic id:0x4) ------------
RAX 00C1C000    RCX 005C4098    RDX 00000043    RBX FFFFBB2E
RSP 00817748    RBP 00817848    RSI 00000000    RDI 00817950
R8  00000001    R9  00817A38    R10 00817A34    R11 FFE20085
R12 00000000    R13 00000000    R14 00000000    R15 00000000
CR0 C0000023    CR2 00000000    CR3 00800000    CR4 00000660
ACR   ES 0000C093 CS 0000A09B SS 0000C093 DS 0000C093 FS 0000C093 GS 0000C093
LIMIT ES (2^64-1) CS (2^64-1) SS (2^64-1) DS (2^64-1) FS (2^64-1) GS (2^64-1)
BASE  ES 00000000 CS 00000000 SS 00000000 DS 00000000 FS 00000000 GS 00000000
SEL   ES 00000008 CS 00000018 SS 00000008 DS 00000008 FS 00000008 GS 00000008
RIP FFFD0475  RFLAGS 00010007  GDTR FFFFFF80+0000001F  IDTR 00817D60+0000021F
EFER 00000500
Exit reason: 48=0x30 (EPT Violation)  
Exit qualification 00000182  VM exit interrupt information 00000000
VM exit errcode 00000000  VMCS IDTR 00817D60+0000021F   VMCS RFLAGS 00010007
Guest phys addr 00c1c000 Guest linear addr 00c1c000
re=0 pg=1 sw:en=0x0 es=0x0 cs=0x0 ss=0x0 ds=0x0 fs=0x0 gs=0x0
------------------------------------------------
panic(CPU0,apic id:0x0): Panic requested by user
s:shell r:reboot ?
2015-04-19 16:31 更新者: yuichi_xy
コメント

数分待ったところ、先に進みました。 

> SecCoreStartupWithStack(0xFFFCC000, 0x818000)
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
Loading PEIM at 0x00000836E00 EntryPoint=0x00000837060 PcdPeim.efi
Install PPI: 06E81C58-4AD7-44BC-8390-F10265F72480
Install PPI: 01F34D25-4DE2-23AD-3FF3-36353FF323F1
Loading PEIM at 0x0000083FDA0 EntryPoint=0x00000840000 StatusCodePei.efi
Install PPI: 229832D3-7A30-4B36-B827-F40CB7D45436
Loading PEIM at 0x000008458A0 EntryPoint=0x00000845B00 PlatformPei.efi
Platform PEIM Loaded
CMOS:
00: 50 00 23 00 16 00 07 19 04 15 00 02 00 80 00 00
10: 00 00 00 00 00 00 00 00 00 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: 00 00 00 00 91 C8 00 00 00 00 00 00 00 23 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 1D 8B 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
Install PPI: 7408D748-FC8C-4EE6-9288-C4BEC092A410
PeiInstallPeiMemory MemoryBegin 0xC5910000, MemoryLength 0x4000000
QemuInitializeRam called
Reserved variable store memory: 0xC98E0000; size: 128kb
Platform PEI Firmware Volume Initialization
Install PPI: 49EDB1C1-BF21-4761-BB12-EB0031AABB39
Notify: PPI Guid: 49EDB1C1-BF21-4761-BB12-EB0031AABB39, Peim notify entry point: 823800
The 1th FV start address is 0x00000900000, size is 0x00700000, handle is 0x900000
Temp Stack : BaseAddress=0x814000 Length=0x4000
Temp Heap  : BaseAddress=0x810000 Length=0x8A0
Total temporary memory:    32768 bytes.
  temporary memory stack ever used: 16384 bytes.
  temporary memory heap used:       2208 bytes.
Old Stack size 16384, New stack size 131072
Heap Offset = 0x0 Stack Offset = 0xC5118000
Stack Hob: BaseAddress=0xC5910000 Length=0x20000
TemporaryRamMigration(0x810000, 0xC592C000, 0x8000)
Loading PEIM at 0x000C98C8000 EntryPoint=0x000C98C8260 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 at 0x000C98BE000 EntryPoint=0x000C98BE260 DxeIpl.efi
Install PPI: 0AE8CE5D-E448-4437-A8D7-EBF5F194F731
Install PPI: 1A36E4E7-FAB6-476A-8E75-695A0576FDD7
DXE IPL Entry
Loading PEIM at 0x000C9886000 EntryPoint=0x000C9886260 DxeCore.efi
Loading DXE CORE at 0x000C9886000 EntryPoint=0x000C9886260
Install PPI: 605EA650-C65C-42E1-BA80-91A52AB618C6
InstallProtocolInterface: 5B1B31A1-9562-11D2-8E3F-00A0C969723B C98B1368
HOBLIST address in DXE = 0xC963B018
Memory Allocation 0x00000006 0xC98E0000 - 0xC990FFFF
Memory Allocation 0x00000004 0x820000 - 0x8FFFFF
Memory Allocation 0x00000004 0x900000 - 0xFFFFFF
Memory Allocation 0x00000004 0xC9866000 - 0xC9885FFF
Memory Allocation 0x00000004 0xC98DF000 - 0xC98DFFFF
Memory Allocation 0x00000004 0xC98C8000 - 0xC98DEFFF
Memory Allocation 0x00000004 0xC98BE000 - 0xC98C7FFF
Memory Allocation 0x00000004 0xC9886000 - 0xC98BDFFF
Memory Allocation 0x00000003 0xC9886000 - 0xC98BDFFF
Memory Allocation 0x00000004 0xC9866000 - 0xC9885FFF
Memory Allocation 0x00000004 0xC9824000 - 0xC9865FFF
Memory Allocation 0x00000004 0xC5910000 - 0xC592FFFF
FV Hob            0x900000 - 0xFFFFFF
InstallProtocolInterface: D8117CFE-94A6-11D4-9A3A-0090273FC14D C98B0E40
InstallProtocolInterface: 8F644FA9-E850-4DB1-9CE2-0B44698E8DA4 C9637B30
InstallProtocolInterface: 09576E91-6D3F-11D2-8E39-00A0C969723B C9638618
InstallProtocolInterface: 220E73B6-6BDB-4413-8405-B974B108619A C9637830
InstallProtocolInterface: EE4E5898-3914-4259-9D6E-DC7BD79403CF C98B1058
Loading driver 9B680FCE-AD6B-4F3A-B60B-F59899003443
InstallProtocolInterface: 5B1B31A1-9562-11D2-8E3F-00A0C969723B C95DCE40
Loading driver at 0x000C97AE000 EntryPoint=0x000C97AE2AF DevicePathDxe.efi
InstallProtocolInterface: BC62157E-3E33-4FEC-9920-2D3B36D750DF C95DDC98
InstallProtocolInterface: 0379BE4E-D706-437D-B037-EDB82FB772A4 C97BA260
InstallProtocolInterface: 8B843E20-8132-4852-90CC-551A4E4A7F1C C97BA2A0
InstallProtocolInterface: 05C99A21-C70F-4AD2-8A5F-35DF3343F51E C97BA2B0
Loading driver 80CF7257-87AB-47F9-A3FE-D50B76D89541
InstallProtocolInterface: 5B1B31A1-9562-11D2-8E3F-00A0C969723B C95DCC40
Loading driver at 0x000C97A2000 EntryPoint=0x000C97A22AF PcdDxe.efi
InstallProtocolInterface: BC62157E-3E33-4FEC-9920-2D3B36D750DF C95DD718
InstallProtocolInterface: 11B34006-D85B-4D0A-A290-D5A571310EF7 C97AA740
InstallProtocolInterface: 13A3F0F6-264A-3EF0-F2E0-DEC512342F34 C97AA840
Loading driver 733CBAC2-B23F-4B92-BC8E-FB01CE5907B7
InstallProtocolInterface: 5B1B31A1-9562-11D2-8E3F-00A0C969723B C95DCA40
Loading driver at 0x000C97E5000 EntryPoint=0x000C97E52AF FvbServicesRuntimeDxe.efi
InstallProtocolInterface: BC62157E-3E33-4FEC-9920-2D3B36D750DF C95DD218
QEMU Flash: Attempting flash detection at FFE00010
QemuFlashDetected => FD behaves as RAM
QemuFlashDetected => No
QEMU flash was not detected. Writable FVB is not being installed.
Error: Image at 000C97E5000 start failed: Write Protected
Loading driver FEDE0A1B-BCA2-4A9F-BB2B-D9FD7DEC2E9F
InstallProtocolInterface: 5B1B31A1-9562-11D2-8E3F-00A0C969723B C95DCA40
Loading driver at 0x000C97E6000 EntryPoint=0x000C97E62AF StatusCodeRuntimeDxe.efi
InstallProtocolInterface: BC62157E-3E33-4FEC-9920-2D3B36D750DF C95DD298
InstallProtocolInterface: D2B2B828-0826-48A7-B3DF-983C006024F0 C97EBE28
Loading driver B601F8C4-43B7-4784-95B1-F4226CB40CEE
InstallProtocolInterface: 5B1B31A1-9562-11D2-8E3F-00A0C969723B C95DC840
Loading driver at 0x000C97DE000 EntryPoint=0x000C97DE2AF RuntimeDxe.efi
InstallProtocolInterface: BC62157E-3E33-4FEC-9920-2D3B36D750DF C95DAD98
InstallProtocolInterface: B7DFB4E1-052F-449F-87BE-9818FC91B733 C97E2700
Loading driver F80697E9-7FD6-4665-8646-88E33EF71DFC
InstallProtocolInterface: 5B1B31A1-9562-11D2-8E3F-00A0C969723B C95DC640
Loading driver at 0x000C979C000 EntryPoint=0x000C979C2AF SecurityStubDxe.efi
InstallProtocolInterface: BC62157E-3E33-4FEC-9920-2D3B36D750DF C95DAA18
InstallProtocolInterface: 94AB2F58-1438-4EF1-9152-18941A3A0E68 C979FCF8
InstallProtocolInterface: A46423E3-4617-49F1-B9FF-D1BFA9115839 C979FCF0
Loading driver 13AC6DD0-73D0-11D4-B06B-00AA00BD6DE7
InstallProtocolInterface: 5B1B31A1-9562-11D2-8E3F-00A0C969723B C95DC440
Loading driver at 0x000C9790000 EntryPoint=0x000C97902AF EbcDxe.efi
InstallProtocolInterface: BC62157E-3E33-4FEC-9920-2D3B36D750DF C95DA698
InstallProtocolInterface: 13AC6DD1-73D0-11D4-B06B-00AA00BD6DE7 C95DA598
InstallProtocolInterface: 2755590C-6F3C-42FA-9EA4-A3BA543CDA25 C95DA498
InstallProtocolInterface: AAEACCFD-F27B-4C17-B610-75CA1F2DFB52 C95DA398
Loading driver 79CA4208-BBA1-4A9A-8456-E1E66A81484E
InstallProtocolInterface: 5B1B31A1-9562-11D2-8E3F-00A0C969723B C95DC240
Loading driver at 0x000C978B000 EntryPoint=0x000C978B2AF Legacy8259.efi
InstallProtocolInterface: BC62157E-3E33-4FEC-9920-2D3B36D750DF C95DA018
InstallProtocolInterface: 38321DBA-4FE0-4E17-8AEC-413055EAEDC1 C978E1E0
Loading driver A19B1FE7-C1BC-49F8-875F-54A5D542443F
InstallProtocolInterface: 5B1B31A1-9562-11D2-8E3F-00A0C969723B C95DC040
Loading driver at 0x000C9785000 EntryPoint=0x000C97852AF CpuIo2Dxe.efi
InstallProtocolInterface: BC62157E-3E33-4FEC-9920-2D3B36D750DF C95C2C18
InstallProtocolInterface: AD61F191-AE5F-4C0E-B9FA-E869D288C64F C9788540
Loading driver 1A1E4886-9517-440E-9FDE-3BE44CEE2136
InstallProtocolInterface: 5B1B31A1-9562-11D2-8E3F-00A0C969723B C95C1E40
Loading driver at 0x000C9776000 EntryPoint=0x000C97762AF CpuDxe.efi
InstallProtocolInterface: BC62157E-3E33-4FEC-9920-2D3B36D750DF C95C2818
InstallProtocolInterface: 26BACCB1-6F42-11D4-BCE7-0080C73C8881 C977F9E0
  Flushing GCD
  Flushing GCD
  Flushing GCD
  Flushing GCD
  Flushing GCD
  Flushing GCD
  Flushing GCD
  Flushing GCD
  Flushing GCD
  Flushing GCD
  Flushing GCD
  Flushing GCD
  Flushing GCD
  Flushing GCD
  Flushing GCD
  Flushing GCD
  Flushing GCD
  Flushing GCD
  Flushing GCD
  Flushing GCD
  Flushing GCD
Loading driver 6F0198AA-1F1D-426D-AE3E-39AB633FCC28
InstallProtocolInterface: 5B1B31A1-9562-11D2-8E3F-00A0C969723B C95C1C40
Loading driver at 0x000C97D8000 EntryPoint=0x000C97D82AF KbcReset.efi
InstallProtocolInterface: BC62157E-3E33-4FEC-9920-2D3B36D750DF C95C2318
InstallProtocolInterface: 27CFAC88-46CC-11D4-9A38-0090273FC14D 0
Loading driver C8339973-A563-4561-B858-D8476F9DEFC4
InstallProtocolInterface: 5B1B31A1-9562-11D2-8E3F-00A0C969723B C95C1A40
Loading driver at 0x000C9771000 EntryPoint=0x000C97712AF Metronome.efi
InstallProtocolInterface: BC62157E-3E33-4FEC-9920-2D3B36D750DF C9557F98
InstallProtocolInterface: 26BACCB2-6F42-11D4-BCE7-0080C73C8881 C9774000
Loading driver 22DC2B60-FE40-42AC-B01F-3AB1FAD9AAD8
InstallProtocolInterface: 5B1B31A1-9562-11D2-8E3F-00A0C969723B C95C1840
Loading driver at 0x000C97D0000 EntryPoint=0x000C97D02AF EmuVariableFvbRuntimeDxe.efi
InstallProtocolInterface: BC62157E-3E33-4FEC-9920-2D3B36D750DF C9557C18
EMU Variable FVB Started
EMU Variable FVB: Using pre-reserved block at C98E0000
EMU Variable FVB: Basic FV headers were invalid
Installing FVB for EMU Variable support
InstallProtocolInterface: 8F644FA9-E850-4DB1-9CE2-0B44698E8DA4 C97D4C80
InstallProtocolInterface: 09576E91-6D3F-11D2-8E39-00A0C969723B C97D4C48
Loading driver CBD2E4D5-7068-4FF5-B462-9822B4AD8D60
InstallProtocolInterface: 5B1B31A1-9562-11D2-8E3F-00A0C969723B C95C1640
Loading driver at 0x000C97BF000 EntryPoint=0x000C97BF2AF VariableRuntimeDxe.efi
InstallProtocolInterface: BC62157E-3E33-4FEC-9920-2D3B36D750DF C9557718
InstallProtocolInterface: CD3D0A05-9E24-437C-A891-1EE053DB7638 C97CAD18
InstallProtocolInterface: 1E5668E2-8481-11D4-BCF1-0080C73C8881 0
Loading driver 79E4A61C-ED73-4312-94FE-E3E7563362A9
InstallProtocolInterface: 5B1B31A1-9562-11D2-8E3F-00A0C969723B C95C1440
Loading driver at 0x000C976C000 EntryPoint=0x000C976C2AF PrintDxe.efi
InstallProtocolInterface: BC62157E-3E33-4FEC-9920-2D3B36D750DF C9557218
InstallProtocolInterface: F05976EF-83F1-4F3D-8619-F7595D41E538 C976F2E0
Loading driver 348C4D62-BFBD-4882-9ECE-C80BB1C4783B
InstallProtocolInterface: 5B1B31A1-9562-11D2-8E3F-00A0C969723B C95C1240
Loading driver at 0x000C9745000 EntryPoint=0x000C97452AF HiiDatabase.efi
InstallProtocolInterface: BC62157E-3E33-4FEC-9920-2D3B36D750DF C9523E18
InstallProtocolInterface: E9CA4775-8657-47FC-97E7-7ED65A084324 C9765DE8
InstallProtocolInterface: 0FD96974-23AA-4CDC-B9CB-98D17750322A C9765E30
InstallProtocolInterface: EF9FC172-A1B2-4693-B327-6D32FC416042 C9765E58
InstallProtocolInterface: 587E72D7-CC50-4F79-8209-CA291FC1A10F C9765EB0
InstallProtocolInterface: 31A6406A-6BDF-4E46-B2A2-EBAA89C40920 C9765E08
Loading driver 96B5C032-DF4C-4B6E-8232-438DCF448D0E
InstallProtocolInterface: 5B1B31A1-9562-11D2-8E3F-00A0C969723B C95C1040
Loading driver at 0x000C973F000 EntryPoint=0x000C973F2AF NullMemoryTestDxe.efi
InstallProtocolInterface: BC62157E-3E33-4FEC-9920-2D3B36D750DF C9523818
InstallProtocolInterface: 309DE7F1-7F5E-4ACE-B49C-531BE5AA95EF C97423E0
Loading driver F9D88642-0737-49BC-81B5-6889CD57D9EA
InstallProtocolInterface: 5B1B31A1-9562-11D2-8E3F-00A0C969723B C9504E40
Loading driver at 0x000C9737000 EntryPoint=0x000C97372AF SmbiosDxe.efi
InstallProtocolInterface: BC62157E-3E33-4FEC-9920-2D3B36D750DF C9523418
InstallProtocolInterface: 03583FF6-CB36-4940-947E-B9B39F4AFAF7 C973C5B0
Loading driver 9622E42C-8E38-4A08-9E8F-54F784652F6B
InstallProtocolInterface: 5B1B31A1-9562-11D2-8E3F-00A0C969723B C9504C40
Loading driver at 0x000C9728000 EntryPoint=0x000C97282AF AcpiTableDxe.efi
InstallProtocolInterface: BC62157E-3E33-4FEC-9920-2D3B36D750DF C9523018
InstallProtocolInterface: FFE06BDD-6107-46A6-7BB2-5A9C7EC5275C C963CB28
Loading driver A210F973-229D-4F4D-AA37-9895E6C9EABA
InstallProtocolInterface: 5B1B31A1-9562-11D2-8E3F-00A0C969723B C9504A40
Loading driver at 0x000C9722000 EntryPoint=0x000C97222AF DpcDxe.efi
InstallProtocolInterface: BC62157E-3E33-4FEC-9920-2D3B36D750DF C9503C18
InstallProtocolInterface: 480F8AE9-0C46-4AA9-BC89-DB9FBA619806 C9725260
Loading driver F2765DEC-6B41-11D5-8E71-00902707B35E
InstallProtocolInterface: 5B1B31A1-9562-11D2-8E3F-00A0C969723B C9504840
Loading driver at 0x000C971D000 EntryPoint=0x000C971D2AF Timer.efi
InstallProtocolInterface: BC62157E-3E33-4FEC-9920-2D3B36D750DF C9503818
InstallProtocolInterface: 26BACCB3-6F42-11D4-BCE7-0080C73C8881 C9720180
Loading driver 2383608E-C6D0-4E3E-858D-45DFAC3543D5
InstallProtocolInterface: 5B1B31A1-9562-11D2-8E3F-00A0C969723B C9504640
Loading driver at 0x000C9712000 EntryPoint=0x000C97122AF PciHostBridge.efi
InstallProtocolInterface: BC62157E-3E33-4FEC-9920-2D3B36D750DF C9503498
InstallProtocolInterface: CF8034BE-6768-4D8B-B739-7CCE683A9FBE C9502F48
InstallProtocolInterface: 09576E91-6D3F-11D2-8E39-00A0C969723B C9719DE0
InstallProtocolInterface: 2F707EBB-4A1A-11D4-9A38-0090273FC14D C94EBE08
Loading driver FE5CEA76-4F72-49E8-986F-2CD899DFFE5D
InstallProtocolInterface: 5B1B31A1-9562-11D2-8E3F-00A0C969723B C9504440
Loading driver at 0x000C9706000 EntryPoint=0x000C97062AF FaultTolerantWriteDxe.efi
InstallProtocolInterface: BC62157E-3E33-4FEC-9920-2D3B36D750DF C94E3F18
Ftw: Remaining work space size - FE0
Ftw: Work block header check error
Ftw: Work block header check error
Ftw: Both are invalid, init workspace
Ftw: start to reclaim work space
Ftw: reclaim work space successfully
InstallProtocolInterface: 3EBD9E82-2C78-4DE6-9786-8D4BFCB7C881 C9430028
InstallProtocolInterface: 6441F818-6362-4E44-B570-7DBA31DD2453 0
Loading driver EBF342FE-B1D3-4EF8-957C-8048606FF671
InstallProtocolInterface: 5B1B31A1-9562-11D2-8E3F-00A0C969723B C9504240
Loading driver at 0x000C96DE000 EntryPoint=0x000C96DE2AF SetupBrowser.efi
InstallProtocolInterface: BC62157E-3E33-4FEC-9920-2D3B36D750DF C94E3B18
InstallProtocolInterface: B9D4C360-BCFB-4F9B-9298-53C136982258 C96FE350
InstallProtocolInterface: A770C357-B693-4E6D-A6CF-D21C728E550B C96FE380
InstallProtocolInterface: 1F73B18D-4630-43C1-A1DE-6F80855D7DA4 C96FE360
Loading driver 4110465D-5FF3-4F4B-B580-24ED0D06747A
InstallProtocolInterface: 5B1B31A1-9562-11D2-8E3F-00A0C969723B C9504040
Loading driver at 0x000C96D8000 EntryPoint=0x000C96D82AF SmbiosPlatformDxe.efi
InstallProtocolInterface: BC62157E-3E33-4FEC-9920-2D3B36D750DF C94E3498
Loading driver 49970331-E3FA-4637-9ABC-3B7868676970
InstallProtocolInterface: 5B1B31A1-9562-11D2-8E3F-00A0C969723B C94E2E40
Loading driver at 0x000C96D0000 EntryPoint=0x000C96D02AF AcpiPlatform.efi
InstallProtocolInterface: BC62157E-3E33-4FEC-9920-2D3B36D750DF C94E3198
Select Item: 0x0
FW CFG Signature: 0x564D4D56
FwCfg interface is supported.
Select Item: 0x5
Select Item: 0x19
Select Item: 0xC002
ACPI S3 disabled
ACPI S4 disabled
ACPI PciWindow32: Base=0xC9910000 End=0xFEEFFFFF Length=0x355F0000
ACPI PciWindow64: Base=0x00000000 End=0x00000000 Length=0x00000000
Loading driver 378D7B65-8DA9-4773-B6E4-A47826A833E1
InstallProtocolInterface: 5B1B31A1-9562-11D2-8E3F-00A0C969723B C94E2C40
Loading driver at 0x000C861E000 EntryPoint=0x000C861E2AF PcRtc.efi
InstallProtocolInterface: BC62157E-3E33-4FEC-9920-2D3B36D750DF C9425A18
InstallProtocolInterface: 27CFAC87-46CC-11D4-9A38-0090273FC14D 0
Loading driver F099D67F-71AE-4C36-B2A3-DCEB0EB2B7D8
InstallProtocolInterface: 5B1B31A1-9562-11D2-8E3F-00A0C969723B C94E2A40
Loading driver at 0x000C96CB000 EntryPoint=0x000C96CB2AF WatchdogTimer.efi
InstallProtocolInterface: BC62157E-3E33-4FEC-9920-2D3B36D750DF C9425698
InstallProtocolInterface: 665E3FF5-46CC-11D4-9A38-0090273FC14D C96CE070
Loading driver AD608272-D07F-4964-801E-7BD3B7888652
InstallProtocolInterface: 5B1B31A1-9562-11D2-8E3F-00A0C969723B C94E2840
Loading driver at 0x000C8615000 EntryPoint=0x000C86152AF MonotonicCounterRuntimeDxe.efi
InstallProtocolInterface: BC62157E-3E33-4FEC-9920-2D3B36D750DF C9425318
InstallProtocolInterface: 1DA97072-BDDC-4B30-99F1-72A0B56FFF2A 0
Loading driver 42857F0A-13F2-4B21-8A23-53D3F714B840
InstallProtocolInterface: 5B1B31A1-9562-11D2-8E3F-00A0C969723B C94E2640
Loading driver at 0x000C860B000 EntryPoint=0x000C860B2AF CapsuleRuntimeDxe.efi
InstallProtocolInterface: BC62157E-3E33-4FEC-9920-2D3B36D750DF C9424F98
InstallProtocolInterface: 5053697E-2CBC-4819-90D9-0580DEEE5754 0
Loading driver FC5C7020-1A48-4198-9BE2-EAD5ABC8CF2F
InstallProtocolInterface: 5B1B31A1-9562-11D2-8E3F-00A0C969723B C94E2440
Loading driver at 0x000C967E000 EntryPoint=0x000C967E2AF BdsDxe.efi
InstallProtocolInterface: BC62157E-3E33-4FEC-9920-2D3B36D750DF C9424B98
Select Item: 0x0
FW CFG Signature: 0x564D4D56
FwCfg interface is supported.
InstallProtocolInterface: 665E3FF6-46CC-11D4-9A38-0090273FC14D C96BB278
Loading driver E660EA85-058E-4B55-A54B-F02F83A24707
InstallProtocolInterface: 5B1B31A1-9562-11D2-8E3F-00A0C969723B C94E2240
Loading driver at 0x000C965F000 EntryPoint=0x000C965F2AF DisplayEngine.efi
InstallProtocolInterface: BC62157E-3E33-4FEC-9920-2D3B36D750DF C9424498
InstallProtocolInterface: 9BBE29E9-FDA1-41EC-AD52-452213742D2E C96770F0
Loading driver 93B80004-9FB3-11D4-9A3A-0090273FC14D
InstallProtocolInterface: 5B1B31A1-9562-11D2-8E3F-00A0C969723B C94E2040
Loading driver at 0x000C9640000 EntryPoint=0x000C96402AF PciBusDxe.efi
InstallProtocolInterface: BC62157E-3E33-4FEC-9920-2D3B36D750DF C8CEB898
InstallProtocolInterface: 18A031AB-B443-4D1A-A5C0-0C09261E9F71 C9659DE0
InstallProtocolInterface: 107A772C-D5E1-11D4-9A46-0090273FC14D C965A060
InstallProtocolInterface: 6A7A5CFF-E8D9-4F70-BADA-75AB3025CE14 C965A080
InstallProtocolInterface: 19CB87AB-2CB9-4665-8360-DDCF6054F79D C9659E38
Loading driver 33CB97AF-6C33-4C42-986B-07581FA366D4
InstallProtocolInterface: 5B1B31A1-9562-11D2-8E3F-00A0C969723B C8CDAE40
Loading driver at 0x000C8602000 EntryPoint=0x000C86022AF BlockMmioToBlockIoDxe.efi
InstallProtocolInterface: BC62157E-3E33-4FEC-9920-2D3B36D750DF C8CEB298
InstallProtocolInterface: 18A031AB-B443-4D1A-A5C0-0C09261E9F71 C8605FC0
InstallProtocolInterface: 107A772C-D5E1-11D4-9A46-0090273FC14D C86062B0
InstallProtocolInterface: 6A7A5CFF-E8D9-4F70-BADA-75AB3025CE14 C86062D0
Loading driver 83DD3B39-7CAF-4FAC-A542-E050B767E3A7
InstallProtocolInterface: 5B1B31A1-9562-11D2-8E3F-00A0C969723B C8CDAC40
Loading driver at 0x000C85FB000 EntryPoint=0x000C85FB2AF VirtioPciDeviceDxe.efi
InstallProtocolInterface: BC62157E-3E33-4FEC-9920-2D3B36D750DF C8CEB018
InstallProtocolInterface: 18A031AB-B443-4D1A-A5C0-0C09261E9F71 C85FF760
InstallProtocolInterface: 107A772C-D5E1-11D4-9A46-0090273FC14D C85FF7C0
InstallProtocolInterface: 6A7A5CFF-E8D9-4F70-BADA-75AB3025CE14 C85FF7E0
Loading driver 11D92DFB-3CA9-4F93-BA2E-4780ED3E03B5
InstallProtocolInterface: 5B1B31A1-9562-11D2-8E3F-00A0C969723B C8CDAA40
Loading driver at 0x000C85F3000 EntryPoint=0x000C85F32AF VirtioBlkDxe.efi
InstallProtocolInterface: BC62157E-3E33-4FEC-9920-2D3B36D750DF C8CD9D18
InstallProtocolInterface: 18A031AB-B443-4D1A-A5C0-0C09261E9F71 C85F8040
InstallProtocolInterface: 107A772C-D5E1-11D4-9A46-0090273FC14D C85F80A0
InstallProtocolInterface: 6A7A5CFF-E8D9-4F70-BADA-75AB3025CE14 C85F80C0
Loading driver FAB5D4F4-83C0-4AAF-8480-442D11DF6CEA
InstallProtocolInterface: 5B1B31A1-9562-11D2-8E3F-00A0C969723B C8CDA840
Loading driver at 0x000C85EB000 EntryPoint=0x000C85EB2AF VirtioScsiDxe.efi
InstallProtocolInterface: BC62157E-3E33-4FEC-9920-2D3B36D750DF C8CD9A18
InstallProtocolInterface: 18A031AB-B443-4D1A-A5C0-0C09261E9F71 C85F0520
InstallProtocolInterface: 107A772C-D5E1-11D4-9A46-0090273FC14D C85F0580
InstallProtocolInterface: 6A7A5CFF-E8D9-4F70-BADA-75AB3025CE14 C85F05A0
Loading driver 51CCF399-4FDF-4E55-A45B-E123F84D456A
InstallProtocolInterface: 5B1B31A1-9562-11D2-8E3F-00A0C969723B C8CDA640
Loading driver at 0x000C85E3000 EntryPoint=0x000C85E32AF ConPlatformDxe.efi
InstallProtocolInterface: BC62157E-3E33-4FEC-9920-2D3B36D750DF C8CD9718
InstallProtocolInterface: 18A031AB-B443-4D1A-A5C0-0C09261E9F71 C85E7CC0
InstallProtocolInterface: 107A772C-D5E1-11D4-9A46-0090273FC14D C85E7E90
InstallProtocolInterface: 6A7A5CFF-E8D9-4F70-BADA-75AB3025CE14 C85E7EB0
InstallProtocolInterface: 18A031AB-B443-4D1A-A5C0-0C09261E9F71 C85E7D00
InstallProtocolInterface: 107A772C-D5E1-11D4-9A46-0090273FC14D C85E7E90
InstallProtocolInterface: 6A7A5CFF-E8D9-4F70-BADA-75AB3025CE14 C85E7EB0
Loading driver 408EDCEC-CF6D-477C-A5A8-B4844E3DE281
InstallProtocolInterface: 5B1B31A1-9562-11D2-8E3F-00A0C969723B C8CDA440
Loading driver at 0x000C85D4000 EntryPoint=0x000C85D42AF ConSplitterDxe.efi
InstallProtocolInterface: BC62157E-3E33-4FEC-9920-2D3B36D750DF C8CD9298
InstallProtocolInterface: 18A031AB-B443-4D1A-A5C0-0C09261E9F71 C85DFAC0
InstallProtocolInterface: 107A772C-D5E1-11D4-9A46-0090273FC14D C85E0040
InstallProtocolInterface: 6A7A5CFF-E8D9-4F70-BADA-75AB3025CE14 C85E0060
InstallProtocolInterface: 18A031AB-B443-4D1A-A5C0-0C09261E9F71 C85DFB80
InstallProtocolInterface: 107A772C-D5E1-11D4-9A46-0090273FC14D C85E0080
InstallProtocolInterface: 6A7A5CFF-E8D9-4F70-BADA-75AB3025CE14 C85E00A0
InstallProtocolInterface: 18A031AB-B443-4D1A-A5C0-0C09261E9F71 C85DFBC0
InstallProtocolInterface: 107A772C-D5E1-11D4-9A46-0090273FC14D C85E00C0
InstallProtocolInterface: 6A7A5CFF-E8D9-4F70-BADA-75AB3025CE14 C85E00E0
InstallProtocolInterface: 18A031AB-B443-4D1A-A5C0-0C09261E9F71 C85DFB00
InstallProtocolInterface: 107A772C-D5E1-11D4-9A46-0090273FC14D C85E0100
InstallProtocolInterface: 6A7A5CFF-E8D9-4F70-BADA-75AB3025CE14 C85E0120
InstallProtocolInterface: 18A031AB-B443-4D1A-A5C0-0C09261E9F71 C85DFB40
InstallProtocolInterface: 107A772C-D5E1-11D4-9A46-0090273FC14D C85E0140
InstallProtocolInterface: 6A7A5CFF-E8D9-4F70-BADA-75AB3025CE14 C85E0160
InstallProtocolInterface: 387477C1-69C7-11D2-8E39-00A0C969723B C85DF6D0
InstallProtocolInterface: DD9E7534-7762-4698-8C14-F58517A625AA C85DF700
InstallProtocolInterface: 31878C87-0B75-11D5-9A4F-0090273FC14D C85DF758
InstallProtocolInterface: 8D59D32B-C655-4AE9-9B15-F25904992A43 C85DF7B0
InstallProtocolInterface: 387477C2-69C7-11D2-8E39-00A0C969723B C85DF890
InstallProtocolInterface: 387477C2-69C7-11D2-8E39-00A0C969723B C85DF9B0
Loading driver CCCB0C28-4B24-11D5-9A5A-0090273FC14D
InstallProtocolInterface: 5B1B31A1-9562-11D2-8E3F-00A0C969723B C8CDA240
Loading driver at 0x000C85C8000 EntryPoint=0x000C85C82AF GraphicsConsoleDxe.efi
InstallProtocolInterface: BC62157E-3E33-4FEC-9920-2D3B36D750DF C8C4E518
InstallProtocolInterface: 18A031AB-B443-4D1A-A5C0-0C09261E9F71 C85CF7C0
InstallProtocolInterface: 107A772C-D5E1-11D4-9A46-0090273FC14D C85CFA60
InstallProtocolInterface: 6A7A5CFF-E8D9-4F70-BADA-75AB3025CE14 C85CFA80
Loading driver 9E863906-A40F-4875-977F-5B93FF237FC6
InstallProtocolInterface: 5B1B31A1-9562-11D2-8E3F-00A0C969723B C8CDA040
Loading driver at 0x000C85B8000 EntryPoint=0x000C85B82AF TerminalDxe.efi
InstallProtocolInterface: BC62157E-3E33-4FEC-9920-2D3B36D750DF C8C4E018
InstallProtocolInterface: 18A031AB-B443-4D1A-A5C0-0C09261E9F71 C85C3440
InstallProtocolInterface: 107A772C-D5E1-11D4-9A46-0090273FC14D C85C3920
InstallProtocolInterface: 6A7A5CFF-E8D9-4F70-BADA-75AB3025CE14 C85C3940
Loading driver 6B38F7B4-AD98-40E9-9093-ACA2B5A253C4
InstallProtocolInterface: 5B1B31A1-9562-11D2-8E3F-00A0C969723B C8C4BE40
Loading driver at 0x000C85AE000 EntryPoint=0x000C85AE2AF DiskIoDxe.efi
InstallProtocolInterface: BC62157E-3E33-4FEC-9920-2D3B36D750DF C8C4CD18
InstallProtocolInterface: 18A031AB-B443-4D1A-A5C0-0C09261E9F71 C85B48E0
InstallProtocolInterface: 107A772C-D5E1-11D4-9A46-0090273FC14D C85B4E30
InstallProtocolInterface: 6A7A5CFF-E8D9-4F70-BADA-75AB3025CE14 C85B4E50
Loading driver 1FA1F39E-FEFF-4AAE-BD7B-38A070A3B609
InstallProtocolInterface: 5B1B31A1-9562-11D2-8E3F-00A0C969723B C8C4BC40
Loading driver at 0x000C85A2000 EntryPoint=0x000C85A22AF PartitionDxe.efi
InstallProtocolInterface: BC62157E-3E33-4FEC-9920-2D3B36D750DF C8C4CA18
InstallProtocolInterface: 18A031AB-B443-4D1A-A5C0-0C09261E9F71 C85AA5E0
InstallProtocolInterface: 107A772C-D5E1-11D4-9A46-0090273FC14D C85AA770
InstallProtocolInterface: 6A7A5CFF-E8D9-4F70-BADA-75AB3025CE14 C85AA790
Loading driver CD3BAFB6-50FB-4FE8-8E4E-AB74D2C1A600
InstallProtocolInterface: 5B1B31A1-9562-11D2-8E3F-00A0C969723B C8C4BA40
Loading driver at 0x000C859C000 EntryPoint=0x000C859C2AF EnglishDxe.efi
InstallProtocolInterface: BC62157E-3E33-4FEC-9920-2D3B36D750DF C8C4C718
InstallProtocolInterface: 1D85CD7F-F43D-11D2-9A0C-0090273FC14D C859F380
InstallProtocolInterface: A4C751FC-23AE-4C3E-92E9-4964CF63F349 C859F3C0
Loading driver 0167CCC4-D0F7-4F21-A3EF-9E64B7CDCE8B
InstallProtocolInterface: 5B1B31A1-9562-11D2-8E3F-00A0C969723B C8C4B840
Loading driver at 0x000C8592000 EntryPoint=0x000C85922AF ScsiBus.efi
InstallProtocolInterface: BC62157E-3E33-4FEC-9920-2D3B36D750DF C8C4C318
InstallProtocolInterface: 18A031AB-B443-4D1A-A5C0-0C09261E9F71 C8598720
InstallProtocolInterface: 107A772C-D5E1-11D4-9A46-0090273FC14D C8598830
InstallProtocolInterface: 6A7A5CFF-E8D9-4F70-BADA-75AB3025CE14 C8598850
Loading driver 0A66E322-3740-4CCE-AD62-BD172CECCA35
InstallProtocolInterface: 5B1B31A1-9562-11D2-8E3F-00A0C969723B C8C4B640
Loading driver at 0x000C8585000 EntryPoint=0x000C85852AF ScsiDisk.efi
InstallProtocolInterface: BC62157E-3E33-4FEC-9920-2D3B36D750DF C8C4C018
InstallProtocolInterface: 18A031AB-B443-4D1A-A5C0-0C09261E9F71 C858EAA0
InstallProtocolInterface: 107A772C-D5E1-11D4-9A46-0090273FC14D C858ED30
InstallProtocolInterface: 6A7A5CFF-E8D9-4F70-BADA-75AB3025CE14 C858ED50
Loading driver 69FD8E47-A161-4550-B01A-5594CEB2B2B2
InstallProtocolInterface: 5B1B31A1-9562-11D2-8E3F-00A0C969723B C8C4B440
Loading driver at 0x000C856F000 EntryPoint=0x000C856F2AF IdeBusDxe.efi
InstallProtocolInterface: BC62157E-3E33-4FEC-9920-2D3B36D750DF C8C49D18
InstallProtocolInterface: 18A031AB-B443-4D1A-A5C0-0C09261E9F71 C8580880
InstallProtocolInterface: 107A772C-D5E1-11D4-9A46-0090273FC14D C8580C70
InstallProtocolInterface: 6A7A5CFF-E8D9-4F70-BADA-75AB3025CE14 C8580C90
InstallProtocolInterface: 0784924F-E296-11D4-9A49-0090273FC14D C8580B50
InstallProtocolInterface: 4D330321-025F-4AAC-90D8-5ED900173B63 C8580B60
Loading driver 99549F44-49BB-4820-B9D2-901329412D67
InstallProtocolInterface: 5B1B31A1-9562-11D2-8E3F-00A0C969723B C8C4B240
Loading driver at 0x000C8568000 EntryPoint=0x000C85682AF IdeController.efi
InstallProtocolInterface: BC62157E-3E33-4FEC-9920-2D3B36D750DF C8C49918
InstallProtocolInterface: 18A031AB-B443-4D1A-A5C0-0C09261E9F71 C856BB60
InstallProtocolInterface: 107A772C-D5E1-11D4-9A46-0090273FC14D C856BD20
InstallProtocolInterface: 6A7A5CFF-E8D9-4F70-BADA-75AB3025CE14 C856BD40
Loading driver 38A0EC22-FBE7-4911-8BC1-176E0D6C1DBD
InstallProtocolInterface: 5B1B31A1-9562-11D2-8E3F-00A0C969723B C8C4B040
Loading driver at 0x000C8561000 EntryPoint=0x000C85612AF IsaAcpi.efi
InstallProtocolInterface: BC62157E-3E33-4FEC-9920-2D3B36D750DF C8C49618
InstallProtocolInterface: 18A031AB-B443-4D1A-A5C0-0C09261E9F71 C8564E60
InstallProtocolInterface: 107A772C-D5E1-11D4-9A46-0090273FC14D C8565130
InstallProtocolInterface: 6A7A5CFF-E8D9-4F70-BADA-75AB3025CE14 C8565110
Loading driver 240612B5-A063-11D4-9A3A-0090273FC14D
InstallProtocolInterface: 5B1B31A1-9562-11D2-8E3F-00A0C969723B C8C18E40
Loading driver at 0x000C8558000 EntryPoint=0x000C85582AF IsaBusDxe.efi
InstallProtocolInterface: BC62157E-3E33-4FEC-9920-2D3B36D750DF C8C49318
InstallProtocolInterface: 18A031AB-B443-4D1A-A5C0-0C09261E9F71 C855E4C0
InstallProtocolInterface: 107A772C-D5E1-11D4-9A46-0090273FC14D C855E5D0
InstallProtocolInterface: 6A7A5CFF-E8D9-4F70-BADA-75AB3025CE14 C855E5F0
Loading driver 93B80003-9FB3-11D4-9A3A-0090273FC14D
InstallProtocolInterface: 5B1B31A1-9562-11D2-8E3F-00A0C969723B C8C18C40
Loading driver at 0x000C854D000 EntryPoint=0x000C854D2AF IsaSerialDxe.efi
InstallProtocolInterface: BC62157E-3E33-4FEC-9920-2D3B36D750DF C8C49018
InstallProtocolInterface: 18A031AB-B443-4D1A-A5C0-0C09261E9F71 C85550C0
InstallProtocolInterface: 107A772C-D5E1-11D4-9A46-0090273FC14D C85553B0
InstallProtocolInterface: 6A7A5CFF-E8D9-4F70-BADA-75AB3025CE14 C85553D0
Loading driver 3DC82376-637B-40A6-A8FC-A565417F2C38
InstallProtocolInterface: 5B1B31A1-9562-11D2-8E3F-00A0C969723B C8C18A40
Loading driver at 0x000C8540000 EntryPoint=0x000C85402AF Ps2KeyboardDxe.efi
InstallProtocolInterface: BC62157E-3E33-4FEC-9920-2D3B36D750DF C8C17D18
InstallProtocolInterface: 18A031AB-B443-4D1A-A5C0-0C09261E9F71 C8548920
InstallProtocolInterface: 107A772C-D5E1-11D4-9A46-0090273FC14D C8548B00
InstallProtocolInterface: 6A7A5CFF-E8D9-4F70-BADA-75AB3025CE14 C8548B20
Loading driver 0ABD8284-6DA3-4616-971A-83A5148067BA
InstallProtocolInterface: 5B1B31A1-9562-11D2-8E3F-00A0C969723B C8C18840
Loading driver at 0x000C8534000 EntryPoint=0x000C85342AF IsaFloppyDxe.efi
InstallProtocolInterface: BC62157E-3E33-4FEC-9920-2D3B36D750DF C8C17A18
InstallProtocolInterface: 18A031AB-B443-4D1A-A5C0-0C09261E9F71 C853BD40
InstallProtocolInterface: 107A772C-D5E1-11D4-9A46-0090273FC14D C853BF10
InstallProtocolInterface: 6A7A5CFF-E8D9-4F70-BADA-75AB3025CE14 C853BF30
Loading driver 961578FE-B6B7-44C3-AF35-6BC705CD2B1F
InstallProtocolInterface: 5B1B31A1-9562-11D2-8E3F-00A0C969723B C8C18640
Loading driver at 0x000C852D000 EntryPoint=0x000C852D570
InstallProtocolInterface: BC62157E-3E33-4FEC-9920-2D3B36D750DF C8C17718
InstallProtocolInterface: 18A031AB-B443-4D1A-A5C0-0C09261E9F71 C852D418
InstallProtocolInterface: 107A772C-D5E1-11D4-9A46-0090273FC14D C852D448
InstallProtocolInterface: 6A7A5CFF-E8D9-4F70-BADA-75AB3025CE14 C852D460
Loading driver A2F436EA-A127-4EF8-957C-8048606FF670
InstallProtocolInterface: 5B1B31A1-9562-11D2-8E3F-00A0C969723B C8C18440
Loading driver at 0x000C851E000 EntryPoint=0x000C851E2AF SnpDxe.efi
InstallProtocolInterface: BC62157E-3E33-4FEC-9920-2D3B36D750DF C8C17418
InstallProtocolInterface: 18A031AB-B443-4D1A-A5C0-0C09261E9F71 C8528BC0
InstallProtocolInterface: 107A772C-D5E1-11D4-9A46-0090273FC14D C8529360
InstallProtocolInterface: 6A7A5CFF-E8D9-4F70-BADA-75AB3025CE14 C8529380
Loading driver 025BBFC7-E6A9-4B8B-82AD-6815A1AEAF4A
InstallProtocolInterface: 5B1B31A1-9562-11D2-8E3F-00A0C969723B C8C18240
Loading driver at 0x000C8509000 EntryPoint=0x000C85092AF MnpDxe.efi
InstallProtocolInterface: BC62157E-3E33-4FEC-9920-2D3B36D750DF C8C17118
InstallProtocolInterface: 18A031AB-B443-4D1A-A5C0-0C09261E9F71 C8518240
InstallProtocolInterface: 107A772C-D5E1-11D4-9A46-0090273FC14D C85196C0
InstallProtocolInterface: 6A7A5CFF-E8D9-4F70-BADA-75AB3025CE14 C85196E0
Loading driver E4F61863-FE2C-4B56-A8F4-08519BC439DF
InstallProtocolInterface: 5B1B31A1-9562-11D2-8E3F-00A0C969723B C8C18040
Loading driver at 0x000C84FB000 EntryPoint=0x000C84FB2AF VlanConfigDxe.efi
InstallProtocolInterface: BC62157E-3E33-4FEC-9920-2D3B36D750DF C8C14E18
InstallProtocolInterface: 18A031AB-B443-4D1A-A5C0-0C09261E9F71 C8504700
InstallProtocolInterface: 107A772C-D5E1-11D4-9A46-0090273FC14D C8504CE0
InstallProtocolInterface: 6A7A5CFF-E8D9-4F70-BADA-75AB3025CE14 C8504D00
Loading driver 529D3F93-E8E9-4E73-B1E1-BDF6A9D50113
InstallProtocolInterface: 5B1B31A1-9562-11D2-8E3F-00A0C969723B C8BE6E40
Loading driver at 0x000C84ED000 EntryPoint=0x000C84ED2AF ArpDxe.efi
InstallProtocolInterface: BC62157E-3E33-4FEC-9920-2D3B36D750DF C8C14B18
InstallProtocolInterface: 18A031AB-B443-4D1A-A5C0-0C09261E9F71 C84F6480
InstallProtocolInterface: 107A772C-D5E1-11D4-9A46-0090273FC14D C84F67A0
InstallProtocolInterface: 6A7A5CFF-E8D9-4F70-BADA-75AB3025CE14 C84F67C0
Loading driver 94734718-0BBC-47FB-96A5-EE7A5AE6A2AD
InstallProtocolInterface: 5B1B31A1-9562-11D2-8E3F-00A0C969723B C8BE6C40
Loading driver at 0x000C84D8000 EntryPoint=0x000C84D82AF Dhcp4Dxe.efi
InstallProtocolInterface: BC62157E-3E33-4FEC-9920-2D3B36D750DF C8C14818
InstallProtocolInterface: 18A031AB-B443-4D1A-A5C0-0C09261E9F71 C84E7980
InstallProtocolInterface: 107A772C-D5E1-11D4-9A46-0090273FC14D C84E80C0
InstallProtocolInterface: 6A7A5CFF-E8D9-4F70-BADA-75AB3025CE14 C84E80E0
Loading driver 26841BDE-920A-4E7A-9FBE-637F477143A6
InstallProtocolInterface: 5B1B31A1-9562-11D2-8E3F-00A0C969723B C8BE6A40
Loading driver at 0x000C84C7000 EntryPoint=0x000C84C72AF Ip4ConfigDxe.efi
InstallProtocolInterface: BC62157E-3E33-4FEC-9920-2D3B36D750DF C8C14518
InstallProtocolInterface: 18A031AB-B443-4D1A-A5C0-0C09261E9F71 C84D2A20
InstallProtocolInterface: 107A772C-D5E1-11D4-9A46-0090273FC14D C84D30B0
InstallProtocolInterface: 6A7A5CFF-E8D9-4F70-BADA-75AB3025CE14 C84D30D0
Loading driver 9FB1A1F3-3B71-4324-B39A-745CBB015FFF
InstallProtocolInterface: 5B1B31A1-9562-11D2-8E3F-00A0C969723B C8BE6840
Loading driver at 0x000C84AC000 EntryPoint=0x000C84AC2AF Ip4Dxe.efi
InstallProtocolInterface: BC62157E-3E33-4FEC-9920-2D3B36D750DF C8C14218
InstallProtocolInterface: 18A031AB-B443-4D1A-A5C0-0C09261E9F71 C84C16E0
InstallProtocolInterface: 107A772C-D5E1-11D4-9A46-0090273FC14D C84C1FF0
InstallProtocolInterface: 6A7A5CFF-E8D9-4F70-BADA-75AB3025CE14 C84C2010
Loading driver DC3641B8-2FA8-4ED3-BC1F-F9962A03454B
InstallProtocolInterface: 5B1B31A1-9562-11D2-8E3F-00A0C969723B C8BE6640
Loading driver at 0x000C8499000 EntryPoint=0x000C84992AF Mtftp4Dxe.efi
InstallProtocolInterface: BC62157E-3E33-4FEC-9920-2D3B36D750DF C8BE3F18
InstallProtocolInterface: 18A031AB-B443-4D1A-A5C0-0C09261E9F71 C84A7180
InstallProtocolInterface: 107A772C-D5E1-11D4-9A46-0090273FC14D C84A72F0
InstallProtocolInterface: 6A7A5CFF-E8D9-4F70-BADA-75AB3025CE14 C84A7310
Loading driver 6D6963AB-906D-4A65-A7CA-BD40E5D6AF4D
InstallProtocolInterface: 5B1B31A1-9562-11D2-8E3F-00A0C969723B C8BE6440
Loading driver at 0x000C8477000 EntryPoint=0x000C84772AF Tcp4Dxe.efi
InstallProtocolInterface: BC62157E-3E33-4FEC-9920-2D3B36D750DF C8BE3C18
InstallProtocolInterface: 18A031AB-B443-4D1A-A5C0-0C09261E9F71 C8490D20
InstallProtocolInterface: 107A772C-D5E1-11D4-9A46-0090273FC14D C8492240
InstallProtocolInterface: 6A7A5CFF-E8D9-4F70-BADA-75AB3025CE14 C8492260
Loading driver 6D6963AB-906D-4A65-A7CA-BD40E5D6AF2B
InstallProtocolInterface: 5B1B31A1-9562-11D2-8E3F-00A0C969723B C8BE6240
Loading driver at 0x000C8463000 EntryPoint=0x000C84632AF Udp4Dxe.efi
InstallProtocolInterface: BC62157E-3E33-4FEC-9920-2D3B36D750DF C8BE3918
InstallProtocolInterface: 18A031AB-B443-4D1A-A5C0-0C09261E9F71 C8472520
InstallProtocolInterface: 107A772C-D5E1-11D4-9A46-0090273FC14D C8472690
InstallProtocolInterface: 6A7A5CFF-E8D9-4F70-BADA-75AB3025CE14 C84726B0
Loading driver 3B1DEAB5-C75D-442E-9238-8E2FFB62B0BB
InstallProtocolInterface: 5B1B31A1-9562-11D2-8E3F-00A0C969723B C8BE6040
Loading driver at 0x000C8450000 EntryPoint=0x000C84502AF UefiPxe4BcDxe.efi
InstallProtocolInterface: BC62157E-3E33-4FEC-9920-2D3B36D750DF C8BE3618
InstallProtocolInterface: 18A031AB-B443-4D1A-A5C0-0C09261E9F71 C845EC00
InstallProtocolInterface: 107A772C-D5E1-11D4-9A46-0090273FC14D C845ED20
InstallProtocolInterface: 6A7A5CFF-E8D9-4F70-BADA-75AB3025CE14 C845ED40
Loading driver 4579B72D-7EC4-4DD4-8486-083C86B182A7
InstallProtocolInterface: 5B1B31A1-9562-11D2-8E3F-00A0C969723B C8BE1E40
Loading driver at 0x000C8430000 EntryPoint=0x000C84302AF IScsi4Dxe.efi
InstallProtocolInterface: BC62157E-3E33-4FEC-9920-2D3B36D750DF C8BE3318
InstallProtocolInterface: 18A031AB-B443-4D1A-A5C0-0C09261E9F71 C8449820
InstallProtocolInterface: 107A772C-D5E1-11D4-9A46-0090273FC14D C8449940
InstallProtocolInterface: 6A7A5CFF-E8D9-4F70-BADA-75AB3025CE14 C8449960
InstallProtocolInterface: 59324945-EC44-4C0D-B1CD-9DB139DF070C C844A4A0
InstallProtocolInterface: 09576E91-6D3F-11D2-8E39-00A0C969723B C8449A20
InstallProtocolInterface: 330D4706-F2A0-4E4F-A369-B66FA8D54385 C8BE2528
Loading driver A92CDB4B-82F1-4E0B-A516-8A655D371524
InstallProtocolInterface: 5B1B31A1-9562-11D2-8E3F-00A0C969723B C8BE1C40
Loading driver at 0x000C8426000 EntryPoint=0x000C84262AF VirtioNetDxe.efi
InstallProtocolInterface: BC62157E-3E33-4FEC-9920-2D3B36D750DF C8BDF998
InstallProtocolInterface: 18A031AB-B443-4D1A-A5C0-0C09261E9F71 C842CB80
InstallProtocolInterface: 107A772C-D5E1-11D4-9A46-0090273FC14D C842CA60
InstallProtocolInterface: 6A7A5CFF-E8D9-4F70-BADA-75AB3025CE14 C842CA80
Loading driver 2FB92EFA-2EE0-4BAE-9EB6-7464125E1EF7
InstallProtocolInterface: 5B1B31A1-9562-11D2-8E3F-00A0C969723B C8BE1A40
Loading driver at 0x000C8417000 EntryPoint=0x000C84172AF UhciDxe.efi
InstallProtocolInterface: BC62157E-3E33-4FEC-9920-2D3B36D750DF C8BDF698
InstallProtocolInterface: 18A031AB-B443-4D1A-A5C0-0C09261E9F71 C8421FE0
InstallProtocolInterface: 107A772C-D5E1-11D4-9A46-0090273FC14D C8422260
InstallProtocolInterface: 6A7A5CFF-E8D9-4F70-BADA-75AB3025CE14 C8422280
Loading driver BDFE430E-8F2A-4DB0-9991-6F856594777E
InstallProtocolInterface: 5B1B31A1-9562-11D2-8E3F-00A0C969723B C8BE1840
Loading driver at 0x000C8405000 EntryPoint=0x000C84052AF EhciDxe.efi
InstallProtocolInterface: BC62157E-3E33-4FEC-9920-2D3B36D750DF C8BDF398
InstallProtocolInterface: 18A031AB-B443-4D1A-A5C0-0C09261E9F71 C8411F40
InstallProtocolInterface: 107A772C-D5E1-11D4-9A46-0090273FC14D C84134D0
InstallProtocolInterface: 6A7A5CFF-E8D9-4F70-BADA-75AB3025CE14 C84134F0
Loading driver 240612B7-A063-11D4-9A3A-0090273FC14D
InstallProtocolInterface: 5B1B31A1-9562-11D2-8E3F-00A0C969723B C8BE1640
Loading driver at 0x000C83F3000 EntryPoint=0x000C83F32AF UsbBusDxe.efi
InstallProtocolInterface: BC62157E-3E33-4FEC-9920-2D3B36D750DF C8BDF098
InstallProtocolInterface: 18A031AB-B443-4D1A-A5C0-0C09261E9F71 C8400420
InstallProtocolInterface: 107A772C-D5E1-11D4-9A46-0090273FC14D C8400E30
InstallProtocolInterface: 6A7A5CFF-E8D9-4F70-BADA-75AB3025CE14 C8400E50
Loading driver 2D2E62CF-9ECF-43B7-8219-94E7FC713DFE
InstallProtocolInterface: 5B1B31A1-9562-11D2-8E3F-00A0C969723B C8BE1440
Loading driver at 0x000C83E5000 EntryPoint=0x000C83E52AF UsbKbDxe.efi
InstallProtocolInterface: BC62157E-3E33-4FEC-9920-2D3B36D750DF C8BDDD98
InstallProtocolInterface: 18A031AB-B443-4D1A-A5C0-0C09261E9F71 C83EE620
InstallProtocolInterface: 107A772C-D5E1-11D4-9A46-0090273FC14D C83EF420
InstallProtocolInterface: 6A7A5CFF-E8D9-4F70-BADA-75AB3025CE14 C83EF440
Loading driver 9FB4B4A7-42C0-4BCD-8540-9BCC6711F83E
InstallProtocolInterface: 5B1B31A1-9562-11D2-8E3F-00A0C969723B C8BE1240
Loading driver at 0x000C83D9000 EntryPoint=0x000C83D92AF UsbMassStorageDxe.efi
InstallProtocolInterface: BC62157E-3E33-4FEC-9920-2D3B36D750DF C8BDDA98
InstallProtocolInterface: 18A031AB-B443-4D1A-A5C0-0C09261E9F71 C83E1040
InstallProtocolInterface: 107A772C-D5E1-11D4-9A46-0090273FC14D C83E1CE0
InstallProtocolInterface: 6A7A5CFF-E8D9-4F70-BADA-75AB3025CE14 C83E1D00
Loading driver E3752948-B9A1-4770-90C4-DF41C38986BE
InstallProtocolInterface: 5B1B31A1-9562-11D2-8E3F-00A0C969723B C8BE1040
Loading driver at 0x000C83CA000 EntryPoint=0x000C83CA2AF QemuVideoDxe.efi
InstallProtocolInterface: BC62157E-3E33-4FEC-9920-2D3B36D750DF C8BDD798
InstallProtocolInterface: 18A031AB-B443-4D1A-A5C0-0C09261E9F71 C83D1620
InstallProtocolInterface: 107A772C-D5E1-11D4-9A46-0090273FC14D C83D1BF0
InstallProtocolInterface: 6A7A5CFF-E8D9-4F70-BADA-75AB3025CE14 C83D1C10
InstallProtocolInterface: 5C198761-16A8-4E69-972C-89D67954F81D C83D18A0
[BdsDxe] Locate Variable Lock protocol - Success
[Variable] Lock: 8BE4DF61-93CA-11D2-AA0D-00E098032B8C:PlatformLangCodes
[Variable] Lock: 8BE4DF61-93CA-11D2-AA0D-00E098032B8C:LangCodes
[Variable] Lock: 8BE4DF61-93CA-11D2-AA0D-00E098032B8C:BootOptionSupport
[Variable] Lock: 8BE4DF61-93CA-11D2-AA0D-00E098032B8C:HwErrRecSupport
[Variable] Lock: 8BE4DF61-93CA-11D2-AA0D-00E098032B8C:OsIndicationsSupported
Variable Driver Auto Update Lang, Lang:eng, PlatformLang:en
InstallProtocolInterface: 09576E91-6D3F-11D2-8E39-00A0C969723B C96BCFD0
InstallProtocolInterface: 330D4706-F2A0-4E4F-A369-B66FA8D54385 C96BCF88
InstallProtocolInterface: 09576E91-6D3F-11D2-8E39-00A0C969723B C96BCFF0
InstallProtocolInterface: 330D4706-F2A0-4E4F-A369-B66FA8D54385 C96BCFA0
InstallProtocolInterface: 09576E91-6D3F-11D2-8E39-00A0C969723B C96BD800
InstallProtocolInterface: 330D4706-F2A0-4E4F-A369-B66FA8D54385 C96BD838
InstallProtocolInterface: 09576E91-6D3F-11D2-8E39-00A0C969723B C96BCC40
InstallProtocolInterface: 330D4706-F2A0-4E4F-A369-B66FA8D54385 C96BCC20
PlatformBdsInit
Registered NotifyDevPath Event
PlatformBdsPolicyBehavior
PCI Bus First Scanning
PciBus: Discovered PPB @ [00|01|00]
ASSERT /home/yuichi_xy/lab/tinyvisor/tinyvisor-sf/uefi/MdeModulePkg/Library/DxeReportStatusCodeLib/ReportStatusCodeLib.c(371): DevicePath != ((void *) 0)
2015-04-19 17:27 更新者: yuichi_xy
  • 詳細が更新されました
2015-04-19 22:15 更新者: yuichi_xy
コメント

Assert に失敗する直前のメッセージを出力している関数を調べてみました。

PCI Bus First Scanning

MdeModulePkg/Bus/Pci/PciBusDxe/PciLib.c PciHostBridgeEnumerator

PciBus: Discovered PPB @ 00|01|00

MdeModulePkg/Bus/Pci/PciBusDxe/PciEnumeratorSupport.c PciSearchDevice

ついでに、以下の改造をする際に参照する必要がありそうな関数も見つけました。

VM に割り当てられた PCI デバイスに割り当てられているメモリリソースについて、4GB以上と、4GB未満の範囲それぞれにおける上限と下限を計算し、 PCI ルートブリッジのリソースウィンドウとする

OvmfPkg/AcpiPlatformDxe/Qemu.c PopulateFwData

VM の割り当てられている論理プロセッサの APIC ID を MADT に格納する(歯抜けに対応する) ★

OvmfPkg/AcpiPlatformDxe/Qemu.c QemuInstallAcpiMadtTable

2015-04-19 23:44 更新者: yuichi_xy
コメント

r328 で PciBusNoEnumeration を使うようにして、PCI デバイスに対し割り当て済みのリソースを変更しないようにしたところ、先に進みました。 

PlatformBdsInit
Registered NotifyDevPath Event
PlatformBdsPolicyBehavior
InstallProtocolInterface: 09576E91-6D3F-11D2-8E39-00A0C969723B C8BAD018
InstallProtocolInterface: 4CF5B200-68B8-4CA5-9EEC-B23E3F50029A C950F528
PciExp - 1 (B-0, D-1, F-0)
InstallProtocolInterface: 09576E91-6D3F-11D2-8E39-00A0C969723B C8BAE818
InstallProtocolInterface: 4CF5B200-68B8-4CA5-9EEC-B23E3F50029A C950F7A8
PciExp - 1 (B-1, D-0, F-0)
InstallProtocolInterface: 09576E91-6D3F-11D2-8E39-00A0C969723B C8BAE798
InstallProtocolInterface: 4CF5B200-68B8-4CA5-9EEC-B23E3F50029A C950F028
InstallProtocolInterface: 09576E91-6D3F-11D2-8E39-00A0C969723B C8BAE718
InstallProtocolInterface: 4CF5B200-68B8-4CA5-9EEC-B23E3F50029A C8AE3CA8
PciExp - 1 (B-0, D-1C, F-0)
InstallProtocolInterface: 09576E91-6D3F-11D2-8E39-00A0C969723B C8BAE698
InstallProtocolInterface: 4CF5B200-68B8-4CA5-9EEC-B23E3F50029A C8AE3A28
PciExp - 1 (B-2, D-0, F-0)
InstallProtocolInterface: 09576E91-6D3F-11D2-8E39-00A0C969723B C8BAE618
InstallProtocolInterface: 4CF5B200-68B8-4CA5-9EEC-B23E3F50029A C8AE37A8
PciExp - 1 (B-0, D-1C, F-5)
InstallProtocolInterface: 09576E91-6D3F-11D2-8E39-00A0C969723B C8BAE598
InstallProtocolInterface: 4CF5B200-68B8-4CA5-9EEC-B23E3F50029A C8AE3528
PciExp - 1 (B-5, D-0, F-0)
Found Mass Storage device: PciRoot(0x0)/Pci(0x1C,0x0)/Pci(0x0,0x0)
PlatformBdsGetDriverOption
Boot Mode:0
Found PCI VGA device
PlatformBdsDiagnostics
PlatformBdsConnectSequence
Select Item: 0x8
Select Item: 0x17
qemu -kernel was not used.
BdsLibConnectAll
Select Item: 0x19
2015-05-04 17:03 更新者: yuichi_xy
コメント

r15214のedk2(uefi)がgcc 4.9ではビルドできなかっため、最新の r17282 に更新しました(r330, r331)。

ビルドして、VM1でuefiを起動してみたところ、ASSERTに失敗しました。 

> SecCoreStartupWithStack(0xFFFCC000, 0x818000)
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
Loading PEIM at 0x00000839F20 EntryPoint=0x0000083A180 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
Loading PEIM at 0x00000843720 EntryPoint=0x00000843980 StatusCodePei.efi
Install PPI: 229832D3-7A30-4B36-B827-F40CB7D45436
Loading PEIM at 0x000008493A0 EntryPoint=0x00000849600 PlatformPei.efi
Select Item: 0x0
FW CFG Signature: 0x564D4D56
FwCfg interface is supported.
Platform PEIM Loaded
CMOS:
00: 49 00 50 00 16 00 01 04 05 15 00 02 00 80 00 00
10: 00 00 00 00 00 00 00 00 00 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: 00 00 00 00 91 BC 00 00 00 00 00 00 00 23 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 1D 8B 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
Select Item: 0x19
Select Item: 0xC002
Install PPI: 7408D748-FC8C-4EE6-9288-C4BEC092A410
PeiInstallPeiMemory MemoryBegin 0xB9910000, MemoryLength 0x4000000
QemuInitializeRam called
Allocated Memory unaligned: Address = 0xBD8E0000, Pages = 0x30, Type = 6
After aligning to 0x10000 bytes: Address = 0xBD8E0000, Pages = 0x20
Updated aligned-mem HOB with BaseAddress = BD8E0000, Length = 20000, MemoryType = 6
Created after-mem HOB with BaseAddress = BD900000, Length = 10000, MemoryType = 7
Reserved variable store memory: 0xBD8E0000; size: 128kb
Platform PEI Firmware Volume Initialization
Install PPI: 49EDB1C1-BF21-4761-BB12-EB0031AABB39
Notify: PPI Guid: 49EDB1C1-BF21-4761-BB12-EB0031AABB39, Peim notify entry point: 824781
The 1th FV start address is 0x00000900000, size is 0x00800000, handle is 0x900000
MiscInitialization: Unknown Host Bridge Device ID: 0xFFFF
ASSERT /home/yuichi_xy/lab/tinyvisor/tinyvisor-sf/uefi/OvmfPkg/PlatformPei/Platform.c(268): ((BOOLEAN)(0==1))

2015-05-04 21:35 更新者: yuichi_xy
コメント

yuichi_xy への返信

ビルドして、VM1でuefiを起動してみたところ、ASSERTに失敗しました。

r332 で ASSERT を削除しました。

先に進みましたが、0 除算例外が発生したようです。　　 

SecCoreStartupWithStack(0xFFFCC000, 0x818000)
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
Loading PEIM at 0x00000839F20 EntryPoint=0x0000083A180 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
Loading PEIM at 0x00000843720 EntryPoint=0x00000843980 StatusCodePei.efi
Install PPI: 229832D3-7A30-4B36-B827-F40CB7D45436
Loading PEIM at 0x000008493A0 EntryPoint=0x00000849600 PlatformPei.efi
Select Item: 0x0
FW CFG Signature: 0x564D4D56
FwCfg interface is supported.
Platform PEIM Loaded
CMOS:
00: 31 00 30 00 17 00 01 04 05 15 00 02 00 80 00 00
10: 00 00 00 00 00 00 00 00 00 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: 00 00 00 00 91 BC 00 00 00 00 00 00 00 23 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 1D 8B 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
Select Item: 0x19
Select Item: 0xC002
Install PPI: 7408D748-FC8C-4EE6-9288-C4BEC092A410
PeiInstallPeiMemory MemoryBegin 0xB9910000, MemoryLength 0x4000000
QemuInitializeRam called
Allocated Memory unaligned: Address = 0xBD8E0000, Pages = 0x30, Type = 6
After aligning to 0x10000 bytes: Address = 0xBD8E0000, Pages = 0x20
Updated aligned-mem HOB with BaseAddress = BD8E0000, Length = 20000, MemoryType = 6
Created after-mem HOB with BaseAddress = BD900000, Length = 10000, MemoryType = 7
Reserved variable store memory: 0xBD8E0000; size: 128kb
Platform PEI Firmware Volume Initialization
Install PPI: 49EDB1C1-BF21-4761-BB12-EB0031AABB39
Notify: PPI Guid: 49EDB1C1-BF21-4761-BB12-EB0031AABB39, Peim notify entry point: 824781
The 1th FV start address is 0x00000900000, size is 0x00800000, handle is 0x900000
MiscInitialization: Unknown Host Bridge Device ID: 0xFFFF
Temp Stack : BaseAddress=0x814000 Length=0x4000
Temp Heap  : BaseAddress=0x810000 Length=0x18C0
Total temporary memory:    32768 bytes.
  temporary memory stack ever used: 16384 bytes.
  temporary memory heap used:       6336 bytes.
Old Stack size 16384, New stack size 131072
Stack Hob: BaseAddress=0xB9910000 Length=0x20000
Heap Offset = 0xB9120000 Stack Offset = 0xB9118000
TemporaryRamMigration(0x810000, 0xB992C000, 0x8000)
Loading PEIM at 0x000BD8C5000 EntryPoint=0x000BD8C5260 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 at 0x000BD8BA000 EntryPoint=0x000BD8BA260 DxeIpl.efi
Install PPI: 0AE8CE5D-E448-4437-A8D7-EBF5F194F731
Install PPI: 1A36E4E7-FAB6-476A-8E75-695A0576FDD7
Loading PEIM at 0x000BD8AF000 EntryPoint=0x000BD8AF260 S3Resume2Pei.efi
Install PPI: 6D582DBC-DB85-4514-8FCC-5ADF6227B147
DXE IPL Entry
Loading PEIM at 0x000BD871000 EntryPoint=0x000BD871260 DxeCore.efi
Loading DXE CORE at 0x000BD871000 EntryPoint=0x000BD871260
Install PPI: 605EA650-C65C-42E1-BA80-91A52AB618C6
InstallProtocolInterface: 5B1B31A1-9562-11D2-8E3F-00A0C969723B BD8A27E8
HOBLIST address in DXE = 0xBD626018
Memory Allocation 0x00000004 0x806000 - 0x806FFF
Memory Allocation 0x00000006 0xBD8E0000 - 0xBD8FFFFF
Memory Allocation 0x00000007 0xBD900000 - 0xBD90FFFF
Memory Allocation 0x00000004 0x820000 - 0x8FFFFF
Memory Allocation 0x00000004 0x900000 - 0x10FFFFF
Memory Allocation 0x00000004 0xBD851000 - 0xBD870FFF
Memory Allocation 0x00000004 0xBD8DF000 - 0xBD8DFFFF
Memory Allocation 0x00000004 0xBD8C5000 - 0xBD8DEFFF
Memory Allocation 0x00000004 0xBD8BA000 - 0xBD8C4FFF
Memory Allocation 0x00000004 0xBD8AF000 - 0xBD8B9FFF
Memory Allocation 0x00000004 0xBD871000 - 0xBD8AEFFF
Memory Allocation 0x00000003 0xBD871000 - 0xBD8AEFFF
Memory Allocation 0x00000004 0xBD851000 - 0xBD870FFF
Memory Allocation 0x00000004 0xBD80F000 - 0xBD850FFF
Memory Allocation 0x00000004 0xB9910000 - 0xB992FFFF
FV Hob            0x900000 - 0x10FFFFF
InstallProtocolInterface: D8117CFE-94A6-11D4-9A3A-0090273FC14D BD8A22C0
InstallProtocolInterface: 8F644FA9-E850-4DB1-9CE2-0B44698E8DA4 BD622270
InstallProtocolInterface: 09576E91-6D3F-11D2-8E39-00A0C969723B BD622658
InstallProtocolInterface: 220E73B6-6BDB-4413-8405-B974B108619A BD621C70
InstallProtocolInterface: EE4E5898-3914-4259-9D6E-DC7BD79403CF BD8A24D8
Loading driver 9B680FCE-AD6B-4F3A-B60B-F59899003443
InstallProtocolInterface: 5B1B31A1-9562-11D2-8E3F-00A0C969723B BD1692C0
Loading driver at 0x000BD798000 EntryPoint=0x000BD7982AF DevicePathDxe.efi
InstallProtocolInterface: BC62157E-3E33-4FEC-9920-2D3B36D750DF BD13AF98
InstallProtocolInterface: 0379BE4E-D706-437D-B037-EDB82FB772A4 BD7A4F80
InstallProtocolInterface: 8B843E20-8132-4852-90CC-551A4E4A7F1C BD7A4FC0
InstallProtocolInterface: 05C99A21-C70F-4AD2-8A5F-35DF3343F51E BD7A4FD0
Loading driver 80CF7257-87AB-47F9-A3FE-D50B76D89541
InstallProtocolInterface: 5B1B31A1-9562-11D2-8E3F-00A0C969723B BD13A700
Loading driver at 0x000BD78B000 EntryPoint=0x000BD78B2AF PcdDxe.efi
InstallProtocolInterface: BC62157E-3E33-4FEC-9920-2D3B36D750DF BD13A558
InstallProtocolInterface: 11B34006-D85B-4D0A-A290-D5A571310EF7 BD794440
InstallProtocolInterface: 13A3F0F6-264A-3EF0-F2E0-DEC512342F34 BD794540
InstallProtocolInterface: 5BE40F57-FA68-4610-BBBF-E9C5FCDAD365 BD7945D0
InstallProtocolInterface: FD0F4478-0EFD-461D-BA2D-E58C45FD5F5E BD7945F0
Loading driver 733CBAC2-B23F-4B92-BC8E-FB01CE5907B7
InstallProtocolInterface: 5B1B31A1-9562-11D2-8E3F-00A0C969723B BD14C340
Loading driver at 0x000BD7D0000 EntryPoint=0x000BD7D02AF FvbServicesRuntimeDxe.efi
InstallProtocolInterface: BC62157E-3E33-4FEC-9920-2D3B36D750DF BD14C798
QEMU Flash: Attempting flash detection at FFE00010
QemuFlashDetected => FD behaves as RAM
QemuFlashDetected => No
QEMU flash was not detected. Writable FVB is not being installed.
Error: Image at 000BD7D0000 start failed: Write Protected
Loading driver FEDE0A1B-BCA2-4A9F-BB2B-D9FD7DEC2E9F
InstallProtocolInterface: 5B1B31A1-9562-11D2-8E3F-00A0C969723B BD14C340
Loading driver at 0x000BD7D0000 EntryPoint=0x000BD7D02AF StatusCodeRuntimeDxe.efi
InstallProtocolInterface: BC62157E-3E33-4FEC-9920-2D3B36D750DF BD14C618
InstallProtocolInterface: D2B2B828-0826-48A7-B3DF-983C006024F0 BD7D6350
Loading driver B601F8C4-43B7-4784-95B1-F4226CB40CEE
InstallProtocolInterface: 5B1B31A1-9562-11D2-8E3F-00A0C969723B BD1492C0
Loading driver at 0x000BD7C8000 EntryPoint=0x000BD7C82AF RuntimeDxe.efi
InstallProtocolInterface: BC62157E-3E33-4FEC-9920-2D3B36D750DF BD149A58
InstallProtocolInterface: B7DFB4E1-052F-449F-87BE-9818FC91B733 BD7CC980
Loading driver F80697E9-7FD6-4665-8646-88E33EF71DFC
InstallProtocolInterface: 5B1B31A1-9562-11D2-8E3F-00A0C969723B BD141040
Loading driver at 0x000BD785000 EntryPoint=0x000BD7852AF SecurityStubDxe.efi
InstallProtocolInterface: BC62157E-3E33-4FEC-9920-2D3B36D750DF BD141E58
InstallProtocolInterface: 94AB2F58-1438-4EF1-9152-18941A3A0E68 BD788E00
InstallProtocolInterface: A46423E3-4617-49F1-B9FF-D1BFA9115839 BD788DF8
Loading driver 13AC6DD0-73D0-11D4-B06B-00AA00BD6DE7
InstallProtocolInterface: 5B1B31A1-9562-11D2-8E3F-00A0C969723B BD141880
Loading driver at 0x000BD778000 EntryPoint=0x000BD7782AF EbcDxe.efi
InstallProtocolInterface: BC62157E-3E33-4FEC-9920-2D3B36D750DF BD141318
InstallProtocolInterface: 13AC6DD1-73D0-11D4-B06B-00AA00BD6DE7 BD1414D8
InstallProtocolInterface: 2755590C-6F3C-42FA-9EA4-A3BA543CDA25 BD148018
InstallProtocolInterface: AAEACCFD-F27B-4C17-B610-75CA1F2DFB52 BD141658
Loading driver 79CA4208-BBA1-4A9A-8456-E1E66A81484E
InstallProtocolInterface: 5B1B31A1-9562-11D2-8E3F-00A0C969723B BD148B00
Loading driver at 0x000BD773000 EntryPoint=0x000BD7732AF Legacy8259.efi
InstallProtocolInterface: BC62157E-3E33-4FEC-9920-2D3B36D750DF BD1481D8
InstallProtocolInterface: 38321DBA-4FE0-4E17-8AEC-413055EAEDC1 BD7762C0
Loading driver A19B1FE7-C1BC-49F8-875F-54A5D542443F
InstallProtocolInterface: 5B1B31A1-9562-11D2-8E3F-00A0C969723B BD148300
Loading driver at 0x000BD76D000 EntryPoint=0x000BD76D2AF CpuIo2Dxe.efi
InstallProtocolInterface: BC62157E-3E33-4FEC-9920-2D3B36D750DF BD148558
InstallProtocolInterface: AD61F191-AE5F-4C0E-B9FA-E869D288C64F BD770600
Loading driver 1A1E4886-9517-440E-9FDE-3BE44CEE2136
InstallProtocolInterface: 5B1B31A1-9562-11D2-8E3F-00A0C969723B BD1409C0
Loading driver at 0x000BD75A000 EntryPoint=0x000BD75A2AF CpuDxe.efi
InstallProtocolInterface: BC62157E-3E33-4FEC-9920-2D3B36D750DF BD140C18
InstallProtocolInterface: 26BACCB1-6F42-11D4-BCE7-0080C73C8881 BD7674C0
  Flushing GCD
  Flushing GCD
  Flushing GCD
  Flushing GCD
  Flushing GCD
  Flushing GCD
  Flushing GCD
  Flushing GCD
  Flushing GCD
  Flushing GCD
  Flushing GCD
  Flushing GCD
  Flushing GCD
  Flushing GCD
  Flushing GCD
  Flushing GCD
  Flushing GCD
  Flushing GCD
  Flushing GCD
!!!! X64 Exception Type - 0000000000000000     CPU Apic ID - 00000004 !!!!
RIP  - 00000000BD75E49D, CS  - 0000000000000028, RFLAGS - 0000000000010246
RAX  - 00000000000F4240, RCX - 0000000000000000, RDX - 0000000000000000
RBX  - 0000000000810248, RSP - 00000000BD870B50, RBP - 00000000BD870B80
RSI  - 0000000000000000, RDI - 0000000000000001
R8   - 000000000000000B, R9  - 0000000000000000, R10 - 0000000000000000
R11  - 0000000000000380, R12 - 0000000000000000, R13 - 0000000000000000
R14  - 0000000000000000, R15 - 0000000000000000
DS   - 0000000000000008, ES  - 0000000000000008, FS  - 0000000000000008
GS   - 0000000000000008, SS  - 0000000000000008
CR0  - 0000000080000023, CR2 - 0000000000000000, CR3 - 00000000BD80F000
CR4  - 0000000000000668, CR8 - 0000000000000000
DR0  - 0000000000000000, DR1 - 0000000000000000, DR2 - 0000000000000000
DR3  - 0000000000000000, DR6 - 00000000FFFF0FF0, DR7 - 0000000000000400
GDTR - 00000000BD7F4F18 000000000000003F, LDTR - 0000000000000000
IDTR - 00000000BD13D018 0000000000000FFF,   TR - 0000000000000068
FXSAVE_STATE - 00000000BD8707B0
!!!! Find PE image /home/yuichi_xy/lab/tinyvisor/tinyvisor-sf/uefi/Build/OvmfX64/DEBUG_GCC49/X64/UefiCpuPkg/CpuDxe/CpuDxe/DEBUG/CpuDxe.dll (ImageBase=00000000BD75A000, EntryPoint=00000000BD75A2AF) !!!!
2015-07-04 23:26 更新者: yuichi_xy
コメント

yuichi_xy への返信

yuichi_xy への返信

ビルドして、VM1でuefiを起動してみたところ、ASSERTに失敗しました。

r332 で ASSERT を削除しました。 先に進みましたが、0 除算例外が発生したようです。　　

r333 で UEFI: apic timer の init count を fffffff に設定するようにしたところ、例外が発生しなくなりました。

先に進みましたが、XHCI の初期化のメッセージが出力されたあと、ストールしました。 

PlatformBdsInit
Registered NotifyDevPath Event
PlatformBdsPolicyBehavior
InstallProtocolInterface: 09576E91-6D3F-11D2-8E39-00A0C969723B BCCF3758
InstallProtocolInterface: 4CF5B200-68B8-4CA5-9EEC-B23E3F50029A BCCF39A8
PciExp - 1 (B-0, D-1, F-0)
InstallProtocolInterface: 09576E91-6D3F-11D2-8E39-00A0C969723B BCCF34D8
InstallProtocolInterface: 4CF5B200-68B8-4CA5-9EEC-B23E3F50029A BCCFDCA8
PciExp - 1 (B-1, D-0, F-0)
InstallProtocolInterface: 09576E91-6D3F-11D2-8E39-00A0C969723B BCCF3F58
InstallProtocolInterface: 4CF5B200-68B8-4CA5-9EEC-B23E3F50029A BCCFD428
InstallProtocolInterface: 09576E91-6D3F-11D2-8E39-00A0C969723B BCCF3D58
InstallProtocolInterface: 4CF5B200-68B8-4CA5-9EEC-B23E3F50029A BCCFD768
PciExp - 1 (B-0, D-1C, F-0)
InstallProtocolInterface: 09576E91-6D3F-11D2-8E39-00A0C969723B BCCFAF18
InstallProtocolInterface: 4CF5B200-68B8-4CA5-9EEC-B23E3F50029A BCCFA028
PciExp - 1 (B-2, D-0, F-0)
InstallProtocolInterface: 09576E91-6D3F-11D2-8E39-00A0C969723B BCCFAF98
InstallProtocolInterface: 4CF5B200-68B8-4CA5-9EEC-B23E3F50029A BCCFABE8
PciExp - 1 (B-0, D-1C, F-5)
InstallProtocolInterface: 09576E91-6D3F-11D2-8E39-00A0C969723B BCCF3558
InstallProtocolInterface: 4CF5B200-68B8-4CA5-9EEC-B23E3F50029A BCCFA368
PciExp - 1 (B-5, D-0, F-0)
Found Mass Storage device: PciRoot(0x0)/Pci(0x1C,0x0)/Pci(0x0,0x0)
PlatformBdsGetDriverOption
Boot Mode:0
Found PCI VGA device
PlatformBdsDiagnostics
PlatformBdsConnectSequence
XhcCreateUsb3Hc: Capability length 0x80
XhcCreateUsb3Hc: HcSParams1 0x8000820
XhcCreateUsb3Hc: HcSParams2 0x84000054
XhcCreateUsb3Hc: HcCParams 0x20007181
XhcCreateUsb3Hc: DBOff 0x3000
XhcCreateUsb3Hc: RTSOff 0x2000
XhcCreateUsb3Hc: UsbLegSupOffset 0x330
XhcCreateUsb3Hc: DebugCapSupOffset 0xFFFFFFFF
XhcSetBiosOwnership: called to set BIOS ownership
XhcResetHC!
XhcInitSched:DCBAA=0xBCCCD000
XhcInitSched:XHC_CRCR=0xBCCCD140
XhcInitSched:XHC_EVENTRING=0xBCCCE140
2016-01-01 20:17 更新者: yuichi_xy
コメント

最新の VMM と UEFI の組み合わせでは、ストールせずに先に進みました。

ホストブリッジの ID が 0 なので ASSERT に失敗しました。

ホストブリッジをゲストに見せていないことが影響しているようです。 

Boot Mode:0
Found PCI VGA device
PlatformBdsDiagnostics
PlatformBdsConnectSequence
XhcCreateUsb3Hc: Capability length 0x80
XhcCreateUsb3Hc: HcSParams1 0x8000820
XhcCreateUsb3Hc: HcSParams2 0x84000054
XhcCreateUsb3Hc: HcCParams 0x20007181
XhcCreateUsb3Hc: DBOff 0x3000
XhcCreateUsb3Hc: RTSOff 0x2000
XhcCreateUsb3Hc: UsbLegSupOffset 0x330
XhcCreateUsb3Hc: DebugCapSupOffset 0xFFFFFFFF
XhcSetBiosOwnership: called to set BIOS ownership
XhcResetHC!
XhcInitSched:DCBAA=0xBCCCD000
XhcInitSched:XHC_CRCR=0xBCCCD140
XhcInitSched:XHC_EVENTRING=0xBCCCE140
InstallProtocolInterface: 3E745226-9818-45B6-A2AC-D7CD0E8BA2BC BCCDD038
XhcDriverBindingStart: XHCI started for controller @ BCCF5F98
XhcResetHC!
XhcInitSched:DCBAA=0xBCCCD000
XhcInitSched:XHC_CRCR=0xBCCCD140
XhcInitSched:XHC_EVENTRING=0xBCCCE140
XhcReset: status Success
XhcGetState: current state 0
XhcSetState: status Success
InstallProtocolInterface: 240612B7-A063-11D4-9A3A-0090273FC14D BCCBB1E0
XhcGetCapability: 8 ports, 64 bit 1
UsbRootHubInit: root hub BCCBAA58 - max speed 3, 8 ports
UsbBusStart: usb bus started on BCCF5F98, root hub BCCBAA58
PciAcpiInitialization: Unknown Host Bridge Device ID: 0x0000
ASSERT /home/yuichi_xy/lab/tinyvisor/tinyvisor-hg/uefi/OvmfPkg/Library/PlatformBdsLib/BdsPlatform.c(889): ((BOOLEAN)(0==1))
2016-01-01 20:28 更新者: yuichi_xy
コメント

ホストブリッジのデバイスIDが0の場合は、ホストブリッジの設定や、各デバイスのPCI_INTERRUPT_LINEレジスタの設定を飛ばすようにしたところ、先に進みました。

EFIシェルを起動した所で、止まっているように見えます。 

UsbRootHubInit: root hub BCCBAA58 - max speed 3, 8 ports
UsbBusStart: usb bus started on BCCF5F98, root hub BCCBAA58
Select Item: 0x8
Select Item: 0x17
qemu -kernel was not used.
BdsLibConnectAll
Select Item: 0x19
Select Item: 0xE
Initialize variable error flag (FF)
Memory  Previous  Current    Next
 Type    Pages     Pages     Pages
======  ========  ========  ========
  0A    00000004  00000001  00000004
  09    00000008  00000002  00000008
  00    00000004  00000000  00000004
  06    00000024  00000041  00000051
  05    00000030  0000004D  00000060
  03    00000180  00000430  0000053C
  04    00000F00  00000AF2  00000F00
Booting EFI Internal Shell
InstallProtocolInterface: 5B1B31A1-9562-11D2-8E3F-00A0C969723B BCCB9700
Loading driver at 0x000BC301000 EntryPoint=0x000BC301260 Shell.efi
InstallProtocolInterface: BC62157E-3E33-4FEC-9920-2D3B36D750DF BCB7C018
InstallProtocolInterface: 387477C2-69C7-11D2-8E39-00A0C969723B BCB79220
InstallProtocolInterface: 752F3136-4E16-4FDC-A22A-E5F46812F4CA BCB79458
InstallProtocolInterface: 6302D008-7F9B-4F30-87AC-60C9FEF5DA4E BC3B2700
2016-01-01 23:27 更新者: yuichi_xy
コメント

EFIシェルを起動した所で、止まっているように見えます。

EFIシェルが起動したことから、UEFIがSATAディスクを認識していない可能性に気づきました。

そこで、UEFIを最新のバージョンにアップデートしてみたところ、SATAディスクを認識するようになりました。

ただ、Memory Poolの解放処理でアサートに失敗しています。

https://osdn.jp/projects/tinyvisor/scm/hg/tinyvisor-uefi/commits/c85a06e7b0de5a77d68a60a5372999de02eac31a 

Prepare to Free Pool
 BlockSize : 512
 LastBlock : F9FFF
 BlockSize : 512
 LastBlock : 1D066FFF
 BlockSize : 512
 LastBlock : 7DD
 BlockSize : 512
 LastBlock : F9FFF
 BlockSize : 512
 LastBlock : 1D066FFF
 BlockSize : 512
 LastBlock : 7DD
Buffer: EFI Hard Drive
EmuVariablesUpdatedCallback
Saved NV Variables to NvVars file
EmuVariablesUpdatedCallback
Saved NV Variables to NvVars file
EmuVariablesUpdatedCallback
Saved NV Variables to NvVars file
EmuVariablesUpdatedCallback
Saved NV Variables to NvVars file
Select Item: 0x19
Select Item: 0xE
Memory  Previous  Current    Next
 Type    Pages     Pages     Pages
======  ========  ========  ========
  0A    00000004  00000000  00000004
  09    00000008  00000002  00000008
  00    00000004  00000001  00000004
  06    00000024  00000055  0000006A
  05    00000030  00000063  0000007B
  03    00000180  00000459  0000056F
  04    00000F00  000010D5  0000150A
EmuVariablesUpdatedCallback
Saved NV Variables to NvVars file
Booting EFI Hard Drive
 BlockSize : 512
 LastBlock : 1D1C596F
 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 : 800
 End LBA : 647FF
 Partition size: 64000
 Start : 100000 End : C8FFE00
 Index : 1
 Start LBA : 64800
 End LBA : 15E7FF
 Partition size: FA000
 Start : C900000 End : 2BCFFE00
 Index : 2
 Start LBA : 15E800
 End LBA : 1D1C57FF
 Partition size: 1D067000
 Start : 2BD00000 End : 3A38AFFE00
 Index : 3
 Start LBA : 22
 End LBA : 7FF
 Partition size: 7DE
 Start : 4400 End : FFE00
Prepare to Free Pool
 BlockSize : 512
 LastBlock : F9FFF
 BlockSize : 512
 LastBlock : 1D066FFF
 BlockSize : 512
 LastBlock : 7DD
InstallProtocolInterface: 5B1B31A1-9562-11D2-8E3F-00A0C969723B BCB26040
Loading driver at 0x000BBE38000 EntryPoint=0x000BBE54000
InstallProtocolInterface: BC62157E-3E33-4FEC-9920-2D3B36D750DF BCB25C98
InstallProtocolInterface: 605DAB50-E046-4300-ABB6-3DD810DD8B23 BBF22C90
ASSERT [DxeCore] /home/yuichi_xy/lab/tinyvisor/tinyvisor-hg/uefi/MdeModulePkg/Core/Dxe/Mem/Pool.c(550): Tail->Signature == ((('p') | ('t' << 8)) | ((('a') | ('l' << 8)) << 16))
2016-01-01 23:28 更新者: yuichi_xy
  • 詳細が更新されました
2016-01-02 21:30 更新者: yuichi_xy
コメント

yuichi_xy への返信

数分待ったところ、先に進みました。

上記のUEFIの初期化に時間がかかる件、デバッグメッセージを入れて、時間がかかる部分を調べてみました。

以下の流れで呼ばれるDecompressMemFvsに時間がかかっているようです。

SecCoreStartupWithStack -> SecStartupPhase2 -> FindAndReportEntryPoints -> FindPeiCoreImageBase -> DecompressMemFvs

2016-09-19 16:55 更新者: yuichi_xy
コメント

0000000-ffffffff の物理メモリを VM1 に割り当てて UEFI を起動したところ、panic しました。 

Install PPI: 7408D748-FC8C-4EE6-9288-C4BEC092A410
PublishPeiMemory: mPhysMemAddressWidth=36 PeiMemoryCap=65800 KB
PeiInstallPeiMemory MemoryBegin 0xFFFFFFFFFBFBE000, MemoryLength 0x4042000
QemuInitializeRam called
Allocated Memory unaligned: Address = 0xFFFFFFFFFFFD0000, Pages = 0x30, Type = 6
After aligning to 0x10000 bytes: Address = 0xFFFFFFFFFFFD0000, Pages = 0x20
Updated aligned-mem HOB with BaseAddress = FFFFFFFFFFFD0000, Length = 20000, MemoryType = 6
Created after-mem HOB with BaseAddress = FFFFFFFFFFFF0000, Length = 10000, MemoryType = 7
Reserved variable store memory: 0xFFFFFFFFFFFD0000; size: 128kb
Platform PEI Firmware Volume Initialization
Install PPI: 49EDB1C1-BF21-4761-BB12-EB0031AABB39
Notify: PPI Guid: 49EDB1C1-BF21-4761-BB12-EB0031AABB39, Peim notify entry point: 82490B
The 1th FV start address is 0x00000900000, size is 0x00900000, handle is 0x900000
Select Item: 0x19
Select Item: 0x19
MiscInitialization: Unknown Host Bridge Device ID: 0xFFFF
Temp Stack : BaseAddress=0x814000 Length=0x4000
Temp Heap  : BaseAddress=0x810000 Length=0x1920
Total temporary memory:    32768 bytes.
  temporary memory stack ever used: 16384 bytes.
  temporary memory heap used:       6432 bytes.
Old Stack size 16384, New stack size 131072
Stack Hob: BaseAddress=0xFFFFFFFFFBFBE000 Length=0x20000
Heap Offset = 0xFFFFFFFFFB7CE000 Stack Offset = 0xFFFFFFFFFB7C6000
TemporaryRamMigration(0x810000, 0xFFFFFFFFFBFDA000, 0x8000)
Fatal error: handler not implemented.
2=0x2 (Triple fault)
panic(CPU3,apic id:0x4): Fatal error: handler not implemented.
CR0 80000039    CR2 FFFFFFFFFBFDE000    CR3 A0920000    CR4 000026A8
RFLAGS 00000012  GDTR 4091C408+0000FFFF  IDTR 401F15C0+0000FFFF
stackdump: 3 4091C760 40160650 401363DA 401363F8 0 0 0 40160650 3 4091C760 40123C72 2 4012429D 0 0 0 8 4090FE68 4090FE08 A 1 1 0 40124780 0 2 2 2 4015B438 0 401314BF
backtrace: 401363DA 401363F8 40123C72 4012429D 40124780 401314BF 40131843 4015075E 40150724 4015077A 40151012 40145966 4011CE0C 401163F3
Guest state and registers of cpu 3 (apic id:0x4) ------------
RAX FFFFFFFFFBFDE000    RCX 00000800    RDX 00810000    RBX 00810248
RSP 00817388    RBP 008173C0    RSI 00810000    RDI FFFFFFFFFBFDE000
R8  00000000    R9  00813FFF    R10 00900000    R11 000000AA
R12 00000000    R13 00000000    R14 00000000    R15 00000000
CR0 C0000023    CR2 FFFFFFFFFBFDE000    CR3 00800000    CR4 00000660
ACR   ES 0000C093 CS 0000A09B SS 0000C093 DS 0000C093 FS 0000C093 GS 0000C093
LIMIT ES (2^64-1) CS (2^64-1) SS (2^64-1) DS (2^64-1) FS (2^64-1) GS (2^64-1)
BASE  ES 00000000 CS 00000000 SS 00000000 DS 00000000 FS 00000000 GS 00000000
SEL   ES 00000008 CS 00000018 SS 00000008 DS 00000008 FS 00000008 GS 00000008
RIP FFFCE3FE  RFLAGS 00010006  GDTR FFFFFF80+0000001F  IDTR 00817D58+0000021F
EFER 00000500
Exit reason: 2=0x2 (Triple fault)
Exit qualification 00000000  VM exit interrupt information 00000000
VM entry interruption-information 00000000  errcode 00000000  instlen 00000000
VM exit errcode 00000000  VMCS IDTR 00817D58+0000021F   VMCS RFLAGS 00010006
re=0 pg=1 sw:en=0x0 es=0x0 cs=0x0 ss=0x0 ds=0x0 fs=0x0 gs=0x0
------------------------------------------------
panic(CPU3,apic id:0x4): Fatal error: handler not implemented.
s:shell r:reboot ?
2016-09-19 20:22 更新者: yuichi_xy
コメント

yuichi_xy への返信

0000000-ffffffff の物理メモリを VM1 に割り当てて UEFI を起動したところ、panic しました。

VMM が UEFI BIOS に返すメモリサイズが間違えていました。

70d496d で修正しました。

0000000-ffffffff の物理メモリを VM1 に割り当てた場合も、同じ所まで進みました。 

Booting EFI Hard Drive
 BlockSize : 512 
 LastBlock : 1D1C596F 
 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 : 800
 End LBA : 647FF
 Partition size: 64000
 Start : 100000 End : C8FFE00
 Index : 1
 Start LBA : 64800
 End LBA : 15E7FF
 Partition size: FA000
 Start : C900000 End : 2BCFFE00
 Index : 2
 Start LBA : 15E800
 End LBA : 1D1C57FF
 Partition size: 1D067000
 Start : 2BD00000 End : 3A38AFFE00
 Index : 3
 Start LBA : 22
 End LBA : 7FF
 Partition size: 7DE
 Start : 4400 End : FFE00
Prepare to Free Pool
 BlockSize : 512 
 LastBlock : F9FFF 
 BlockSize : 512 
 LastBlock : 1D066FFF 
 BlockSize : 512 
 LastBlock : 7DD 
InstallProtocolInterface: 5B1B31A1-9562-11D2-8E3F-00A0C969723B 2876E100
Loading driver at 0x00027A48000 EntryPoint=0x00027A64000 
InstallProtocolInterface: BC62157E-3E33-4FEC-9920-2D3B36D750DF 2876F258
InstallProtocolInterface: 605DAB50-E046-4300-ABB6-3DD810DD8B23 27B32C90
ASSERT [DxeCore] /home/yuichi_xy/lab/tinyvisor/tinyvisor-hg/uefi/MdeModulePkg/Core/Dxe/Mem/Pool.c(550): Tail->Signature == ((('p') | ('t' << 8)) | ((('a') | ('l' << 8)) << 16))

添付ファイルリスト

  • qemu-stdio.txt(53KB)
    • EDK r15214のOVMFを「-D DEBUG_ON_SERIAL_PORT」オプション付きでビルドし、qemuで実行した時のコンソールログ (qemu-system-x86_64 -L . -hda fat:hba-contents -serial stdio)

編集

ログインしていません。ログインしていない状態では、コメントに記載者の記録が残りません。 » ログインする