Versions Compared


  • This line was added.
  • This line was removed.
  • Formatting was changed.
Comment: emphasize detaching volumes on shelve


Shutting down, suspending, stopping, or shelving instances


After launching an instance, several options are available under the Actions menu located on the right hand side of your screen.

Report() an instance if these situations occur:

  • you can't connect via SSH or VNC
  • the status never changes from pending to running
  • you receive errors when running or installing software
  • the metrics for the instance do not display
  • the instance exhibits any other unexpected behavior

Image() request - see Customizing and Saving a VM

Suspend( ) an instance to:

  • stop active computing while still consuming system resources
  • safely preserve the state of your instance (though cannot image)
  • preserve your allocation (75% normal usage rate) a
  • NOTE: The IP address is likely to change when the instance is resumed.
  • It may take 1-5 minutes to resume your instance
  • status will change from " Active" to "◉ Suspended"

Shelve() an instance to:

  • free up compute resources for other users 
  • preserve your allocation (0% normal usage rate) a
  • allow for imaging of the instance
  • NOTE: The IP address is likely to change when the instance is resumed.
  • we strongly recommend detaching volumes before shelving.
  • It may take 5-15 minutes to resume (Unshelve) your instance
  • status will change from " Active" to "◉ Shelved_offloaded"

Stop(◼︎) an instance to:

  • stop active computing, consuming fewer resources than a suspend.
  • preserve your allocation (50% normal usage rate) a
  • allow for imaging of the instance
  • NOTE: The IP address is likely to change when the instance is resumed.
  • It may take 1-5 minutes to resume your instance
  • status will change from " Active" to "◉ Shutoff"

Reboot() an instance to send:

  • an 'ACPI Restart' request to the VM that will start the reboot process for your VM
  • a 'Hard Reboot', which will forcibly restart your VM, if it doesn't respond to a 'Reboot'

Redeploy(an instance:

  • to fix intances that show up as 'active - deploy_error'
  • Contact support if your VM returns to the deploy_error state after redeployment.

Delete(x) an instance:

  • Unmount volumes within your instance before deleting the instance or risk corrupting your data and the volume.
  • Your instance will be shut down and all data will be permanently lost!
  • Your resource usage charts will not reflect changes until the instance is completely deleted and has disappeared from your list of instances.


Open Web Shell/wiki/spaces/JWT/pages/17465492(to instance:

  • Web/Browser-based command line interface

Open Web Desktop(to instance:

  • Web/Browser-based VNC Graphical User Interface Desktop


a Currently, actively running instances consume SUs at the rate of 1 SU per cores*hours used. Suspended instances consume 75% and Stopped instances consume 50%. Policy subject to change.

titleShutting down a VM from Linux

If you are going to stop your instance, shut down the VM gracefully and securely. In a GUI environment on Linux, the methods may vary.

Launching a terminal and running the shutdown command as root (or with sudo privileges) should work consistently across Linux versions:

            /sbin/shutdown –h now OR sudo /sbin/shutdown –h now

This will stop all operations, log out other active users on your VM as the system powers down and show your VM as "◉ Shutoff" in Atmosphere once the VM has shut down.

Note that sometimes the Atmosphere interface doesn't update in a timely manner to reflect the true status of the VM. If you have done a shutdown from the console, then do a hard refresh of your browser about a minute after shutdown. This is usually ⌘-R on a Mac and Ctrl-F5 on a PC. Check your browser's documentation to verify.

In general, refresh the browser to verify the VM state if in doubt.


  • Suspend: Instance in-memory state and disk are preserved, such that the instance can quickly be resumed. Network IP addresses will not be maintained. Applications and other processes running at the time of suspend will resume when the instance boots. Note: Some processes may not resume naturally, such as processes involving network connections. This state is comparable to "hibernate" or "sleep" modes in a laptop.

    SUSPENDing an instance continues to consume system compute and storage resources. (75% normal usage rate)

  • Shutdown: Instance operating system is shut-down, in-memory states are not stored, and only disk is preserved for a quick start. This state is comparable to "shutdown" modes in a laptop.

    While the system storage footprint is smaller than that of SUSPEND, but SHUTDOWN continues to consume system storage resources (50% normal usage rate).

  • Shelve: Much like SHUTDOWN, the instance operating system is shut-down and instance in-memory states are not stored. Unlike SHUTDOWN, a disk snapshot is stored to long-term storage and thus will be relatively slower to re-start. HOWEVER, shelving BENEFITS the cloud by no longer consuming computation resources and using far less disk resources. This state does not currently consume service units (0% normal usage rate).

Table: Comparison of Instance state characteristics

Consumes allocationYesYes, 75%Yes, 50%No
Consume system resourcesYesYesYesNo b
Saves running programsYesYescNoNo
Preserves IP addressYesNoNoNo
Time to resumen/a1-5 min1-10 min1-15 min


b Some disk resources consumed

c Some processes, particularly those tied to networking, may not resume fully.