Frequently Asked Question
Proxmox Memory
RAM requirements for Debian 12 (Bullseye) and Debian 13 (Bookworm)
- Debian 12 – the base OS used by Proxmox 7-8.
- Minimum: 512 MiB (bare‑minimum for a headless install).
- Recommended for a typical Proxmox host: 2 GiB or more, to allow comfortable operation of the Proxmox web UI, pve‑daemon, and system services.
- Debian 13 – the base OS used by Proxmox 9.
- Minimum: 512 MiB.
- Recommended for a typical Proxmox host: 2 GiB or more, with 4 GiB advised for larger clusters or when many LXC containers are running.
Note: Proxmox itself adds only a modest overhead (≈ 200–300 MiB) for its daemons and GUI components. The bulk of RAM consumption comes from the guest OSes and any storage‑backends you enable.
RAM overhead of Proxmox daemons and subsystems
| Component | Typical RAM usage (steady‑state) | Remarks |
|---|---|---|
pve-manager (GUI) | 100–200 MiB | Spawns a PHP‑FPM worker; usage rises with many simultaneous UI sessions. |
pve-detect / pve-ha-cron | Background health‑checking and HA scripts. | |
pve-cluster (corosync) | 30–70 MiB | Required for clustering; negligible on a single node. |
lxc container manager | 30–100 MiB per 10–20 containers | Depends on container count and nesting depth. |
qemu‑system‑x86_64 (KVM VMs) | Not counted here – each VM’s RAM is allocated separately. |
Overall, a single‑node Proxmox host with modest workloads typically needs 2 GiB of RAM to keep the host OS and management services comfortably responsive. Add 1 GiB for each 5–10 active LXC containers, or 2–4 GiB per 10–20 concurrent KVM guests, depending on their individual memory allocations.
RAM impact of storage filesystems
| Filesystem | RAM usage characteristics | Practical guidance |
|---|---|---|
| ZFS | Uses ARC cache; default ARC size is ~½ of total RAM (capped at ~1 GiB on low‑memory systems). | - For a host that only stores VM disk images, 2–4 GiB RAM is usually sufficient. - If you enable heavy deduplication, compression, or run many VMs with large datasets, allocate 8 GiB+ to keep cache responsive. |
| BTRFS | Keeps metadata and checksums in RAM; typical usage | - No special RAM planning needed beyond the base host requirement. |
| Ceph RBD (client side) | RBD cache (default 64 MiB) plus OSD client buffers; modest. | - For a Ceph‑backed storage pool, allocate an extra 1 GiB if you expect many concurrent RBD connections. |
| CephFS | Uses FUSE client cache; default 16 MiB, can be tuned up to 256 MiB. | - Add 1 GiB if you run many clients or heavy file‑serving workloads. |
Tip: When planning RAM, sum the host baseline (≈ 2 GiB) + expected ARC/ cache usage + any extra buffers for Ceph clients. This gives a safe upper bound before allocating memory to guests.
Calculating total RAM for a given configuration
- Determine host baseline
- Base OS (Debian 12/13) + Proxmox daemons ≈ 2 GiB.
- Add 0.5 GiB if you run a large number of LXC containers (> 30).
- Add storage‑filesystem cache
- ZFS ARC: ½ GiB per 8 GiB of RAM allocated to ZFS, up to a maximum of 8 GiB.
- BTRFS: negligible (≈ 0.1 GiB).
- Ceph RBD/FUSE: 1 GiB each if you use those back‑ends.
- Allocate guest memory separately
- Guest RAM is not counted in the host’s RAM budget; it is reserved per VM/LXC.
- Ensure the host has enough free RAM after step 1‑2 to comfortably start the intended number of guests.
- Example calculation
- Host: 16 GiB total RAM.
- Baseline: 2 GiB.
- ZFS cache: 4 GiB (half of 8 GiB, capped at 8 GiB).
- CephFS client cache: 1 GiB.
- Total reserved for host services ≈ 7 GiB.
- Remaining 9 GiB can be distributed among guests (e.g., 4 VMs × 2 GiB each).
Practical steps to size RAM for a new Proxmox deployment
- Identify the storage backend you will use (ZFS, BTRFS, Ceph RBD, CephFS).
- Estimate the amount of data you will store and the I/O intensity (e.g., many concurrent VMs).
- Calculate required host RAM using the formula above.
- Add a safety margin of 10–20 % to avoid swapping under load.
- Allocate guest RAM based on the workload of each VM/LXC, ensuring the sum of guest allocations does not exceed the remaining host RAM after step 4.
By following these calculations, you can reliably predict the RAM needed for a Proxmox host that runs Debian 12 or Debian 13, supports the required storage filesystems, and comfortably hosts the desired number of guest VMs or containers.
Proxmox support from the engineers who wrote this article
This article came out of a real case resolved by GEN engineers, not from upstream documentation. GEN have run Proxmox in production in our own UK data centres since 2015, and have been in enterprise IT for 37 years. If this one has not solved your problem, we can.
- 30 minute response, 24 hours a day, every day of the year on critical production infrastructure.
- No contracts. Buy hours, use hours. No minimum term and no notice period.
- Genuinely independent. We hold no software partner status with Proxmox or any other vendor, so nothing we recommend is shaped by a licence margin.
- UK based, in-house engineers. No outsourced first line.
Proxmox support · VMware to Proxmox migration · Proxmox training · Support rates
Registering a GEN account is free, so the route to an engineer is open before you need it. You only ever pay for the time you use.
