Bug 1729897

Summary: [RFE] Per-vNUMA node tuning modes
Product: Red Hat Enterprise Virtualization Manager Reporter: Stefan Hajnoczi <stefanha>
Component: ovirt-engineAssignee: Liran Rotenberg <lrotenbe>
Status: CLOSED ERRATA QA Contact: Polina <pagranat>
Severity: medium Docs Contact:
Priority: medium    
Version: 4.2.6CC: ahadas, aperotti, aromito, dfodor, emarcus, ljelinko, lrotenbe, mkalinin, mtessun, sfroemer
Target Milestone: ovirt-4.4.4Keywords: FutureFeature
Target Release: 4.4.4   
Hardware: Unspecified   
OS: Unspecified   
Whiteboard:
Fixed In Version: ovirt-engine-4.4.4.4 Doc Type: Enhancement
Doc Text:
Previously, the NUMA tune mode was set according to the Virtual Machine, using the same setting for every virtual NUMA node of the Virtual Machine. In this release, it is possible to set the NUMA tune mode for each virtual NUMA node.
Story Points: ---
Clone Of: Environment:
Last Closed: 2021-02-02 13:58:29 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:
Bug Depends On:    
Bug Blocks: 1789090    

Description Stefan Hajnoczi 2019-07-15 09:19:54 UTC
The NUMA Tuning Mode can be set to Preferred or Interleave in RHV.  Preferred is only allowed when there is 1 vNUMA node.

Libvirt is more flexible and supports per-vNUMA node tuning, so it's conceivable that RHV could offer per-vNUMA node tuning:
https://libvirt.org/formatdomain.html#elementsNUMATuning

The "Preferred" NUMA Tuning Mode is more attractive than "Interleave" when there are multiple vNUMA nodes.  Each vNUMA node should allocate memory from one host NUMA node for best locality, if possible.  This should work even when vNUMA nodes are not pinned to host NUMA nodes.  The underlying libnuma APIs in Linux seem to make this possible so RHV and possibly libvirt should expose this behavior.

Comment 6 Polina 2020-12-30 15:15:35 UTC
verified according to the attached polarion cases on ovirt-engine-4.4.4.6-0.1.el8ev.noarch.

Comment 12 errata-xmlrpc 2021-02-02 13:58:29 UTC
Since the problem described in this bug report should be
resolved in a recent advisory, it has been closed with a
resolution of ERRATA.

For information on the advisory (RHV Engine and Host Common Packages 4.4.z [ovirt-4.4.4]), and where to find the updated
files, follow the link below.

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

https://access.redhat.com/errata/RHBA-2021:0312