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