Superclouds
Create account

Manage machines

Resize, stop, start, open the console of, image and terminate a machine.

Everything you do to an existing machine starts from its Action menu, on its card or its row in Super MachinesMachines. The menu only lists what is possible in the machine's current status, so if an item is missing, check the status first (see Statuses).

You want toUseAvailable when
Add disk spaceEdit DisksizeRunning, Stopped, Paused
Change memoryEdit MemoryRunning, Stopped, Paused
Change vCPUsEdit VCPURunning, Stopped, Paused
Power offStopRunning, Paused
Power onStartStopped, Paused
Recover a stuck machineForce StartStopped, Paused, Creating, Starting, Updating, or a failed status
Open its screen in the browserGo to ConsoleRunning, Paused
Save it as a reusable imageBuild as Custom ImageRunning, Paused
Delete itTerminateRunning, Stopped, Paused

A Terminated machine only offers View.

Resize a machine

You can give a machine more disk, and change its memory and vCPUs up or down. The limits come from your Tier and from what is free in the region; if a size is too big, the console shows the reason and nothing changes.

Change memory or vCPUs

  1. Open Super MachinesMachines and select the prefix.
  2. Open the machine's Action menu and click Edit Memory or Edit VCPU. You can also open the machine, go to the General tab and click Edit next to Memory or VCUPs.
  3. Set the new value. Memory (MB) moves in steps of 512 MB with − and + (minimum 128 MB). vCPUs moves in steps of 1 (minimum 1). You can also type a value.
  4. Leave Live resize (no restart) ticked to resize without a restart where possible. Untick it if you want a clean stop, resize and start.
  5. Click Modify.

The message tells you how it went:

  • Successfully resized memory (live, no restart) or Successfully resized vCPUs (live, no restart): the change is applied and the machine kept running.
  • Successfully resized memory (VM restarted) or Successfully resized vCPUs (VM restarted): a live change wasn't possible, so the machine was restarted to apply it. Anything running inside it was interrupted.

While the change is applied the status may show Updating. The list reloads on its own.

A live resize can still restart the machine

With Live resize (no restart) ticked, the console falls back to a restart if the operating system can't take the change live. Resize at a quiet time if a restart would hurt.

Add disk space

The disk can only grow

You can't make a disk smaller again. Adding space can briefly interrupt the machine, so plan for a short interruption.

  1. Open the machine's Action menu and click Edit Disksize.
  2. Check Machine Name and Super Id at the top of the Disksize dialog.
  3. Use + to add space in GB, or type the new size. The field starts at the current size.
  4. Click Modify.

You'll see Successfully resized. The list doesn't reload by itself: click Refresh to see the new size.

If you type a size smaller than the current one, a browser message says Can not go less then NGB disksize. (N is the current size) and the value goes back to the current size.

The extra space is added to the disk. Depending on the operating system, you may need to extend the partition and file system inside the machine before you can use it.

Stop and start

There is no restart button. To restart a machine, stop it, wait until it shows Stopped, then start it.

Stop a machine

  1. Open the machine's Action menu and click Stop.
  2. Check the Super Id and Machine Name in the Warning! dialog: Are you sure you want to stop machine?
  3. Click Stop.

The list reloads and the machine becomes Stopped. Its disk, IP addresses and settings are kept. Save your work inside the machine first: stopping is like switching off the power.

Start a machine

  1. Open the machine's Action menu and click Start.

There is no confirmation. The machine goes to Starting and then Running. Click Refresh if the status doesn't change after a minute.

If a machine is stuck

If a machine stays in Creating, Starting or Updating for a long time, or shows Failed to provision or Failed to process, use ActionForce Start. It sends the start command again and runs straight away without a confirmation. Failed machines are hidden by default: click Clear in the filter bar to see them. If it still doesn't start, check the Logs tab (see Logs) and contact support with the Super Id.

Open the console

The console shows the machine's screen in your browser, as if a monitor and keyboard were plugged in. Use it to sign in when SSH or remote desktop isn't working, for example after a network change.

  1. Make sure the machine is Running or Paused.
  2. Open its Action menu and click Go to Console.
  3. Sign in on the screen that opens with the machine's user name and password. The password is in the General tab of the machine's details.

The console opens in a new browser tab. If nothing opens, your browser blocked the pop-up: allow pop-ups for this site and try again.

Console sessions are short: about three minutes after you open one, the console closes it on its own, even if the tab is still open. To keep working, click Go to Console again. If you see an error instead of a new tab, wait a moment and try again.

Build a custom image

A custom image is a copy of a machine's disk that you can use to create new machines with the same software and settings already in place.

  1. Make sure the machine is Running or Paused, and set up the way you want new machines to start.
  2. Open its Action menu and click Build as Custom Image.
  3. In Build Machine As Image, type an Image Name you'll recognise, for example web-base-2026-10.
  4. Click Build Custom Image.

You'll see Successfully build. The image may take a few minutes before it appears in the image list.

To use it, start a new machine (see Create a machine), click Browse Images, set the first filter to CSI and click Select on your image. The form then shows Using Custom Image (CSI) with the image's name and id.

Clean up before you build

Anything on the disk goes into the image, including files, saved passwords and keys. Remove what new machines shouldn't have before building.

Terminate a machine

Terminating can't be undone

Terminating deletes the machine and its disk, and the console has no way to bring it back. Copy anything you need first, or build a custom image to keep its setup.

  1. Open the machine's Action menu and click Terminate.
  2. Check the Super Id and Machine Name in the Warning! dialog: Are you sure you want to terminate machine?
  3. Click Terminate.

The list reloads and the machine disappears, because terminated machines are hidden by default. To see it again, click Clear in the filter bar. Its status is Terminated and only View is available.

Troubleshooting

  • The item I need isn't in the Action menu. It isn't possible in the current status. For example, stop isn't offered on a stopped machine, and the console needs a running one.
  • "unauthorized" or "unable to process request" The request was rejected: your role may not allow it in this prefix, a size may be over your tier's limit, or your session expired. Sign in again, or ask an administrator (roles).
  • The new size doesn't show. Click Refresh.