-
Notifications
You must be signed in to change notification settings - Fork 0
FAQ
No. XAIOS has its own freestanding kernel, userspace ABI, applications, and filesystems. FreeBSD is its primary reference for portable Unix command and protocol behavior, not its kernel ABI.
No. Programs must be built for the XAIOS ABI and packaged into the image.
The ARM and x86_64 QEMU core-OS paths boot and provide processes, threads, filesystems, IPv4/IPv6, SSH/SFTP, local and remote shells, administration, storage lifecycle operations, and diagnostic applications. See Home and Applications.
Provision an Ed25519 public key, boot QEMU, then run:
ssh -p 7788 -i build/local-ssh/admin admin@127.0.0.1See Getting Started and Networking and SSH.
No. Default and release images contain no built-in password. Password login is an explicit development-image option and release builds reject it.
No. The declared QEMU core-OS correctness gate passes, but physical hardware, independent security review, production key management, and real-model parity remain open. See Current Limitations.
Not yet. Model-v2, architecture adapters, backend interfaces, and scalar packed kernels are foundations. No official checkpoint has completed tokenizer, logits, deterministic decode, and physical-hardware acceptance.
QEMU provides reproducible boot, ABI, fault, protocol, CPU-count, and device correctness tests on ARM and x86_64. It cannot establish physical performance.
Only in Project Tracker. GitHub issues may hold discussion, but they are not a second status authority.
XAIOS is a freestanding Unix-like operating system. QEMU and VMware results are correctness evidence, not physical performance or production certification.