Status of XCP-ng 7.6: beta out soon

stormi

Hi there!

I suppose you want to know how close we are from releasing XCP-ng 7.6.

So:

The online repositories are up and populated with most of the packages we need: https://updates.xcp-ng.org/7/7.6/
I built a test installer ISO, not published yet

We are close from a state where we can release a beta version, but there's a last important thing to sort out: remember the closed-source emu-manager that XenServer requires in order to be able to suspend, resume or live-migrate VMs? We wrote a replacement called xcp-emu-manager for XCP-ng 7.5 and also opened https://bugs.xenserver.org/browse/XSO-878, but suspend and resume are broken again in XCP-ng 7.6. As soon as it is sorted out, we'll release the beta.

Update: the beta is now out: https://xcp-ng.org/forum/topic/454/xcp-ng-7-6-beta

maxcuttins

borzel

@stormi said in Status of XCP-ng 7.6: beta out soon:

https://bugs.xenserver.org/browse/XSO-878

not fun

sriccio

So, if I understand correctly, XenServer is not an Open Source project anymore. As the basic features relies on a closed source component ?
(and will stay like this).

stormi

Not all the basic features. Some of them, but important ones.

r-pufky

Is there a general roadmap or feature set that will release with 7.6 (I haven't been able to find one). Please let me know.

I'm interested in seeing if 7.6 will include a 4.10+ kernel with it.

stormi

We'll have the same kernel as XenServer 7.6, which is a 4.4 kernel with many patches.

Andre

@stormi said in Status of XCP-ng 7.6: beta out soon:

Not all the basic features. Some of them, but important ones.

By the look of XSO-878, it seems that VM lifecycle is going to be "locked" away for GPU bound VM?
I mean regular server headless VMs can carry on with your closed source or even vGPU VM could?
I can see XCP-ng doing nicely for server like VMs and Citrix focusing on licenced products for GPU VMs....
I'm not sure I read this intent well, so I'd gladly welcome any insight from NG team (if not too time consuming) or anybody else.

Thx

olivierlambert

No, the problem is that's not only for vGPU bound VM, but all VMs. That's why we are not very happy with this "issue". VGPU is mainly done on Nvidia, which is proprietary anyway, so yes, we are focused on server virtualization.

But in this case, it breaks all VMs for suspend/resume, regardless vGPU or not. And obviously, that's not something bothering Citrix…

Andre

@olivierlambert was afraid so. Thx for taking the time to clarify.
Don't you feel this is a blocker for ng's future and might call for the community to try and help in some way?

olivierlambert

This is the case since 7.5, we already found a workaround, we'll find it here too. This time, we'll probably document more the procedure. It's just that the person who did it the first time is less available recently, so we have to wait a bit.

stormi

Beta is out: https://xcp-ng.org/forum/topic/454/xcp-ng-7-6-beta