Goodbye VMware, Hello XCP-ng

If any of you are looking at the massive cost of Broadcom’s takeover of VMware, well, let me introduce the freeware version of Citrix’s VM Hypervisor.

 

Hello XCP-ng V8.3

 

Over the last few years, I’ve been working to move from VMware cluster to XCP-ng Pools. Here’s the difference, in a VMware cluster, you can have all sorts of different network setups between the ESXi nodes. In XCP-ng, every xcp-ng node MUST MATCH the other node(s) Network. This means if ETH0 goes to 10.1.1.0 network, then every system’s ETH0 must go to the 10.1.1.0 network. If ETH1 and ETH2 are bonded to a “trunk” connection, then every xcp-ng’s eth1 and eth2 must do the same.

 

I will soon show some examples of how to migrate from VMware to XCP-ng.