Running several virtual machines on a single server
The question is not core count, it is memory: here is how to work it out before ordering.
Starting at from €13.99/mo
Introduction
"How many VMs on this server?" is the question we get most, and the honest answer fits in one sentence: as many as memory allows. We impose no count limit. What limits you is that every virtual machine reserves its RAM, whether it uses it or not.
A simple sum before choosing: add up what each VM will ask for, add 2 to 4 GB for the Proxmox host, and take the plan above. On 16 GB, three or four small VMs fit comfortably. On 32 GB, you add a serious database. On 96 GB, the constraint becomes CPU or disk rather than memory.
Two settings buy a lot of room without buying hardware. LXC containers share the host kernel and use a fraction of what a full VM demands: for a simple Linux service, that is often the right call. And Proxmox ballooning lets a VM hand back memory it is not using — useful, but not to be mistaken for free memory.
What the server brings, across the whole range
Proxmox VE already installed
The server arrives with <strong>Proxmox VE</strong> in place and its web interface reachable. You create your virtual machines and LXC containers from the browser, without a support ticket or a wait. <strong>Reinstalls are unlimited</strong>: an experiment that goes wrong is redone in minutes.
RAM, because that is what runs out first
On a hypervisor it is almost never the processor that caps out first: it is <strong>memory</strong>, because every virtual machine reserves its own. The range starts at <strong>16 GB</strong> and goes up to <strong>96 GB</strong>, which leaves room to stack several VMs without starving them.
Unlimited snapshots and backups
A snapshot before an update, another before a configuration change: that is what separates a test from a gamble. Neither the count nor the frequency is billed, so nothing discourages taking one more.
Up to 16 additional IPv4 addresses
Each VM can hold its own public address, which avoids routing everything through port forwards on the host. Useful as soon as a virtual firewall, a web server and a third-party service have to coexist cleanly.
Layouts that work
Three VMs on 16 GB
A web server (4 GB), a database (6 GB), a test service (4 GB), and there is still room for the host to breathe. That is the S plan at €13.99, and it is already a real little estate.
Five or six VMs on 32 GB
Web, database, cache, monitoring, backup, plus a staging VM you switch on when needed. The L plan at €26.99 covers that profile without crowding.
Around ten VMs on 96 GB
At that scale you stop counting VMs and start watching IOPS and cores. The MAX plan brings 24 vCore and 700 GB to match.
Many containers rather than VMs
Twenty LXC containers on 16 GB is not unrealistic if they host small services. The kernel is shared, isolation is weaker than a VM, and the memory saving is enormous.
Grow without redoing everything
A plan change is requested from the client area. The virtual machines and their disks follow: you do not reinstall because one more VM turned up.
Frequently asked questions
None from us. The limit is hardware: memory first, then cores and disk. You create as many machines as the server can carry.
Count 2 GB for light use, 4 GB if you run ZFS — its ARC cache is hungry by design. Never hand the whole memory to the VMs.
It lets a VM return unused memory, which helps fill a server better. It does not create memory: overcommitting heavily ends in swap, and swap on a hypervisor is paid for in general slowness.
Several small ones, as soon as the services do not share a life cycle. An update, a reboot or an application failure should not take down something unrelated.