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:
libvirt could have a check to host node during use numatune
Version-Release number of selected component (if applicable):
libvirt-1.2.17-6.el7.x86_64
How reproducible:
100%
Steps to Reproduce:
1. prepare a running guest and bind guest to a invalid nodeset:
# virsh numatune test3 0 100
error: Unable to change numa parameters
error: Invalid value '100' for 'cpuset.mems': Invalid argument
2.
3.
Actual results:
libvirt do not check if the node is available then try to set the node to cgroup
Expected results:
just like when we start a guest with invalid nodeset:
# virsh start test3
error: Failed to start domain test3
error: unsupported configuration: NUMA node 100 is unavailable
Additional info:
Upstream patch could fix this:
commit c8e5177303f1b17a5e3116c6a8693391a3539bb9
Author: Luyao Huang <lhuang>
Date: Fri Aug 14 17:37:28 2015 +0800
qemu: add a check for nodeset in qemuDomainSetNumaParamsLive
v1.2.18-175-gc8e5177
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: libvirt could have a check to host node during use numatune Version-Release number of selected component (if applicable): libvirt-1.2.17-6.el7.x86_64 How reproducible: 100% Steps to Reproduce: 1. prepare a running guest and bind guest to a invalid nodeset: # virsh numatune test3 0 100 error: Unable to change numa parameters error: Invalid value '100' for 'cpuset.mems': Invalid argument 2. 3. Actual results: libvirt do not check if the node is available then try to set the node to cgroup Expected results: just like when we start a guest with invalid nodeset: # virsh start test3 error: Failed to start domain test3 error: unsupported configuration: NUMA node 100 is unavailable Additional info: Upstream patch could fix this: commit c8e5177303f1b17a5e3116c6a8693391a3539bb9 Author: Luyao Huang <lhuang> Date: Fri Aug 14 17:37:28 2015 +0800 qemu: add a check for nodeset in qemuDomainSetNumaParamsLive v1.2.18-175-gc8e5177