Requirements
Understand what is needed to run XCP-ng.
An XCP-ng server is dedicated entirely to running XCP-ng and hosting VMs. It is not used for other applications.
Installing third-party software directly in the XCP-ng control domain is not supported, except for software supplied in the official repositories. If you wish to add extra packages to XCP-ng, please submit your request here.
π XCP-ng System Requirementsβ
XCP-ng is generally deployed on server-class hardware, but it also supports many workstation and laptop models. For more information, refer to the Hardware Compatibility List (HCL).
The following outlines the recommended XCP-ng hardware specifications.
XCP-ng must be a 64-bit x86 server-class machine dedicated to hosting VMs. It creates a hardened Linux partition using a Xen-enabled kernel, which manages interactions between VMs and the physical hardware.
The system requirements for XCP-ng are:
CPUsβ
- One or more 64-bit x86 CPUs, minimum 1.5 GHz; 2 GHz or faster multicore CPUs are recommended.
- To run Windows VMs or recent Linux versions, an Intel VT or AMD-V 64-bit x86-based system with one or more CPUs is required.
Note: For Windows VMs or newer Linux distributions, enable hardware virtualization in the BIOS. It may be disabled by defaultβconsult your BIOS documentation for guidance.
- For VMs running supported paravirtualized Linux, a standard 64-bit x86-based system with one or more CPUs is required.
Memoryβ
- Minimum 2 GB, recommended 4 GB or more.
- A fixed amount of RAM is allocated to the control domain (dom0). Optimal allocation depends on your workload.
Disk Spaceβ
- Local storage (PATA, SATA, SCSI) with a minimum of 46 GB, recommended 70 GB or more.
- SAN access via HBA (not software) when installing with multipath boot from SAN.
For more details, refer to the Hardware Compatibility List (HCL).
Installation on USB Drivesβ
Strongly discouraged due to heavy write operations in XCP-ng:
- XAPI Database: Undergoes frequent changes, resulting in extensive write operations, potentially reducing USB drive lifespan. The XAPI database maintains the state of all XCP-ng operations and is replicated across all hosts.
- Logging: XCP-ng generates a high volume of logs. Consider using a remote syslog service as an alternative.
Installation on SD Cardsβ
Similarly, installing XCP-ng on SD cards is highly discouraged. A basic SSD offers a vastly more durable and effective alternative for managing system partitions.
Networkβ
- Minimum 100 Mbit/s NIC. Recommended: one or more Gb or 10 Gb NICs for faster data transfers, including P2V, import/export, and VM live migrations.
- Use multiple NICs for redundancy. Network configuration depends on your storage typeβrefer to vendor documentation for guidance.
XCP-ng 8.2 requires an IPv4 network for management and storage traffic. Starting from XCP-ng 8.3, the management network supports IPv6.
XCP-ng 8.2 is EOL. This 8.2-specific information is retained solely to assist with the transition from 8.2 to a supported release.
Set the server's BIOS clock to the current UTC time. For debugging support cases, serial console access may be required. Consider configuring serial console access for XCP-ng. For systems without physical serial ports, explore embedded management devices like Dell DRAC or HP iLO. See CTX228930 - How to Configure Serial Console Access on XenServer 7.0 and later.
π XCP-ng Configuration Limitsβ
XCP-ng supports the following per host:
RAMβ
- Up to 6 TB.
In XCP-ng 8.3, Xen theoretically supports up to 12 TiB with security support, and even more without security support.
Physical Network Interface Cards (NICs)β
- Up to 16 physical NICs.
Logical Processorsβ
The maximum number of supported logical processors may vary depending on the CPU. For more information, see the Hardware Compatibility List (HCL).
XCP-ng 8.3 LTSβ
XCP-ng 8.2 is EOL. This 8.2-specific information is retained solely to assist with the transition from 8.2 to a supported release.
- Up to 960 logical processors, depending on CPU support (theoretical, untested: 1024).
XCP-ng 8.2 LTSβ
- Up to 448 logical processors (theoretical, untested: 512).
Virtual Network Interface Cards (vNICs)β
- Up to 512 virtual NICs.
Virtual Local Area Networks (VLANs)β
- Up to 800 VLANs.
Virtual Machine Configuration Limitsβ
Below are the supported limits for virtual machines on XCP-ng.
CPUβ
XCP-ng 8.3 LTSβ
- Virtual CPUs (vCPUs) per VM:
- For untrusted VMs, the security-supported limit is 32 vCPUs.
- For trusted VMs, the tested limits areΒ 128 vCPUsΒ in BIOS mode andΒ 96 vCPUsΒ in UEFI mode. Developments are planned to increase these limits.
Guest OS support is also an important factor to consider.