@agowa338@chaos.social @txt_file@chaos.social Xen was developed for security, KVM for performance. Nowadays, they don’t differ much in those aspects (even they’re completely different architecturell concepts). One thing was mono-threaded disk devices which came on a par by the count of VM instances but as said, nothing for nowadays anymore.

Today, it’s more about conceptions designs and “orchestrators”. Everyone is talking about Proxmox as a KVM orchestrator/frontend but it also has some major cons. The multi-master architecture with corosync may not fit always (cluster size, latency, distance,..). I crafted a solution for this (#ProxWire https://cdn.gyptazy.com/talks/ProxWire_Connecting_Proxmox_Clusters_Around_the_World_Without_Corosync.pdf) but this also comes with some pitfalls.

With my tools like #ProxLB (bringing in DRS alike resource scheduling which also got invited for a presentation at the Dutch Proxmox Day 2025), #ProxCLMC for something like EVC evaluation, #ProxSnap (snapshot manager), ProxWall (microsegmentation) and #ProxWire, I try to fill the gaps my customers have.

Personally, I like #xcpng really much and it’s closer to the VMware approach while #proxmox might provide a faster quickstart (where often people later run into issues). The best is like always: evaluate your requirements and see which fits best.