I'm rolling my own discovery iso but UEFI support seems to fail during
build.
Building on a CentOS 7.2 host running build-livecd then build-livecd. The
ISO builds OK and is bootable from legacy BIOS but I need to boot UEFI
hosts too.
I have the below in my 20-packages.ks
grub2-efi
efibootmgr
shim
Missing EFI file (/boot/efi/EFI/*/gcdx64.efi)
Failed to copy EFI files, no EFI Support will be included.
usage: mkefiboot [-h] [–debug] [-d] [-a] [-l LABEL] [-i ICONFILE]
[-n DISKNAME] [-p PRODUCT]
EFIBOOTDIR OUTPUTFILE
mkefiboot: error: /tmp/imgcreate-1xfrZU/iso-E4oXxM/EFI/BOOT is not a
directory
usage: mkefiboot [-h] [–debug] [-d] [-a] [-l LABEL] [-i ICONFILE]
[-n DISKNAME] [-p PRODUCT]
EFIBOOTDIR OUTPUTFILE
mkefiboot: error: /tmp/imgcreate-1xfrZU/iso-E4oXxM/EFI/BOOT is not a
directory
ensure /etc/os-release is present (needed for RHEL 7.0)
What am I missing here? Any help would be appreciated.
Hello, we do only build on Fedora, the livecd tooling in RHEL7 might
be little bit outdated.
What is the reason for shim/efibootloader in discovery image? You want
SecureBoot over PXE?
LZ
···
On Sun, Oct 22, 2017 at 3:11 PM, Oleg Mcnoleg wrote:
> Hello,
>
> I'm rolling my own discovery iso but UEFI support seems to fail during
> build.
>
> Building on a CentOS 7.2 host running build-livecd then build-livecd. The
> ISO builds OK and is bootable from legacy BIOS but I need to boot UEFI hosts
> too.
>
> I have the below in my 20-packages.ks
>
> grub2-efi
> efibootmgr
> shim
>
> Missing EFI file (/boot/efi/EFI/*/gcdx64.efi)
> Failed to copy EFI files, no EFI Support will be included.
> usage: mkefiboot [-h] [--debug] [-d] [-a] [-l LABEL] [-i ICONFILE]
> [-n DISKNAME] [-p PRODUCT]
> EFIBOOTDIR OUTPUTFILE
> mkefiboot: error: /tmp/imgcreate-1xfrZU/iso-E4oXxM/EFI/BOOT is not a
> directory
> usage: mkefiboot [-h] [--debug] [-d] [-a] [-l LABEL] [-i ICONFILE]
> [-n DISKNAME] [-p PRODUCT]
> EFIBOOTDIR OUTPUTFILE
> mkefiboot: error: /tmp/imgcreate-1xfrZU/iso-E4oXxM/EFI/BOOT is not a
> directory
> * ensure /etc/os-release is present (needed for RHEL 7.0)
>
> What am I missing here? Any help would be appreciated.
>
> Thanks,
>
>
> --
> You received this message because you are subscribed to the Google Groups
> "Foreman users" group.
> To unsubscribe from this group and stop receiving emails from it, send an
> email to foreman-users+unsubscribe@googlegroups.com.
> To post to this group, send email to foreman-users@googlegroups.com.
> Visit this group at https://groups.google.com/group/foreman-users.
> For more options, visit https://groups.google.com/d/optout.
Worked for me on Fedora, do a PR and I can add those files into the
official build.
LZ
···
On Wed, Oct 25, 2017 at 4:16 PM, Lukas Zapletal wrote:
> Hello, we do only build on Fedora, the livecd tooling in RHEL7 might
> be little bit outdated.
>
> What is the reason for shim/efibootloader in discovery image? You want
> SecureBoot over PXE?
>
> LZ
>
> On Sun, Oct 22, 2017 at 3:11 PM, Oleg Mcnoleg wrote:
>> Hello,
>>
>> I'm rolling my own discovery iso but UEFI support seems to fail during
>> build.
>>
>> Building on a CentOS 7.2 host running build-livecd then build-livecd. The
>> ISO builds OK and is bootable from legacy BIOS but I need to boot UEFI hosts
>> too.
>>
>> I have the below in my 20-packages.ks
>>
>> grub2-efi
>> efibootmgr
>> shim
>>
>> Missing EFI file (/boot/efi/EFI/*/gcdx64.efi)
>> Failed to copy EFI files, no EFI Support will be included.
>> usage: mkefiboot [-h] [--debug] [-d] [-a] [-l LABEL] [-i ICONFILE]
>> [-n DISKNAME] [-p PRODUCT]
>> EFIBOOTDIR OUTPUTFILE
>> mkefiboot: error: /tmp/imgcreate-1xfrZU/iso-E4oXxM/EFI/BOOT is not a
>> directory
>> usage: mkefiboot [-h] [--debug] [-d] [-a] [-l LABEL] [-i ICONFILE]
>> [-n DISKNAME] [-p PRODUCT]
>> EFIBOOTDIR OUTPUTFILE
>> mkefiboot: error: /tmp/imgcreate-1xfrZU/iso-E4oXxM/EFI/BOOT is not a
>> directory
>> * ensure /etc/os-release is present (needed for RHEL 7.0)
>>
>> What am I missing here? Any help would be appreciated.
>>
>> Thanks,
>>
>>
>> --
>> You received this message because you are subscribed to the Google Groups
>> "Foreman users" group.
>> To unsubscribe from this group and stop receiving emails from it, send an
>> email to foreman-users+unsubscribe@googlegroups.com.
>> To post to this group, send email to foreman-users@googlegroups.com.
>> Visit this group at https://groups.google.com/group/foreman-users.
>> For more options, visit https://groups.google.com/d/optout.
>
>
>
> --
> Later,
> Lukas @lzap Zapletal
Do you have any specifics around your Fedora build env?
Using a fresh Fedora 26 install and latest master.zip, I'm modifying
00-repos-f21.ks and pointing to nightly f24. At which point the
build-livecd-root finishes but I get an offensive message:
dracut: dracut module 'dmsquash-live' cannot be found or installed.
mkinitrd failed
Followed by:
The ISO image doesn't look like a LiveCD ISO image to me.
Which version of Fedora are you building on and what is the contents of
your fedora ks files?
I am on latest stable Fedora, haven't done anything special, but this
is my development instance, I might have some packages that clean
installation don't have. It should be as easy as:
Quick look into yum/dnf database shows this package you are missing: dracut-live
Try to grab it and see if it works, file a README update if you are
using clean environment, there might be other missing bits, thanks!
LZ
···
On Fri, Oct 27, 2017 at 3:33 PM, Oleg Mcnoleg wrote:
> Hi LZ, thanks for the reply.
>
> Do you have any specifics around your Fedora build env?
>
> Using a fresh Fedora 26 install and latest master.zip, I'm modifying
> 00-repos-f21.ks and pointing to nightly f24. At which point the
> build-livecd-root finishes but I get an offensive message:
>
> dracut: dracut module 'dmsquash-live' cannot be found or installed.
> mkinitrd failed
>
>
> Followed by:
>
> The ISO image doesn't look like a LiveCD ISO image to me.
>
> Which version of Fedora are you building on and what is the contents of your
> fedora ks files?
>
> Thanks a lot.
>
>
> --
> You received this message because you are subscribed to the Google Groups
> "Foreman users" group.
> To unsubscribe from this group and stop receiving emails from it, send an
> email to foreman-users+unsubscribe@googlegroups.com.
> To post to this group, send email to foreman-users@googlegroups.com.
> Visit this group at https://groups.google.com/group/foreman-users.
> For more options, visit https://groups.google.com/d/optout.