Can I please see an example of how you are chaining these together. I have yet
to get iPXE to be able to chainload an EFI image for CentOS or any other OS for
that matter
- Original Message -
| Out of curiosity, did it work without issue if you didn't have
| multiple efi executables in
Yes it does work with single efi image.
Thanks and Regards,
Niket Kandya,
Graduate Student CS,
Columbia University, NY
On Sun, Aug 25, 2013 at 4:13 PM, Jarrod Johnson
wrote:
> Out of curiosity, did it work without issue if you didn't have multiple
> efi executables in play?
>
> I've not had a r
Out of curiosity, did it work without issue if you didn't have multiple efi
executables in play?
I've not had a reason to try that use case myself, I just chain esxboot.efi
(modified for iPXE DL protocol) or elilo (also modified for IPXE DL
protocol support). I also had shell working with the sim
Hi,
I was wondering if any of you guys ran into/worked around this problem.
Following my previous query about UEFI image execution,
I enabled snponly.efi image execution, partly from Jarrod's patch and
partly my own.
My addition there was:
If you try to run 2 efi images 1 after the other, the se
If trying to use snponly.eif, the following two patches will help:
https://git.ipxe.org/vendor/xcat/ipxe.git/commitdiff/73d1ff05b058a2507fda0119825715fa2253d722
and
https://git.ipxe.org/vendor/xcat/ipxe.git/commitdiff/f411dcea1ce12ddcdfafa3fa2a89566a16f86bce
I still have been meaning to make snpon
Hi,
I was trying to chain boot an efi image.
My setup is all like traditional PXE with snponly.efi as the PXE file.
While chainloading an EFI file, I always fail at last_opened_snpdev() as it
internally tries to find a PCI SNP device which it does not find. Is the
problem here itself ??
Or what
6 matches
Mail list logo
