On Wed, Jul 31, 2013 at 10:54:31PM +0200, Borislav Petkov wrote:
efi: mem08: type=7, attr=0xf, range=[0x4000-0x7c00)
(960MB)
efi: mem09: type=4, attr=0xf, range=[0x7c00-0x7c02)
(0MB)
efi: mem10: type=7, attr=0xf,
On Wed, Jul 31, 2013 at 11:51:30PM +0200, Borislav Petkov wrote:
But the problem is, something messes up the upper boundary of the region
and it is an EFI_BOOT_SERVICES_DATA region which we need for the runtime
services mapping and if we can't map it properly, we're probably going
to miss
On Wed, 2013-07-31 at 22:54 +0200, Borislav Petkov wrote:
so I'm seeing this funny thing where an EFI region changes when we enter
efi_enter_virtual_mode when booting with edk2 on kvm. Here's the diff:
Perhaps the edk2-de...@lists.sourceforge.net list should be in Cc?
--
dwmw2
smime.p7s
