ski-efi fails to load setupldr.efi

[Vort]

When setupldr.efi file from Windows XP 64-Bit Edition Version 2003 (Itanium) is launched with screen bski -noconsole ski-efi setupldr.efi command, only loading setupldr.efi... message appears on screen, suggesting hang inside of ski-efi.
Such hang happens because of incorrect parameter passed into memset function, on this line:

ski/ski-efi/bootloader.c

Lines 231 to 232 in 6984f89

	memset((char *)__pa(sec_hdr->virtual_address + image_base) + sec_hdr->raw_data_size, 0,
	sec_hdr->virtual_size - sec_hdr->raw_data_size);

However, with such problem fixed by adding if (sec_hdr->virtual_size > sec_hdr->raw_data_size) code before this line, loading still fails, this time with Unknown relocation type message.
There may be more problems with loading of this file, but at least these two should be easy to fix.

[trofi]

Note that ski currently can't boot unmodified kernels: it does not support ACPI namespace to discover devices, does not support PCI to discover disks or even serial (and it's discovery by kernel) to print anything today. It still relies on ski-specific calls to read kernel itself from disk and print debug info to the console.

For example ski replies on the guest to call pal_emulator_static to implement basic PAL calls to fetch data about the systems.

It might be feasible to load the external EFI programs into memory, but they will likely fail miserably.

[Vort]

It might be feasible to load the external EFI programs into memory, but they will likely fail miserably.

1. It is good to have properly working EFI loader even if loaded program won't be able to do anything useful;
2. There is a chance of this program printing something via EFI calls or by directly accessing video RAM;
3. Instead of randomly implementing different stuff, it is better to focus on features which absence prevent loaded program from doing its job. In other words, it is important to know at which exact point setupldr.efi will fail in case of properly working ski-efi.

[Vort]

Here is more information:

1. Unknown relocation type is actually 9 (IMAGE_REL_BASED_IA64_IMM64). It is needed to relocate offsets inside of movl instructions (with some bit manipulation magic);
2. Instead of adding just image_base during relocations, diff value of image_base - opt_header->image_base should be added instead;
3. To prevent relocation algorithm from reading empty data if (fb.block_size == 0) break; check may be added.

With these 3 fixes implemented correctly, setupldr.efi should be able to print SuMain: HandleProtocol failed messages to the console.

[Vincent392]

I've had this on my phone for a while

I'll upload it now so you can all try to get it to boot, because bar the wallpaper, it's practically just Windows XP Version 2003's Pre-installation Environment

Edit: https://archive.org/download/cursed_xpwinpes/IA-64/en_windows_glass_professional_ia64_dvd_vl_m3.iso