← Production Guide · Compute operations
PG-35 · After a reboot, VMs stay off?¶

Operational lesson. A reboot brings back what is written down. Nova does not restart guests by default.
The memo as text¶
Situation. A rebooted compute answers again, but its instances stay SHUTOFF, or run without network while Nova shows ACTIVE.
First checks (read-only):
- Instances, once nova-compute is up:
openstack server list --all-projects --host <host> --long - Kolla units: did all come back?:
systemctl list-units 'kolla-*' --state=failed,inactive,activating - Does Nova resume guests?:
grep -rn resume_guests_state /etc/nova/ - Interfaces up, expected MTU?:
ip -br link ; ip link show <tunnel-if> | grep -o 'mtu [0-9]*'
Think before acting:
- ⚠️ State-changing. Check with the owner before starting a
SHUTOFFinstance: one stopped on purpose looks the same. - ℹ️ Know this. Until
nova-computeis up and has synchronised, Nova still shows the instancesACTIVE, from before the reboot.
Go deeper¶
This memo is a memory aid. The procedure, with every command, its risk warning and its limits, is in the runbook:
- After a compute reboot, instances stay SHUTOFF or come back without network ·
lab-verifiedon 2026.1 · highest risk in the page: state-changing - Every instance on one compute loses the network while Nova shows them ACTIVE (ovs-vswitchd down) ·
lab-verifiedon 2026.1 · highest risk in the page: state-changing - Instances of one compute answer ping, but large transfers stall ·
lab-verifiedon 2026.1 · highest risk in the page: state-changing
Where this holds. Written from the Nova 2026.1 configuration reference and Kolla-Ansible 2026.1, which does not set resume_guests_state_on_host_boot. Observed on one all-in-one lab: instances SHUTOFF without the option and resumed with it, and an external interface taken down without a reboot. Not observed: a container that does not come back, a lost MTU, a host address on br-ex, a multinode platform. A failed unit of a service disabled after deployment is not the cause: compare with globals.yml. ML2/OVN and DPDK are not covered.
LinkedIn kit¶
- Image:
dist/pg-35-after-a-compute-reboot.png(1080 × 1350) - Post title: After a compute reboot, the instances stay SHUTOFF. That is the default.
A compute was rebooted for a kernel update. It is back, it answers SSH, nova-compute is up. And every instance on it is SHUTOFF.
Nothing is broken. resume_guests_state_on_host_boot defaults to False: Nova does not start the guests that were running before a host reboot. Someone has to.
The other surprises after a reboot come from the same place: what was never written down.
→ a service that did not come back, and if it is ovs-vswitchd, every instance is cut off
→ an external interface or bond that is DOWN
→ an MTU that was set by hand, months ago, and is back to the default
One caution before starting everything again: an instance that was stopped on purpose before the reboot looks exactly like the others.
Runbook: https://github.com/OzarLand/ozarland-academy/blob/main/docs/runbooks/recovery/after-a-compute-reboot-instances-shutoff-or-without-network.md
More memos: https://github.com/OzarLand/ozarland-academy/tree/main/docs/production
#OpenStack #Nova #Maintenance #CloudOperations #SRE #OzarLand
Source: after-a-compute-reboot.yml. Found an error, or does your platform behave differently? Open an issue or see CONTRIBUTING.