Suspend, stop, or reset Compute Engine instances

This document explains the behavior, billing, and limitations for suspending, stopping, or resetting a Compute Engine instance. To learn how to perform these operations, see the following instead:

You can suspend, stop, or reset an instance to do the following:

  • Save costs.

  • Perform maintenance.

  • Troubleshoot issues.

  • Free up resources.

You can repeatedly suspend and resume, stop and restart, or reset a running instance until its deletion.

About suspending, stopping, or resetting an instance

Stop, suspend, or reset a compute instance depending on your needs. Specifically:

  • Suspend an instance

    Suspending an instance is analogous to closing the lid of your laptop, and it's useful in the following scenarios:

    • You want to stop paying for the core and memory costs of running an instance, and pay the comparatively cheaper cost of storage, to preserve the state of your instance instead.

    • You don't need the instance at this time, but you want to be able to bring it back up quickly with its OS and application state where you left it.

    To learn more, see Suspending an instance in this document.

  • Stop an instance

    Stopping an instance is analogous to shutting down your laptop, and it's useful in the following scenarios:

    • You no longer need the instance, but you want to remove and reuse the resources attached to the instance—such as its internal IP addresses or Google Cloud Hyperdisk volumes.

    • You don't need to preserve the guest OS memory, device state, or application state.

    • You want to change certain properties of the instance that require you to first stop the instance.

    To learn more, see Stopping an instance in this document.

  • Reset an instance

    Resetting an instance is analogous to doing a reset of your computer, such as when you press a reset button or press and hold the power button. This doesn't perform a graceful reboot, and loss of unsaved data is possible. Resetting an instance is useful in the following scenarios:

    • You want to re-initialize the instance to its boot state to help ensure optimal performance and stability.

    • You want to resume your workload after your guest OS has crashed and is unresponsive, and you have no other options than resetting the instance.

    To learn more, see Resetting an instance in this document.

To see an overview of the differences between stopping, suspending, or resetting an instance, see the comparison table in this document.

Suspending an instance

When you suspend a compute instance, the following happens:

  1. Compute Engine sends an Advanced Configuration and Power Interface (ACPI) G1 Sleeping signal to the guest OS in the instance and sets the state of the instance to SUSPENDING. Then, Compute Engine uses persistent storage to store the following:

    • The guest OS memory

    • The device state

    • The application state of the instance

    The storing operation might take some time to complete, depending on the amount of data to store.

  2. After Compute Engine has completed storing the data, the instance state transitions to SUSPENDED within a few seconds, and the suspend operation completes. All resources attached to the instance, like disks and static IP addresses, remain attached to the instance. However, any ephemeral IP addresses are released unless you promote them to a static IP address.

Unless you resume or delete the instance, the instance remains in the SUSPENDED state for up to 60 days. After that, Compute Engine automatically transitions the instance state to TERMINATED, and the instance loses the preserved guest OS memory, device state, and application state.

Stopping an instance

When you stop a compute instance, or Compute Engine is doing so for a scheduled stop, the following happens:

  1. If graceful shutdown is enabled, then the instance enters the PENDING_STOP state, giving you time to finish running tasks before the shutdown process begins. The instance remains in this state until the graceful shutdown process times out or you manually end it.

  2. Compute Engine sends the ACPI G2 Soft Off signal to the guest OS in the instance, and then sets the instance state to STOPPING. The guest OS shutdown time depends on the instance type as follows:

    • Spot VMs: for Spot VMs and preemptible instances, the shutdown period lasts 30 seconds. This period is the same length as the preemption process.

    • Other instance types: for any other instance types, the shutdown period lasts 120 seconds.

    If a shutdown script is still running at the end of the shutdown period, then Compute Engine forcefully stops it. However, if you initiate the shutdown from within the guest OS, the guest OS shuts down only after any shutdown scripts have finished running.

  3. After the guest OS has shut down, Compute Engine sends the ACPI G3 Mechanical Off signal to instance, and, depending on the operation that is running, does one of the following:

    • For stop operations: Compute Engine sets the instance state to TERMINATED within a few seconds, and the stop operation completes. The instance retains its attached resources, configuration settings, internal IP addresses, MAC addresses, and metadata.

    • For delete operations: Compute Engine deletes the instance and all attached resources within a few seconds.

Resetting an instance

When you reset a compute instance, Compute Engine immediately restarts the instance without sending an ACPI shutdown signal to the guest OS, bypassing any shutdown procedure. When resetting an instance, Compute Engine does the following:

  • Re-initializes the instance to its initial boot state, without modifying metadata or disks.

  • Wipes the contents of the instance's memory.

  • Keeps the instance state to RUNNING throughout the reset operation.

Resetting an instance doesn't change any instance properties. The instance retains its ephemeral IPs, static external IPs, attached disks, machine type, and Local SSD disks (if any).

Comparison table

The following table shows how stopping, suspending, and resetting a compute instance affects the instance and its resources:

Suspend an instance Stop an instance Reset an instance
Billing While an instance is in the SUSPENDING or SUSPENDED state, you don't incur charges for CPU usage. However, you keep incurring charges for the resources attached to the instance until you delete them. While an instance is in the STOPPING or TERMINATED state, you don't incur charges for CPU usage. However, you keep incurring charges for the resources attached to the instance until you delete them. Because the instance remains in the RUNNING state when it's resetting, you keep incurring charges for the instance at the same rate as a running instance.
Instance state SUSPENDED TERMINATED RUNNING
Attached disks Attached disks are maintained and you keep incurring charges for them. Attached disks are maintained and you keep incurring charges for them. Attached disks are maintained and you keep incurring charges for them.
Memory and instance state The guest OS and application state are preserved and restored when the instance is resumed.

You incur charges at a specific rate for storing the preserved data. For more information, see the pricing for suspended instances.		 The instance resets to power-on state and no data is saved. The instance resets to power-on state and no data is saved.
GPUs Not supported.

If a GPU is attached to an instance, then you can't suspend the instance.		 You don't incur charges for GPUs when an instance is stopped.

A GPU that is attached to an instance with a TERMINATED state doesn't count against your project quota.		 You incur charges at standard GPU prices.
Local SSD disks When you suspend an instance, you can choose whether to discard or preserve the data on the attached Local SSD disks.

If you opt to preserve Local SSD data (Preview), then Compute Engine migrates the Local SSD data to durable storage, and you incur charges for the used storage space until you resume or delete the instance. 		When you stop an instance, you can choose whether to discard or preserve the data on the attached Local SSD disks.

If you opt to preserve Local SSD data (Preview), then Compute Engine migrates the Local SSD data to durable storage, and you incur charges for the used storage space until you restart or delete the instance.		 Local SSD disks and their data are maintained; however, resetting an instance can cause data loss or corrupt file systems.
External ephemeral IP addresses Compute Engine releases ephemeral IP addresses when an instance is suspended, and it assigns a new ephemeral IP address to the instance when the instance resumes. To retain an external IP address, promote it to a static IP address. Compute Engine releases ephemeral IP addresses when an instance is stopped, and it assigns a new ephemeral IP address to the instance when the instance restarts. To retain an external IP address, promote it to a static IP address. Ephemeral IP addresses are maintained.
External static IP addresses Static external IP addresses are maintained.

If you reserve a static external IP address and don't assign it to an instance, then you're charged at a higher rate than for static and ephemeral external IP addresses that are in use. For more information, see External IP address pricing. 		Static external IP addresses are maintained.

If you reserve a static external IP address and don't assign it to an instance, or you assign it an instance in the TERMINATED state, then you're charged at a higher rate than for static and ephemeral external IP addresses that are in use. For more information, see External IP address pricing. 		Static external IP addresses are maintained.
Internal IP or MAC addresses Internal IP and MAC addresses are maintained. Internal IP and MAC addresses are maintained. Internal IP and MAC addresses are maintained.
VM metadata VM metadata is maintained. VM metadata is maintained. VM metadata is maintained.

Pricing

The following sections outlines the pricing for stopping, suspending, or resetting a compute instance.

Pricing for suspending an instance

After a compute instance state transitions to SUSPENDING, you no longer incur charges for CPU usage. However, you continue incurring charges for the following resources attached to the instance until you delete them:

  • The instance's memory.

  • Any disks attached attached to the instance.

  • Any static IP addresses assigned to the instance.

Additionally, you might still incur charges for your software license fees. For example, if you suspend Windows Server instances, you don't incur charges for Windows Server license fees. However, you might still incur charges for other types of licenses.

For more information, see the pricing for suspended instances.

Pricing for stopping an instance

After a compute instance state transitions to STOPPING, you no longer incur charges for CPU usage. However, you continue incurring charges for any resources attached to the instance, such as disks and external IP addresses, until you delete them.

For more information, see Instance uptime.

Pricing for resetting an instance

Since the state of a compute instance remains RUNNING when you reset it, you continue to incur charges for the instance at the same rate as a running instance.

For more information, see VM instance pricing.

What's next