Proxmox on a VPS: nested virtualization, guest networking and backups
Proxmox VE is a Debian-based hypervisor: KVM for full virtual machines, LXC for containers, a web panel, clustering and built-in backups. It is usually installed on a dedicated server, where the hypervisor gets direct access to the CPU and disks. Proxmox on a VPS is a different case: you run a hypervisor inside a machine that is itself virtual, and almost everything that will or will not work is decided by that second layer.
Nested virtualization: check it before you build a lab
For KVM machines to run inside a VPS, the host must enable nested virtualization on its node and pass the CPU extensions through to the guest: Intel VT-x (the vmx flag) or AMD-V (the svm flag). Most hosts do not do this: machines with nested guests are harder to migrate between nodes, put more load on the host and disturb the neighbours. A Proxmox template in the order panel does not by itself mean nested is enabled.
The check takes a minute: grep -cE 'vmx|svm' /proc/cpuinfo should return a non-zero number, and the /dev/kvm device should exist. If the flags are missing, Proxmox will install, but a virtual machine will only start with the KVM option turned off, that is, in software emulation, dozens of times slower. LXC containers work without nested, and for a set of lightweight services that may be enough; the limits of containers are described in the VPS on LXC selection. The VPS itself must be on KVM: Proxmox cannot be installed on OpenVZ or inside a container. If the host offers a trial period or a refund, check the flags in the first few hours.
Memory and disk: leave headroom for the hypervisor
Proxmox itself, with its web interface and services, takes about 1–2 GB of memory; the rest is shared between guests. Do not overcommit: if the total memory of the machines exceeds what the VPS has, swapping starts, and that is a double degradation, inside your server and on the host's node. For two or three small Linux machines a sensible minimum is 8 GB; for a lab with Windows, a cluster or Kubernetes, start at 32 GB.
- File system. ZFS on a VPS is usually overkill: it wants a lot of memory for the ARC cache, and redundancy on a virtual disk gives almost nothing. Ext4 with qcow2 images or LVM-thin is simpler.
- Disk. Choose NVMe: several guests create parallel random load, and a disk with a shared IOPS limit hits that limit first.
- CPU. In a nested setup every call to the hypervisor costs more, so I/O- and network-heavy workloads lose more than pure computation. Expect a noticeable performance loss compared with bare metal.
Networking for guest machines
The most common surprise is the network. On a dedicated server, guests are attached to a bridge and each gets an additional IP. On a VPS the host usually filters traffic by your machine's MAC address, and packets from a guest with its own MAC are dropped. There are three working setups:
- NAT. A separate bridge vmbr1 with a private subnet, masquerading via iptables or nftables, and port forwarding to the guests. Suitable when you have a single public address.
- Routed additional IPs. The addresses are routed to the VPS's main IP, and Proxmox hands them to guests without bridging to the external interface. Ask the host whether it sells extra addresses and whether it binds them to a MAC.
- IPv6. If you get a /64 subnet, every guest can have a public address without buying IPv4; plans with it are collected in the VPS with IPv6 selection.
For guests to talk to each other, an internal bridge without external access is enough, and a private network between several such VPS is easy to build with WireGuard.
Backups and the subscription
The built-in vzdump takes full copies of machines on a schedule, but storing them on the same VPS makes no sense. Proxmox Backup Server on a separate server with a large disk is more convenient: it makes incremental, deduplicated copies, so a daily backup of a dozen machines takes little space and transfers quickly. How to organise backup storage is covered in the VPS for backups selection. How these copies differ from the machine snapshots Proxmox takes in seconds is covered in Snapshots vs Backups.
Proxmox VE is distributed free of charge under the AGPLv3 licence, and every feature is available without paying. A paid subscription opens the enterprise repository with more thoroughly tested updates, plus technical support; the price depends on the number of CPU sockets. Without a subscription you enable the pve-no-subscription repository: the packages are the same but arrive earlier and are tested less, and a subscription reminder appears when you log in to the panel. After installation the enterprise repository is enabled by default, and without a key updates will fail with an error until you disable it.
When a dedicated server is better
Proxmox on a VPS is good for learning, a cloud lab, cluster tests and a few lightweight services under one panel. For a production workload with a dozen machines, device passthrough, ZFS arrays and predictable speed, a dedicated server is more reliable: there the hypervisor gets all the hardware, and subnets of extra addresses are a standard service.