“And in the fullness of time, on the last day of the promised Q1 2018, lo did Olivier deliver unto the world the primal release of XCP-ng.
And the sysadmins at large saw, and said “It is good.””
The promised day has come and gone, and left us with the first release of XCP-ng! I was a little late to the game to be on the “official” mirrors for this initial drop, but I’ve also got the .
Update Dec 30 2017
The open-source world has responded to this egregious action by re-awakening the old XCP program under a new name, XCP-ng.
I'm all for this, and will be watching closely and helping them out any way I can. Anyone else that has the personal bandwidth is encouraged to do so as well.
After using the open-source Xen hypervisor for a while, I moved to XenServer and loved it for years.
As I digressed in my last post, virtualizing pfSense wasn’t as difficult as I expected. From what I’d read online I was afraid it would have some adverse affect on network performance, especially considering most of my “infrastructure” is reclaimed, second-hand, or otherwise cast-off from production use.
It fully appears, however, that these fears were unfounded (standard Spectrum cable, don’t judge):
Physical 32bit Xen Virtualized 64bit Barely noticeable, and honestly well within the standard variance of such types of throughput tests.
Update Jan 31, 2018
This is verified (by me, at least) to work on both the official XenServer 7.2, and with the experimental xcp-ng. I've also semi-automated the process with these Ansible bits for new hardware / pool upgrades.
Don’t get me wrong, XenServer 7 is a huge improvement over previous versions, and still my product of choice for those that don’t want to pay a literal fortune for vmWare licensing.