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:
guest have broken settings after use setvcpus --maximum to make vcpu number < vcpu number in numa
Version-Release number of selected component (if applicable):
libvirt-1.3.3-2.el7.x86_64
How reproducible:
100%
Steps to Reproduce:
1.prepare a guest which have numa element in xml
# virsh dumpxml rhel7.0-rhel --inactive
<vcpu placement='static'>20</vcpu>
...
<cpu>
<numa>
<cell id='0' cpus='0,2' memory='512000' unit='KiB'/>
<cell id='1' cpus='1,3' memory='512000' unit='KiB'/>
<cell id='2' cpus='4-19' memory='512000' unit='KiB'/>
</numa>
</cpu>
...
2. use setvcpus --maximum to change max vcpu:
# virsh setvcpus rhel7.0-rhel 10 --maximum --config
3. recheck xml:
<vcpu placement='static'>10</vcpu>
...
<cpu>
<numa>
<cell id='0' cpus='0,2' memory='512000' unit='KiB'/>
<cell id='1' cpus='1,3' memory='512000' unit='KiB'/>
<cell id='2' cpus='4-19' memory='512000' unit='KiB'/>
</numa>
</cpu>
...
4. restart libvirtd
# service libvirtd restart
Redirecting to /bin/systemctl restart libvirtd.service
# virsh list --all
Id Name State
----------------------------------------------------
5. check libvirtd log
internal error: Number of CPUs in <numa> exceeds the <vcpu> count
Actual results:
guest have broken settings after use setvcpus --maximum to make vcpu number < vcpu number in numa, and guest will disappear after restart libvirtd
Expected results:
report error when use setvcpus --maximum or guest won't have broken settings
Additional info:
commit b527e7c8e2e13c194cf32fee76d3be3d89365524
Author: Peter Krempa <pkrempa>
Date: Wed Apr 27 16:39:41 2016 +0200
qemu: Error out if setting vcpu count would lead to invalid config
When the domain definition describes a machine with NUMA, setting the
maximum vCPU count via the API might lead to an invalid config.
Add a check that will forbid this until we add more advanced cpu config
capabilities.
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/RHSA-2016-2577.html
Description of problem: guest have broken settings after use setvcpus --maximum to make vcpu number < vcpu number in numa Version-Release number of selected component (if applicable): libvirt-1.3.3-2.el7.x86_64 How reproducible: 100% Steps to Reproduce: 1.prepare a guest which have numa element in xml # virsh dumpxml rhel7.0-rhel --inactive <vcpu placement='static'>20</vcpu> ... <cpu> <numa> <cell id='0' cpus='0,2' memory='512000' unit='KiB'/> <cell id='1' cpus='1,3' memory='512000' unit='KiB'/> <cell id='2' cpus='4-19' memory='512000' unit='KiB'/> </numa> </cpu> ... 2. use setvcpus --maximum to change max vcpu: # virsh setvcpus rhel7.0-rhel 10 --maximum --config 3. recheck xml: <vcpu placement='static'>10</vcpu> ... <cpu> <numa> <cell id='0' cpus='0,2' memory='512000' unit='KiB'/> <cell id='1' cpus='1,3' memory='512000' unit='KiB'/> <cell id='2' cpus='4-19' memory='512000' unit='KiB'/> </numa> </cpu> ... 4. restart libvirtd # service libvirtd restart Redirecting to /bin/systemctl restart libvirtd.service # virsh list --all Id Name State ---------------------------------------------------- 5. check libvirtd log internal error: Number of CPUs in <numa> exceeds the <vcpu> count Actual results: guest have broken settings after use setvcpus --maximum to make vcpu number < vcpu number in numa, and guest will disappear after restart libvirtd Expected results: report error when use setvcpus --maximum or guest won't have broken settings Additional info: