Docs: Instance Operations

Mon, 01 Jan 0001 00:00:00 +0000

Sync status

When a VM is maliciously damaged or improperly forced-operated and enters an abnormal service state (for example system hang), administrators need to repair it in the background, sync the VM environment status, and provide system-level service repair. You can also sync the running status when resources are overcommitted. Batch sync status supports selecting VMs on different platforms.

Sync status one

On the VM page, click “More” in the row actions for the target VM, then choose “Sync status”.
Confirm the action.

Sync status in batch

In the VM list, select one or more VM, then click “Sync status” above the list.
Confirm the action.

Start

Start a VM that is in the stopped state. Batch start supports selecting VMs in the “Stopped” state on different platforms.

Start one

On the VM page, click “More” in the row actions for the target VM, then choose “Start”.
Confirm the action.

Start in batch

In the VM list, select one or more VM (stopped), then click “Start” above the list.
Confirm the action.

Stop

Stop a VM that is in the running state. Batch stop supports selecting VMs in the “Running” state on different platforms.

Currently only pay-as-you-go VMs on Alibaba Cloud and Tencent Cloud support stop without charging.

After stop, CPU and memory are released and billing for CPU and memory stops; associated disks, images, and public bandwidth (if billed) continue to be billed

After stop, the instance CPU and memory are no longer reserved, so starting the instance again may fail. In that case, try starting again, or try at another time

After stop, ordinary public IPs are released and cannot be recovered; convert them to elastic public IPs before stopping

After stop, elastic public IPs are retained and not released, and are not charged during the stopped period

During the stopped period, many instance operations (such as resize configuration and reinstall OS) may be unavailable; start the instance first if you need those operations

Some instances that do not support stop-without-charge continue normal billing after stop

Stop one

On the VM page, click “More” in the row actions for the target VM, then choose “Stop”.
Confirm the action.

Stop in batch

In the VM list, select one or more VM (running), then click “Stop” above the list.
Confirm the action.

Restart

Restart a VM that is in the running state. The VNC connection is interrupted during restart. Batch restart supports selecting VMs in the “Running” state on different platforms.

Restart one

On the VM page, click “More” in the row actions for the target VM, then choose “Restart”.
Confirm the action.

Restart in batch

In the VM list, select one or more VM (running), then click “Restart” above the list.
Confirm the action.

If “Force restart” is selected, unsaved data in the VM will be lost.

Reset

Restart a VM that is in the running state without interrupting the VNC connection. Only supported for VMs on the OneCloud platform.

On the VMs page, click the “More” button in the Actions column of a VM in the “Running” state, then choose “Instance state - Reset”.
Confirm the operation.

Suspend

Put a VM that is in the running state into hibernation. In the suspended state, the VM saves its current state; services pause without ending, and you can quickly restore the state using Resume.

Currently only VMware VMs support suspend/resume.

Suspend one

On the VM page, click “More” in the row actions for the target VM, then choose “Suspend”.
Confirm the action.

Suspend in batch

In the VM list, select one or more VM (running), then click “Suspend” above the list.
Confirm the action.

Resume

Resume a VM that is in the suspended state to the running state.