(2015-12-28 15:53)silver310 Wrote:  Yeah I just read about the efi stub issue.
I tried doing that with bootx64.efi but couldn't figure out how to automate it to boot vmlinuz immediately.

How hard would it be to compile a kernel for rhel 6 with efi stub enabled?

(2015-12-28 16:24)silver310 Wrote:  OK I get it. Any advice on how to pass a conf file to grub so it'll boot automatically?
I tried '' chain ${http-images} /rhel67/EFI/BOOT/BOOTX64.efi ${http-images} /rhel67/EFI/BOOT/BOOTX64.conf''

But I just get the grub shell.

(2015-12-28 21:53)MultimediaMan Wrote:  

(2015-12-28 16:24)silver310 Wrote:  OK I get it. Any advice on how to pass a conf file to grub so it'll boot automatically?
I tried '' chain ${http-images} /rhel67/EFI/BOOT/BOOTX64.efi ${http-images} /rhel67/EFI/BOOT/BOOTX64.conf''

But I just get the grub shell.

https://access.redhat.com/documentation/en-US/Red_Hat_Enterprise_Linux/6/html/Installation_Guide/s1-netboot-pxe-config-efi.html

It's a little messy with the 6.x kernels...

(2015-12-29 09:55)silver310 Wrote:  

(2015-12-28 21:53)MultimediaMan Wrote:  

(2015-12-28 16:24)silver310 Wrote:  OK I get it. Any advice on how to pass a conf file to grub so it'll boot automatically?
I tried '' chain ${http-images} /rhel67/EFI/BOOT/BOOTX64.efi ${http-images} /rhel67/EFI/BOOT/BOOTX64.conf''

But I just get the grub shell.

https://access.redhat.com/documentation/en-US/Red_Hat_Enterprise_Linux/6/html/Installation_Guide/s1-netboot-pxe-config-efi.html

It's a little messy with the 6.x kernels...

OK I officially give up, I've tried EVERYTHING!

set 210:string ${tftp-server}
set 209:string bootx64.efi
chain ${tftp-server}/bootx64.efi

set 210:string ${tftp-server}
set 209:string efidefault
chain ${tftp-server}/bootx64.efi

set 210:string ${tftp-server}
set 209:string /pxelinux.cfg/efidefault
chain ${tftp-server}/bootx64.efi

set netX.dhcp/filename:string bootx64.efi || goto failed
chain ${tftp-server}/bootx64.efi || goto failed

set netX.dhcp/filename:string bootx64.efi || goto failed
set 210:string ${tftp-server}
set 209:string efidefault
chain ${tftp-server}/bootx64.efi || goto failed

And about 100 more variations of those, and also 10 different grub versions, on many different locations on the server (at root of tftp, http, in folders in tftp, etc...), I've been doing this for the last 4 hours.
This is just ridicules, i've tried exactly what people posted that have worked, and what was written in that red-hat guide, every single time i get the grub shell.
Can i somehow tell when grub is looking for the config file? (if it's looking at all)

Also when trying to use "set netX.dhcp/xxxxx" manu times i get an invalid argument error even thou i have those exact same lines in the same file working without a problem.

(2015-12-30 13:43)silver310 Wrote:  could not boot: Error 0x7f048281 (http://ipxe.org/7f048281)"

What am I doing wrong?

(2015-12-30 13:47)NiKiZe Wrote:  

(2015-12-30 13:43)silver310 Wrote:  could not boot: Error 0x7f048281 (http://ipxe.org/7f048281)"

What am I doing wrong?

It says that the efi can't be started, is it an efi executable in the correct format? (32bit vs 64bit etc)

(2015-12-31 11:43)silver310 Wrote:  SOLVED, finally.
So after 3 days I finally found a solution/workaround, I'll explain everything so other people might use this.

Basically it all comes down to GRUB2, I created a standalone bootx64.efi image with a single menu entry for the desired installation image, in this case RHEL 6.7

To make the standalone bootx64.efi:
install required packages

Code:

sudo yum install grub2-efi*

grub2 uses tftp to download images, while i use http with ipxe, so I had to create a new folder structure in my tftp root folder (until now it only had ipxe for legacy and efi)

Code:

cd /tftpboot
mkdir -p grub2-efi/rhel67server/boot/grub/
cd grub2-efi/rhel67server

now the config file:

Code:

vim boot/grub/grub.cfg

set timeout=0

menuentry 'RHEL 6.7 Server' --class os {
     insmod net
     insmod efinet
     insmod tftp
     insmod gzio
     insmod part_gpt
     insmod efi_gop
     insmod efi_uga

     # tftp server
     set net_default_server=192.168.0.1

     # dhcp did not work, no idea why
     # net_bootp

     # assign a static IP
     net_add_addr eno0 efinet0 192.168.0.100

     echo 'Loading vmlinuz ...'
     linux (tftp)/grub2-efi/rhel67server/vmlinuz repo="http://192.168.0.1/images/iso_images/RHEL_6.7_server" root=/dev/null

     echo 'Loading initial ramdisk ...'
     initrd (tftp)/grub2-efi/rhel67server/initrd.img
}

without "root=/dev/null" the installation couldn't find any hard-drives (no idea why)

now, while in /tftpboot/grub2-efi/rhel67server/ run the following command:

Code:

grub2-mkstandalone -d /usr/lib/grub/x86_64-efi/ -O x86_64-efi --fonts="unicode" -o bootx64.efi boot/grub/grub.cfg

you'll see a new file "bootx64.efi", copy to the same directory the kernel and initrd files of the wanted installation.

Finally in ipxe I just chain to the newly created file:

Code:

:rhel67-efi
echo Starting RHEL 6.7 Server x64 (EFI)
chain ${tftp-server}/grub2-efi/rhel67server/bootx64.efi || goto rhel67-efi

And that's it, work perfectly fine, hope this helps someone else, I'm going to add some older versions of RHEL and hopefully it'll work for them as well.
Only issue is that grub uses tftp and it's a lot slower, loading the same files (vmlinuz, initrd.img) via http takes less then a second, while via tftp it can take up to 15-20 seconds, is it possible from grub to use http instead of tftp?

(2017-03-15 12:04)adokania Wrote:  ... is it possible from grub to use http instead of tftp?