On Wed, Jul 31, 2013 at 10:55:27PM +0100, David Woodhouse wrote: > 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-devel@xxxxxxxxxxxxxxxxxxxxx list should be in Cc? Good idea and message repeated below. One more thing: I'm using a self-built OVMF with top commit from March: ------------------------------------------------------------------------ r14165 | sfu5 | 2013-03-06 02:42:04 +0100 (Wed, 06 Mar 2013) | 4 lines Fix a bug that IsSignatureFoundInDatabase() incorrectly computes CertCount. --- Hi guys, 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: --- before 2013-07-31 22:20:52.316039492 +0200 +++ after 2013-07-31 22:21:30.960731706 +0200 @@ -9,7 +9,7 @@ efi: mem07: type=2, attr=0xf, range=[0x0 efi: mem08: type=7, attr=0xf, range=[0x0000000040000000-0x000000007c000000) (960MB) efi: mem09: type=4, attr=0xf, range=[0x000000007c000000-0x000000007c020000) (0MB) efi: mem10: type=7, attr=0xf, range=[0x000000007c020000-0x000000007e0ad000) (32MB) -efi: mem11: type=4, attr=0xf, range=[0x000000007e0ad000-0x000000007e0cc000) (0MB) +efi: mem11: type=4, attr=0xf, range=[0x000000007e0ad000-0x000000007e0ad000) (0MB) efi: mem12: type=7, attr=0xf, range=[0x000000007e0cc000-0x000000007e0cd000) (0MB) efi: mem13: type=4, attr=0xf, range=[0x000000007e0cd000-0x000000007e55d000) (4MB) efi: mem14: type=3, attr=0xf, range=[0x000000007e55d000-0x000000007e59c000) (0MB) That second boundary of region mem11 suddenly changes *before* we merge the regions. edk2 bug? Whole dmesg attached. -- Regards/Gruss, Boris. Sent from a fat crate under my desk. Formatting is fine. --
Attachment:
test-x86_64.log.gz
Description: Binary data