OpenCloudOS
9, three arches for users
opencloudos-cloud-9 on x86_64, aarch64 and loongarch64, the only loongarch64 system, downloads one pinned 9.6 build from the project's mirror, checks it against the .sha256 file next to it and boots with efi; its first boot is the common template with an opencloudos user, and pkgproxy sets up snapd and Go but not the package manager.
On the map: systems
▶ Watch this deck — 6 scenes, ~4 min
Worth seeing first
- From a system's name to a running VM — the path one system takes from a name to a running VM
01 One release, three machines
opencloudos-cloud-9 on x86_64, aarch64 and loongarch64, the only loongarch64 system: image-garden make opencloudos-cloud-9.loongarch64.run.
Say your software ships for Enterprise Linux, and someone asks whether it runs on LoongArch too. OpenCloudOS answers both. It's an Enterprise Linux distribution, and its release 9 has cloud images for x86_64, aarch64 and loongarch64. image-garden has all three, named opencloudos-cloud-9 with the architecture on the end, and it's the only system there is for loongarch64. You build each one like ubuntu-cloud-24.04.x86_64, with one make command for its .run script. This deck shows where the images come from, how the three machines boot, what the first boot gives you, and what to keep in mind when you test.
Details and sources
Details
data/opencloudos.ini:Group=opencloudos,Variant=cloud, and[opencloudos-cloud-9.x86_64],[opencloudos-cloud-9.aarch64]and[opencloudos-cloud-9.loongarch64], each withRelease=9(opencloudos.ini:9-32).- The README: "Versions: 9 (currently 9.6, build 20260922.0)", "Architectures: x86\_64, aarch64, loongarch64", "The only system for loongarch64" (README.md:657-662); the release notes: "image-garden's first loongarch64 system" (NEWS:52-53).
- image-garden's CI calls it "OpenCloudOS, which is EL" (.gitlab-ci.yml:1004) and tests it with the other Enterprise Linux systems. That OpenCloudOS is a distribution led from China, by Tencent and partners, is outside the tree (derived).
Read more
02 Nine means one build
The download names build 20260922.0 of 9.6, checked against the .sha256 file next to the image. Everyone gets the same image, until a new image-garden names a newer build.
The name says 9, but the image is more exact than that. OpenCloudOS publishes each build in a directory of its own, named after the build, and keeps no link to the latest one. So image-garden downloads one build of 9.6, from the project's own mirror, and everyone who downloads it gets the same bytes. That's the opposite of Arch and Gentoo. Each image has its own checksum file right next to it: the same address with .sha256 on the end. Moving to a newer build is a change in image-garden itself, so it arrives with a new image-garden, not on its own.
Details and sources
Details
- The file's comment: OpenCloudOS publishes each build "in a directory named after the build, with the build in the file name, and no alias for the latest one: pin a build, and move to a newer one by hand. Builds of 9.6 for the three architectures appear together, on the project's own mirror" (opencloudos.ini:4-7).
- The URLs:
https://mirrors.opencloudos.tech/opencloudos/9.6/images/qcow2/ARCH/20260922.0/OpenCloudOS-GenericCloud-9.6-20260922.0.ARCH.qcow2, withSHA256SUMS=@URL@.sha256(opencloudos.ini:13-32).@URL@is the URL from the.urlfile (rulegen.py:51-58). - The
.sha256file holds one line,HASH OpenCloudOS-GenericCloud-9.6-20260922.0.x86_64.qcow2(run with curl on 21 November 2026); the x86_64 image was 839712768 bytes. - The system name keeps
9, theRelease=; the point release and the build are only in the URL. On 21 November 2026 the mirror answered through a content delivery network (run); where it is served from is not in the tree. - How the section compares with Ubuntu's, and the loongarch64 one in full: a pinned build.
Read more
03 Three machines, one way to boot
UEFI on all three. x86_64 on q35 and aarch64 on virt run with KVM on a matching host; loongarch64, on virt, is emulated on a PC. On any host, only its own architecture gets KVM.
All three systems boot with UEFI firmware. What differs is the machine underneath. On a PC, the x86_64 system runs on QEMU's q35 machine with KVM, at full speed. On a 64-bit Arm host, the aarch64 one does the same on the virt machine. loongarch64 is another matter. It runs on virt too, but few people have a LoongArch host, so QEMU emulates it, one instruction at a time, and that's slow. Whichever host you have, KVM only helps the system of its own architecture: on a PC, the aarch64 one is emulated as well, and on an Arm host the x86_64 one is.
Details and sources
Details
Boot=efiin all three sections (opencloudos.ini:13-32); x86_64 may boot efi or bios, aarch64 and loongarch64 only efi (rulegen.py:300-309).- Machines:
q35with-cpu maxon x86_64 (010-qemu-x86_64.mk:5-6),virt,gic-version=maxon aarch64 (010-qemu-aarch64.mk:4-5),virtwith-cpu maxon loongarch64 (010-qemu-loongarch64.mk:4-5). Each asks forkvm:tcgwhen QEMU lists KVM, so on a LoongArch host the loongarch64 system would use KVM too (010-qemu-loongarch64.mk:13-14); the host's own architecture also gets 4 vCPUs (010-qemu.mk:5-6). - The aarch64 system uses the regular EDK2 search list, not the Fedora or Jammy builds some older aarch64 systems need (010-qemu-aarch64.mk:134-145).
- That few people have LoongArch hardware is a judgement (derived).
for contributors
In image-garden's CI
- CI:
x86_64: [el 2/2](.gitlab-ci.yml:833-839) andaarch64: [el], on Raspberry Pi 5s, allowed to fail (.gitlab-ci.yml:897-905, .gitlab-ci.yml:649-652);loongarch64: [el]with Ubuntu'sqemu-system-miscandqemu-efi-loongarch64(.gitlab-ci.yml:1004-1015) extends.systems-emulated:GARDEN_TEST_BOOT_ONLY: "1",allow_failure: true, run on version tags and by hand elsewhere (.gitlab-ci.yml:663-690).
Read more
04 What the first boot gives you
The common template: root/root and opencloudos/opencloudos with sudo, host name opencloudos-9. pkgproxy adds its hosts line, the snap setup and GOPROXY; the package manager is not set up.
There's no make file of OpenCloudOS quirks, so its first boot runs the common template, just like Ubuntu's. You get root with the password root, and a user named opencloudos, with the password opencloudos and sudo without a password. The host name joins the group and the release: opencloudos-9. With a pkgproxy in reach, the guest learns its address, runs pkgproxy's snap setup script, and gets GOPROXY for Go. There's nothing for its package manager. The package step is apt's, for Debian and Ubuntu only, so packages come from OpenCloudOS's mirrors, uncached, on every test run that installs them.
Details and sources
Details
- No
mk/file names OpenCloudOS: noOPENCLOUDOS_9_orOPENCLOUDOS_template is defined, so the picker falls back to the common template (010-qemu.mk:285-298); the user-data passes the groupopencloudosand the release9(rulegen.py:467). - Users:
root/root, andopencloudos/opencloudosinuserswith passwordless sudo (010-qemu.mk:200-211); spread-demo logs in withopencloudos/opencloudos(spread-demo/spread.yaml:258-261). - Host name and
local-hostname:opencloudos-9, the group and release joined by a dash (010-qemu.mk:94-104); the meta-data'sinstance-idisiid-opencloudos-9. - With a pkgproxy: the
/etc/hostsline, the snap script fromruncmd, no apt script, andGOPROXYin/etc/environment(010-qemu.mk:127-180). pkgproxy serves apt, the snap store and Go modules (proxy/README.md:40-48). That OpenCloudOS 9 installs packages with dnf from its own repositories is the distribution's behaviour (derived).
Read more
05 Worth knowing when you test on it
Packages are as old as the pinned build until a test updates them. The first, uncached download dominates; pkgproxy keeps the image by its checksum. Emulated loongarch64 is slow.
A few things worth knowing. A pinned build holds still, but it ages. The first boot asks for no updates, so the guest has the packages of that build, and an install in your test may pull in newer ones from the mirror. The first download can be slow. On one machine, making the loongarch64 image without a cache took eight minutes, and most of that went into downloading it. With a pkgproxy, that happens once: later downloads come from the proxy, by checksum. And loongarch64 is emulated, so give it time, and expect only a boot, not a full test run, to be practical in CI.
Details and sources
Details
- Pinned: one build in every URL (opencloudos.ini:4-7). The common template asks for no package update (010-qemu.mk:187-247); that an install resolves dependencies against the mirror's current repositories, and may upgrade packages of the image, is dnf's behaviour (derived).
- The CI comment: "On novigrad the image was made in 8.4 minutes, 6.8 of them downloading it uncached; 1.6 minutes on ciri since" (.gitlab-ci.yml:1004-1005). That is one runner's network; yours may differ.
- With a pkgproxy, the image is asked of it by its checksum, so every machine that uses that pkgproxy downloads it from the internet once (image-garden:272-308); CI runners with a pkgproxy work the same way (.gitlab-ci.yml:550-556).
- The emulated jobs: "Each image only boots once (GARDEN_TEST_BOOT_ONLY). My CI server is so slow this will likely time out and fail" (.gitlab-ci.yml:663-669). More vCPUs or memory for a slow guest: the .run script.
Read more
06 Where to go from here
Next: loongarch64, the support matrix, the users, pkgproxy family by family, the six architectures, and Enterprise Linux.
So OpenCloudOS is one release on three machines, from one pinned build, with the common first boot. From here, the loongarch64 deck covers the machine, its firmware and the network card's ROM, and which install brings them. The support matrix sets OpenCloudOS beside the other families. The users deck covers the accounts every system gets, and the pkgproxy deck what a guest is set up to cache. The architecture deck compares the six machines. And the Enterprise Linux deck covers the family OpenCloudOS belongs to.
Details and sources
Read more
Basis of the statements on this page
Read in data/opencloudos.ini, rulegen.py, mk/010-qemu.mk and the per-architecture make files, the image-garden script, the README, NEWS and .gitlab-ci.yml of image-garden at the commit in garden.commit ("code"). The checksum file and the image size were fetched from the mirror on 21 November 2026 ("run"). Where the mirror is served from, and how dnf behaves in the guest, are "derived".
The systems
| System | Arch | Boot | Release | Image | Checksum |
|---|---|---|---|---|---|
opencloudos-cloud-9.x86_64 | x86_64 | efi | 9 | OpenCloudOS-GenericCloud-9.6-20260922.0.x86_64.qcow2 | @URL@.sha256 |
opencloudos-cloud-9.aarch64 | aarch64 | efi | 9 | OpenCloudOS-GenericCloud-9.6-20260922.0.aarch64.qcow2 | @URL@.sha256 |
opencloudos-cloud-9.loongarch64 | loongarch64 | efi | 9 | OpenCloudOS-GenericCloud-9.6-20260922.0.loongarch64.qcow2 | @URL@.sha256 |
Image URL pattern: https://mirrors.opencloudos.tech/opencloudos/9.6/images/qcow2/ARCH/20260922.0/OpenCloudOS-GenericCloud-9.6-20260922.0.ARCH.qcow2; the checksum is that URL plus .sha256, a one-line HASH NAME file. Source: opencloudos.ini:4-32.
Machines
| Arch | Machine | Usual host | CI job |
|---|---|---|---|
| x86_64 | q35, -cpu max | a PC, with KVM | x86_64: [el 2/2] |
| aarch64 | virt,gic-version=max, -cpu max | a 64-bit Arm machine, with KVM | aarch64: [el] (may fail) |
| loongarch64 | virt, -cpu max | a PC, emulated | loongarch64: [el] (boot only, may fail) |
The loongarch64 machine's options, firmware search list and per-install support are in loongarch64 and OpenCloudOS.
First boot
| Item | Value |
|---|---|
| Template | the common template (no OpenCloudOS quirk) |
| Users | root/root; opencloudos/opencloudos, group users, passwordless sudo |
| Host name | opencloudos-9 |
| pkgproxy | /etc/hosts line, snap setup script (runcmd), GOPROXY in /etc/environment; no apt step; the package manager not set up |
| Updates | none asked for at first boot |
Sources: 010-qemu.mk:94-104, 010-qemu.mk:127-180, 010-qemu.mk:187-247.
Testing on it
| Item | Value |
|---|---|
| Size | about 840 MB for x86_64 (run, 21 November 2026) |
| First download in CI | 6.8 of 8.4 minutes, uncached (.gitlab-ci.yml:1004-1005) |
| spread | opencloudos-cloud-9 with opencloudos/opencloudos in spread-demo |
| A newer build | comes with an edit to data/opencloudos.ini, in a new image-garden |
Roads from here
SYSTEMS · distributions
- The support matrix — OpenCloudOS beside every other family and architecture
- AlmaLinux, CentOS Stream, Oracle Linux and Rocky Linux — the Enterprise Linux family OpenCloudOS belongs to
ARCHITECTURES · machines and firmware
- loongarch64 and OpenCloudOS — the loongarch64 machine, its firmware and the installs that bring it
- Six architectures, six QEMU machines — the QEMU machine of each architecture, and why emulation is slow
FIRST BOOT · cloud-init changes
- The users every system gets — root and the group's user, on every system
PKGPROXY · caching for guests
- What pkgproxy adds to user-data — what pkgproxy sets up in a guest, family by family