Amazing guys ! By this way, the platform will become better than ever
I will follow this very closely.

Keep going !

Done

Tested on Windows 10 1903 (French locale as usual), seems good too and easier than ever.
I let you know if something bad happens.

Wow didn't expected this kind of news so early after the launch of the project.
Congrats team, this is so much merited

No problem here, RHEL 8 support for guest tools works as expected (tested on the last RHEL 8.1 release), good job

Just updated my homelab server from XCP-ng 7.6 to XCP-ng 8.0 Beta, so far so good. I also tested the new experimental UEFI mode with Windows VM, seems good too.

I also tested the new XOA deployment through the Web interface of my host, perfect !

We will see during the following week how it goes

Niiicce Especially the new quick XOA deployment, that is more turnkey than ever
I will migrate to XCP-ng 8.0 in my lab this weekend and start provide some tests.

I continue to work on it but the results are not that good. The main problem is one of the main feature, "everything is container".

I managed to start the xe-daemon in a privileged CentOS container by installing the xe-guest RPMs, but only the show of virtualization mode worked, nothing for the network or soft shutdown. RancherOS should work in PVHVM mode by default for sure due to it's recent 4.14 kernel btw.

I hate give up on things, but I start to think more and more to use CoreOS instead of RancherOS, and use Rancher Server or RKE on top, it will be the same and much more hassle-free. Moreover, the XenServer tools supports CoreOS, it's clearly a better way to proceed.

I will give an another try this evening.

Usually I use English version, but I only have access to a French version of WS 2019 (still waiting stuff from MS Imagine ). I can test with W10 and WS 2016 too.

For Windows Update, that was just a XOA test, just try to install the drivers but they seems not available.

Exactly.

• Installation of a fresh Windows Server 2016/2019
• Load the ISO provided by borzel
• Tools installation with the Setup.exe
• Reboot, that's it. Simple as VMware Tools

Why not using a systemd unit instead of forever ?

Even with the package 'xscontainer' is installed, CoreOS is moving very fast and the compatibility is not good atm. And Citrix doesn't seems to give much interest in this plugin.

Try to disable C-States, it could also improve a lot of operations, including storage.

I had an issue too yesterday with XO 5.51.1 for importing an exported VM (IMPORT_ERROR_EOF). Update to XO 5.52 solved the problem.

Interesting news

But the improvements in export/import should be more amazing with the zstd from XCP-ng :
The reduction in the time it takes to import or export a VM depends on the specific hardware of the machine. Reductions of 30% to 40% are common. Reductions of 30% to 40% are common

Wow didn't expected this kind of news so early after the launch of the project.
Congrats team, this is so much merited

Yes, 32 vCPU is for very specific use cases. So, enjoy your experience

Have you tried XenOrchestra ? It removes some dumb limits (without further problems), and I guess you can set more than 32 vCPU without using CLI.

I heard some issues on a French Discord about a guy who tried to allocate more than 64 vCPU on a Windows VM and he had constants BSOD. So, 32 vCPU should be fine I guess.

There is indeed a limitation described here concerning the maximum number of vCPU per VM :
https://docs.citrix.com/en-us/citrix-hypervisor/system-requirements/configuration-limits.html