public inbox for isar-users@googlegroups.com
 help / color / mirror / Atom feed
From: "'Arjunan, Srinu' via isar-users" <isar-users@googlegroups.com>
To: "Kiszka, Jan" <jan.kiszka@siemens.com>,
	"isar-users@googlegroups.com" <isar-users@googlegroups.com>
Cc: "K L, Shivaschandra" <shivaschandra.k-l@siemens.com>
Subject: RE: [PATCH] rootfs: run kernel-install after update-initramfs
Date: Fri, 17 Apr 2026 04:55:20 +0000	[thread overview]
Message-ID: <PUZPR06MB57475ADF58813411880F623488202@PUZPR06MB5747.apcprd06.prod.outlook.com> (raw)
In-Reply-To: <7e120fa6-703a-4b7e-b242-bea198ea10ce@siemens.com>

> Err, where/how do you define "primary" and "secondary" EFI bootloaders?
> Note that EBG is isar-cip-core, and there we definitely do not have such a concept. Can you
> elaborate what you want to achieve?

In our downstream project, we use a combination of EBG and systemd-boot, along with UKI (ukify) images.

EBG acts as the primary bootloader to enable watchdog support during early boot,
while systemd-boot is used as a secondary bootloader to select the appropriate Btrfs snapshot along with its corresponding UKI image.

If the system fails to be successfully “blessed” (e.g., due to issues detected during validation of a newly created Btrfs snapshot),
 we need a mechanism to fall back to a previously working snapshot and its associated UKI image. This fallback selection is handled by systemd-boot.

To support this flow, the WIC plugin expects /boot/EFI/Linux to contain the unified kernel image required for the first boot.

Therefore, we run kernel-install after update-initramfs to ensure that the unified kernel image is properly 
generated and placed in the expected location.

Many thanks,
Srinu

-----Original Message-----
From: Kiszka, Jan (FT RPD CED) <jan.kiszka@siemens.com> 
Sent: 15 April 2026 18:35
To: Arjunan, Srinu (FT FDS CES LX PBU 2) <srinuvasan.a@siemens.com>; isar-users@googlegroups.com
Cc: K L, Shivaschandra (FT FDS CES LX PBU 1) <shivaschandra.k-l@siemens.com>
Subject: Re: [PATCH] rootfs: run kernel-install after update-initramfs

On 15.04.26 14:55, srinuvasan.a via isar-users wrote:
> From: srinuvasan <srinuvasan.a@siemens.com>
> 
> When efibootguard is used as the primary bootloader and systemd-boot 
> as secondary, the WIC plugin expects /boot/EFI/Linux to contain a 
> unified kernel image for first boot.
> 

Err, where/how do you define "primary" and "secondary" EFI bootloaders?
Note that EBG is isar-cip-core, and there we definitely do not have such a concept. Can you elaborate what you want to achieve?

> Run kernel-install after update-initramfs to ensure the unified kernel 
> image is generated and placed correctly.
> 
> Invoke kernel-install for UKI generation only when:
> - ukify binary is available
> - /usr/lib/kernel/install.conf exists
> 
> Signed-off-by: Shivaschandra KL <shivaschandra.k-l@siemens.com>
> Signed-off-by: srinuvasan <srinuvasan.a@siemens.com>
> ---
>  meta/classes-recipe/rootfs.bbclass | 20 +++++++++++++++++---
>  1 file changed, 17 insertions(+), 3 deletions(-)
> 
> diff --git a/meta/classes-recipe/rootfs.bbclass 
> b/meta/classes-recipe/rootfs.bbclass
> index a9233111..9024f006 100644
> --- a/meta/classes-recipe/rootfs.bbclass
> +++ b/meta/classes-recipe/rootfs.bbclass
> @@ -14,10 +14,20 @@ ROOTFS_DISTRO ?= "${DISTRO}"
>  ROOTFS_USE_DRACUT ??= ""
>  
>  def initramfs_generator_cmdline(d):
> -    rootfs_packages =  d.getVar('ROOTFS_PACKAGES') or ''
> +    rootfs_packages = d.getVar('ROOTFS_PACKAGES') or ''
> +
>      if 'dracut' in rootfs_packages or bb.utils.to_boolean(d.getVar('ROOTFS_USE_DRACUT')):
> -        return "dracut --force --kver \"$kernel_version\""
> -    return "update-initramfs -u -v -k \"$kernel_version\""
> +        return 'dracut --force --kver "$kernel_version"'
> +
> +    cmdline = 'update-initramfs -u -v -k "$kernel_version"'
> +
> +    cmdline += (
> +        '; command -v ukify >/dev/null && [ -f /usr/lib/kernel/install.conf ] && '

Who is using ukify? No one in isar or isar-cip-core at least. Are you referring to an out-of-tree wic plugin with these changes?

In-tree (Isar), we still need to enable
meta/scripts/lib/wic/plugins/source/bootimg-efi-isar.py to generate UKIs. But that would be systemd-boot UKI-only, no EBG then.

Jan

> +        'kernel-install add "$kernel_version" "/boot/${kernel##*/}" '
> +        '"/boot/initrd.img-$kernel_version" || :'
> +    )
> +
> +    return cmdline
>  
>  ROOTFS_PACKAGES ?= ""
>  ROOTFS_VARDEPS ?= ""
> @@ -627,6 +637,10 @@ python do_generate_initramfs_setscene () {  }
>  
>  rootfs_generate_initramfs[progress] = "custom:rootfs_progress.InitrdProgressHandler"
> +rootfs_generate_initramfs:prepend() {
> +    export kernel
> +}
> +
>  rootfs_generate_initramfs() {
>      if [ -n "$(sudo find '${ROOTFSDIR}/boot' -type f -name 'vmlinu[xz]*')" ]; then
>          for kernel in ${ROOTFSDIR}/boot/vmlinu[xz]-*; do


--
Siemens AG, Foundational Technologies
Linux Expert Center

-- 
You received this message because you are subscribed to the Google Groups "isar-users" group.
To unsubscribe from this group and stop receiving emails from it, send an email to isar-users+unsubscribe@googlegroups.com.
To view this discussion visit https://groups.google.com/d/msgid/isar-users/PUZPR06MB57475ADF58813411880F623488202%40PUZPR06MB5747.apcprd06.prod.outlook.com.

  parent reply	other threads:[~2026-04-17  4:55 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-04-15 12:55 srinuvasan.a via isar-users
2026-04-15 13:05 ` 'Jan Kiszka' via isar-users
2026-04-16 12:16   ` Srinuvasan Arjunan
2026-04-20  9:33     ` Srinuvasan Arjunan
2026-04-17  4:55   ` 'Arjunan, Srinu' via isar-users [this message]
2026-04-17  7:27     ` 'Jan Kiszka' via isar-users
2026-04-17  7:35 ` 'Quirin Gylstorff' via isar-users

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=PUZPR06MB57475ADF58813411880F623488202@PUZPR06MB5747.apcprd06.prod.outlook.com \
    --to=isar-users@googlegroups.com \
    --cc=jan.kiszka@siemens.com \
    --cc=shivaschandra.k-l@siemens.com \
    --cc=srinuvasan.a@siemens.com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox