Repository navigation
CPU cores per socket setting not functional #2583
Description
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
Activity
yadvr commentedon May 1, 2018
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 commentedon Oct 19, 2018
@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?
yadvr commentedon Oct 19, 2018
@bdonnahue we'll need to test this, if you've a XCP-ng setup, can you test?
bdonnahue commentedon Oct 19, 2018
@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 commentedon Oct 28, 2018
@rhtyd any updates? Building cloudstack from source was more complicated that I thought. I have not been able to make any progress here
yadvr commentedon Oct 29, 2018
Let's revisit this after 4.11.2.0 gets released. /cc @DagSonsteboSB @PaulAngus
24 remaining items
progiss commentedon Dec 4, 2019
Hello,
We have the same problem with version 4.13 and KVM hypervisors.
How can we solve this problem because we are trying to create offering services with 45 cores and it affects only 2 cores
DaanHoogland commentedon Nov 25, 2020
there is a PR out for 4.14 that fixes this for KVM: #4497
AlexanderKgr commentedon May 28, 2021
this is still happening with 4.15.0 and xcp-ng
DaanHoogland commentedon May 28, 2021
The PR i mentioned is merged in the 4.14 branch @AlexanderKgr . If you need to it in 4.15 please test a nightly build, Otherwise it should be fixed in any upcoming release.
DaanHoogland commentedon Jul 20, 2021
@AlexanderKgr can you please check if this is still an issue on a recent 4.15 or on main and close if appropriate?
yadvr commentedon Aug 9, 2021
A PR claiming to fix this issue #4497 has been merged.
@AlexanderKgr @DagSonsteboSB please test 4.15.1/4.14.1 and re-open this if not satisfied, thanks.
Merge branch 'fix-failed-login-redirect-config' into '4.20.0.0-scclouds'