Re: [OE-core] [PATCH v7 0/8] systemd uki support

Re: [OE-core] [PATCH v7 0/8] systemd uki support

[Mikko Rapeli]

On Thu, Oct 10, 2024 at 11:56:39AM +0300, Mikko Rapeli via lists.openembedded.org wrote:
> v7: add missing "ovmf" to runqemu argument to
>     test_efi_plugin_plain_systemd_boot_qemu_x86 to fix boot hang

This test is passing now in my local build. Running full wic and uki
selftests on qemux86-64 MACHINE takes a long time so I will try to setup
hash server to speed execution and run full tests with that.

Cheers,

-Mikko

Re: [OE-core] [PATCH v7 0/8] systemd uki support

[Ross Burton]

On 10 Oct 2024, at 09:56, Mikko Rapeli via lists.openembedded.org <mikko.rapeli=linaro.org@lists.openembedded.org> wrote:
> Tested on qemuarm64-secureboot machine from meta-arm with changes to
> support secure boot. Slightly different configuration tested on
> multiple arm64 System Ready boards with UEFI firmware, real and firmware
> based TPM devices. Tested with ovmf firmware on x86_64 with selftests but
> without secure boot which seems to be harder to setup in ovmf.

I thought I followed the instructions to enable genericarm64 with UKI, including changing the WKS image, but when systemd-boot pops up its menu there are still two entries: one presumably the UKI, the other from an explicit loader.conf:

root@genericarm64:~# find /boot/ -type f
/boot/EFI/BOOT/bootaa64.efi
/boot/EFI/Linux/uki.efi
/boot/Image
/boot/core-image-initramfs-boot-genericarm64.cpio.gz
/boot/loader/entries/boot.conf
/boot/loader/loader.conf

I’m sure I’m doing something obviously wrong - any idea?

Ross

Re: [OE-core] [PATCH v7 0/8] systemd uki support

[Mikko Rapeli]

Hi,

On Thu, Oct 10, 2024 at 08:21:11PM +0000, Ross Burton wrote:
> On 10 Oct 2024, at 09:56, Mikko Rapeli via lists.openembedded.org <mikko.rapeli=linaro.org@lists.openembedded.org> wrote:
> > Tested on qemuarm64-secureboot machine from meta-arm with changes to
> > support secure boot. Slightly different configuration tested on
> > multiple arm64 System Ready boards with UEFI firmware, real and firmware
> > based TPM devices. Tested with ovmf firmware on x86_64 with selftests but
> > without secure boot which seems to be harder to setup in ovmf.
> 
> I thought I followed the instructions to enable genericarm64 with UKI, including changing the WKS image, but when systemd-boot pops up its menu there are still two entries: one presumably the UKI, the other from an explicit loader.conf:
> 
> root@genericarm64:~# find /boot/ -type f
> /boot/EFI/BOOT/bootaa64.efi
> /boot/EFI/Linux/uki.efi
> /boot/Image
> /boot/core-image-initramfs-boot-genericarm64.cpio.gz
> /boot/loader/entries/boot.conf
> /boot/loader/loader.conf
> 
> I’m sure I’m doing something obviously wrong - any idea?

I think the wks file still has initrd=... in --sourceparams
which installs the initrd and a boot.conf.
With uki, only "loader=systemd-boot" needs to be there.

Not sure how kernel still got installed to /boot. Maybe
it's in IMAGE_EFI_BOOT_FILES?

Since uki.bbclass embeds the kernel command line,
wks file bootloader entry to append to command line
is not effective so --append="rootwait rootfstype=ext4"
should be UKI_CMDLINE now.

Cheers,

-Mikko