CPU architecture support
The Solnix OS is a supported distribution of illumos aimed at four CPU
targets — x86_64, aarch64, RISC-V, and SPARC — across both
server and desktop use, and optimized for virtualized hosting on the major
cloud platforms (AWS/EC2, Microsoft Azure, Google Cloud, and the rest). That
is the design target; this page states current support honestly — the table
reflects reality, not aspiration. Only x86_64 is a working primary target; the
others are at various stages of bring-up. The desktop is x86_64-only: COSMIC runs
on one Intel laptop, and there is no graphical install image yet. This page gives
the status of each CPU target, what “bring-up” means for it, and how
cross-compilation fits in.
The four targets
| Arch | Platform tuple | Status | Cache | Phase |
|---|---|---|---|---|
| x86_64 (amd64) | x86_64-solaris | Primary target | live | 1 |
| aarch64 | aarch64-solaris | Native builder (EC2 Graviton) builds packages; boots on EC2 Nitro VMs. No Rust or Go target, so no desktop | live | 3 |
| SPARC v9 (sun4u) | sparcv9-solaris | sun4u: reaches SMF under QEMU (not a clean boot); Nix builds on a sun4u host. No builder; sun4v not started | live | 4 |
| RISC-V | riscv64-solaris | illumos riscv64 boots under QEMU with a ZFS root and SMF, and Nix runs in the guest; No builder or cache yet | none yet | 5 |
amd64 first, always. No phase starts before the previous phase’s gate is green. This is the same honesty stance the binary cache takes: platforms without a builder yet appear as “no objects yet,” never as coverage that does not exist.
What each status means
x86_64 (amd64) — primary
The reference platform. illumos-gate builds natively on amd64, the seed toolchain is extracted here, and this is where the Nix-native stdenv comes up first. Everything in the roadmap is validated on amd64 before any other arch starts. If a Solnix feature works anywhere, it works here first.
aarch64 — native builder running
The work is not “port illumos to ARM from scratch” but “integrate the out-of-tree illumos aarch64 port and bring a Nix-native stdenv up on it.” A native aarch64 builder (an EC2 Graviton host) now builds packages, and 84 aarch64 packages it built are signed and in the cache. They are built natively on illumos aarch64, not cross-built from Linux. The image boots on EC2 Nitro VMs (c6g). Rust and Go have no aarch64 illumos target yet, so anything written in them (including the COSMIC desktop) does not build for aarch64.
SPARC v9 (sun4u) — revive
SPARC support exists in illumos-gate but has bit-rotted from disuse. The work so far is on sun4u: under QEMU, illumos gets as far as SMF (not a clean boot yet), and Nix 2.24 builds on a sun4u host. sun4v work has not started. The cache holds 4 sparcv9 recipe builds plus some older imported paths; there is no SPARC builder in the build fleet. This is later in the roadmap (Phase 4) because it is revival work, not integration.
RISC-V
There is an illumos riscv64 port (the n-hys illumos-gate port). It boots under QEMU with a ZFS root and SMF, and ssh and Nix 2.24 run in the guest, which makes it a prototype build host; it is not in the build fleet. This is the furthest-out target (Phase 5): there is no riscv64 builder and nothing in the cache yet.
Cross-compilation notes
There are two distinct build directions and they matter for how the cache is populated per arch:
- Linux → target (cross). nixpkgs can cross-compile many packages from a Linux builder to a Solaris target tuple. It does not cover the load-bearing base or anything that needs a native illumos build — the gate does not cross-build from Linux (see How Solnix is built).
- Native (illumos host). The seed toolchain and the load-bearing
pkgs.solnix.*world must be built natively on an illumos host of that arch. This is the gated part: an arch is only fully supported once a native builder for it exists.
So “Cache: live” means signed paths for that arch are in the cache, not that the arch is fully covered. For aarch64 they are native builds from the aarch64 builder; for sparcv9 they are a few recipe builds plus older imported paths. Full coverage arrives with a native builder for each arch, and the cache never advertises coverage it does not have.
Further reading
- How Solnix is built — how the platform tuple, seed toolchain, and native stdenv fit together.
- The binary cache — per-arch coverage and how artifacts are distributed.
- Contributing — every arch needs a builder; this is the most direct way to help.