Skip to content

AGENTS.md: CPUs, memory and devices stay dynamic #254

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
aledbf merged 1 commit into from
Nov 13, 2026
Merged

AGENTS.md: CPUs, memory and devices stay dynamic #254

Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
6 changes: 6 additions & 0 deletions AGENTS.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -32,6 +32,12 @@ of the two moved, never a target of its own. `docs/log.md` shows what optimising
VM that ever boots from that image. `image/build.sh` asserts each of these on the finished
filesystem.

3. **CPUs, memory and devices stay dynamic.** CPU hotplug up to the machine's ceiling, memory
through virtio-mem and the balloon's free page reporting, and disks attached and detached
while the machine runs: a workspace grows, shrinks and gives memory back without a restart.
Nothing trades any of it for boot time - not a lower ceiling, not a missing device, not a
machine without ACPI. Make what they cost cheaper instead.

**The fingerprint says which checkpoints a machine resumes, nothing more.**
`machine.Spec.Fingerprint` hashes what a resumed guest sees (`Spec.Contract`, the machine type,
the shape, the BIOS's size, the host CPU under `-cpu host`); a resume across two fingerprints is
Expand Down
Loading