Replies: 3 comments 2 replies
-
|
Thanks for opening your first issue here! Be sure to follow the issue template! |
Beta Was this translation helpful? Give feedback.
-
|
We are using mixed hardware in sinlge cluster and vm.allocation.algorithm global setting set to "firstfitleastconsumed" cpu.overprovisioning.factor = 1 Below are the HW types |
Beta Was this translation helpful? Give feedback.
-
|
we are using same OS and HW is also same but only difference is CPU cycle. Any suggestions why cpu allocation is exceeding 100% though overprovisioning is set to 1 and cluster.cpu.allocated.capacity.disablethreshold is also 100% |
Beta Was this translation helpful? Give feedback.
Uh oh!
There was an error while loading. Please reload this page.
-
problem
We are experiencing an issue with the cpu overprovisioning factor in ACS. Although the parameter cpu.overprovisioning.factor is set to 1, VMs are still being deployed on hosts even after reaching full CPU allocation. This is resulting in allocation exceeding 100%.
Refer the attached snippet
CPU: 2 processors, Intel(R) Xeon(R) Gold 6148 CPU (2.40 GHz / 20-core). Hyperthreading is enabled. (80 * 2.4 = 192 GHZ )
Memory: 768 GB
cpu.overprovisioning.factor is set to 1 globally and at cluster level.
versions
ACS Version: 4.20.2.0
DB : Maria DB 10.3.39
ACS and KVM host : RHEL 8
The steps to reproduce the bug
...
What to do about it?
Beta Was this translation helpful? Give feedback.
All reactions