guideXOS Server Supported Architectures
Purpose: separate what is in-tree, what is documented, and what still needs stronger proof.
How to read this page
The repository contains a large amount of architecture-related code, but that does not mean every target is equally mature or hardware-tested. This page separates in-tree presence, documented build/emulator support, and hardware-tested confidence so the wiki does not overclaim.
Current status: amd64 is the strongest current path, with multiple additional architectures in active experimental work.
Known gaps: many targets still need broader validation and should not be treated as equally mature.
Back to /Wiki/Server
Architecture status table
| Architecture | Current Status | Notes | Build / Test Coverage |
|---|---|---|---|
| amd64 | Primary | Main public build path, UEFI/QEMU flow, dedicated arch directory, and strongest repo-wide evidence. | build.ps1, run-qemu.bat, UEFI bootloader flow, hosted development emphasis |
| x86 | Supported | Dedicated arch directory and kernel build hooks exist; older build/docs also reference x86-focused flows. | kernel/build-x86.bat, older QEMU/i386 references in repo docs and csproj targets |
| riscv64 | Experimental | Dedicated arch directory and Linux/Windows helper scripts exist. README lists it in the MVP group. | scripts/build-riscv64.sh, build-and-run-riscv64_in_linux.sh, run-riscv64_in_windows.bat |
| arm | Experimental | In-tree architecture directory and hardware-abstraction code exist, but the main build docs do not present it as the stable daily path. | Arch directory present; limited surfaced workflow evidence |
| arm64 | Planned / High Priority | An arm64 arch directory exists, but the hardware support report still labels ARM64 as missing/high priority rather than mature. |
In-tree code exists; current docs still treat maturity as unfinished |
| ia64 | Experimental | In-tree architecture directory, Ski console support, and dedicated helper scripts provide real evidence of intentional work. | scripts/build-ia64.sh, run-ia64_in_linux.sh, README and hardware report references |
| sparc (SPARC v8) | Experimental | In-tree arch directory and serial/framebuffer references exist; your project notes also call out hardware testing on sparc8. | kernel/arch/sparc/, build-and-run-sparcv8_in_linux.sh, project notes |
| sparc64 (SPARC v9) | Experimental | In-tree arch directory plus dedicated scripts indicate active bring-up interest. | build-sparcv9.sh, build-and-run-sparcv9_in_linux.sh, run-sparcv9_in_windows.bat |
| ppc64 / powerpc64 | Experimental | Architecture directory is present and the README includes ppc64 in the extended architecture set. | In-tree code present; no first-class daily build path surfaced in main docs |
| mips64 | Experimental | Architecture directory is present and kernel docs mention Malta/virt-style support ideas, but maturity should not be overstated. | In-tree code present; no prominent top-level build script exposed |
| loongarch64 / loongarch | Experimental | Architecture directory is present with console/graphics hooks, but this is still far from the everyday validated path. | In-tree code present; limited surfaced workflow evidence |
Important notes about confidence
- Best-proven path: Windows-hosted development and amd64 UEFI/QEMU validation.
- In-tree does not equal fully working: many architecture directories are real and meaningful, but they should still be described honestly as experimental until stronger test evidence is surfaced.
- Hardware-tested notes: your project notes mention amd64, x86, and sparc8 as hardware-tested so far. This wiki preserves that as a project-note claim rather than expanding it into a blanket support claim.
- Crosscompiler work: your project notes mention sparc8, sparc64, and ia64 crosscompiler effort. The repo also contains matching scripts and architecture directories, which supports describing those targets as active experimental work.