ppc64

pseries, ppc64el names for users for contributors

64-bit POWER: ten little-endian Ubuntu systems named ppc64el, run by qemu-system-ppc64 on QEMU's pseries machine with a POWER9 CPU and its own SLOF firmware, all devices on PCI; a ppc64le host counts as ppc64 and runs them under KVM with four vCPUs, anywhere else TCG emulates them on one.

On the map: architectures

▶ Watch this deck — 9 scenes, ~6 min

Worth seeing first

01 POWER, little-endian

PPC64 a failure on IBM POWER that you can't reproduce on a PC 64-bit POWER on QEMU's pseries Ubuntu's systems only ubuntu-cloud- 14.04 16.04 18.04 20.04 22.04 24.04 25.04 25.10 26.04 26.10 ten releases, all little-endian, all named ubuntu-cloud-R.ppc64el $ image-garden make ubuntu-cloud-24.04.ppc64el.run on a PC: emulated, so give it time three spellings the machine emulation the installs gotchas
A failure on IBM POWER that cannot be reproduced on a PC. image-garden runs 64-bit POWER on QEMU's pseries machine with ten Ubuntu systems, ubuntu-cloud 14.04, 16.04, 18.04, 20.04, 22.04, 24.04, 25.04, 25.10, 26.04 and 26.10, all little-endian and named ppc64el, such as ubuntu-cloud-24.04.ppc64el. image-garden make ubuntu-cloud-24.04.ppc64el.run builds it; on a PC it is emulated. The deck covers the three spellings, the machine, emulation, the installs and the gotchas

Ten Ubuntu systems, 14.04 to 26.10, all little-endian and named .ppc64el: image-garden make ubuntu-cloud-24.04.ppc64el.run.

Say your software ships for IBM's POWER servers, or someone reports a failure there that you can't reproduce on a PC. image-garden runs 64-bit POWER on QEMU's pseries machine, and the systems there are Ubuntu's: ten releases, from 14.04 on. Ubuntu builds them little-endian, so the running example is named ubuntu-cloud-24.04.ppc64el. You build it with one make command for its .run script, like any other system. On a PC it's emulated, so give it time. This deck shows the three spellings of its name, the machine, what emulation costs, the installs that bring it, and the gotchas, starting with what POWER doesn't test.

Details and sources

Details

  • Ubuntu on ppc64, "systems named .ppc64el": 14.04, 16.04, 18.04, 20.04, 22.04, 24.04, 25.04, 25.10, 26.04, 26.10 (README.md:692-697). No other distribution has a ppc64 system, and there is no big-endian ppc64 system.
  • They are little-endian: "a ppc64le host runs the ppc64 (little-endian) systems natively" (mk/000-garden.mk:14-16).
  • The release notes that added the architecture: "Currently all systems emulate a virtual Power 9 processor in a P-Series machine" (NEWS:624-628).

for contributors

In the data

02 Where the spellings meet in the code for contributors in place of the general version

IN THE CODE [ubuntu-cloud-24.04.ppc64el] URL=…/noble-server-cloudimg-ppc64el.img Arch=ppc64 Release=24.04 name and URL must contain the Arch value: ppc64el contains ppc64 Arch picks ruleset_ppc64 and the test ifeq ($(GARDEN_ARCH),ppc64) for all:: GARDEN_HOST_ARCH := $(patsubst ppc64le,ppc64,$(shell uname -m)) QEMU_SMP_$(GARDEN_HOST_ARCH, upper-cased) = 4 → QEMU_SMP_PPC64 ubuntu-cloud-24.04@web.ppc64el _qemu_arch := $(or $(_$(_base_full)_arch),…) so the instance gets the PPC64 command line, not a PPC64EL one that does not exist
The section [ubuntu-cloud-24.04.ppc64el] has Arch=ppc64; rulegen.py checks only that the section name and the URL contain ppc64, which both do. Arch picks ruleset_ppc64 and the all:: test against GARDEN_ARCH. GARDEN_HOST_ARCH is uname -m with ppc64le replaced by ppc64, and QEMU_SMP_PPC64 = 4 follows from it. define-instance reads the base's _arch from the systems metadata, so ubuntu-cloud-24.04@web.ppc64el gets the PPC64 command line

[ubuntu-cloud-24.04.ppc64el] has Arch=ppc64; GARDEN_HOST_ARCH maps ppc64le to ppc64; define-instance takes the architecture from Arch.

Inside, the three spellings meet in a few places. The section is named for Ubuntu, ubuntu-cloud-24.04.ppc64el, but says Arch=ppc64. rulegen.py only checks that the name and the URL contain the Arch value, and both do. Arch picks the ppc64 rules and decides when a system joins make all. To match it on a POWER host, GARDEN_HOST_ARCH is uname -m with ppc64le replaced by ppc64, and the native CPU count follows that name. Named instances read their base's Arch from the systems metadata rather than the suffix of its name, so they get the pseries command line too.

Details and sources

Details

  • [ubuntu-cloud-24.04.ppc64el] has Arch=ppc64 (data/ubuntu.ini:264-268). rulegen.py requires the section name to contain the Arch value ("Suspicious image") and, for architectures other than x86\_64 and aarch64, the URL too ("Suspicious URL") (rulegen.py:396-416).
  • all:: and fetch compare GARDEN_ARCH with the Arch value (rulegen.py:453-459, rulegen.py:480-484); ppc64 sections get ruleset_ppc64 (rulegen.py:707-724, rulegen.py:820-821).
  • GARDEN_HOST_ARCH := $(patsubst ppc64le,ppc64,$(shell uname -m)), the default of GARDEN_ARCH (mk/000-garden.mk:14-18); the native vCPU count is set on QEMU_SMP_ followed by that name upper-cased (mk/010-qemu.mk:5-6).
  • define-instance takes the QEMU architecture from the base's _SYSTEM_arch metadata, written by rulegen.py from Arch, and compares it with GARDEN_ARCH for all:: (mk/020-instances.mk:53-65).
  • Known discrepancy: define-instance without an arch suffix finds no base on a POWER host. When the base is given without a suffix, define-instance appends GARDEN_ARCH, ppc64 there, and looks for ubuntu-cloud-24.04.ppc64, which has no metadata: the instance gets no boot type and no .run or .qcow2 rule (mk/020-instances.mk:31-39, mk/020-instances.mk:84-146). Derived from the code, not run.

03 ppc64, ppc64el, ppc64le general version

THREE SPELLINGS ppc64 what QEMU calls it qemu-system-ppc64 image-garden+qemu-ppc64 the emulator, the component ppc64el Ubuntu's little-endian port ubuntu-cloud-24.04.ppc64el make, allocate, instances the system name ppc64le what uname -m prints on a POWER host the host's kernel image-garden counts a ppc64le host as ppc64: make all builds them, with four CPUs your script: "$SYSTEM.$(uname -m)" ubuntu-cloud-24.04.ppc64le no such system
Three spellings of one architecture. ppc64: qemu-system-ppc64 and the snap component image-garden+qemu-ppc64. ppc64el: Ubuntu's little-endian port and the system name ubuntu-cloud-24.04.ppc64el, which you make, allocate and define instances of. ppc64le: what uname -m prints on a POWER host, which image-garden counts as ppc64, so make all builds the ppc64el systems there with four CPUs. Pasting uname -m onto a system name gives ubuntu-cloud-24.04.ppc64le, which is no system

qemu-system-ppc64 and the qemu-ppc64 component, the system ubuntu-cloud-24.04.ppc64el, and a host whose uname -m says ppc64le, which image-garden counts as ppc64.

One architecture, three spellings. QEMU calls it ppc64: that's the emulator, and the snap's component. Ubuntu calls its little-endian port ppc64el, and that's the system name, so you make ubuntu-cloud-24.04.ppc64el .run, allocate that same name, and define named instances of it. A POWER host's kernel says ppc64le, from uname -m. image-garden treats such a host as ppc64, so make all there builds the ppc64el systems and gives them four CPUs. Your own scripts are another matter: anything that pastes uname -m onto a system name asks for ppc64le, which names no system.

Details and sources

Details

04 The pseries machine

THE MACHINE qemu-system-ppc64 -machine pseries,accel=… -cpu power9 -smp 1 4 on a POWER host -m 2048 everything on PCI virtio-blk → virtio-blk-pci, bootindex=0 virtio-net-pci the network card virtio-rng-pci random numbers no firmware to copy SLOF, from QEMU's data disk with bootindex=0 virtio-blk the seed, first boot only
ubuntu-cloud-24.04.ppc64el.run runs qemu-system-ppc64 with -machine pseries, -cpu power9, -smp 1 (4 on a POWER host) and -m 2048. Every device is on PCI: the disk virtio-blk becomes virtio-blk-pci with bootindex=0, virtio-net-pci, virtio-rng-pci, and during the provisioning boot the seed as a second virtio-blk. No firmware to install or copy: the machine loads SLOF from QEMU's data files, and SLOF boots the disk with bootindex=0

qemu-system-ppc64 -machine pseries -cpu power9, -smp 1 (4 on POWER), -m 2048; every device on PCI; QEMU's SLOF boots the disk with bootindex=0.

The .run script starts QEMU's ppc64 emulator on pseries, the paravirtualised POWER machine that IBM's hypervisors present to their guests, with a POWER9 CPU. It gets one CPU, or four on a POWER host, and two gigabytes. Unlike s390x, everything here sits on PCI: the disk, asked for as plain virtio-blk, becomes a virtio PCI disk, beside the network card and the random number generator. There's no firmware to install or copy: the machine loads SLOF, its own Open Firmware, from QEMU's data files, and SLOF boots the disk marked as boot index zero. The provisioning boot adds the seed as a second virtio disk.

Details and sources

Details

  • QEMU_SYSTEM_PPC64_MACHINE = pseries, QEMU_CPU_PPC64 = power9, QEMU_SMP_PPC64 = 1, -netdev user with virtio-net-pci, and the disk -device virtio-blk,drive=drive0,bootindex=0; no firmware option (mk/010-qemu-ppc64.mk:3-21). -m 2048, -nographic and -device virtio-rng-pci are common to every architecture (mk/010-qemu.mk:5-13, mk/010-qemu.mk:45).
  • The snap's ppc64 component carries efi-virtio.rom, slof.bin, u-boot-sam460.bin, vgabios-stdvga.bin, vgabios-virtio.bin, vof.bin and vof-nvram.bin (snap/snapcraft.yaml:409-411).
  • That pseries loads SLOF by default, that SLOF boots the device with the lowest boot index, and that QEMU resolves virtio-blk to virtio-blk-pci on this machine are QEMU's behaviour (derived).

for contributors

In the rules

  • ppc64 boots only platform, the default without Boot (rulegen.py:300-333). ruleset_ppc64 adds the seed to the provisioning boot as -device virtio-blk,drive=drive1 (rulegen.py:707-724).

05 KVM on POWER, TCG elsewhere general version

WHAT EMULATION COSTS is the host POWER, ppc64le with KVM? yes: KVM, counted as ppc64 accel=kvm:tcg, -smp 4 no: TCG translates every instruction -accel help lists no kvm, so accel=tcg -smp 1 four go only to the host's own architecture making and booting one image once, on x86_64: up to 9.8 minutes so: long timeouts, and more CPUs for your own runs $ QEMU_SMP_OPTION="-smp 4" ./ubuntu-cloud-24.04.ppc64el.run
On a POWER host with KVM, which image-garden counts as ppc64, the guest gets accel=kvm:tcg and four CPUs; anywhere else -accel help offers only TCG, which translates every POWER instruction, on one CPU. Making and booting one image once took up to 9.8 minutes on x86_64, so set long timeouts; QEMU_SMP_OPTION=-smp 4 gives your own run more CPUs

On a ppc64le host with KVM: accel=kvm:tcg and -smp 4. Elsewhere TCG and -smp 1; one image took up to 9.8 minutes to make and boot on x86_64.

On a POWER host with KVM, the guest runs close to native speed, and since image-garden counts a ppc64le host as ppc64, it gets four CPUs there. Everywhere else, the .run script finds only TCG, and QEMU translates every POWER instruction, on one CPU. To give you a feel for it, making and booting one of these images once has taken up to ten minutes on an x86_64 machine. So set long timeouts, and for your own runs, QEMU_SMP_OPTION gives an emulated guest more CPUs.

Details and sources

Details

06 How image-garden's CI tests ppc64el for contributors in place of the general version

IN IMAGE-GARDEN'S CI a POWER host with KVM: native, -smp 4; the pipeline has none stage ppc64el x86_64 runners, tagged qemu-emulated ARCH: ppc64el ppc64el: [ubuntu 1/2] 14.04 … 22.04 ppc64el: [ubuntu 2/2] 24.04 … 26.10 GARDEN_TEST_BOOT_ONLY: "1" QEMU_SMP_OPTION: -smp 2 GARDEN_CI_SYSTEM_TIMEOUT: 40m allow_failure: true when: manual runs on version tags; elsewhere by hand recorded in the comments: 25.9 and 28.5 minutes per job, up to 9.8 minutes for one image
A POWER host with KVM runs these systems natively with four CPUs. image-garden's pipeline has none, so a ppc64el stage on x86_64 runners tagged qemu-emulated, with ARCH: ppc64el, runs two jobs of five Ubuntu releases. Each makes and boots every image once (GARDEN_TEST_BOOT_ONLY), with -smp 2, 40 minutes per system, on version tags or by hand, allowed to fail. Recorded: 25.9 and 28.5 minutes per job, up to 9.8 minutes for one image

Stage ppc64el: two jobs on x86_64 runners with ARCH: ppc64el, GARDEN_TEST_BOOT_ONLY, -smp 2, 40 minutes per system, allow_failure: true.

On a POWER host with KVM the guest runs natively, with four CPUs, since a ppc64le host counts as ppc64. image-garden's own pipeline has no such host, so it tests these systems under TCG, in a stage named ppc64el on x86_64 runners, with ARCH set to ppc64el: two jobs of five Ubuntu releases each. They only make and boot every image once, with -smp 2, give each system forty minutes, run on version tags or by hand, and may fail without holding anything up. The comments record about twenty-six and twenty-nine minutes per job, and up to ten for a single image.

Details and sources

Details

  • Every system job sets QEMU_SMP_OPTION: -smp 2 and QEMU_MEM_OPTION: -m 1024 (.gitlab-ci.yml:568-569); .systems-emulated runs on x86\_64 runners tagged qemu-emulated, GARDEN_TEST_BOOT_ONLY: "1", GARDEN_CI_SYSTEM_TIMEOUT: 40m, allow_failure: true, manual outside version tags (.gitlab-ci.yml:663-690).
  • ppc64el: [ubuntu 1/2] (14.04 to 22.04, 80 minutes, "25.9 minutes on novigrad; calvin took up to 9.4 for one") and ppc64el: [ubuntu 2/2] (24.04 to 26.10, 85 minutes, "28.5 minutes on novigrad; calvin took up to 9.8 for one"), both with ARCH: ppc64el (.gitlab-ci.yml:982-1002).
  • tests/ci/run-systems.sh knows ppc64el as an architecture suffix and makes SYSTEM.ARCH.run (tests/ci/run-systems.sh:38, tests/ci/run-systems.sh:62-72). The CI installs Ubuntu's qemu-system-ppc package (.gitlab-ci.yml:292-310).

07 Snap, container or packages

EVERY INSTALL the snap $ snap install image-garden+qemu-ppc64 the snap installs only the host's own: on a PC, by hand components/qemu-ppc64/bin/qemu-system-ppc64 components/qemu-ppc64/share/qemu/slof.bin, vof.bin, … without it, after the download: It seems that the component with QEMU ppc64 is not installed. the container QEMU_TARGET_LIST=…,ppc64-softmmu,… no firmware prefix: there is no firmware to find a distribution Ubuntu: qemu-system-ppc (no 64 in the name)
The snap: snap install image-garden+qemu-ppc64, as the snap installs only the host's own component; it holds bin/qemu-system-ppc64 and share/qemu with slof.bin, vof.bin, vof-nvram.bin and the other files pseries loads; without it the provisioning boot, after the download, says the component with QEMU ppc64 is not installed. The container: QEMU built with ppc64-softmmu, no firmware prefix. Ubuntu: the qemu-system-ppc package, without the 64

Snap: snap install image-garden+qemu-ppc64. Container: ppc64-softmmu, no prefix. Ubuntu: qemu-system-ppc.

Every install can run it. In the snap, QEMU for ppc64 is a component: snap install image-garden+qemu-ppc64. On a PC you add it by hand, as the snap only installs your host's own. It brings the emulator, SLOF and the other files its machines load. Forget it, and you find out after the image has downloaded: the provisioning boot stops with a notice that names the command. The container builds QEMU with ppc64 among its targets, and needs no firmware prefix for it. On a distribution, install its POWER QEMU, which on Ubuntu is the package called qemu-system-ppc, without the sixty-four.

Details and sources

Details

  • The qemu-ppc64 component: "This component contains the ppc64 64-bit system emulator (QEMU)" (snap/snapcraft.yaml:87-92), with qemu-system-ppc64, the keymaps, efi-virtio.rom, slof.bin, u-boot-sam460.bin, vgabios-stdvga.bin, vgabios-virtio.bin, vof.bin and vof-nvram.bin (snap/snapcraft.yaml:409-411).
  • The install hook installs the component for the host's architecture and +pkgproxy (snap/hooks/install:6-14); on an x86\_64 host the ppc64 component is added by hand (README.md:309-324).
  • Without it, the snap's stand-in for qemu-system-ppc64 prints "It seems that the component with QEMU ppc64 is not installed" and snap install image-garden+qemu-ppc64, and exits 1 (qemu-stubs/qemu-system-ppc64:9-31). The first QEMU to run is the provisioning boot, after the download.
  • The container's QEMU target list includes ppc64-softmmu (Dockerfile:33); it sets GARDEN_*_PREFIX only for the four efi architectures (Dockerfile:98-102).
  • On Ubuntu the emulator is in the qemu-system-ppc package. Distribution packages of image-garden may be older than the upstream release (the maintainer's statement).

for contributors

In the tree

  • The install and post-refresh hooks name the host's component qemu-$(uname -m) with _ made - (snap/hooks/install:7, snap/hooks/post-refresh:11). On a POWER host that is qemu-ppc64le, a component the snap does not have. Whether the snap is published for POWER is not in the tree; suspected, not run.
  • The first QEMU to run is the .qcow2 rule's provisioning boot (rulegen.py:716-723). image-garden's CI installs qemu-system-ppc (.gitlab-ci.yml:292-310).

08 Gotchas, and what POWER doesn't test

GOTCHAS little-endian, like a PC: byte order passes for big-endian tests, use s390x 64 KiB pages on Ubuntu's kernels code that assumes 4096 bytes goes wrong plain char is unsigned signed on x86, unsigned here allocate: exec image-garden allocate --spread "$SPREAD_SYSTEM"."$(uname -m)" on POWER → ubuntu-cloud-24.04.ppc64le no such system ARCH=ppc64el → ubuntu-cloud-24.04.ppc64el $(eval $(call define-instance,ubuntu-cloud-24.04.ppc64el,web)) not ubuntu-cloud-24.04 alone: on a POWER host that would name ubuntu-cloud-24.04.ppc64
Every ppc64 system is little-endian, like a PC, so byte-order mistakes pass; for big-endian tests use s390x. What POWER catches: Ubuntu's ppc64el kernels use 64 KiB pages, so code assuming 4096-byte pages goes wrong, and plain char is unsigned. A spread backend that appends uname -m asks a POWER host for ubuntu-cloud-24.04.ppc64le, which does not exist; ARCH=ppc64el gives ubuntu-cloud-24.04.ppc64el. A named instance there needs the full base name, define-instance,ubuntu-cloud-24.04.ppc64el,web

Little-endian, like a PC. Watch for 64 KiB pages, unsigned char, and uname -m giving ppc64le: spread backends need ARCH=ppc64el, instances the full base name.

First, what ppc64 doesn't test. Every system here is little-endian, so byte-order mistakes pass just as they do on a PC; for big-endian, use s390x. What POWER does catch is different. Ubuntu's kernels there use sixty-four kilobyte pages, so code that assumes four kilobytes gets its mappings wrong. Plain char is unsigned, too. And the name trips scripts: a spread backend that appends uname -m asks a POWER host for a ppc64le system, which doesn't exist. Set ARCH to ppc64el for such a backend. And a named instance there needs its base's full name, ending in ppc64el.

Details and sources

Details

  • Every ppc64 system is Ubuntu's little-endian ppc64el (mk/000-garden.mk:14-16), so byte-order assumptions are not tested here; s390x is the big-endian architecture.
  • Ubuntu's ppc64el kernels use 64 KiB pages, and plain char is unsigned in the POWER Linux ABI (derived: general knowledge, not in image-garden's tree). Use sysconf(_SC_PAGESIZE) rather than 4096.
  • The README's spread backend appends $(uname -m) (README.md:740-745); image-garden's own spread.yaml appends $ARCH, defaulting to uname -m (spread.yaml:43-47). On a POWER host uname -m is ppc64le; set ARCH=ppc64el, or use the system name with its suffix.
  • Known discrepancy: define-instance without an arch suffix finds no base on a POWER host. Given ubuntu-cloud-24.04 alone, define-instance appends ppc64 there and finds no such system (mk/020-instances.mk:31-39); give the full ubuntu-cloud-24.04.ppc64el. Derived from the code, not run.

for contributors

In image-garden's CI

09 Where to go from here

ROADS ppc64 Six architectures the other five machines s390x the big-endian one Ubuntu cloud images every release Named instances Spread names names meet architectures Snap components how components install The .run script
Roads from ppc64: six architectures, s390x, Ubuntu cloud images, named instances, spread names, snap components and the .run script

Next: six architectures, s390x, Ubuntu cloud images, named instances, spread names, snap components and the .run script.

So ppc64 is one machine with its own firmware, three spellings of one name and ten little-endian Ubuntu systems. From here, the architectures deck sets it beside the other five machines, and the s390x deck covers the big-endian one, for the tests POWER can't do. The Ubuntu deck shows the releases and what each holds. The instances and spread names decks show how names and architectures meet, the snap components deck how components install, and the run script deck how to give a slow guest more CPUs.

Details and sources

Read more

Basis of the statements on this page

Read in mk/010-qemu-ppc64.mk, mk/010-qemu.mk, mk/000-garden.mk, mk/020-instances.mk, rulegen.py, data/ubuntu.ini, snap/snapcraft.yaml, the snap's hooks, qemu-stubs/qemu-system-ppc64, the Dockerfile, spread.yaml, .gitlab-ci.yml, NEWS and the README of image-garden at the commit in garden.commit ("code"). The timings are the comments in .gitlab-ci.yml. What QEMU does with the device names and firmware on pseries, page sizes, the C ABI and KVM CPU compatibility are general knowledge ("derived"). Nothing was run for this page.

The ppc64 machine

FactValueWhere
QEMU binaryqemu-system-ppc64; in the snap the image-garden.qemu-system-ppc64 appQEMU_SYSTEM_PPC64
MachinepseriesQEMU_SYSTEM_PPC64_MACHINE
CPUpower9QEMU_CPU_PPC64
vCPUs1, or 4 on a ppc64le hostQEMU_SMP_PPC64, QEMU_SMP_OPTION
Memory2048 MiBQEMU_MEM_SIZE, QEMU_MEM_OPTION
Acceleratorkvm:tcg when QEMU lists KVM, else tcgQEMU_ACCEL_MACHINE_PROP
Disk-device virtio-blk,drive=drive0,bootindex=0, virtio-blk-pci (derived)QEMU_STORAGE_OPTION
Seed (provisioning boot)a second virtio-blk, media=cdromthe .qcow2 rule
Network-netdev user, -device virtio-net-pciQEMU_NET_OPTION
Random numbers-device virtio-rng-pciQEMU_RNG_OPTION
Display-nographicQEMU_DISPLAY_OPTION
Bootplatform: no firmware files; QEMU's SLOF (derived)
Snap componentqemu-ppc64: qemu-system-ppc64, keymaps, efi-virtio.rom, slof.bin, u-boot-sam460.bin, vgabios-stdvga.bin, vgabios-virtio.bin, vof.bin, vof-nvram.binsnap/snapcraft.yaml
ContainerQEMU built with ppc64-softmmu; no prefix variableDockerfile
Ubuntu packageqemu-system-ppc
Byte orderlittle-endian (all systems are ppc64el)

Sources: mk/010-qemu-ppc64.mk:3-21, mk/010-qemu.mk:5-13, mk/000-garden.mk:14-18, snap/snapcraft.yaml:409-411, Dockerfile:33.

The ten systems

SystemImage
ubuntu-cloud-14.04.ppc64eltrusty-server-cloudimg-ppc64el-disk1.img
ubuntu-cloud-16.04.ppc64elxenial-server-cloudimg-ppc64el-disk1.img
ubuntu-cloud-18.04.ppc64elbionic-server-cloudimg-ppc64el.img
ubuntu-cloud-20.04.ppc64elfocal-server-cloudimg-ppc64el.img
ubuntu-cloud-22.04.ppc64eljammy-server-cloudimg-ppc64el.img
ubuntu-cloud-24.04.ppc64elnoble-server-cloudimg-ppc64el.img
ubuntu-cloud-25.04.ppc64elubuntu-25.04-server-cloudimg-ppc64el.img
ubuntu-cloud-25.10.ppc64elquesting-server-cloudimg-ppc64el.img
ubuntu-cloud-26.04.ppc64elresolute-server-cloudimg-ppc64el.img
ubuntu-cloud-26.10.ppc64elstonking-server-cloudimg-ppc64el.img

All from cloud-images.ubuntu.com, checked against the release's SHA256SUMS, all booting platform. See Ubuntu cloud images and the support matrix.

Three spellings

SpellingWhere you meet it
ppc64the emulator qemu-system-ppc64, the snap component qemu-ppc64, QEMU_SMP_PPC64, QEMU_CPU_PPC64
ppc64elsystem names: image-garden make ubuntu-cloud-24.04.ppc64el.run, image-garden allocate ubuntu-cloud-24.04.ppc64el, the base of a named instance, ARCH for a spread backend
ppc64leuname -m on a POWER host; image-garden treats that host as ppc64

for contributors

Inside: Arch, GARDEN_HOST_ARCH and instances

The .run command line

What ubuntu-cloud-24.04.ppc64el.run runs with every default, outside the snap, on an x86\_64 host:

qemu-system-ppc64 -cpu power9 -machine pseries,accel=tcg \
  -m 2048 -smp 1 -nographic \
  -drive file=ubuntu-cloud-24.04.ppc64el.qcow2,if=none,format=qcow2,id=drive0,media=disk,cache=writeback,discard=unmap \
  -device virtio-blk,drive=drive0,bootindex=0 \
  -device virtio-rng-pci \
  -netdev user,id=netdev0 -device virtio-net-pci,netdev=netdev0,id=net0

-netdev user also takes QEMU_NETDEV_USER_EXTRA, which allocate sets to forward SSH (image-garden:1107), and the pkgproxy bridge when one is in use; see the .run script.

for contributors

In image-garden's CI

JobSystemsTimeoutRecorded time
ppc64el: [ubuntu 1/2]14.04, 16.04, 18.04, 20.04, 22.0480m25.9 minutes; up to 9.4 for one
ppc64el: [ubuntu 2/2]24.04, 25.04, 25.10, 26.04, 26.1085m28.5 minutes; up to 9.8 for one

Both run on x86\_64 runners tagged qemu-emulated with ARCH: ppc64el, boot each image once with -smp 2 and -m 1024, 40 minutes per system, allow_failure: true (.gitlab-ci.yml:663-690, .gitlab-ci.yml:982-1002).

Porting notes (derived)

  • Byte order is the same as on x86\_64: test big-endian code on s390x.
  • Ubuntu's ppc64el kernels use 64 KiB pages: ask sysconf(_SC_PAGESIZE), do not assume 4096.
  • Plain char is unsigned on POWER.

Roads from here

SYSTEMS · distributions

ARCHITECTURES · machines and firmware

RUNTIME · make rules and the CLI

SPREAD · tests

SNAP · snap-only features

  • Snap components — how the snap's per-architecture QEMU components install