> For clean Markdown of any page, append .md to the page URL.
> For a complete documentation index, see https://docs.ibee.co.in/docs/infrastructure/cloud-vms/os-images/llms.txt.
> For AI client integration (Claude Code, Cursor, etc.), connect to the MCP server at https://docs.ibee.co.in/_mcp/server.

# OS images

> Pick an operating system template for your Cloud VM, or boot from an ISO, snapshot, or backup — and find the credentials to sign in.

When you deploy a Cloud VM, the **Operating System** picker lets you choose where the boot disk comes from. There are four sources.

## Sources

| Tab           | Use it for                                                                           |
| ------------- | ------------------------------------------------------------------------------------ |
| **Templates** | Curated, official OS images maintained by IBEE. The fastest path to a clean install. |
| **ISOs**      | Boot from an ISO image you added under **Tools → ISOs**.                             |
| **Snapshots** | Create the VM from a snapshot captured from another VM.                              |
| **Backups**   | Create the VM from a scheduled backup recovery point.                                |

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-init` for first-boot configuration (hostname, SSH keys, networking).
* `qemu-guest-agent` pre-installed for [Storage Utilization metrics](/docs/infrastructure/cloud-vms/monitoring#storage-and-disk-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:

| VM                                 | How you sign in                                                                                                                  |
| ---------------------------------- | -------------------------------------------------------------------------------------------------------------------------------- |
| Linux, deployed with an SSH key    | **SSH Key Connection** — the username, host, and a ready-to-copy SSH command. Use the private key that matches the selected key. |
| Linux, deployed without an SSH key | **SSH Connection** — the username, host, and password.                                                                           |
| Windows                            | **Remote Desktop (RDP)** — the IP address, the `Administrator` username, and the password.                                       |

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](/docs/infrastructure/block-storage), which you can detach and reattach to the new VM.

## ISOs, snapshots, and backups

For non-template installs:

* **ISOs** — see [ISOs](/docs/tools/isos) for adding an ISO, and [Custom images](/docs/infrastructure/cloud-vms/custom-images#isos) for the current console limitation.
* **Snapshots** — see [Restore a snapshot](/docs/tools/snapshots/restore-a-snapshot).
* **Backups** — see [Restore from backup](/docs/tools/backups/restore-from-backup).

## Related pages

* [Create a VM](/docs/infrastructure/cloud-vms/create-a-vm)
* [Custom images](/docs/infrastructure/cloud-vms/custom-images)
* [SSH keys](/docs/tools/ssh-keys)

> Pick an operating system template for your Cloud VM, or boot from an ISO, snapshot, or backup — and find the credentials to sign in.