Course contentsShow
← Cloud and Infrastructure
Lesson 88 of 2,9892. Compute FoundationsFree lesson

VM Hibernation

Understanding hibernation vs. stop, memory state preservation, use cases, and provider support differences.

What You'll Learn

You'll learn how VM hibernation differs from simply stopping a VM, why it's useful for faster resumption, and how cloud providers approach this feature.

Understanding VM Hibernation

Hibernation is like putting your laptop to sleep with all your programs still open. When you hibernate a VM, the cloud provider saves the entire contents of the VM's memory (RAM) to disk before shutting it down. When you start it again, that memory state is restored, and your VM picks up exactly where it left off—running processes, open applications, and all.

Hibernation vs. Stop

When you stop a VM (as you learned earlier), the operating system shuts down cleanly, but all memory state is lost. When you start it again, the OS boots from scratch, applications must restart, and you lose any in-memory data.

When you hibernate a VM, the memory contents are preserved to disk. On restart, the OS doesn't reboot—it restores from the saved state, making resumption much faster and maintaining active sessions.

Use Cases for Hibernation

  • Long-running analysis jobs: Pause expensive computations overnight, pay nothing while hibernated, resume instantly in the morning
  • Development environments: Preserve your IDE state, debugger breakpoints, and loaded data between work sessions
  • Pre-warmed applications: Keep applications loaded in memory for faster activation without full boot cycles

Provider Support Differences

Not all cloud providers support hibernation equally. Some require specific instance types, operating systems, or root volume configurations. Hibernation typically requires enough storage space to hold your entire RAM contents. Check your provider's documentation for limitations—hibernation may not work with all instance families or sizes.

Key Takeaway: VM hibernation saves your memory state to disk, enabling faster resumption and preserved application state, unlike a simple stop which requires a full OS reboot and loses all in-memory data.