A server in VMStack is either a KVM virtual machine or an LXC system container. Both are made from a hosting plan, placed on a node of the chosen location, and managed from the same server page. A server is installed from an image, an ISO or a one-click application, and its page shows its state, addresses, usage and tasks, with tabs for storage, snapshots, backups, settings and management.
This chapter covers what you set up once (plans, images, ISOs, Windows templates, applications) and what you do with a server afterwards.
- Hosting plans and creating a server: what a plan sets, and the create form
- KVM virtual machines and LXC containers: what differs, and how to enable containers on a node
- Images: the image library, downloads to nodes, checksums, images made from servers, container images, FreeBSD
- ISOs, boot order and reinstall: the ISO library, customers' own ISOs, installing from an ISO, reinstalling, the build log
- Windows templates: building a Windows Server image in the panel or by hand, licensing and activation
- One-click applications and recipes: the built-in catalogue, custom applications, first-boot scripts
- Disks, CPU limits and GPUs: extra disks, I/O and CPU limits, dedicated CPUs, GPU passthrough
- Snapshots: point-in-time copies on the node
- Rescue and recovery: root password reset, network reconfiguration, the rescue system
- Console: the screen and text consoles
- Upgrades and resizing: moving a server to a larger size
- Moves and live migration: moving a server to another node
- High availability: restarting servers elsewhere when a node dies
Before you create the first server you need an online node with an IP block (Adding nodes, IP pools) and at least one enabled image.
- Hosting plans and creating a serverWhat a hosting plan sets for its servers, how to create one, how placement picks a node, and how administrators and customers create a server.
- KVM virtual machines and LXC containersThe two kinds of server VMStack sells, what each can and cannot do, how to enable LXC containers on a node, and the container-only plan switches.
- ImagesThe image library servers are made from: adding images, downloads to every node, checksums, images made from servers, clones, container images and FreeBSD.
- ISOs, boot order and reinstallThe ISO library, customers' own ISOs, ISO drives and boot order on a server, installing from an ISO, reinstalling a server, and the build log.
- Windows templatesMake Windows Server 2022 and 2025 images for VMStack: the panel's unattended build, the manual way, drivers, UEFI and TPM, licensing and activation.
- One-click applications and recipesOffer control panels, web stacks, databases and tools that install at a server's first boot, write your own applications, and run recipes as root.
- Disks, CPU limits and GPUsExtra disks and their allowance, disk bus and cache, disk I/O limits, CPU limits and weight, dedicated CPUs, and GPU passthrough for virtual machines.
- SnapshotsPoint-in-time copies of a server's disks on its own node, optionally with its memory: plan limits, taking, reverting, expiry and space.
- Rescue and recoveryStart a broken server from a rescue system, reset its root or Administrator password, and write its network settings back into it.
- Console and password accessThe browser console of a server (text on the serial port, screen over VNC), the console relay behind it, and root password and SSH access.
- Upgrading and suspending serversGive a server more vCPUs, memory or disk by plan or by typed sizes, what happens on the node, and how suspending and lifting a suspension work.
- Moving servers and live migrationMove a server to another node offline or live, what travels and what changes, how failures are taken back, and the placement log.
- High availabilityRestart protected servers on another node of the location when their node dies, after their disks on shared storage are confirmed free.
- The server page, power and tasksWhat the server page shows, the power actions, start on boot after a node reboot, and how to follow and cancel tasks on the nodes.