XCP-ng is a free, open-source virtualization platform built on the Xen hypervisor, and Xen Orchestra is its web management tool. Together they are an alternative to Proxmox VE or VMware ESXi. This guide shows how to install XCP-ng and manage it with Xen Orchestra.
Before you start
- A 64-bit server with VT-x/AMD-V enabled; see enable hardware virtualization.
- IPMI or physical access to boot an ISO, and a static IP for the host.
- A second machine or VM to run Xen Orchestra, or let the quick deploy create it on the host.
- Background: Xen hypervisor explained.
Install XCP-ng
- Download the XCP-ng ISO from the official site and verify its checksum.
- Boot the server from it and follow the installer: keyboard, accept the EULA, choose the installation disk.
- Select a disk for local VM storage and choose EXT (thin provisioned, file-based) or LVM (thick provisioned).
- Set a root password, the management network interface, a static IP, hostname and DNS, and NTP.
- Reboot. The console shows the host's IP and a text menu (xsconsole).
Deploy Xen Orchestra
- XOA quick deploy: open
http://host-ipin a browser and use the deploy page to create the Xen Orchestra appliance VM. Check the current XOA edition terms on the vendor site. - From sources: the open-source community builds Xen Orchestra from source on a Debian VM with community install scripts, giving full features without a subscription but without vendor support.
Log in to Xen Orchestra and add your host under Settings → Servers with its IP and root credentials.
Create a VM
- Upload an ISO: create an ISO storage repository (local ISO library or NFS/SMB share) and upload the image.
- Click New → VM, choose a template matching the OS, set vCPUs, RAM, disk and network, and attach the ISO.
- Start the VM and install the OS from the web console.
Install guest tools
- Linux: install the
xe-guest-utilitiespackage (available from XCP-ng's guest tools ISO or distribution repositories) so the host sees IPs and can shut down cleanly. - Windows: install the XCP-ng/Xen PV drivers for performance.
Secure and maintain
- Keep management interfaces on a private network or VPN; see Tailscale for servers.
- Apply updates with
yum updateon the host (XCP-ng is CentOS-based in its dom0) or through Xen Orchestra. - Schedule backups in Xen Orchestra to a remote target.
Troubleshooting
- Host not reachable after install: wrong management NIC selected; fix it in xsconsole.
- VM creation greyed out: no storage repository with free space.
- Poor VM performance: guest tools missing.
Frequently asked questions
XCP-ng or Proxmox VE?
Both are free. Proxmox is Debian/KVM with built-in web UI and containers; XCP-ng is Xen with Xen Orchestra. Pick based on familiarity and ecosystem; see hypervisor comparison.
Can I migrate from VMware?
Xen Orchestra includes tools to import VMs from VMware.
Does XCP-ng support clustering?
Yes, hosts form pools with shared storage and live migration.