Bug 2065152

Summary:	Implicit CPU pinning for NUMA VMs destroyed because of invalid CPU policy
Product:	[oVirt] ovirt-engine	Reporter:	Tomáš Golembiovský <tgolembi>
Component:	Backend.Core	Assignee:	Liran Rotenberg <lrotenbe>
Status:	CLOSED CURRENTRELEASE	QA Contact:	Polina <pagranat>
Severity:	high	Docs Contact:
Priority:	unspecified
Version:	4.5.0	CC:	ahadas, bugs, mperina
Target Milestone:	ovirt-4.5.0	Keywords:	Regression
Target Release:	4.5.0.1	Flags:	pm-rhel: ovirt-4.5? pm-rhel: blocker?
Hardware:	Unspecified
OS:	Unspecified
Whiteboard:
Fixed In Version:	ovirt-engine-4.5.0.1	Doc Type:	If docs needed, set a value
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:	2022-04-20 06:33:59 UTC	Type:	Bug
Regression:	---	Mount Type:	---
Documentation:	---	CRM:
Verified Versions:		Category:	---
oVirt Team:	Virt	RHEL 7.3 requirements from Atomic Host:
Cloudforms Team:	---	Target Upstream Version:
Embargoed:

Description Tomáš Golembiovský 2022-03-17 11:58:11 UTC

When VM with NUMA configured is started Engine generates CPU pinning to make sure vCPUs are located on respective NUMA nodes on host (based on configured NUMA pinnig). But because Engine specifies CPU policy as "none" this CPU pinning is later destroyed by VDSM and CPUs from shared pool are used.

The CPU policy for NUMA VMs should be set to "manual" to preserve the CPU pinning.

Comment 1 RHEL Program Management 2022-03-17 12:05:49 UTC

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.

Comment 2 Polina 2022-04-11 14:12:57 UTC

verified on 4.5.0.2-0.7.el8ev
by running automation tests (sla/rhevmtests.compute.sla.numa.numa_test.TestStrictNumaModeOnVM.test_cpu_pinning and numa_test.TestPreferModeOnVm.test_cpu_pinning) . the tests get numa cpu pinning on host , compares the VM cpu pinning in cat /proc/700992/task/*/status |grep Cpus_allowed_list.
Tested also for the migration case.

Comment 3 Sandro Bonazzola 2022-04-20 06:33:59 UTC

This bugzilla is included in oVirt 4.5.0 release, published on April 20th 2022.

Since the problem described in this bug report should be resolved in oVirt 4.5.0 release, it has been closed with a resolution of CURRENT RELEASE.

If the solution does not work for you, please open a new bug report.