Created attachment 1868541 [details] logs Description of problem: VM with resize_and_pin policy having topology cores*threads 23*2. Version-Release number of selected component (if applicable): ovirt-engine-4.5.0.1-602.3fe8f849c244.6.el8ev.noarch How reproducible:100% on host with topology CPU(s): 48 On-line CPU(s) list: 0-47 Thread(s) per core: 2 Core(s) per socket: 24 Socket(s): 1 NUMA node(s): 4 Steps to Reproduce: 1. Build VM on the base of infra template . Configure it with resize_and_pin policy and pin to the host with mentioned topology. 2. Run the VM 3. Check on host: virsh -r dumpxml 11 |grep "<vcpupin vcpu=" Also run GET https://{{host}}/ovirt-engine/api/vms Actual results: The VM has correct cpu topology <topology> <cores>23</cores> <sockets>1</sockets> <threads>2</threads> </topology> but under dynamic_cpu we have only 40 vcpus instead of 46. Expected results: all 46 vcpus must be under dynamic_cpus Additional info: the issue happens on ocelot05.qa.lab.tlv.redhat.com in engine log line 18314
We assume it's a regression but please correct us if we're wrong
This bug report has Keywords: Regression or TestBlocker. Since no regressions or test blockers are allowed between releases, it is also being identified as a blocker for this release. Please resolve ASAP.
Removing regression flag and lowering the priority. Polina, did it work before on this environment? We have BZ 1955388, where we decided to not allow hosts with number of sockets != NUMA node count. This means in your current host (1 socket, 4 NUMA nodes) the policy will be forbidden.
Hi I didn't set regression flag , maybe it was set automatically. Also, I'm not sure if it worked before in this environment. Do you mean before the resize_and_pin policy? I'm not sure. if this is important I can deploy the 4.4.10 on this environment to re-check. If your question is about resize_and_pin policy , I think this test is performed on this env for the first time.
(In reply to Liran Rotenberg from comment #3) > We have BZ 1955388, where we decided to not allow hosts with number of > sockets != NUMA node count. > This means in your current host (1 socket, 4 NUMA nodes) the policy will be > forbidden. +1 *** This bug has been marked as a duplicate of bug 1955388 ***