Bug 1913843
Summary: | Disable NUMA Tuning for non-pinned vNUMA nodes | ||
---|---|---|---|
Product: | [oVirt] ovirt-engine | Reporter: | Arik <ahadas> |
Component: | BLL.Virt | Assignee: | Lucia Jelinkova <ljelinko> |
Status: | CLOSED CURRENTRELEASE | QA Contact: | Polina <pagranat> |
Severity: | unspecified | Docs Contact: | |
Priority: | unspecified | ||
Version: | 4.4.4 | CC: | aperotti, bugs |
Target Milestone: | ovirt-4.5.0 | Flags: | 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
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. The UI could be modified so that the numa tuning dropdown would be disabled or hidden for unpinned nodes. 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 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. |