Il 06/12/2013 14:46, Yao, Jiewen ha scritto: > Hi Paolo > I am a little confused here. You said "Still, indeed it's OVMF's fault." and > "Still an EDK2 problem." ??????
Sorry for the confusion. I wrote OVMF/EDK2 interchangeably, just to say "not KVM". > EDKII BIOS should always create 1:1 mapping virtual-physical address. But I > am not clear about OS waking vector. > For "EPT_VIOLATION rip 0xffffffff81000110.", is that happen in EDKII BIOS or > in OS waking vector? That's after the OS waking vector is invoked. But that memory was corrupted by EDKII/OVMF before the OS waking vector is invoked. Paolo > All in all, I have interesting to know one thing at first: > Is OVMF crash in BIOS before jump to OS waking vector? Or is OVMF crash > inside OS waking vector? > > Thank you ------------------------------------------------------------------------------ Sponsored by Intel(R) XDK Develop, test and display web and hybrid apps with a single code base. Download it for free now! http://pubads.g.doubleclick.net/gampad/clk?id=111408631&iu=/4140/ostg.clktrk _______________________________________________ edk2-devel mailing list edk2-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/edk2-devel
