As of today, when using the high performance VM profile the user has to manually create the CPU core pinning _and_ a NUMA pinning. While the NUMA pinning is UI based, the according CPU pinning requires generating a text string that represents the CPU core mapping. This is rather error prone and is requires "wrapping your head around" how that notion works, how the actual NUMA architecture is on the hypervisor. This feature request proposes that the actual CPU pinning should be derived from the NUMA architecture and pinning. Taking this idea even further, one could think of premade templates/profiles in order to pin to sockets/half a socket/quarter of sockets/two sockets, etc.
Additionally, this should be implemented in respect to live migration as well. As of today, the live migration of a CPU and memory pinned VM requires manually removing the memory pinning, migrating, restoring the memory pinning. This should be automated. Also CPU pinning should be flexible, so that it could migrate VM1 which uses e.g. NUMA node 0 on host A gets migrated to host B, NUMA node 1 automatically.
*** Bug 1887356 has been marked as a duplicate of this bug. ***
As mentioned in bz 1887356, we introduced auto-pinning only to REST-API in BZ 1862968. We can build on that to simplify the configuration on pinning for high-performance VMs from the UI as well.
(In reply to Nils Koenig from comment #1) > Additionally, this should be implemented in respect to live migration as > well. As of today, the live migration of a CPU and memory pinned VM requires > manually removing the memory pinning, migrating, restoring the memory > pinning. This should be automated. Also CPU pinning should be flexible, so > that it could migrate VM1 which uses e.g. NUMA node 0 on host A gets > migrated to host B, NUMA node 1 automatically. Nils, this part seems like a different requirement - can you please file a separate bug for this?
verified on ovirt-engine-4.4.5.6-0.11.el8ev.noarch according to the attached Polarion plan
Liran, please check the doc text, and explain how to update the CPU and NUMA pinning.
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 (Moderate: RHV Manager (ovirt-engine) 4.4.z [ovirt-4.4.5] security, bug fix, enhancement), 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/RHSA-2021:1169