Bug 1688186
Summary: | [RFE] CPU and NUMA Pinning shall be handled automatically | |||
---|---|---|---|---|
Product: | Red Hat Enterprise Virtualization Manager | Reporter: | Nils Koenig <nkoenig> | |
Component: | ovirt-engine | Assignee: | Liran Rotenberg <lrotenbe> | |
Status: | CLOSED ERRATA | QA Contact: | Polina <pagranat> | |
Severity: | high | Docs Contact: | ||
Priority: | high | |||
Version: | unspecified | CC: | aarnold, ahadas, aperotti, daniele, dfodor, djdumas, emarcus, lrotenbe, lsurette, mavital, mtessun, nkoenig, sfroemer, sgoodman, srevivo, ycui | |
Target Milestone: | ovirt-4.4.5 | Keywords: | FutureFeature | |
Target Release: | --- | |||
Hardware: | x86_64 | |||
OS: | Linux | |||
Whiteboard: | ||||
Fixed In Version: | ovirt-engine-4.4.5.5 | Doc Type: | Enhancement | |
Doc Text: |
Previously, the CPU and NUMA pinning were done manually or automatically only by using the REST API when adding a new virtual machine.
With this update, you can update the CPU and NUMA pinning using the Administration portal and when updating a virtual machine.
|
Story Points: | --- | |
Clone Of: | ||||
: | 1919804 (view as bug list) | Environment: | ||
Last Closed: | 2021-04-14 11:39:53 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: | 1919804, 1970426 |
Description
Nils Koenig
2019-03-13 10:51:31 UTC
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 |