Hide Forgot
Hello, for Satellite 6 bootdisk support, we would like be able to generate bootdisks with ixpe.efi chainbooted from Grub2. This allows specifying script location via arguments. For BIOS we use: default ipxe label ipxe kernel /ipxe initrd /script For EFI we would like to do the same, but this does not work: set default=0 set timeout=1 menuentry "Chainload iPXE - this does not work" { linuxefi /ipxe.efi initrdefi /script.ipxe } menuentry "Chainload iPXE - this does not work either" { search --no-floppy --set=root -f /ipxe.efi chainloader /ipxe.efi chain /script.ipxe } Arguments are ignored by the EFI firmware at the moment. Can you guys estimate how feasible is implementing such a feature, thanks. If that turns out to be hard, we could compile our own ipxe.efi with embedded script that chainloads another one from the media.
iPXE mailing list and forum references: http://lists.ipxe.org/pipermail/ipxe-devel/2016-December/005279.html http://forum.ipxe.org/showthread.php?tid=8244
Created attachment 1229966 [details] Proof-of-concept patch Lukas, can you please try the attached prototype patch? I can pass EFI command line arguments from iPXE to iPXE, e.g. iPXE> chain ipxe.efi echo Hello world! but I haven't tried it with grub.
A patch has just been posted by Christian Nilsson. Should be identical in functionality modulo some extra command line cruft stripping. http://lists.ipxe.org/pipermail/ipxe-devel/2016-December/005306.html
Thanks, I will test the patch from Christian then.
Unfortunately, I am not able to boot that from Grub2, it looks like there is no way of providing entry options. I am afraid the only solution is to build a regular UEFI boot image (FAT image with iPXE EFI ROM) with embedded "chain script.ipxe" command. The thing I was trying to avoid (to carry own build of ipxe with embedded script in Satellite repositories).
Two more replies to Christian Nilsson's patch (pipermail doesn't show them, presumably because the original email was sent last year): http://lists.ipxe.org/pipermail/ipxe-devel/2017-May/005617.html
The patch was not accepted upstream. Closing the BZ.