-
Notifications
You must be signed in to change notification settings - Fork 0
Hardware Support
| Target | Current status |
|---|---|
QEMU AArch64 virt
|
Complete core-OS correctness target with UEFI, SMP, GIC, VirtIO, SMMUv3 gates, filesystems, network, SSH/SFTP, and userspace. |
QEMU x86_64 q35
|
Common kernel/userspace service parity with AArch64, including ACPI/MADT AP startup, xAPIC, XSAVE/FXSAVE, PCI VirtIO, network, SSH/SFTP, storage, and userspace. Block MSI-X setup is exercised, with bounded polling when a post-reset edge is not delivered. |
| VMware Fusion ARM64 | Limited boot path through the UEFI/GRUB compatibility stage to /init; no VMware NIC, persistent-disk driver, or multi-vCPU discovery. |
QEMU CPU-count gates cover 1 through 256 emulated CPUs and a focused 130-CPU NUMA case. Hosted cpuset tests cover CPU IDs beyond 4,096. These checks prove dynamic sizing and ABI behavior, not physical scaling or performance.
The x86_64 path starts MADT-discovered application processors. QEMU service parity with AArch64 is complete for the declared common core-OS scope.
- AArch64: scalar baseline, NEON context handling, and experimental packed NEON kernel interfaces. SVE/SVE2 remain capability-gated future work.
- x86_64: CPUID/topology discovery, AVX2 packed-kernel interfaces, XSAVE state, and conservative FXSAVE fallback. AVX-512, VNNI, and AMX production backends remain incomplete.
- NUMA: runtime-sized node and CPU metadata exists; physical SRAT/SLIT/HMAT placement and bandwidth validation remain open.
No current QEMU or VMware result establishes physical Apple Silicon, Intel desktop, Xeon, NVMe, NIC, SMMU/IOMMU, thermal, power, or performance support. Physical qualification requires boot logs, device inventory, correctness gates, and immutable benchmark artifacts from the actual machine.
See VMware Fusion, Testing XAIOS, and the single Project Tracker.
XAIOS is a freestanding Unix-like operating system. QEMU and VMware results are correctness evidence, not physical performance or production certification.