Skip to main content
Updated May 8, 2026 Reinstall replaces the VM’s OS disk with a fresh OS template. The VM keeps its ID, public IPv4, attached volumes, and CPU/RAM/disk specs — everything else on the OS disk is destroyed.

Before you start

Reinstall is destructive. The OS disk is wiped and all snapshots and backups of this VM are deleted. If you want to keep anything, take a snapshot to attached volumes or push to Object Storage first.

What’s preserved vs reset

The VM is unavailable during the rebuild. Typical duration is a few minutes; the actual time depends on:
  • Template size — bigger images (Windows Server, Marketplace apps with bundled software) take longer to copy than minimal Linux base images
  • Hypervisor I/O — busier hosts copy slower; quieter ones copy faster
  • Disk size — base disk being wiped and reprovisioned scales with size (a 25 GiB disk is faster than a 480 GiB one)
  • First boot work — cloud-init / sysprep / OS first-boot configuration runs after the disk lands; some templates do more work on first boot than others
There’s no published SLA for reinstall duration. For reference: a fresh Ubuntu 24.04 on a 25 GiB disk typically completes in 1–3 minutes; a Windows Server 2022 on a 50 GiB disk typically takes longer due to sysprep. Plan for up to 10 minutes in worst-case scenarios so you don’t get nervous mid-rebuild. See Storage model for the survival matrix across reinstall, factory reset, and delete.

Two ways to start

a. VM detail page → Actions tab → Change OS

Open the Actions tab on the VM detail page. Under System Operations find the OS Reinstallation card and click Change OS.
Actions tab on VM detail page with the OS Reinstallation card and Change OS button

b. Instance list row → Actions menu → Reinstall OS

In the Instances list, open the row’s menu and pick Reinstall OS. Both paths open the same 3-step dialog.
Row Actions menu showing Reinstall OS option

Step 1 — Select OS

Pick the new OS template (or stay on the same one for a clean reinstall) and the version.
Reinstall Step 1: OS grid with Ubuntu, Fedora, Debian, CentOS, AlmaLinux, Rocky Linux, FreeBSD, Alpine Linux, openSUSE, and a Version dropdown
Same OS lineup as VM creation. Switch between Linux distros, jump from Linux to Windows, or stay put for a clean reinstall. The Marketplace tab is also available for pre-built application images.

Step 2 — Authentication

Pick how you’ll log in to the rebuilt VM.
Reinstall Step 2: three authentication options — SSH Key, Set Password, Email Me Password

Step 3 — Confirm

Review what’s preserved and reset, tick the acknowledgement box, and click Reinstall OS.
Reinstall Step 3: confirmation listing preserved/reset items and the 1-5 minute unavailability warning

After reinstall

  • The VM transitions provisioningbootingactive — typically a few minutes; up to ~10 for larger templates / Windows / large disks.
  • Public IPv4 is unchanged — DNS records still point at the right place.
  • Connect with the new credentials (your SSH key, the password you set, or the emailed password).
  • Attached volumes are still attached but may need re-mounting; the new OS won’t have your old /etc/fstab.

Reinstall vs other options

Next steps

Create a snapshot

Capture state before reinstalling.

Connect via SSH

Reconnect after the rebuild.
Last modified on May 9, 2026