With Broadcom's licensing changes to VMware's portfolio, more and more admins and homelabbers are looking for alternatives to vSphere for virtualization. One of the most mature open-source options is XCP-ng, a free Xen-based hypervisor, paired with Xen Orchestra as its management interface — the equivalent of what vCenter is for ESXi.
In this article we'll walk through setting up a complete XCP-ng + Xen Orchestra environment entirely inside VMware Fusion on a Mac. This is a great way to try out the stack in a lab environment before committing physical hardware to it, or simply to get familiar with the tooling.
Why XCP-ng?
XCP-ng is built on the Xen hypervisor — the same technology underpinning AWS EC2 for many years — and is completely free and open source, with no artificial feature gating. Paired with Xen Orchestra, it offers:
- Pool/cluster management
- Live migration
- Backup and replication
- A full REST API
- A modern web UI
Unlike ESXi, there's no license key, no feature tiers, and no vendor lock-in. The commercial model (XOA, the official Xen Orchestra Appliance) is entirely optional — you can build Xen Orchestra yourself from source for free, which is exactly what we did here using the Xen Orchestra Community Edition (XOA CE).
The Lab Setup
For this test we used two VMs inside VMware Fusion on an Intel-based Mac:
- XCP-ng host — the hypervisor itself
- Xen Orchestra — a minimal Debian 13 VM running the XO management stack
Both VMs were placed on bridged networking so they'd get their own IP addresses on the local LAN and could reach each other (and the outside world) directly.
A note on nested virtualization
Since XCP-ng is itself a type-1 hypervisor, running it inside a VM means you need nested virtualization support. In VMware Fusion, this is the "Enable hypervisor applications in this virtual machine" / "Virtualize Intel VT-x/EPT" option in the VM's processor settings. Without this enabled, the XCP-ng installer will refuse to boot properly or VMs created on top of it won't start.
Keep in mind this setup is for testing and learning purposes. Running a hypervisor nested inside another hypervisor adds overhead, so for production use, XCP-ng should be installed directly on bare-metal hardware.
Step 1 — Installing XCP-ng
- Download the XCP-ng ISO from the official XCP-ng website.
- Create a new VM in VMware Fusion, pointing the installer to the ISO. Give it a reasonable amount of RAM and CPU (4+ GB RAM and 2+ vCPUs is a sane minimum for a lab), a disk of at least 50 GB, and bridged networking.
- Enable nested virtualization in the VM's CPU settings before first boot.
- Boot the VM and walk through the XCP-ng text-mode installer: accept the keyboard layout, select the installation disk, set a strong root password, and configure networking (DHCP is fine for a lab).
- Once installation finishes and the VM reboots, the console will show the host's IP address — this is what you'll use later to connect from Xen Orchestra.
Since XCP-ng 8.3, the host actually ships with a built-in web UI called XO Lite, reachable by simply browsing to the host’s IP address. It’s more capable than you might expect — a dashboard with host/VM status, resource usage stats, available patches, network and storage overviews, and even basic VM creation. What it doesn’t do is backup/replication jobs or multi-pool orchestration — for that, and for the full management experience, a proper Xen Orchestra instance is still the way to go (XO Lite even has a handy “Access XOA” button that links straight to it once it’s set up).
Step 2 — Installing Xen Orchestra (Community Edition)
Rather than using the official paid XOA appliance, we deployed Xen Orchestra from source, using the community-maintained xen-orchestra-installer-updater script by ronivay. This script automates the otherwise tedious process of building xo-server and xo-web from the official Vates repository.
- Create a second VM in Fusion — a minimal Debian 13 (Trixie) install works well. During the Debian installer's software selection step, we deselected the desktop environment and GNOME (a GUI isn't needed for a headless server), keeping things lightweight.
- After Debian finishes installing and reboots, log in as root on the console.
- Install the basic tools needed to fetch the installer script:
apt update && apt install -y git curl sudo - Clone the installer/updater repository:
git clone https://github.com/ronivay/XenOrchestraInstallerUpdater.git cd XenOrchestraInstallerUpdater - Copy the sample configuration file — the defaults are sensible for a first install:
cp sample.xo-install.cfg xo-install.cfg - Run the installer:
sudo ./xo-install.sh --install
The script takes care of everything: installing Node.js, Yarn, and Redis, fetching the Xen Orchestra source code, and building xo-server and xo-web. This build step is the most time-consuming part of the whole process — on a modest lab VM it can easily take 10–15 minutes, so this really is a "grab a coffee" moment, as the script itself helpfully points out.
Once finished, the script reports that the web UI is available on port 80, with default credentials:
Default username: admin@admin.net
Default password: admin
Change this password immediately after your first login — more on that below.
Step 3 — Connecting Xen Orchestra to the XCP-ng Host
With Xen Orchestra running, open a browser and navigate to the IP address of the Debian VM (e.g. http://<xo-ip-address>). After logging in with the default credentials:
- Click "+ Connect pool" on the dashboard.
- Fill in:
- IP address: the IP of your XCP-ng host
- Username:
root - Password: the root password you set during the XCP-ng install
- Check "Accept self-signed certificates", since XCP-ng uses a self-signed cert by default.
- Click Connect.
Within a few seconds, Xen Orchestra discovers the pool and host, and they appear in the tree view on the left. From here you have full access to create and manage VMs, monitor resource usage, configure storage repositories, and set up backup jobs — all from a clean, modern web interface.
Housekeeping: Change the Default Password
The very first thing to do after a fresh install is change the default Xen Orchestra admin password. In the web UI, go to Administration → Users, select the admin@admin.net account, and update the credentials to something strong and unique. Leaving the default admin/admin combination in place — even in a lab — is an easy way to get caught out later.
Where to Go From Here
This lab setup only scratches the surface of what the XCP-ng + Xen Orchestra combination offers. If you want to explore further, some good next steps are:
- Pools: add multiple XCP-ng hosts into a single pool for live migration and shared resource management.
- Storage repositories: connect NFS, iSCSI, or local storage, and experiment with shared storage across a pool.
- Backups: Xen Orchestra has a built-in backup/replication engine — well worth testing against a few throwaway VMs.
- Updates: the same
XenOrchestraInstallerUpdaterscript used for the install can also be used to update Xen Orchestra in place by re-running it — keeping your CE build current without needing the paid XOA subscription. - REST API: XCP-ng and Xen Orchestra both expose APIs, useful if you want to automate VM provisioning as part of an infrastructure-as-code workflow.
- Bare-metal install: once comfortable with the tooling, the natural next step is installing XCP-ng directly on physical hardware — nested virtualization is great for learning, but it adds a performance penalty you won't want in production.
Conclusion
For anyone evaluating alternatives to ESXi following VMware's licensing changes, XCP-ng combined with Xen Orchestra is a serious, mature, and completely free option. Spinning it up inside VMware Fusion — as shown here — is a low-risk, zero-cost way to get hands-on experience with the platform before deciding whether it's the right fit for your environment.




