# Fedora 44

Validated Fedora 44 Cloud Base template for CloudStack KVM, rebuilt on 2026-08-12.

## Artifact

- File: `fedora-44.qcow2`
- Format: standalone, uncompressed, sparse QCOW2 with no backing file
- Architecture: x86_64
- Virtual disk: 30 GiB (32212254720 bytes)
- Physical file: 1.90 GiB (2035941376 bytes)
- SHA-256: `8c588131f5b3abeab48dbf99954cfcf9569d89ca1a5f2edc47ddd9364e813af8`
- Mirror URL: https://cloud-mirrors.noc.sh/fedora-44/fedora-44.qcow2
- Final CloudStack template UUID: `49975d19-c138-437b-8b9d-63474ea9c2c8`
- Retained private source UUID: `239071ae-278e-4601-b28f-9a38a49b02b3`
- State: Ready / Download Complete

## Source and preparation

- Official source: https://dl.fedoraproject.org/pub/fedora/linux/releases/44/Cloud/x86_64/images/Fedora-Cloud-Base-Generic-44-1.7.x86_64.qcow2
- Official source SHA-256: `28680fe5b371a5a82ebf43a31926e086a168e59949d03969c5093e7071f90b7f`
- Fully updated; 440 installed packages and no manual package removals
- Kernel: `7.1.8-200.fc44.x86_64`
- Cloud-init: `26.1-1.fc44`
- QEMU Guest Agent: `10.2.2-1.fc44`
- Fixed swap: 1 GiB `/swap.img`; Fedora zram disabled through the supported empty `/etc/systemd/zram-generator.conf` override
- The source image contains cloud-init 25.3 and needs the temporary first-boot workaround documented in the production runbook. The final cloud-init 26.1 package catches `NoDHCPLeaseError` natively and passed `rpm -V`; its installed source is unmodified.

## CloudStack registration

- Hypervisor: KVM
- Format: QCOW2
- OS type: Fedora Linux (64-bit)
- HVM: Yes
- Password enabled: Yes
- SSH key enabled: Yes
- Public: No
- Featured: No
- Template details: `guest.cpu.mode=host-model` only

Fresh Base, Pro, and Ultra instances passed password provisioning, SSH-key isolation, hostname and public networking, 30/50/80 GiB root growth, fixed 1 GiB swap, fresh SSH host keys, SELinux enforcing, zero failed systemd units, and QEMU Guest Agent checks. Base also passed a reboot test. A separate password-only Base smoke test from the canonical mirror URL and final UUID passed. Cloud-init reported `status: done` and `errors: []`; the known `Unable to obtain a DHCP lease on ens3` messages remained recoverable warnings only.