Do these 3 things before closing this tab:
1Clear out junk files and repair common Windows errors2Fix the driver behind crashes, sound loss and screen glitches3Repair Windows errors before they cause bigger problemsTo configure Proxmox memory ballooning safely, first decide whether you mean a QEMU/KVM virtual machine, an LXC container, the Proxmox host, or swap inside a guest operating system. For a VM, ballooning lets Proxmox adjust the guest’s assigned RAM within a configured minimum and maximum; swap is separate and may be used when memory is under pressure. Ballooning redistributes memory—it does not create RAM or guarantee that the host will avoid swapping or out-of-memory handling.
What Proxmox ballooning does—and how it relates to swap
A VM’s balloon driver works with the host to reclaim or supply guest memory pages. With automatic allocation, the VM has a minimum and a maximum: Proxmox guarantees the configured minimum and can raise the allocation toward the maximum when host memory is available. Under pressure, the guest may release memory; guest processes may then swap, and the OOM killer may be used as a last resort. The behavior is described in the Proxmox VE 6.4 Administration Guide.
Ballooning and swap are not the same setting. Ballooning adjusts how much RAM a VM receives. Swap is slower backing storage used by an operating system when it cannot keep all active memory in RAM. It may be configured on the Proxmox node or inside the guest OS. Proxmox ballooning does not itself configure either swap area.
Identify which memory and swap settings you need
| Layer | What the setting controls | Where to configure it |
|---|---|---|
| QEMU/KVM VM | Guest RAM allocation and, separately, the guest OS’s swap | VM memory settings in Proxmox; guest swap in the VM’s operating system |
| Proxmox node | Host RAM available to Proxmox and host-level swap behavior | The node’s Linux configuration; the correct procedure depends on its OS and storage setup |
| LXC container | Container memory limit and host-swap allowance through cgroup controls | Container configuration, not the QEMU VM ballooning controls |
For LXC, the Proxmox VE 9 beta pct manual describes container memory and swap as cgroup settings and says container swap uses host swap space. Do not treat a container’s swap value as a VM’s guest swap setting.
Free tools Windows power users keep installed
One-click scans. No signup required.
#1 Best Overall
Choose fixed memory or a ballooned range for a VM
Fixed memory
Use fixed memory when a workload needs predictable RAM or is sensitive to memory changes. Setting the minimum equal to the VM’s assigned amount results in Proxmox allocating that specified amount, as described in the 6.4 guide. Fixed memory does not necessarily mean the balloon device is absent: Proxmox says the device can still provide detailed guest memory-usage information.
Automatic allocation
Use a minimum and a higher maximum when the VM can tolerate changing RAM and you want Proxmox to reclaim capacity when needed. Choose a minimum the host can sustain and a maximum the workload can use; the documentation does not establish a universal ratio. Consider the RAM demand of all running guests as well as the host’s own needs before setting either value.
Configure ballooning and node allocation
- Confirm the guest type and Proxmox release. The VM guidance below applies to QEMU/KVM VMs. Proxmox’s detailed behavior cited here comes from the 6.4 Administration Guide, while current interface labels and complete current VM configuration syntax are not established by the cited material. Check the documentation matching the release installed on your node before following exact UI labels or editing VM configuration.
- Set the VM’s memory range in its memory settings. Enter the intended maximum and minimum for automatic allocation, or use equal values for fixed allocation. The roles of minimum and maximum are documented, but exact current field names and paths vary by release and are not specified here.
- Check balloon-driver support in the guest. Proxmox’s guide says Linux distributions released after 2010 include the kernel driver, but that historical statement is not a guarantee for every distribution or configuration. The guide says Windows guests require manual installation of a balloon driver. Confirm the supported VirtIO driver package and installation steps for the specific Windows version before proceeding.
- Keep host headroom. The 6.4 guide gives 1 GB available to the host as a general rule of thumb, not a modern workload-sizing guarantee. Size host and guest memory for the actual node, workloads, and concurrency rather than relying on that figure as a safety threshold.
- Consider the node-wide automatic-allocation target separately. The current Administration Guide search result describes a default target of 80% host memory use and gives
pvenode config set --ballooning-target 90as an example of changing it to 90%. This is a node-level target, not an individual VM’s minimum or a promise that a VM will receive a particular amount. Confirm the behavior and command against the documentation for your installed Proxmox VE release.
Disable ballooning only when you mean to disable the device
If you want a VM to keep fixed memory, you can set its minimum and maximum to the same amount; that is different from removing the balloon device. Proxmox recommends generally leaving the device enabled and notes that it can report guest memory usage even with fixed memory. Its 6.4 guide describes disabling the device for debugging through a GUI checkbox or with balloon: 0 in the VM configuration. Verify the current GUI label and configuration syntax for your installed release before changing them.
Disabling the device is not a substitute for choosing appropriate fixed RAM or configuring swap. It also removes the balloon device’s guest memory-usage information.
Configure swap at the layer that needs it
Proxmox node swap
Host swap belongs to the Proxmox node’s Linux configuration. The correct steps depend on the node’s distribution, filesystem, and deployment; the cited Proxmox materials do not provide a current, distribution-specific procedure. Do not apply a generic swap-file command without checking that it fits the node’s storage and operating-system setup.
Guest OS swap
Guest swap belongs to the operating system running inside the VM. Configure it using that OS’s current documentation and account for the workload’s latency requirements: disk-backed swap is slower than RAM and should not be treated as equivalent capacity. The cited sources do not establish a universal swap size or swap-to-RAM ratio.
LXC container swap
Container swap is a host-swap allowance controlled through the container’s cgroup configuration, according to the Proxmox VE 9 beta pct manual. It is distinct from both QEMU ballooning and swap configured inside a VM guest.
Quick Recap
Common configuration mistakes
- Confusing the 80% target with a VM limit: it is described as a node-wide target for automatic allocation, not a per-VM cap.
- Assuming ballooning prevents memory exhaustion: memory is redistributed, and the documented pressure response can include guest swapping and, as a last resort, the OOM killer.
- Disabling the device when you only want fixed RAM: fixed minimum and maximum values can avoid dynamic resizing while retaining the device’s memory-reporting function.
- Using an LXC swap value as a VM swap configuration: container swap controls host-swap allowance through cgroups; VM guest swap is configured within its operating system.
- Applying a universal memory ratio or swap size: the cited documentation does not prescribe one. Workload behavior, guest support, and node capacity determine suitable values.
Product prices and availability are accurate as of the date/time indicated and are subject to change. Any price and availability information displayed on Amazon at the time of purchase will apply.
The Tool Desk
Outbyte Driver Updater FREEScan for outdated or missing drivers - takes under a minuteDriver Scan →Outbyte PC Repair FREEClear out junk files and repair common Windows errorsFree Scan →
