CPU cores per socket setting not functional

[DagSonsteboSB]

ISSUE TYPE

• Bug Report
• Enhancement Request

COMPONENT NAME

• Cores per socket setting in user_vm_details / vm_template_details table when using XenServer hypervisor

CLOUDSTACK VERSION

• CloudStack version 4.9.2
• Not attempted reproduced in other versions but assumption is issue is still present in 4.11.x

CONFIGURATION, OS / ENVIRONMENT

• CloudStack 4.9.2
• XenServer 6.2 and 7.0 - fully licensed with Citrix licensing
• Advanced zone

SUMMARY

• Even with cpu.corespersocket (or cpuid.coresPerSocket as suggested in some mailing list threads) specified CloudStack will ignore this setting.
• All ACS specifications for cores and sockets will translate to "sockets" in XenServer
• Overall problem is some VMs when given a higher core count does not see all it's CPU cores/sockets.

STEPS TO REPRODUCE

• Create a VM with cpu count 4 cores
• Add entry for cpu.corespersocket=2 in user_vm_details
• Start VM
• Check allocation in XenCentre

EXPECTED RESULTS

• VM with 2 sockets and 2 cores per socket

ACTUAL RESULTS

• VM with 4 sockets

[rohityadavcloud]

Tentatively marked for 4.11.1.0 milestone, for testing this we'll require a pro version of XenServer. @DagSonsteboSB @PaulAngus do we have a test env to test a fix against?

[bdonnahue]

@PaulAngus is this still an issue? With XCP-ng, is a XenServer Pro license still required? Could the default behavior be to specify cores rather than sockets?

[rohityadavcloud]

@bdonnahue we'll need to test this, if you've a XCP-ng setup, can you test?

[bdonnahue]

@rhtyd I am happy to test but I want to clarify some things and ask some dumb questions. Are you on the slack channel?

[bdonnahue]

@rhtyd any updates? Building cloudstack from source was more complicated that I thought. I have not been able to make any progress here

[rohityadavcloud]

Let's revisit this after 4.11.2.0 gets released. /cc @DagSonsteboSB @PaulAngus