VM statuses

List of statusesList of statuses

A VM can have one of the following statuses:

• PROVISIONING: Yandex Cloud is allocating resources to the VM.
• STARTING: VM is starting.
• RUNNING: VM is running.
• STOPPING: VM is stopping.
• STOPPED: VM is stopped.
• RESTARTING: VM is restarting.
• UPDATING: VM is being updated.
• CRASHED: VM crashed and will be restarted automatically.
• ERROR: Fatal error; the VM cannot be recovered.
• DELETING: VM is being deleted.

VM connection statuses to Cloud BackupVM connection statuses to Cloud Backup

You can view info on the status of a VM connection to Cloud Backup using the management console, on the VM list page in Compute Cloud. The following statuses are available:

• Connected: Cloud Backup is connected to the VM, backups are being created under the specified policies, the Cloud Backup agent is online.
• No backup policy: Cloud Backup is connected, but no policies are set up, and backups are not being created.
• Failed: Agent is offline, or agent registration failed.
• Not connected: Cloud Backup is not connected to the VM.

You can view the VM connection status and learn more about the VM backup in the backup log.

Operations on a VMOperations on a VM

The diagram below shows only switching statuses under normal operation during the following actions:

• Creating a VM.
• Stopping and starting a VM.
• Restarting a VM.

The diagram does not show the following intermediate statuses:

• UPDATING for updating.
• DELETING for deleting.
• CRASHED and ERROR for error situations.

CreatingCreating

A newly created VM gets the PROVISIONING status. This is when computing resources are allocated to the VM: the number and capacity of vCPUs, the amount of RAM. It also gets an IP address, and its disks are created.

With that done, the VM automatically starts and enters the STARTING status.

Once successfully started, it will get the RUNNING status, and the operating system will start booting up. After that you will be able to connect to the VM.

Stopping and startingStopping and starting

⁶ When a VM stops, the hypervisor sends a shutdown signal to the VM operating system. The OS has 30 seconds to gracefully terminate all running processes to avoid data loss. When this time expires, the VM's process is forced to stop, and the VM enters the STOPPED status.

At the next start, the VM will go through the same statuses as when it was created: PROVISIONING → STARTING → RUNNING.

RestartingRestarting

When restarting, the VM gets the RESTARTING status. All its computing resources being already allocated, following the restart, the VM will go back to the RUNNING status.

UpdatingUpdating

You can update the VM parameters, such as change its name, regardless of the VM status. Following an update (the UPDATING status), the VM will go back to its previous status.

If you update the metadata, it will be available from inside the VM immediately after the update. You do not need to stop or restart the VM in this case.

DeletingDeleting

When you delete a VM, first all ongoing operations are canceled and stopped, then the VM enters the DELETING status.

When the deletion is complete, the VM disappears from the list of available resources.

ErrorsErrors

There are two error statuses:

• CRASHED: Error; the VM cannot continue to operate.

  If the VM has entered this status, Yandex Cloud will try to restart it. Restart attempts will be repeated until the VM's status changes to RUNNING or ERROR.

• ERROR: Fatal error; the VM cannot be recovered.

  To fix the error, try stopping and re-starting the VM.

  If the ERROR status persists or the VM keeps getting the CRASHED status, contact support or create a new VM.