ipxe uefi x64 WimBoot [answered]

[Fimlore]

(2016-03-15 16:08)mcb30 Wrote:  

(2016-03-15 15:22)Fimlore Wrote:  

(2016-03-14 18:59)mcb30 Wrote:  

(2016-03-14 16:22)Fimlore Wrote:  The WIM is definitely a x64 version, so that can't be the issue; leaves me only with the BCD and sdi files, are those platform dependent?

Could you extract the file \Windows\Boot\EFI\bootmgfw.efi from your .wim image and post a copy of it somewhere?

I've extracted and uploaded it to mega:
https://mega.nz/#!9YETFDSD!xR-9WgajnmMbw...U5dc7waq_I

Thanks. That file is definitely a 32-bit UEFI executable:

Code:

[mcb30@squirrel ~]$ objdump -x ~/tmp/bootmgfw.efi
/home/mcb30/tmp/bootmgfw.efi:     file format pei-i386
/home/mcb30/tmp/bootmgfw.efi
architecture: i386, flags 0x0000012f:
HAS_RELOC, EXEC_P, HAS_LINENO, HAS_DEBUG, HAS_LOCALS, D_PAGED
start address 0x10013b80

Characteristics 0x2102
        executable
        32 bit words
        DLL

Time/Date               Fri Oct 30 02:09:32 2015
Magic                   010b    (PE32)

For reference, here's the equivalent for a 64-bit UEFI executable:

Code:

/vault/images/efi/x64/Shell.efi:     file format pei-x86-64
/vault/images/efi/x64/Shell.efi
architecture: i386:x86-64, flags 0x0000010b:
HAS_RELOC, EXEC_P, HAS_DEBUG, D_PAGED
start address 0x0000000000000240

Characteristics 0x2e
        executable
        line numbers stripped
        symbols stripped
        large address aware

Time/Date               Thu Jan  1 01:00:00 1970
Magic                   020b    (PE32+)

A 32-bit UEFI executable cannot be loaded on a 64-bit UEFI system. This fully explains the error that you were seeing.

The question then becomes why would there be a 32-bit UEFI bootmgfw.efi in your apparently 64-bit WIM? I wonder if your toolchain is somehow including both 32-bit and 64-bit versions of bootmgfw.efi, and wimboot is erroneously picking up the 32-bit version. Could you post a full list of all *.efi files present within the problematic WIM?

Thanks,

Michael

... I retraced my steps to find out where this went wrong. And i've found out where it went wrong. I extracted the x64 file from my WDS server and copied it over to my linux server.. This is where i made the big mistake.. instead of the x64 image, I took the export from the x86 folder.

I was able to trace this back because my export folder didn't contain files in the x64 folder but did in the x86.

That explains why my other images were able to boot.


Thank you for your support Michael.

Btw, what tool do you use to read the EFI files?