OS images
When you deploy a Cloud VM, the Operating System picker lets you choose where the boot disk comes from. There are four sources.
Sources
The default is Templates. The available images are automatically filtered based on the VM type — Cloud VM templates only appear on the Cloud VM deploy page, and GPU VM templates on the GPU VM deploy page.
Available templates
Templates are grouped by OS family — for example Ubuntu, Debian, AlmaLinux, Rocky Linux, Fedora, and Windows. The families and versions you see depend on the location and VM type.
Pick the family card, then choose a version from the OS Version dropdown — for example Ubuntu 24.04. The selection is confirmed with a Selected: <version> chip below the dropdown.
Windows images require a Windows licence. It’s added automatically under Licences & control panels on the Deploy page, with its monthly price.
How templates are built
IBEE templates are derived from upstream cloud images and hardened with:
cloud-initfor first-boot configuration (hostname, SSH keys, networking).qemu-guest-agentpre-installed for Storage Utilization metrics and graceful shutdown.- The official package repositories for the distribution.
- Security updates current to the image release date.
Default credentials
Once the VM is running, open the VM detail page → Overview → Connection Details for the exact username and sign-in method:
Passwords are shown only to members with write access while the VM is running. Use the eye icon to reveal a password and the copy button to copy it.
To change access later on a Linux VM, open Settings → Access. There you can add or remove SSH keys, turn Password Login on or off, and Reset Password. The VM must be running. For Windows, manage passwords and users inside Windows after connecting over RDP.
Switching OS
Changing the OS of an existing VM isn’t available in the portal yet — Settings → Change OS shows “This section is under development.”
To move to a different OS today, deploy a new VM with the template you need, migrate your data, and delete the old VM. Keep data you want to carry over on a block storage volume, which you can detach and reattach to the new VM.
ISOs, snapshots, and backups
For non-template installs:
- ISOs — see ISOs for adding an ISO, and Custom images for the current console limitation.
- Snapshots — see Restore a snapshot.
- Backups — see Restore from backup.
