Note: This bug is displayed in read-only format because
the product is no longer active in Red Hat Bugzilla.
RHEL Engineering is moving the tracking of its product development work on RHEL 6 through RHEL 9 to Red Hat Jira (issues.redhat.com). If you're a Red Hat customer, please continue to file support cases via the Red Hat customer portal. If you're not, please head to the "RHEL project" in Red Hat Jira and file new tickets here. Individual Bugzilla bugs in the statuses "NEW", "ASSIGNED", and "POST" are being migrated throughout September 2023. Bugs of Red Hat partners with an assigned Engineering Partner Manager (EPM) are migrated in late September as per pre-agreed dates. Bugs against components "kernel", "kernel-rt", and "kpatch" are only migrated if still in "NEW" or "ASSIGNED". If you cannot log in to RH Jira, please consult article #7032570. That failing, please send an e-mail to the RH Jira admins at rh-issues@redhat.com to troubleshoot your issue as a user management inquiry. The email creates a ServiceNow ticket with Red Hat. Individual Bugzilla bugs that are migrated will be moved to status "CLOSED", resolution "MIGRATED", and set with "MigratedToJIRA" in "Keywords". The link to the successor Jira issue will be found under "Links", have a little "two-footprint" icon next to it, and direct you to the "RHEL project" in Red Hat Jira (issue links are of type "https://issues.redhat.com/browse/RHEL-XXXX", where "X" is a digit). This same link will be available in a blue banner at the top of the page informing you that that bug has been migrated.
description of problem:
numa settings disapear after restart libvirtd
Version-Release number of selected component (if applicable):
libvirt-1.2.13-1.el7.x86_64
How reproducible:
100%
Steps to Reproduce:
1.edit a vm like this:
# virsh edit r6
<cpu>
<numa>
<cell id='0' cpus='0,2,4,6,8' memory='512000' unit='KiB'/>
<cell id='1' cpus='1,3,5,7,9' memory='512000' unit='KiB'/>
</numa>
</cpu>
2.start it and check running vm xml:
# virsh start test3
# virsh dumpxml test3
<cpu>
<numa>
<cell id='0' cpus='0,2,4,6,8' memory='512000' unit='KiB'/>
<cell id='1' cpus='1,3,5,7,9' memory='512000' unit='KiB'/>
</numa>
</cpu>
3. restart libvirtd and recheck
# service libvirtd restart
Redirecting to /bin/systemctl restart libvirtd.service
# virsh dumpxml test3
...
<cpu/>
...
Actual results:
numa settings disapear after restart libvirtd
Expected results:
fix it
infomation:
patch was just pushed these days:
commit d75e23bbfb92793ac6828a6eff6d909c5f92cc9b
Author: Luyao Huang <lhuang>
Date: Thu Mar 19 18:13:04 2015 +0800
conf: fix parsing of NUMA settings in VM status XML
Commit 5bba61f changed the XPath strings to be absolute when parsing
the VM NUMA configuration. Unfortunately the <domain> element is not a
top level element when parsing the domain status XML thus the absolute
XPath string doesn't match.
Use the relative string so that the <numa> settings are not lost.
Signed-off-by: Luyao Huang <lhuang>
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, 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://rhn.redhat.com/errata/RHBA-2015-2202.html
description of problem: numa settings disapear after restart libvirtd Version-Release number of selected component (if applicable): libvirt-1.2.13-1.el7.x86_64 How reproducible: 100% Steps to Reproduce: 1.edit a vm like this: # virsh edit r6 <cpu> <numa> <cell id='0' cpus='0,2,4,6,8' memory='512000' unit='KiB'/> <cell id='1' cpus='1,3,5,7,9' memory='512000' unit='KiB'/> </numa> </cpu> 2.start it and check running vm xml: # virsh start test3 # virsh dumpxml test3 <cpu> <numa> <cell id='0' cpus='0,2,4,6,8' memory='512000' unit='KiB'/> <cell id='1' cpus='1,3,5,7,9' memory='512000' unit='KiB'/> </numa> </cpu> 3. restart libvirtd and recheck # service libvirtd restart Redirecting to /bin/systemctl restart libvirtd.service # virsh dumpxml test3 ... <cpu/> ... Actual results: numa settings disapear after restart libvirtd Expected results: fix it infomation: patch was just pushed these days: commit d75e23bbfb92793ac6828a6eff6d909c5f92cc9b Author: Luyao Huang <lhuang> Date: Thu Mar 19 18:13:04 2015 +0800 conf: fix parsing of NUMA settings in VM status XML Commit 5bba61f changed the XPath strings to be absolute when parsing the VM NUMA configuration. Unfortunately the <domain> element is not a top level element when parsing the domain status XML thus the absolute XPath string doesn't match. Use the relative string so that the <numa> settings are not lost. Signed-off-by: Luyao Huang <lhuang>