ISOs, boot order and reinstall

The ISO library, customers' own ISOs, ISO drives and boot order on a server, installing from an ISO, reinstalling a server, and the build log.

Besides images, a virtual machine can be installed from an ISO: an installer disc, booted from one of the server's two CD-ROM drives. ISOs are also how drivers discs (the VirtIO drivers for Windows) and live systems reach a server. Containers have no ISO drives.

The ISO library#

  1. Go to Images and ISOs › Images and open the ISOs tab.
  2. Press Add ISO and fill in:
    • Name, and Slug (the name nodes keep the ISO under; it cannot be changed later);
    • OS type, for the logo (Other for a disc of no system; Windows for a Windows installer, which matters for Windows templates);
    • Link: where a node downloads it, http:// or https://, at most 16 GB;
    • SHA-256, optional: a download that does not match is thrown away.
  3. Save. Every online node downloads the ISO ahead of time, after the images, and checks it is an ISO image (ISO 9660 or UDF), whatever the file is called. The list shows "Ready on N of M nodes", as for images (Images on every node).

php artisan vmstack:seed-images adds the VirtIO drivers for Windows ISO (virtio-win). Keep it enabled if you sell Windows.

A disabled ISO is not offered for new inserts, stays in the drives it is in, and is removed from the nodes once no drive holds it. An ISO in a drive cannot be deleted. Every enabled library ISO is offered to every account that may use ISOs (the plan's Insert ISOs and boot from them switch).

Customers' own ISOs#

Off by default. When on, an account can bring an ISO by link for its own servers.

  1. Go to System › Settings and find Customers' ISOs.
  2. Turn on Let accounts bring their own ISOs by link and set Kept for (hours) (default 2, 1 to 72), Largest ISO (GB) (default 8, at most 16), ISOs per account (default 2, counted across all nodes) and Who may (every account, resellers and their users, or accounts that may create servers).
  3. Fill in This panel's public addresses: the IPv4 and IPv6 addresses the panel is reached at, one per line. Nodes refuse a link that leads there. With none set, every node refuses customers' links unless its own configuration names the panel (install.sh --upgrade --panel-ip <address>).
  4. Save.

Customers also need the plan's Own ISOs by link switch. The customer then uses Use my own ISO in a server's ISO drives, gives the link (http or https on port 80 or 443, no user name or password, a server on the internet), an optional SHA-256 and the drive, and presses Download and insert. The node checks the link itself: every address the host resolves to must be public, at most 3 redirects are followed with the same checks, and nothing private (loopback, private ranges, the node's own addresses, the panel, the node's IP blocks) is ever reached.

The ISO belongs to the server's owner and node: it is offered in that account's servers on that node only, with its time left. Ten minutes before it expires the drive panel warns; at expiry the node ejects it from every drive and deletes it, and a server that booted from it boots from its disk again. An own ISO that no drive holds any more is deleted at once.

Administrators see customers' ISOs on the ISOs tab with owner, node and time left, and can press Delete now.

ISO drives and boot order#

On a virtual machine's Storage tab:

  • ISO drives has two drives, CD-ROM 1 and CD-ROM 2. Insert an enabled ISO, or Eject. This works on a running server. The first use of an ISO on a node may download it first.
  • Boot sets the Boot order: the device tried first (hard disk, CD-ROM 1, CD-ROM 2 or network); the others follow in that order. It is applied with the hardware settings by Apply and restart (a stopped server: Apply, used at its next start).
  • Boot once from a device, with Set: the next start after a shut down or power off boots from it, then the server goes back to its boot order. The server is not restarted for it, and a reboot from inside the system does not use it.

A server made before ISO drives existed gets them at its next power off and start; until then the page says so.

The Settings tab holds the rest of the hardware: Network card (VirtIO, Realtek 8139, Intel PRO/1000), Disk driver, the Advanced options (APIC, ACPI, PAE, tablet input device), and for administrators Firmware (BIOS, UEFI, UEFI with Secure Boot), TPM 2.0 and Windows optimisations. Nothing changes until Apply and restart.

Warning: Servers installed from the standard images have VirtIO drivers only. Another network card makes them lose their network; another disk driver stops them from starting. UEFI needs the q35 machine type and ACPI on; a system installed for BIOS may not start under UEFI.

Install a server from an ISO#

  1. On Create server, under Install from, choose ISO.
  2. Choose the ISO for ISO in CD-ROM 1, and optionally ISO in CD-ROM 2 (for example the VirtIO drivers a Windows installer asks for).
  3. Choose the plan or size as usual and create the server.

The server starts with an empty disk and the ISO in CD-ROM 1, booting from it. Nothing is set up inside it: no root password, no SSH keys, no network. Open the Screen console (Console) and install the system by hand. The server's Overview shows Set up inside the installer: the address, netmask and prefix, gateway and DNS servers to type in, each with a copy button. A routed address whose gateway is outside its subnet needs an on-link route; the panel says how.

When CD-ROM 1 holds a Windows ISO and CD-ROM 2 is empty, the panel puts the VirtIO drivers ISO in CD-ROM 2 and gives the server Windows optimisations and the tablet. Image minimums do not apply to ISO installs.

Reinstall a server#

Reinstalling writes a new system on the server's first disk. It keeps the server's id, addresses, size and owner; it counts against no limit.

  1. On the server's Manage tab, under Reinstall, press Reinstall.
  2. Choose what to Install from: an Image, an Application, or an ISO (with CD-ROM 1 and 2).
  3. Set the Hostname, the root password (a new one is generated unless you type one), Allow SSH login with the password, SSH keys, and the Recipes to run at first boot.
  4. Optionally turn on Take a snapshot first: the reinstall then starts once the snapshot is taken, and nothing is reinstalled if it cannot be.
  5. Type the server's name under Confirm and press Reinstall server.

Warning: Everything on the server's first disk is lost: the system, the files, the databases. Extra disks are kept as they are and stay attached.

Who may reinstall: administrators, the owner's reseller, and the owner (when the plan's Reinstall switch allows it). A plan's Reinstall limit caps how many reinstalls a server gets per day, week or month; administrators are not held to it.

A reinstall from an image takes the image's firmware and TPM, and puts the network card and disk driver back to VirtIO; the form says so when the server has others. If the node cannot prepare the new disk (the image does not download, the checksum does not match, no space), the old disk is left in place, the server is started as it was, and the page says "The server could not be reinstalled. It was left as it was."

The build log#

Every create and reinstall keeps a build log, for administrators. It is linked from the server's Overview (Build log, the latest build) and from the create or reinstall task's page.

The log shows:

  • Steps: what the node did, in order, with the time, outcome, duration and message: reserving the address, fetching the image (or "already on this node"), the checksum, the disk copy and resize, each ISO, the first-boot seed, the definition, the network, the start. A failure carries the error output of the tool that failed. Passwords, keys and the seed's contents are never in it.
  • Inside the server: the steps a one-click application or recipe reported from inside the server (One-click applications).
  • First-boot output: what the server printed on its serial port when it first started, fetched once, ten minutes after a successful build. Fetch again reads it anew while the panel still has the server.

Logs outlive the server. They are kept for the days set for Build logs under System › Settings › Logs, then deleted once a day.