pages / Overview
Overview
An AArch64 machine emulator written in Rust. It boots unmodified arm64 Linux, in a
browser tab (WebAssembly, driven by js/armless.js) and natively
(a Rust crate and the armless-run command). The whole machine, devices included, is
Rust; the host only provides time, file contents and the other end of network connections.
snowglobe uses armless to turn Docker images into static sites that restore a running app in the visitor's browser in about a second. armless started as a fork of v86.
What it has#
- CPU: ARMv8-A at EL0 and EL1 with FP/AdvSIMD, AES/PMULL, SHA1, SHA256, SHA512, SHA3, SM3, SM4, CRC32 and the ARMv8.1 atomics (LSE). A software MMU with a TLB, and up to 8 CPUs, one Web Worker or native thread each.
- Execution backends: an interpreter; a JIT that turns hot pages into WebAssembly modules (browser) or host code with Cranelift (native); and, opt in, hardware virtualization (Hypervisor.framework on Apple silicon macOS, KVM on Linux arm64).
- Interrupts and time: GICv2, the generic timer, a PL031 RTC, and a VM generation ID so a restored guest reseeds its random generator.
- Devices: a 16550 UART (
ttyS0), and virtio-pci devices: console (hvc0, with the terminal size), 9p filesystem, and network. - Filesystem: a 9p root built from content-addressed blobs, fetched on first read. Large files are split into chunks, so a read fetches only what it covers.
- Network: virtio-net with an in-process TCP/IP stack. DHCP, DNS and ping are answered
locally. HTTP and HTTPS (ports 80 and 443; HTTPS ends in the machine with a CA the guest
trusts) and WebSockets reach the host as requests to make: a page answers them with
fetch()andWebSocket, a native host with its own HTTP client, proxies included. Other TCP connections become streams the host accepts, refuses, or carries over a WebSocket tunnel. - Snapshots: the whole machine can be saved and restored. A restore streams straight into guest memory, zstd-compressed or not, and a save is handed out in pieces. With free page reporting on, memory the guest freed is zeroed and left out.
- User mode (experimental): a Linux program runs with no guest kernel at all
(
user/): the CPU runs it at EL0 and its system calls are answered by the host. Static and dynamically linked programs, the machine's filesystem, a terminal, threads, processes (fork, exec and wait), pipes, sockets (in memory, unix and loopback TCP and UDP, with the host's network behind them), epoll, poll and select, signals, virtual memory with protections (an address space far larger than the RAM, backed as it is touched), shared memory (System V, POSIX and MAP_SHARED files), users and groups, timers, timerfd, signalfd, pidfds, AIO and the network's interfaces, and snapshots of the running processes work. Go, Python 3.14, DuckDB, Java, Erlang and Elixir, Postgres and Supabase's whole stack run this way from their own images, natively and in the browser (a snapshot made on one restores on the other).