Preparing for Installation

Proxmox CPU/IO Requirements

OS and Hardware Requirements

Component Requirement
Supported OS versions

Proxmox VE ISO can be directly downloaded and installed from the Proxmox website

Alternatively, install the Proxmox VE on Debian 12. Refer to (Install Proxmox VE on Debian 12 Bookworm - Proxmox VE) for more information.

CPU
  • Intel EMT64 or AMD64 with Intel VT/AMD-V CPU flag
  • For PCI(e) passthrough the CPU needs to support the VT-d/AMD-d flag
Memory
  • For OS and Proxmox VE services: Minimum 2 GB
  • For Ceph and ZFS: Approximately 1 GB of memory for every TB of used storage
  • For guests: Additional memory
Follow the PROXMOX VE ADMINISTRATION GUIDE (Proxmox VE Administration Guide), 2.1.2 Recommended System Requirements section.
Disk
  • OS Storage: Use a hardware RAID with battery-backed write cache (BBU) or non-RAID with ZFS (optional SSD for ZIL)
  • VM Local Storage: A hardware RAID with battery-backed write cache (BBU), or non-RAID for ZFS and Ceph
Follow the PROXMOX VE ADMINISTRATION GUIDE (Proxmox VE Administration Guide), 7.1 Storage Types section.
NICs Supported NICs include:
  • Intel I350 and Intel I210 (1GbE)
  • Intel X520, X550, X710, XL710, and X722 (10GbE)
  • Intel E810-XXV (2-port 10/25GbE adapter)
Web Browsers
  • Firefox, a release from the current year, or the latest Extended Support Release
  • Chrome, a release from the current year
  • Microsoft Edge
  • Safari, a release from the current year
USB Flash Drive At least 1 GB of storage

BIOS Settings

These settings ensure the underlying hardware is optimized for virtualization and cryptographic performance. Enabling Hyperthreading, VT-d, and AVX512 improves throughput, supports virtual machine operations, and prepares the system for future IPSec enhancements.

BIOS Settings

Configuration Description Recommendation Mandatory
Hyperthreading Enables multiple threads per CPU. Enable Yes
Virtualization (VT-d) Required for VM operation. Enable Yes
AVX512 Enhances cryptographic performance. Enable Yes (for future IPSec support)
PCIe Hot-Plug Error Control Required for Intel E810 NIC passthrough stability. Set to eDPC OS Control Yes
Note: When using Intel E810 NICs for PCI passthrough, configure PCIe Hot-Plug Error Control to eDPC OS Control. This setting is mandatory to prevent Proxmox host instability and VM crashes during E810 passthrough deployments.

Recommended Configuration Guidelines for Proxmox VE

To ensure optimal performance and stability of RUCKUS Virtual Edge on Proxmox VE, the following hardware, BIOS, and hypervisor settings are recommended:

Proxmox VM Settings

Proper VM configuration is critical for performance and stability. Assigning dedicated vCPUs, enabling NUMA awareness, and setting the processor type ensures efficient resource utilization and avoids cross-socket latency. VM affinity settings help isolate workloads and optimize cache usage.

Proxmox VM Settings

Configuration Description Recommendation Mandatory
vCPUs per VM Required for VM operation 4-8 vCPUs No
CPU Affinity* Enhances cryptographic performance. Assign vCores per VM Use dedicated core ranges per VM such that the sibling vCores are not allocated. No
Edge VMs per server Enables multiple threads per CPU 2-4 per socket. Do not span VMs across sockets Yes
Numa checkbox* Exposes NUMA topology to the VM Keep VM’s CPU affinity placement on the same host NUMA node as its passed-through NICs Optional (depends on CPU affinity settings)
Processor Type VM CPU type Select or type host Yes
Ballooning Memory reclamation Disable Yes
VM Bridge Settings Makes cluster connections None Optional
SCSI Controller VM disk controller Set to VMware PVSCSI Optional
Machine Settings VM machine type Select q35 Yes
NIC Passthrough Raw NIC access Enable Yes
PCI Settings PCI passthrough configuration Enable Q35 and ROM-Bar Yes
Note: For the E810 NIC, incorrect CPU affinity or NUMA settings can cause the RUCKUS Edge VM to enter an internal-error state, fail to boot, or experience port flapping and port-down conditions.

Memory Allocation

Each Edge VM should be provisioned with following: requirements

  • 12 GB RAM to support high client and tunnel density.
  • Sibling cores should remain free for hypervisor to manage lightweight monitoring tasks without impacting VM performance.