How to start, stop, edit and delete a VM
This guide covers the common actions on an existing VM from the console: start, stop, restart, changing resources, and deletion.
Prerequisites
- A Hikube account and a project
- An existing VM in Infrastructure > VM Instances
Where to find the actions
| Location | Available actions |
|---|---|
| VM Instances list, Actions menu (⋯) of a row | View details, Start, Stop, Restart, Reload UserData, Edit, Delete |
| Detail page, header | Edit, Delete |
| Detail page, Actions section | Start (stopped VM), Stop and Restart (running VM), Reload UserData (running VM) |
The list also offers a search (Search instances...) and a status filter (All statuses, Running, Stopped).
Steps
1. Stop a VM
- Click Stop.
- Confirm in the Stop virtual machine? dialog: hosted services are interrupted until the VM is started again.
The status changes to Stopping, then Stopped.
Stopping releases the GPU, which may be assigned to another workload. You may not be able to start the VM again right away if no GPU is available afterwards. See GPU unavailable at startup.
2. Start a VM
Click Start. The status changes to Starting, then Running.
3. Restart a VM
Click Restart and confirm in Restart virtual machine?. Applications are temporarily unavailable. The status goes through Restarting.
4. Edit a VM
- On the detail page, click Edit (or Edit in the Actions menu of the list, available only for a Running VM).
- Change the sections you need:
- Resources (CPU / RAM): series and size, GPU;
- Storage: adding disks, detaching data disks;
- Network & Security: public IP, firewall, ports, VPC;
- Advanced Configuration: SSH keys, cloud-init script, Automatic Restart.
- Check the quota summary at the top of the page and click Save.
If the instance type, the disks or the GPUs change, the console shows Restart required: these changes only take effect on the next VM restart. Click Restart to apply them. Otherwise, it shows Instance updated.
If saving is refused, the console shows Incomplete form and names the invalid fields.
The name and the system image cannot be changed.
In the Storage section, the disks the VM already has are shown read-only (Volume Name, Size (GB)):
- the System Disk (Boot) has no action; the console explains why: "The system disk of an existing VM cannot be replaced: the VM boots from it.";
- a data disk only offers Detach disk;
- the New / Existing choice only appears on disks added with Add a disk.
To expand a disk, use its page in the Disks menu (see Resize a disk).
To boot the VM from another system disk, delete the VM: its disks are detached and kept in the Disks menu. Then recreate it with the wizard, choosing Existing on the System Disk (Boot) and then the disk you want; reattach its data disks the same way. Through the API, an update that replaces, removes or moves the system disk of a VM is refused (code 20208).
5. Delete a VM
- Click Delete.
- Type the exact name of the VM, then click Permanently delete.
The VM's disks are detached and remain in the Disks menu, where you can reattach them to another VM or delete them (see Disks).
Verification
The status shown in the list and on the detail page updates without reloading the page. The counters at the top of the list (Active Instances, Stopped Instances, Total CPU, Total RAM) reflect the changes.