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

teams/cloud: Drop /boot partition and use a Btrfs subvolume for /boot

2025-12-09T18:50:44Z

This lets us free up the space allocated for the partition and gives us dynamically allocated space for boot data like we have with the rest of the operating system. We do not do this for s390x because zipl does not support it. Reference: https://fedoraproject.org/wiki/Changes/BtrfsBootForCloud

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

Cloud: Adjust aarch64 images to use the correct serial console

2025-05-29T20:17:06Z

The serial device name on Arm is ttyAMA, not ttyS. This splits the configuration for Cloud images based on the architecture and adjusts the kernel command line. Note that prior to this change, aarch64 would still output kernel logs to the ttyAMA0 console (on Azure, at least) due to the ACPI SPCR table. On aarch64 the console in this table, if it's present, is _always_ configured as the kernel's default console. However, systemd logs would not be sent to the serial console because it seems it was honoring the kernel command line configuration which had ttyS0 as the default. Also see: https://pagure.io/cloud-sig/issue/394 Also see: https://bugzilla.redhat.com/show_bug.cgi?id=1661288 Signed-off-by: Jeremy Cline

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.

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

Azure: include azure-vm-utils package in the image

2024-09-25T15:52:25Z

This package is intended to be the place for Azure utilities along with the various udev rules that currently live in the WALinuxAgent package. At the moment it just contains the `azure-nvme-id` binary and udev rules for providing symlinks in /dev/disk/azure/ for local, data, and OS disks.

cloud: updates for s390x

2024-06-03T15:36:44Z

updates for "virtual image" usable under KVM - don't use 4k block size - don't use CDL partitioning - don't use DASD related kernel parameters

cloud: don't use 4k block size on ppc64le

2024-06-03T14:02:34Z

Disable systemd-firstboot on Cloud images via cmdline (#2282195)

2024-05-22T15:15:12Z

systemd 256 added a new feature which wants to create users on boot if none exist yet: https://github.com/systemd/systemd/commit/3ccadbce3358ba1db7ce5fa3f8dd17c627ffd93b We don't want that, cloud-init handles this situation. So let's disable it. Signed-off-by: Adam Williamson

AmazonEC2: Add more helpful packages

2024-05-10T11:39:20Z

The amazon-ec2-utils package includes udev rules that make it easier to identify block storage devices and sets some configuration for other storage devices. Users can run awscli2 to manage their AWS cloud resources. The ec2-instance-connect package allows one click console access to a Fedora instance from the AWS console (website). Signed-off-by: Major Hayden