fedora-linux-surface-pro-12in/kiwi-descriptions.git/teams/server.xml, branch rawhide

Raise the size of the boot partition to 2G for Fedora images

2025-10-06T14:18:44Z

With the increase in content in initramfs, a long-overdue raise of the default size for /boot is warranted. Reference: https://fedoraproject.org/wiki/Changes/2GbootPartition

teams/server: aarch64: Set 16 MiB starting offset for ServerDisk partitions

2025-09-28T17:12:11Z

This ensures that there's empty space for arm-image-installer to inject firmware blobs into images as part of preparing to install for various single board computers.

grub2: Enable `bls` for all non-live images

2025-04-29T20:36:27Z

This became necessary with 10.0.13 / after merging https://github.com/OSInside/kiwi/pull/2535 but doesn't seem to noticeable effects besides miisin "GRUB_ENABLE_BLSCFG=true" in /etc/default/grub.

components/boot, teams/server: Add partitioning hack for the Raspberry Pi 3

2025-02-20T19:46:28Z

The Raspberry Pi 3 does not recognize a FAT filesystem marked with the 0xef type, so until we drop support for this device, hack the partition manually to use a legacy FAT filesystem partition type.

teams/server: Bump the ESP size to 500 MB

2025-02-20T19:15:26Z

Now that we have a lot more stuff installed in the ESP, we need the ESP to be bigger. This matches the size used for the desktop disk variants.

components, teams/server: Use a common profile for hardware support

2025-02-20T19:15:26Z

It is hard to ensure that hardware support packages are pulled in universally when it's splintered across different variant profiles. To fix this and ensure Server benefits from this, unify everything into a common profile and make everything require it.

teams/server: Use ext4 for /boot for the AArch64 host disk image

2025-02-20T12:55:35Z

U-Boot does not support XFS and this causes significant issues when trying to boot Fedora Server on single board computers. Resolve this by using ext4 here, as all U-Boot variants generally support this.

server: Remove console=ttyS0 from riscv64 images

2025-02-19T18:15:14Z

Turns out that different boards needs different values, so hardcoding a specific one here is not a good idea. Luckily, Linux can usually figure things out on its own and automatically provide a working serial console. Signed-off-by: Andrea Bolognani

Initial riscv64 support

2025-02-07T14:06:22Z

Most of the changes are self-explanatory and just follow what's already happening for existing architectures. Two things are worth pointing out: * we need to use shim-unsigned instead of shim-signed because riscv64 is not fully integrated into Fedora yet and so we can't do Secure Boot signing for the time being; * we use ext4 as bootfilesystem since in most cases the underlying firmware is going to be U-Boot, which needs to be able to load the board's DTB from /boot and doesn't support XFS. Signed-off-by: David Abdurachmanov

server: Set bootloader timeout to 3s and show menu

2025-01-27T13:36:05Z

While cloud images can usually be booted without any issues and for workstation installs we want a visually polished experience, in the case of server installs on real hardware it is generally expected to have convenient access to the bootloader menu for troubleshooting purposes. Signed-off-by: Andrea Bolognani