> Is there a fix for this problem to let me proceed with normal foreman build?
> I think my other options are going to mean forgoing foreman's un-attended
> install.
Try updating to latest iPXE:
Then regenerate bootdisk and try again. Depending on your distribution,
iPXE firmware can be pretty dated.
If it does not work, use Full host image as a workaround, it's SYSLINUX
based (no PXE involved).
Lukas thank you for taking time to answer my question.
I went ahead and updated ipxe.lkrn as suggested.
Still having same issue with the host.iso file but full host.iso got me
further till it failed with an unrelated error.
(Internal disk was not enumerated as sda, whereas ,I guess, OS template was
expecting it to be there.)
As I watch the isolinux boot the initrd.img and vmlinuz, the names of these
two files are somewhat mangled.
For example /var/lib/tftpboot/boot directory contains
"RedHat-6.7-x86_64-initrd.img" and "RedHat-6.7-x86_64-vmlinuz" files, yet,
isolinux prints below on the console.
Is there a way to take a look in to what isolinux parameters are included
in the iso image?
In one occasion while booting from boot-iso, isolinux program complained
that it can not locate the programs initrd/vmlinuz.
I wanted to verify it is searching for correct file names but I don't know
how to go about verifying it.
