The AMD EPYC 7543P delivers 32 cores and 64 threads, with 128GB or 256GB of DDR4-3200 ECC memory.
Preinstallation does not replace VM planning. The account holder manages disk layout, IP allocation, and backups.
Host specifications
AMD EPYC 7543PCompute
32 cores / 64 threadsAMD-V (SVM) and NPT provide hardware virtualization for KVM VMs.
Storage
2×1TB NVMeBoth drives are direct-attached and independent. Configure storage pools and mirroring on the host.
Management IP
First IPv4 addressThe first address is reserved for host management; allocate additional addresses according to your needs.
The EPYC 7543P is a single-socket processor, and the processor and memory in the server are dedicated to one account. The host configuration determines how resources are allocated between VMs, overcommit ratios, and scheduling.
AMD-V SVM enables hardware-assisted virtualization. After installing Proxmox VE, check that the host recognizes the virtualization features before creating KVM VMs and assigning vCPUs.
64 threads describes the server's hardware; it is not a capacity commitment for 64 VMs running at full load. Capacity planning should account for concurrency, CPU utilization, and disk load on each VM.
Allocate vCPUs for actual workloadsNPT provides nested page tables for virtual memory address translation. Actual performance also depends on guest memory, access patterns, available host memory, and storage latency.
When setting up production VMs, plan CPU and memory budgets together. Adding vCPUs alone does not address memory pressure.
Plan CPU and memory togetherEnable nested virtualization on the host and expose the required CPU features to a first-level VM to run KVM inside it. This is useful for validating virtualization workflows, isolated lab environments, and test images.
Nested virtualization is not enabled automatically when a VM is created. Check the host kernel settings, the first-level VM's CPU configuration, and the guest's reported features. Include nested virtualization overhead in capacity planning.
Check virtualization features at each layerBoth tiers use DDR4-3200 ECC RDIMMs. ECC can detect and correct memory errors, making it suitable for always-on hosts. It does not replace VM backups or guarantee that application data is always correct.
Suitable for deployments with a defined VM count and memory limit. Reserve capacity for the host, storage cache, and background tasks before allocating the remainder to guests. Do not assign the full advertised capacity to VMs.
With ZFS, include cache requirements in the host budget. Account for peak memory use from databases, build jobs, and bulk imports in each VM's allocation.
128GB DDR4-3200 ECCSuitable when total VM memory requirements exceed the 128GB tier's budget or when capacity needs to be kept available for additional guests. The processor, standard drives, and default network specifications remain the same across memory tiers.
Select the memory tier before ordering. The existing server cannot be upgraded after deployment; changing tiers requires ordering another server and arranging workload and data migration.
256GB DDR4-3200 ECCGuest budget = total server memory − host and storage budget − operating headroom
The example below illustrates a budgeting method; it does not represent default system usage or guaranteed available capacity. For example, reserve 16GB for the host and storage and another 16GB for operating headroom. At 8GB per guest:
| Server memory tier | Guest memory budget | Example allocations at 8GB per guest |
|---|---|---|
| 128GB | 128 − 16 − 16 = 96GB | 96 ÷ 8 = 12 VMs |
| 256GB | 256 − 16 − 16 = 224GB | 224 ÷ 8 = 28 VMs |
This example accounts for memory only; it does not mean these VMs can all run at full compute or storage load simultaneously. Before going live, test representative workloads, monitor memory reclamation, disk wait, and CPU usage, then adjust allocations. Swap space cannot make up for a sustained shortage of physical memory.
The standard setup includes 2×1TB NVMe drives, each direct-attached, with no hardware RAID. The drives do not come preconfigured as a RAID-1 array. Decide on capacity, redundancy, and recovery before creating a storage pool.
Proxmox VE can use the two standard drives to create a ZFS mirror. Usable capacity is based on one member drive, minus formatting, metadata, and required headroom. Do not estimate capacity by adding the two drive sizes together.
Creating or rebuilding a storage pool may overwrite disk contents. Verify device identities and complete a backup before performing storage operations.
A mirror is not a backupThe two drives can also be planned as separate devices, with storage allocated to different VMs or workloads. This setup does not provide mirrored redundancy automatically; a drive failure may affect guest disks and data on that drive.
When estimating capacity, allow for snapshots, image templates, and data growth—not just the initial size of VM disks.
Direct-attached, no hardware RAIDAdd 0 to 2 additional 2TB NVMe SSDs for $70/month each. Each drive is direct-attached. New drives can be placed in a separate data pool for guest disks or other storage needs.
Adding drives does not automatically expand an existing ZFS mirror. Plan pool structure, data migration, and backups for the actual layout.
Add up to 2×2TB NVMeSnapshots stored on the same server remain vulnerable to server failure and accidental changes. A recovery plan should include off-site backups and recovery testing; backup copies should not be kept only in the original storage pool.
Each server includes 1 dedicated IPv4 address, with up to 255 additional addresses available, for a maximum of 256. Additional IPv4 addresses cost $2/month each and are billed individually. Assigned addresses are available in the portal after delivery.
The first address is for host management and the initial SSH connection.
Choose a quantity based on guest count and workload requirements.
The number of addresses and the number of VMs the server can run are separate measures.
Check the first IPv4 address and host credentials in the portal, and confirm that the management connection works. Record management and workload addresses separately to avoid configuring the same public IP on both the host and a guest.
Use a Proxmox VE network bridge to assign additional addresses to VMs. Use the delivered gateway, netmask, and routing details; do not infer network settings from neighboring addresses or enter unverified parameters.
Assign a purchased address to the guest, check its network settings, firewall, and return route, then verify inbound and outbound connectivity. Keep a record mapping each address to its guest after every change to help troubleshoot conflicts and plan workload migrations.
The configurator offers the free operating systems below. Proxmox VE 8 and 9 can be used as virtualization hosts; the other distributions are options for guest systems. Choosing a preinstalled OS for the server and installing an OS inside a VM are separate steps. A preinstalled host does not create guest VMs automatically.
Host option. Manage KVM VMs, storage pools, and network bridges after installation. The host allocates resources to guests.
Preinstalled free · virtualization hostAvailable as a free server OS and as an option for Linux workloads in guest VMs. Match the version to application dependencies, software repositories, and upgrade plans.
Guest OS optionAvailable as a free server OS and for development or production guests. Before deployment, check that the required software supports the chosen distribution version.
Guest OS optionAvailable as a free server OS or as a Linux guest. Updates, networking, and workload services must be configured separately after installing it in a VM.
Guest OS optionAvailable as a free server OS or as an application guest. Verify compatibility between the image version and application runtime before migration.
Guest OS optionAvailable as a free server OS and as a guest option. Test the combination of guest network adapter, disk controller, and drivers.
Guest OS optionGuest operating systems must be installed and managed separately in the virtualization environment. Check image sources, drivers, software licensing, and update policies independently. Free preinstallation does not include a commercial support subscription.
Standard and Datacenter are available in versions 2019, 2022, and 2025, with English, Traditional Chinese, or Simplified Chinese as the system language. Choose Windows as the server OS to connect over RDP. This is a separate host option from Proxmox VE.
+$19/month
Suitable for a server deployment centered on a single Windows workload. Choose a version that meets application compatibility requirements, then configure remote access, security updates, and data backups.
An OS license option does not include licenses for business software. Check licensing separately for databases, middleware, and other commercial applications.
2019 / 2022 / 2025+$31/month
Suitable for a Windows host deployment that plans to use Hyper-V. After enabling the role, plan virtual switches, guest memory, disk locations, and management addresses separately.
Check the applicable license terms for guest operating systems. This monthly price does not grant general-use rights for arbitrary guests or commercial software.
2019 / 2022 / 2025Choose the host after deciding on management tools and guest requirements. With Proxmox VE, manage KVM guests on that host; with Windows Server, configure Windows roles as needed. These are separate host options, not two host operating systems preinstalled on the same server.
Choose 128GB or 256GB of memory, then select Proxmox VE 8 or 9 and review the drives, bandwidth, and additional IPv4 addresses. All prices are in USD; available payment methods are listed in the configurator.
Amount due = monthly total × number of months. Preinstallation does not create VMs, storage pools, or workload networks.