XCP-ng review: open-source Xen hypervisor for VMware escapees
8.3Genuinely free enterprise hypervisor with solid Xen foundations, but management requires separate Xen Orchestra layer.
Free (no license fees); optional commercial support from Vates starting approximately €2,000/year for 3-host Essential plan
- ✓Truly no-cost enterprise features: HA clustering, live migration, PCI passthrough all included
- ✓Strong security model inherited from Xen: Dom0 isolation, monthly patches, minimal attack surface
- ✓Zero vendor lock-in; GPLv2 licensed, Linux Foundation hosted, transparent development
- ✓Compatible with existing XenServer deployments; in-place upgrade path available
- ✓Active community and commercial support options from Vates without forced subscriptions
- ✗Management UI split: built-in XO Lite is basic; full features need separate Xen Orchestra VM deployment
- ✗Virtual disk size capped at 2 TiB per VDI when using snapshots with VHD storage driver
- ✗No native container support; LXC or Docker must run inside a guest VM, adding overhead
- ✗Steeper learning curve than Proxmox; Xen and XAPI concepts less familiar to many admins
- ✗Smaller hardware compatibility list and community size compared to KVM-based rivals
What XCP-ng is and where it came from
XCP-ng is a Type 1 bare-metal hypervisor built on the Xen Project, distributed as a turnkey Linux-based appliance with the Xen hypervisor and XAPI management layer pre-configured. The name stands for Xen Cloud Platform next generation. It was created by Vates in 2018 as a fork of Citrix XenServer, responding to Citrix's decision to move key features like live migration behind paid licensing tiers. The project aimed to revive the original open-source XCP vision from 2010.
Since January 2020 XCP-ng has been an incubation project within the Xen Project, itself hosted by the Linux Foundation. It receives investment from Vates, which employs around 20 dedicated developers and has poured over 15 million euros into the platform. The current LTS version is 8.3, released in October 2024, with regular monthly security updates. The underlying Xen hypervisor has been in production use for over two decades and powers major cloud providers including Amazon, IBM Cloud, and Oracle Cloud.
Core capabilities and what is included
XCP-ng ships with enterprise-grade features at no cost and with no artificial limits. High-availability clustering automatically restarts VMs on healthy hosts if a physical server fails. Live migration moves running VMs between hosts with zero downtime, and storage can similarly be migrated live. PCI passthrough allows direct GPU or network card assignment to VMs. VM snapshots, cloning, and templating are all included, though the VHD storage format caps individual virtual disks at 2,040 GiB when snapshots are enabled.
The platform supports up to 1.5 TiB of RAM per VM and up to 128 vCPUs per UEFI guest, with host scalability reaching 12 TiB of physical RAM. It runs Linux, Windows, and BSD guest operating systems in HVM and PVH virtualization modes; legacy PV mode was removed in version 8.3. Storage options include local LVM and EXT, plus shared NFS and iSCSI. The newer XOSTOR hyper-converged storage layer uses DRBD for distributed redundancy. Networking supports Open vSwitch, VLANs, and SR-IOV for near-native performance.
The two-tier management experience
Out of the box, XCP-ng provides a text-mode installer, command-line tools, and XAPI for programmatic control. Version 8.3 introduced XO Lite, a lightweight web interface that runs directly on each host for basic single-pool tasks like creating and starting VMs. For more advanced operations, including backups, replication, multi-pool orchestration, and fine-grained monitoring, users deploy Xen Orchestra. This is a separate web application, typically run as a VM on XCP-ng itself or built from source.
Xen Orchestra is developed by Vates and available in three forms: built from open-source code for free, as a community quick-deploy script, or as a commercial appliance with support subscriptions starting around 2,000 euros per year for small clusters. This split means the initial setup involves installing the hypervisor and then deploying or compiling the management layer. Compared to Proxmox, which ships a full web UI out of the box, the XCP-ng approach adds a configuration step but offers clearer separation between platform and orchestration.
Positioning versus Proxmox and the value equation
XCP-ng and Proxmox are the two leading open-source hypervisors for organizations leaving VMware, but they differ in architecture and philosophy. Proxmox uses KVM and is built on Debian, supports native LXC containers alongside VMs, integrates ZFS and Ceph storage natively, and ships with a comprehensive web UI. XCP-ng is Xen-based, does not support containers natively, relies on VHD or external storage solutions, and requires Xen Orchestra for full functionality. Proxmox tends to attract home labs and smaller shops valuing simplicity; XCP-ng appeals more to enterprise environments familiar with Citrix or seeking Xen's security isolation model.
Both platforms are free to use without subscriptions. Proxmox offers optional repository subscriptions for around 1,000 dollars per year for a small cluster; Vates bundles XCP-ng and Xen Orchestra support starting around 2,000 euros annually for up to three hosts under its Essential tier. Community forum users report that for very small deployments, post-Broadcom VMware pricing can be competitive or cheaper, but XCP-ng with free community support or self-compiled Xen Orchestra remains cost-effective for budget-conscious teams willing to invest the learning time.
Security, updates, and the road ahead
Xen's security architecture places the control domain Dom0 as the only component with direct hardware access, limiting the attack surface from unprivileged guest VMs. XCP-ng publishes monthly security updates and follows a transparent vulnerability disclosure process. Recent 2026 updates addressed kernel CVEs and Xen-specific issues; the project responded promptly to audit findings, including dismissing AI-generated false positives. GPG-signed ISOs and repositories provide supply-chain integrity.
The 8.3 LTS branch receives ongoing feature additions alongside bug fixes, diverging from the more conservative 8.2 LTS that preceded it. Vates has stated work is already underway on the next major platform version. The project maintains active GitHub repositories, a Discord server, and community forums where developers regularly engage. The commitment to upstream-first development and alignment with Citrix XenServer means XCP-ng benefits from a mature, tested codebase while retaining the freedom to diverge when the community requires it.
- +Organizations migrating from VMware seeking truly free enterprise features
- +Xen-familiar teams who value Type 1 hypervisor security architecture
- +Shops comfortable with command-line configuration and community support
- +Environments already standardized on NFS or iSCSI shared storage
- −First-time hypervisor users expecting turnkey point-and-click setup throughout
- −Shops that need native LXC container support alongside VMs
- −Teams requiring virtual disks larger than 2 TiB with snapshot capability
- −Environments unwilling to deploy and maintain a separate management VM
XCP-ng delivers on its promise of a fully open, community-governed hypervisor built on mature Xen technology, with no artificial feature limits and strong Linux Foundation backing. High-availability clustering, live migration, and enterprise-grade security come at no licensing cost. The two-tier management approach, where XCP-ng itself is bare-bones and full functionality requires deploying Xen Orchestra separately, adds setup friction. For those willing to navigate that, it is a credible VMware alternative for production workloads.
| Hypervisor type | Type 1 bare-metal, based on Xen Project 4.17 |
| Current LTS version | 8.3 LTS (released October 2024) |
| Maximum RAM per VM | 1.5 TiB |
| Maximum vCPUs per VM | Up to 128 vCPUs (UEFI guests) |
| Maximum host RAM | Up to 12 TiB (with security features) |
| Virtual disk limit (VHD format) | 2,040 GiB per disk (snapshots supported) |
| Management | CLI, API, XO Lite web UI (basic); Xen Orchestra (full features) |
| Guest OS support | Linux, Windows, BSD; HVM and PVH modes |
| License | GPLv2 and compatible free licenses |