Bug 1550021 - rhvm GUI do not prompt warning message when the numa settings can not take effect immediately
Summary: rhvm GUI do not prompt warning message when the numa settings can not take ef...
Keywords:
Status: CLOSED DUPLICATE of bug 1573218
Alias: None
Product: ovirt-engine
Classification: oVirt
Component: Frontend.WebAdmin
Version: 4.2.0
Hardware: Unspecified
OS: Unspecified
low
medium
Target Milestone: ovirt-4.3.0
: ---
Assignee: Andrej Krejcir
QA Contact: Polina
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2018-02-28 10:32 UTC by yalzhang@redhat.com
Modified: 2019-04-28 10:03 UTC (History)
9 users (show)

Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed: 2018-12-04 15:31:49 UTC
oVirt Team: SLA
Embargoed:
rule-engine: ovirt-4.2?
mgoldboi: ovirt-4.3?
pm-rhel: devel_ack?


Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
Red Hat Bugzilla 1573218 0 medium CLOSED Updating CPU pinning setting or NUMA nodes setting for a running VM requires VM restart (should be updated only for VM n... 2021-02-22 00:41:40 UTC
oVirt gerrit 92806 0 master ABANDONED core: Show popup that numa config change requires VM restart 2018-12-03 09:34:14 UTC

Internal Links: 1573218

Description yalzhang@redhat.com 2018-02-28 10:32:41 UTC
Description of problem:
rhvm GUI do not prompt message like "changes need vm restart" when the changes can not take effect immediately 

Version-Release number of selected component (if applicable):
ovirt-engine-4.2.2.1-0.1.el7.noarch

How reproducible:
100%

Steps to Reproduce:
1. Register and host with numa node>1 to rhv server

2. Create an vm, then edit the vm from edit the VM.  
In 'System' page, set the Total Virtual CPUs to be 10
In "Host" page, set the vm "start Running on" the numa host

3. start the guest
Edit the vm, in "Host" page, 
change the Migration options to be "do not allow migration"
"Configure NUMA" -> "NUMA node count" as 2 (it will configure guest with 2 numa nodes)
Click the "NUMA pinning", on the NUMA Topolopy page, drag the vNUMA to NUMA node to pin the vNUMA to that node
pin vNUMA 0 to NUMA 0, and vNUMA1 to NUMA 1
click ok

4.  check the guest xml on host, the guest still has only 1 node and do not pin to any host NUMA node
# virsh dumpxml rhel 
...
 <numa>
      <cell id='0' cpus='0-9' memory='1703936' unit='KiB'/>
    </numa>
...

Actual results:
In step 3, after click "OK"  the setting can be saved, but no warning to indicate that such setting will take effect on next boot.


Expected results:
When click "OK" to save the setting, there should be a dialog box to inform the user that such setting will take effect on next boot, like:
"
Changes that require VM restart:
numa pin
numa node count
....
"

Comment 2 Andrej Krejcir 2018-08-17 14:23:33 UTC
This bug is a subset of Bug 1573218.


Note You need to log in before you can comment on or make changes to this bug.