Use the following configuration limits as a guideline when selecting and configuring your virtual and physical environment for XenServer. The following tested and recommended configuration limits are fully supported for XenServer.
Virtual machine limits
XenServer host limits
Resource pool limits
Factors such as hardware and environment can affect the limitations listed below. More information about supported hardware can be found on the Hardware Compatibility List. Consult your hardware manufacturers’ documented limits to ensure that you do not exceed the supported configuration limits for your environment.
Virtual machine (VM) limits
|Virtual CPUs per VM (Linux)||32/64 (see note 1)|
|Virtual CPUs per VM (Windows)||32/64 (see note 1)|
|RAM per VM||1.5 TiB (see note 2)|
|Virtual Disk Images (VDI) (including CD-ROM) per VM||255 (see note 3)|
|Virtual CD-ROM drives per VM||1|
|Virtual Disk Size (NFS)||2040 GiB|
|Virtual Disk Size (LVM)||2040 GiB|
|Virtual Disk Size (GFS2)||16 TiB|
|Virtual NICs per VM||7 (see note 4)|
|vGPUs per VM||8|
|Passed through GPUs per VM||1|
|Pass-through USB devices||6|
Consult your guest OS documentation to ensure that you do not exceed the supported limits. As of yet, Red Hat Enterprise Linux 8 and derivatives do not support more than 32 vCPUs. Though the limit is 64, we recommend to set the limit to 32 if your VMs might not be trustworthy or if you want to prevent a potential impact on system availability.
The maximum amount of physical memory addressable by your operating system varies. Setting the memory to a level greater than the operating system supported limit may lead to performance issues within your guest.
The maximum number of VDIs supported depends on the guest operating system. Consult your guest operating system documentation to ensure that you do not exceed the supported limits.
Several guest operating systems have a lower limit, other guests require installation of the XenServer VM Tools to achieve this limit.
XenServer host limits
|Logical processors per host||512 (see note 1)|
|Concurrent VMs per host||1000 (see note 2)|
|Concurrent protected VMs per host with HA enabled||500|
|Virtual GPU VMs per host||128 (see note 3)|
|RAM per host||6 TB|
|Concurrent active virtual disks per host||2048 (see note 4)|
|Storage repositories per host (NFS)||400|
|Physical NICs per host||16|
|Physical NICs per network bond||4|
|Virtual NICs per host||512|
|VLANs per host||800|
|Network Bonds per host||4|
|GPUs per host||8 (see note 5)|
The maximum number of logical physical processors supported differs by CPU. For more information, see the Hardware Compatibility List.
The maximum number of VMs per host supported depends on VM workload, system load, network configuration, and certain environmental factors. We reserve the right to determine what specific environmental factors affect the maximum limit at which a system can function. For larger pools (over 32 hosts), we recommend allocating at least 8GB RAM to the Control Domain (Dom0). For systems running over 500 VMs or when using the PVS Accelerator, we recommend allocating at least 16 GB RAM to the Control Domain. For information about configuring Dom0 memory, see CTX134951 - How to Configure dom0 Memory.
For NVIDIA vGPU, 128 vGPU accelerated VMs per host with 4xM60 cards (4x32=128 VMs), or 2xM10 cards (2x64=128 VMs). For Intel GVT-g, 7 VMs per host with a 1,024 MB aperture size. Smaller aperture sizes can further restrict the number of GVT-g VMs supported per host. This figure might change. For the current supported limits, see the Hardware Compatibility List.
The number of concurrent active virtual disks per host is also constrained by the number of SRs you have attached to the host and the number of attached VDIs that are allowed for each SR (600). For more information, see the “Attached VDIs per SR” entry in the Resource pool limits.
This figure might change. For the current supported limits, see the Hardware Compatibility List.
Resource pool limits
|VMs per resource pool||2400|
|Hosts per resource pool||64 (see note 1)|
|VLANs per resource pool||800|
|Integrated site recovery storage repositories per resource pool||8|
|Paths to a LUN||8|
|Multipathed LUNs per host||150 (see note 2)|
|Multipathed LUNs per host (used by storage repositories)||150 (see note 2)|
|VDIs per SR (NFS, SMB, EXT, GFS2)||20000|
|VDIs per SR (LVM)||1000|
|Attached VDIs per SR (all types)||600|
|Storage repositories per pool (NFS)||400|
|Storage repositories per pool (GFS2)||62|
|Storage live migration|
|(non-CDROM) VDIs per VM||6|
|Snapshots per VM||1|
|Concurrent operations per pool||25|
- Clustered pools that use GFS2 storage support a maximum of 16 hosts in the resource pool.
- When HA is enabled, we recommend increasing the default timeout to at least 120 seconds when more than 30 multipathed LUNs are present on a host. For information about increasing the HA timeout, see CTX139166 - How to Change High Availability Timeout Settings.