After a host reboot
Updated
A host reboot stops everything. When Virtainer Free starts again it rebuilds machines from what it recorded before, so a reboot is an interruption rather than a rebuild.
What comes back
Section titled “What comes back”| Before the reboot | After |
|---|---|
| Running | Rebuilt and started, keeping its MAC address, so the guest keeps the same IP |
| Created but never booted | Rebuilt, not started, ready to boot |
| Powered off | Left off |
| Stopped by you | Never started automatically |
A reboot is not a power cut. Before the host goes down, Virtainer Free asks every running machine to shut itself down. Windows VMs get up to 120 seconds each, within a 150-second total shutdown budget. Machines still running when their budget expires are powered off, so a guest still writing may need its filesystem checked afterwards.
The host preserves the intent to restore running VMs even if a VM reboot was in the middle of a stop-and-boot fallback when shutdown began. Machines you explicitly stopped or deleted are not restarted, and one-shot AppVM jobs must be rerun manually.
Turning off VM autostart in Settings changes the first row only: machines that were running come back stopped, and you start them when you are ready. Everything else behaves the same.
Checking what happened
Section titled “Checking what happened”The agent’s log records the startup reconcile and recovery passes, including how many machines were attempted, recovered, failed, or skipped. Read it in Logs and diagnostics, under Run log.
When something did not come back
Section titled “When something did not come back”| What you see | What to do | Why |
|---|---|---|
| A machine is Failed | Read its failure reason, fix the host problem, boot it again. Delete and recreate if it will not recover | Rebuilding it failed partway |
| Machines skipped, disk missing | Restore the machine from a backup and boot, or delete the record and recreate | The disk file is gone, and no empty disk was put in its place |
| Everything running is now Powered off | Boot what you need, or turn VM autostart back on | VM autostart is off. The setting working, not a fault |
| Running but guest unreachable | Open its console and read the boot output | The guest did not come up on the network. Whether it is ever marked failed depends on the host being able to observe it (see below) |
| Unexpectedly Stopped | Boot it again | It was reaped at startup as an orphan of a previous failed start |
A host that does not sleep
Section titled “A host that does not sleep”The host image ignores the lid switch, the sleep and hibernate keys and idleness, and masks every sleep target, so a laptop or small box with a lid keeps running machines when it is closed. A suspended host looks like a dead one from outside: its machines freeze, its network goes quiet, and its watchdog cannot rescue it. The power button still shuts the host down normally. A host installed before this image picks it up with an OS update.
What is not covered
Section titled “What is not covered”Recovery only restores this host’s machines. Moving workloads to another host after a failure is clustering, which belongs to Virtainer Pro, not to Free.