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

VM Reboot Operations

Understanding graceful vs. forced reboots, when to use each, and their impact on running applications.

VM Reboot Operations

What you'll learn: How to choose between graceful and forced reboots and understand their impact on your running applications.

When you need to restart a virtual machine, you have two options: a graceful reboot (also called "soft reboot") and a forced reboot (also called "hard reboot"). Understanding the difference is critical for protecting your data and applications.

Graceful Reboot (Soft Reboot)

A graceful reboot is like politely asking your VM to restart. The operating system receives a reboot signal, allowing it to:

  • Save open files and flush caches to disk
  • Cleanly shut down running applications
  • Complete in-progress database transactions
  • Terminate processes in an orderly fashion

Analogy: It's like telling someone you're leaving in 5 minutes, giving them time to wrap up their work and save everything properly.

Forced Reboot (Hard Reboot)

A forced reboot immediately cuts power to the VM—like pulling the plug on a physical computer. The operating system has no warning and cannot perform cleanup operations.

When to use forced reboot: Only when your VM is frozen, unresponsive, or a graceful reboot has failed. This is your emergency option.

Impact on Applications

  • Graceful reboot: Applications shut down cleanly, minimizing data loss risk. Database transactions complete or roll back properly.
  • Forced reboot: Risk of corrupted files, lost unsaved data, incomplete transactions, and potential file system damage.

Key Takeaway: Always use graceful reboots for planned maintenance and normal operations; reserve forced reboots only for emergencies when the VM is completely unresponsive.