Bug 1573218
Summary: | Updating CPU pinning setting or NUMA nodes setting for a running VM requires VM restart (should be updated only for VM next run) | ||
---|---|---|---|
Product: | [oVirt] ovirt-engine | Reporter: | Sharon Gratch <sgratch> |
Component: | BLL.Virt | Assignee: | Steven Rosenberg <srosenbe> |
Status: | CLOSED CURRENTRELEASE | QA Contact: | Beni Pelled <bpelled> |
Severity: | low | Docs Contact: | |
Priority: | medium | ||
Version: | 4.2.3 | CC: | ahadas, bpelled, bugs, mavital, michal.skrivanek, mtessun, sgratch, yalzhang |
Target Milestone: | ovirt-4.4.2 | Keywords: | EasyFix |
Target Release: | 4.4.2.3 | Flags: | pm-rhel:
ovirt-4.4+
mtessun: planning_ack+ ahadas: devel_ack+ mavital: testing_ack+ |
Hardware: | Unspecified | ||
OS: | Unspecified | ||
Whiteboard: | |||
Fixed In Version: | rhv-4.4.2-3, ovirt-engine-4.4.2.3 | Doc Type: | Bug Fix |
Doc Text: |
Cause: NUMA Node and CPU Pinning were not being updated properly when modified while the Virtual Machine was running. They were not supported by the Next Run mechanism that preserves changes until the Virtual Machine is brought down.
Consequence: Changes to the Numa Nodes and CPU pinning were not saved to the database.
Fix: Preserved changes to the Numa Nodes and CPU Pinning via the Next Run mechanism so that the values can be updated to the database when the Virtual Machine is brought down.
Result: Numa Node and CPU Pinning changes are preserved and updated to the database when the Virtual Machine is brought down.
|
Story Points: | --- |
Clone Of: | Environment: | ||
Last Closed: | 2020-09-18 07:11: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: |
Description
Sharon Gratch
2018-04-30 14:08:17 UTC
should be as simple as adding onStatuses = VMStatus.Down to @EditableVmField for these two. Severity...? *** Bug 1550021 has been marked as a duplicate of this bug. *** Re-targeting to 4.3.1 since it is missing a patch, an acked blocker flag, or both Missed the latest build Verified with: - ovirt-engine-4.4.2.3-0.6.el8ev.noarch - libvirt-6.0.0-25.module+el8.2.1+7154+47ffd890.x86_64 - vdsm-4.40.26-1.el8ev.x86_64 Verification steps: 1. Configure NUMA node on a running VM under 'Hosts > Numa Pinning' (NUMA Node Count == 1) 2. Check current CPU with 'virsh -r vcpuinfo <vm_name>' (CPU is 6 in my case) 3. Set 'CPU Pinning topology' under 'VM Edit > Resource Allocation > CPU Pinning topology' (0#12 in my case) Result: - After section 3, the CPU remains 6, and the next-run icon added to the VM. the CPU changed to 12 once the VM rebooted. This bugzilla is included in oVirt 4.4.2 release, published on September 17th 2020. Since the problem described in this bug report should be resolved in oVirt 4.4.2 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. |