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:
cannot change the nodeset if we do not set the numatune in guest xml
Version-Release number of selected component (if applicable):
libvirt-1.2.16-1.el7.x86_64
How reproducible:
100%
Steps to Reproduce:
1. prepare a guest *without* numatune settings:
<memory unit='KiB'>1024000</memory>
<currentMemory unit='KiB'>1024000</currentMemory>
<vcpu placement='static'>5</vcpu>
<resource>
<partition>/machine</partition>
</resource>
<os>
<type arch='x86_64' machine='pc-i440fx-rhel7.2.0'>hvm</type>
<boot dev='hd'/>
</os>
2. start it and check the numa policy:
# virsh start test4
Domain test4 started
# virsh numatune test4
numa_mode : strict
numa_nodeset :
3.
# virsh numatune test4 --mode strict --nodeset 1
error: Unable to change numa parameters
error: Requested operation is not valid: change of nodeset for running domain requires strict numa mode
Actual results:
Cannot change the nodeset if we do not set the numatune in guest xml
from 2 step we know the mode is strict, but when we change the nodeset, libvirt
point out that our mode is not strict
cannot reproduce this issue with libvirt-1.2.15-2.el7.x86_64, so i think maybe this is a regression
Expected results:
2 option
1. show the "default" when we use numatune to check the mode, because we didn't set the numa bind mode in guest xml, and the display from numatune is against itself when we change the node set.
2. allow change the nodeset in step 3 (if with cgroup), because we allow change the nodeset even the guest have no numatune settings in libvirt-1.2.15-2.el7.x86_64, and as we change the nodeset via cgroup, we do not use the libnuma API if cgroup is available.
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: cannot change the nodeset if we do not set the numatune in guest xml Version-Release number of selected component (if applicable): libvirt-1.2.16-1.el7.x86_64 How reproducible: 100% Steps to Reproduce: 1. prepare a guest *without* numatune settings: <memory unit='KiB'>1024000</memory> <currentMemory unit='KiB'>1024000</currentMemory> <vcpu placement='static'>5</vcpu> <resource> <partition>/machine</partition> </resource> <os> <type arch='x86_64' machine='pc-i440fx-rhel7.2.0'>hvm</type> <boot dev='hd'/> </os> 2. start it and check the numa policy: # virsh start test4 Domain test4 started # virsh numatune test4 numa_mode : strict numa_nodeset : 3. # virsh numatune test4 --mode strict --nodeset 1 error: Unable to change numa parameters error: Requested operation is not valid: change of nodeset for running domain requires strict numa mode Actual results: Cannot change the nodeset if we do not set the numatune in guest xml from 2 step we know the mode is strict, but when we change the nodeset, libvirt point out that our mode is not strict cannot reproduce this issue with libvirt-1.2.15-2.el7.x86_64, so i think maybe this is a regression Expected results: 2 option 1. show the "default" when we use numatune to check the mode, because we didn't set the numa bind mode in guest xml, and the display from numatune is against itself when we change the node set. 2. allow change the nodeset in step 3 (if with cgroup), because we allow change the nodeset even the guest have no numatune settings in libvirt-1.2.15-2.el7.x86_64, and as we change the nodeset via cgroup, we do not use the libnuma API if cgroup is available.