Repository navigation
Guest architectures
Nido 4.10.3 - Seamless Wings provides native guest selection by default, explicit CLI --arch, MCP arch and a TUI Arch selector. Release binaries cover Linux, macOS and Windows on both AMD64 and ARM64.
ARM64 QEMU/UEFI profiles, architecture-aware caches and templates preserve each guest ISA. Native acceleration requires matching host/guest ISA and an available KVM, HVF or WHPX backend. Foreign guests use TCG software emulation.
Version 4.10.1 makes private UEFI variables writable even when firmware/template seeds are read-only, preserving the original seed and repairing existing private copies on start. No further metadata migration is required after 4.10.0.
Upgrade from the earlier AMD64-only versions: stop VMs and close old Nido clients, update normally and reopen clients. From 4.10.3, self-update and binary installers prepare state automatically; an older updater/package manager finalizes the same conversion on the new binary's first invocation. No manual migration command is required. The conversion saves original metadata and preserves disks, backing paths, identities, ports and credentials. The Go module remains /v4.
Read the versioned architecture guide for catalog variants, dependencies, automatic state preparation and recovery and physical hardware qualification limits. Operational instructions stay in the repository with the implementation. MCP remains local stdio, with opt-in event notifications; Glama provides discovery and local setup instructions.
Self-update in 4.10.2 allows a 15-minute archive transfer and resumes interrupted bodies within the same invocation, while preserving the installed executable on failure. VM disks and state remain intact. Older clients still have their old timeout: use the versioned upgrade instructions if bootstrapping times out. Current 4.10.x metadata needs no rewrite; a one-time completion marker makes later starts skip conversion.
The automatic transition was verified from the official 4.9.0 binary through its real self-update to 4.10.3: original metadata and disk/backing identities preserved, followed by guest SSH and a persisted sentinel after restart. Concurrent CLI/MCP starts and recovery after killing a conversion mid-transition also passed. Legacy VMs must be stopped before conversion; Nido refuses live legacy PIDs without shutting VMs down.