Before you start
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
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.
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.
Step 1 — Select OS
Pick the new OS template (or stay on the same one for a clean reinstall) and the version.
Step 2 — Authentication
Pick how you’ll log in to the rebuilt VM.
Step 3 — Confirm
Review what’s preserved and reset, tick the acknowledgement box, and click Reinstall OS.
After reinstall
- The VM transitions
provisioning→booting→active— 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.