Nulx documentation

Virtual Machines

Use the amd64 Nulx image across major VM families without confusing targets with verified support.

One portable amd64 image

Nulx is not a Hyper-V-only operating system. The current hybrid amd64 ISO targets UEFI x86-64 virtual computers, with legacy BIOS available where both the host and image support it. Start with four virtual CPUs, 8 GB RAM, and an 80 GB virtual disk. The documented floor is 4 GB RAM and 40 GB disk.

Current host matrix

A host moves to verified only after one exact ISO hash passes live boot, networking, storage, clean Calamares installation, ISO ejection, direct disk boot, greeter arrival, and installed-session checks.

  • Hyper-V Generation 2 — clean installation and direct boot verified.
  • QEMU/KVM with OVMF — exact-hash live runtime verified; clean installation remains.
  • Proxmox VE — QEMU/VirtIO integration implemented; real host not tested.
  • VMware Workstation, Fusion, and ESXi — Open VM Tools included in the new source profile; real host not tested.
  • Oracle VirtualBox — Debian kernel guest modules available; real host not tested and host-supplied Guest Additions are not bundled.

ARM64 timing

ARM64 is the next CPU architecture and will have its own ISO, packages, boot chain, hashes, signatures, SBOM, and evidence. Implementation starts after the remaining amd64 public Beta gates pass. No ARM64 artifact or support claim exists today.

Safe defaults

  • Use UEFI firmware and keep Secure Boot disabled until its release gate passes.
  • Prefer VirtIO devices on QEMU, KVM, or Proxmox; VMware SCSI and VMXNET3 on VMware; SATA or NVMe plus Intel PRO/1000 for the first VirtualBox test.
  • Treat clipboard, shared folders, drag-and-drop, and host guest-agent commands as trust boundaries.

Use a new empty virtual disk. Never attach a disk containing important data to an unverified installer test.