Both of these are on the VM's Boot tab, and need the Use rescue mode permission. Each section only shows when there's something available for your VM.
Reinstalling erases the VM's main disk. There's no undo. Copy off anything you want to keep first, and take a backup if you can.
Install an OS
This is the quick way to get a clean system. It usually takes under two minutes.
- On the Boot tab, under Install an OS, choose an Operating system. If one is greyed out, your disk is too small for it, and it says how much it needs.
- Choose a Hostname, or leave it empty to use the VM's name.
- Type
REINSTALLto confirm, and press Erase this disk and install. - Watch the progress bar. Copy the root password when it's shown, as it's only shown once.
The VM restarts into the new system, which takes another minute or two to set itself up.
What stays the same: the VM's private address, its ports, its firewall rules, and any extra disks. What goes: everything on the main disk.
Your SSH keys work for both your new system's normal user and for root. Since the system is new, PuTTY warns you that the host key has changed, which is expected this time.
Some systems need a newer CPU type. If so, the form tells you, and your VM is moved to it and stays there.
Choose your own disk layout
By default, the system takes up the whole disk. To split it up, open Custom disk layout, with one line for each partition: PART, a mount point, ext4 or xfs, and a size in M, G or T. Use all on the last one for the remaining space. Add a SWAP line for swap.
SWAP 2G
PART /boot ext4 1G
PART / ext4 20G
PART /srv xfs all
The boot partitions your VM needs are added for you. LVM isn't supported. The option only appears on systems that can take a layout, which are currently Debian and Ubuntu.
Install from rescue by hand
If you'd rather look around first, start rescue and run:
install
It lists the images available to your VM, then offers the whole disk or a custom layout, which opens in nano. It shows what it's about to erase, and you have to type the disk's name to confirm. Its progress shows on the Boot tab too.
An install you start by hand doesn't restart the VM afterwards, so you can check on things first. Exit rescue when you're ready. If an install fails, the VM stays in rescue and tells you why. The disk may be left incomplete, so try it again.
Boot from an ISO
This attaches an ISO as a CD and starts your VM from it, so you can run any installer or live system.
- Under Boot from an ISO, choose one from the list. Where it's allowed, you can also press Add your own ISO from a web address and wait for it to be fetched.
- Press Boot this ISO and confirm.
- Open the Console tab and choose Graphical (VNC). Installers generally need a screen, not the serial console.
The installer gets its network settings automatically by DHCP, so the VM keeps its usual address. If you ever need them by hand, your private address and gateway are on the Info tab and the project's Network tab.
When you've finished, press Eject and boot from disk, or the VM will keep on starting from the ISO. It's ejected by itself after three days.
Windows
You can install Windows from your own ISO, but it needs your own licence, which you supply and activate. We don't provide one. Tick Also attach the virtio drivers disc where it's offered, as Windows Setup needs it to see the VM's disk and network.
Which one should I use?
| You want to | Use |
|---|---|
| Start fresh with a supported system | Install an OS |
| Choose your own partitions on Debian or Ubuntu | Custom disk layout |
| Run something that isn't on the list | Boot from an ISO |
| Repair a system instead of replacing it | Rescue mode |