I see people suggesting alternatives in the comments, I just wanted to give a small hands-on experience of running XCP-ng at work and Proxmox at home.<p>1. XCP-ng is a bit more polished and stable than Proxmox.
Both are supposedly level 1 hypervisors, but while XCP-ng separates the hypervisor from the rest of the OS, Proxmox bumps it all together. Meaning that if something goes wrong with other part of the base OS, it will affect Proxmox.<p>2. It's simpler to do hardware pass-through on Proxmox (there's a GUI for that), but XCP-ng is more stable. There were occasions in which I couldn't pass through a device on Proxmox, but it worked perfectly fine on XCP-ng.<p>3. Xen Orchestra is the new manager for XCP-ng, the old Windows utility (which was great and had more functionality) is now EOL. But the creators from Xen Orchestra are too focused on getting VMWare clusters to migrate to their product and fail to add much needed functionality.<p>4. XCP-ng doesn't allow you to start VMs at boot in a certain order.<p>5. XCP-ng doesn't auto-mount shares when they come online.<p>6. XCP-ng doesn't have vGPU functionality for Nvidia or for newer Intel GPUs.<p>7. XCP-ng makes it much easier to create clusters than Proxmox.<p>8. Proxmox has a big community behind, meaning you can do some nifty hacks like: install MacOS, install Synology NAS software, do vGPU unlock (don't confuse this with proper vGPU support).<p>Bottom line:
- I really want to like XCP-ng, but I'm migrating the work machines to Proxmox. Points 4, 5 and 6 are a big no-go, and it became a hassle to live with them. Unfortunately the developers, although polite, show no interest in improving those areas.