You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
Repository navigation
Commit 8275daa
Browse filesBrowse the repository at this point in the historyBrowse files
composefs: Use an XBOOTLDR partition with systemd-boot
The Boot Loader Specification lets systemd-boot read Type #1 entries
and UKIs from an Extended Boot Loader Partition (XBOOTLDR) on the
ESP's disk. The composefs backend always wrote them to the ESP, which
doesn't work when the ESP is small. That's the usual case next to
Windows: its ESP is often 100 MB, a UKI with a full initramfs can be
bigger than that, and composefs keeps the booted, staged and rollback
ones side by side.
For bootloaders that read entries the way BLS describes, which for
now is only systemd-boot, install the UKIs, BLS entries and their
kernels and initramfs images to a VFAT XBOOTLDR partition next to the
ESP when there is one. The bootloader and loader.conf, which
systemd-boot only reads from the ESP, stay there.
When booted, BootedStorage, which upgrades, rollback, finalize and GC
go through, uses the XBOOTLDR partition next to the ESP named by
LoaderDevicePartUUID only if it holds the booted deployment's entries,
and the ESP otherwise. That way systems installed by an older bootc,
or before an XBOOTLDR partition was added, keep their entries on the
ESP.
GRUB keeps its own /boot handling, and grub-cc is left alone since
it's unclear whether it reads XBOOTLDR.
The new tmt test splits the VM's ESP in half with an empty XBOOTLDR
partition, and checks that a switch keeps the entries on the ESP. It
then moves them to the XBOOTLDR partition, as an install there would
have put them, and upgrades and rolls back. Sealed runs skip it, since
the derived images are built in the VM without keys to sign them.
Assisted-by: AI
Signed-off-by: Kristof Imeri <kristof@lanth.me>
0 commit comments