XenServer 8.0 - Major update due Q1 2019
-
I have removed the Feature Restricton of Corosync, that it is also available, because it is availbale in the Citrix Hypervisor 8, but I think you aren't allow to distribute this Feature, as it isn't Open Source. I wanted to test the GFS2 Feature.
I have added Corosync in additional_feature and in keys_of_additional_features the same I also did for the UEFI Secureboot.
I added it in additional_feature with the Name "GuefiSecureBoot" and in "keys_of_additional_features" with "GuefiSecureBoot, (Negative, "restrict_guefi-secureboot");"I hope it is clear what I did.
I forgot to save the patch File otherwise I could send it to you. The Compilation of the Package was done with your xcp-ng-build-env. -
-
@akurzawa: What do you want to say?
-
Just wondering strongly if xcp-ng will support disks bigger than 2TBs
-
I think there is a lot of conversations around this forum about this
SMAPIv3 is able to use qcow2instead of VHD, allowing to get rid of the 2TiB limit.However, SMAPIv3 is far from being production ready now. See the dev diary in News section
-
@olivierlambert said in XenServer 8.0 - Major update due Q1 2019:
However, SMAPIv3 is far from being production ready now. See the dev diary in News section
We all wait for updates
-
@gangsterrapper22 Thanks. The reason why we restrict corosync in the license daemon is to avoid XCP-ng Center advertise it as available when it isn't.
-
Still max 32 vcpu limit per VM. This is too litle!
-
This is not a real limit: we even unlocked this artificial limit in Xen Orchestra.
It's 128 in HVM guest, see https://wiki.xenproject.org/wiki/Xen_Project_Release_Features
-
You should consider, that efficiency of vCPUs goes down by each one you add. I don't have the link to that Citrix document handy, so you need to google that.
If you really need that many cores, you should consider a physical machine, which should make a serious bump in performance.
AFAIR it was the overhead of the Xen scheduler, which needs to balance the needs of your VM. The more vCPUs one VM has, the bigger the overhead. I'm sure it didn't change in more recent versions. -
Absolutely @cg
-
Well, it's not entirely true. You can do vCPU pinning if you want to avoid any bad placement on very large core setup, so Xen cost will be virtually non-existent. This is working well.
The main reason for Citrix to limit vCPU number is for support reasons: there is some odd combination possible in some case on some hardware.
-
@ Oli and the XCP-NG team ..
Will the Westmere EP (aka X5xx series etc) Xeons be supported by XCP-NG 8.0 as the XS HCL no longer lists them as a supported CPU?
-
How about doing your own matrix?
