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.
verified according to the attached polarion cases on ovirt-engine-4.4.4.6-0.1.el8ev.noarch.
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