Bug 1913843

Summary: Disable NUMA Tuning for non-pinned vNUMA nodes
Product: [oVirt] ovirt-engine Reporter: Arik <ahadas>
Component: BLL.VirtAssignee: Lucia Jelinkova <ljelinko>
Status: CLOSED CURRENTRELEASE QA Contact: Polina <pagranat>
Severity: unspecified Docs Contact:
Priority: unspecified    
Version: 4.4.4CC: aperotti, bugs
Target Milestone: ovirt-4.5.0Flags: pm-rhel: ovirt-4.5?
pm-rhel: planning_ack?
ahadas: devel_ack+
pm-rhel: testing_ack+
Target Release: 4.5.0   
Hardware: Unspecified   
OS: Unspecified   
Whiteboard:
Fixed In Version: ovirt-engine-4.5.0 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 Arik 2021-01-07 17:31:57 UTC
We currently write <numatune> only to vNUMA nodes that are pinned to physical NUMA nodes. Now that we can the 'mode' property at the NUMA node-level (bz 1729897), it's time to write it also for vNUMA nodes that are not pinned to physical NUMA nodes.

Comment 1 Liran Rotenberg 2021-04-25 10:53:30 UTC
After some research - it's impossible to set the vNUMA tune without pinning it (automatically or not).
We could use libvirt automatic pinning and providing a physical NUMA set to use. Or, explicitly pin the NUMAs in the engine to our desire.

This will require us to have a layer managing everything, for now we are aligned with libvirt NUMAs and we shouldn't pin them.

We should however change the UI so we won't let the user set a vNUMA tuning without the pinning.

Comment 2 Lucia Jelinkova 2021-06-23 12:15:46 UTC
The UI could be modified so that the numa tuning dropdown would be disabled or hidden for unpinned nodes.

Comment 3 Polina 2022-03-23 12:32:32 UTC
verified on ovirt-engine-4.5.0.1-602.3fe8f849c244.6.el8ev.noarch.

In UI the 'Tune mode' is disabled for not pinned vNUMA nodes and enabled for pinned vNUMA nodes

Comment 4 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.