Ryzen Proxmox Setup: VMs and IOMMU | SistemDC

Installing Proxmox on a Ryzen Server

Installing Proxmox on a Ryzen Server

Proxmox can be installed on Ryzen dedicated. Because the node already comes without a hypervisor, writing the ISO from IPMI/KVM or the rescue environment is your job; do not expect a “Proxmox template” from the VDS panel. This article does not copy every menu step by step. The aim: when Proxmox makes sense, which Ryzen plan, and how to think about IOMMU and disks. Hardware: AMD Ryzen bare metal servers. Model summary: 2026 dedicated guide.

Short answer: For a few VMs/LXCs (panel, DB, staging), Proxmox sits on a 16-core 5950X or 9950X dedicated server. For a single game world or a single render queue, Proxmox is an extra layer; for those jobs install the OS directly. Do not overcommit RAM; splitting NVMe into OS and VM disks is more readable than RAID-0 in most scenarios.

Why Proxmox on Dedicated?

The machine you rent is already bare metal. Adding Proxmox means dividing that physical CPU/RAM/NVMe into a KVM+LXC layer under your control. There are no neighbouring customers; the “noisy neighbor” is your own VM.

What this means: snapshots, separate network bridges, test/prod isolation. The cost: hypervisor time, memory loss (each VM's OS) and one more layer to back up. A single process (game tick, a single FFmpeg) gains no speed from Proxmox.

Which Ryzen Plan Is Enough for Proxmox?

There is no 12-core Ryzen 7900 sold on SistemDC's line. The 16C SKUs available for virtualization are the 5950X and 9950X.

  • R7 5700G (8C/16T, 32 or 64 GB): 1–2 light LXCs or a lab. RAM runs out quickly for a few production VMs + the Proxmox UI.
  • R9 5950X (16C/32T, 128 GB DDR4, 2×1 TB NVMe): A suitable skeleton for a homelab/prod mix of a few VMs. Zen 3, AM4.
  • R9 9950X Non-ECC (16C/32T, 128 GB DDR5): The same core count, higher base/boost (4.3 / up to 5.7 GHz, 170 W). VM density is limited by RAM and disk rather than cores.
  • 9950X Business ECC: ECC makes sense for a long-running hypervisor + database VMs. Details: Ryzen ECC RAM.

The 9950X's core/clock summary: Ryzen 9 9950X server. Disk layout: NVMe SSD guide.

Setup Skeleton

  1. ISO: Get the Proxmox VE ISO from the official source. Verify the checksum.
  2. Installation environment: IPMI virtual media or the provider's rescue/ISO mount tool. There is no “one-click template” on dedicated.
  3. Disk: If there are two NVMe drives: disk0 = Proxmox + local ZFS/LVM, disk1 = VM datastore. With a single NVMe (5700G 500 GB / 1 TB) root and data are on the same device; scale down the snapshot policy accordingly.
  4. Network: The vmbr0 bridge goes to the physical NIC. Think about the firewall both at the Proxmox datacenter level and inside the VMs. Do not leave the management port open to the internet; use a VPN or IP restriction.
  5. Updates: With the no-subscription repository, do not tie production to “the latest, untested” packages. The subscription decision is your licensing policy.

The first tasks after installation: root password, SSH key, backup target (separate object storage or a second disk). Without a hypervisor backup, snapshots will not save you from a disk failure.

IOMMU (AMD-Vi) and Passthrough

For PCI passthrough (GPU, NIC, HBA), IOMMU must be enabled on the motherboard and in the BIOS. With a Ryzen desktop chip + server motherboard combination this is not “guaranteed on every consumer board”; check the BMC/BIOS menu of the node you ordered.

If you want GPU passthrough, this category is not GPU servers with cards. Ryzen dedicated plans have no GPU. For CUDA/NVENC work you move to the GPU line; Proxmox does not create that card “out of hardware that does not exist”.

CPU pinning: giving a game VM 4–8 cores and the rest to the DB/panel yields a more predictable tick than “splitting 16 cores equally among 8 VMs”. Overcommitting RAM is a swap storm in production.

Frequently Asked Questions

Can Proxmox be installed on a VDS?
Unless nested virtualization is enabled, KVM inside KVM is disabled or slow with most providers. This article is for bare metal dedicated, not a nested lab.

Is Xeon a better fit for a hypervisor?
For a farm that wants multiple sockets, plenty of PCIe and ECC by default, the Xeon/EPYC class is evaluated separately. A 16C Ryzen is enough for a homelab and a moderate number of VMs. The decision: Ryzen vs Intel Xeon.

Should I run the game server inside a VM?
It works; there is added latency and core sharing. For a single world + DDoS, most teams install the OS on bare metal. General framework: Ryzen game server.

Is ZFS a must?
No. ZFS eats RAM; under 64 GB, an aggressive ARC + multiple VMs get squeezed. LVM-thin is also valid.

A physical node for Proxmox

16 cores · 128 GB · 2× NVMe · IPMI

AMD Ryzen bare metal servers

Server packages covered in this article

+902243340242