--- Comment #37 from lists dev <lists(a)ssl-mail.com> ---
(In reply to Gary Ching-Pang Lin from comment #36)
However, with bios_path_override, the Secure Boot
issue can be worked around.
Yes, can boot with SecureBoot DISabled.
2) The system failed at initrd.
Per comment#16, the system dropped into the dracut emergency shell. Does
Leap 42.2 DVD work? Just wonder whether there is anything missing in initrd.
Launching it as a Guest?
I'll have to give that a try.
3) Customized grub2
Per comment#24, a customized grub2 was created. In this case,
"ovmf-x86_64-ms.bin" should not be used since the new grub.efi cannot be
verified by shim.efi.
A standalone grub-standalone-test.efi is NOT being currently used
From my perspective, the real problem is 2) since it's using the default
setup of the bootloader and kernel.
Without the ability to boot into the Guest, isn't `mkinitrd` in a chrooted
Guest env generally sufficient? Perhaps parameterless mkinitrd isn't ... and
passing specific params to it? I'll take a look; if you have a specific recipe
that should be tried, pls post.
You are receiving this mail because:
You are on the CC list for the bug.