Problem:
I am trying to pxe boot debian 9 32 bit image but stuck at a point.
I have change my hw bios setting from legecy to uefi. i have also updated the dhcp server. but when i try to boot my machine, it download the 32 bit efi but does not go beyond and stuck there. It says successfully downloaded NBP program and again try to download the NBP file and does not download grub file.
DHCP Configuration:
# Bootfile Handoff
next-server 192.168.21.1;
option architecture code 93 = unsigned integer 16 ;
if option architecture = 00:06 {
filename "grub2/grubia32.efi";
} elsif option architecture = 00:07 {
filename "grub2/shim.efi";
} elsif option architecture = 00:09 {
filename "grub2/shim.efi";
} else {
filename "pxelinux.0";
}
-
i have used debian 9 32 bit iso and extracted the uefi bootloader “bootia32.efi and rename it as grubia32.efi and pasted in /var/lib/tftp/grub2/”.
-
the /var/lib/tftp/grub2/ folder contain grub.cfg and grub.cfg-01-system-mac-addresss file. i have opened the grub.cfg file and tried to run the command manually. ex- insmod regexp but it says no module found.
-
I am using HP-z440 hardware for this testing.
-
i have selected grub2 uefi as bootloader in foreman UI.
-
Even if i do not add eny pxefile in my dhcpd.conf file, my system still ask for grubia32.efi , even though i have defined other filename for NBP.
-
Am i using the right 32 bit efi bootloader? as far as i have search on internet, i have to create my own bootloader for the same. foreman does not ship 32-bit efi for debian.
Expected outcome:
My system should pxe boot and run the debian kernel.
Foreman and Proxy versions:
HOSTNAME: r8sysdpl01.localdomain
OS: redhat
RELEASE: CentOS Linux release 7.4.1708 (Core)
FOREMAN: 1.15.6
RUBY: ruby 2.0.0p648 (2015-12-16) [x86_64-linux]
PUPPET: 4.10.10
DENIALS: 1921
Foreman and Proxy plugin versions:
DHCP 1.15.6
DNS 1.15.6
TFTP 1.15.6
Other relevant data:
[e.g. logs from Foreman and/or the Proxy, modified templates, commands issued, etc]
(for logs, surround with three back-ticks to get proper formatting, e.g.)
logs
Foreman-proxy log does not show any info or error regarding this.