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.
Bug 2137804 - Inconsistent error msg prompts when setting inexistent nodeset with restrictive numa tuning mode
Summary: Inconsistent error msg prompts when setting inexistent nodeset with restricti...
Keywords:
Status: CLOSED DUPLICATE of bug 2156289
Alias: None
Product: Red Hat Enterprise Linux 9
Classification: Red Hat
Component: libvirt
Version: 9.1
Hardware: Unspecified
OS: Unspecified
medium
low
Target Milestone: rc
: ---
Assignee: khanicov
QA Contact: liang cong
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2022-10-26 09:29 UTC by liang cong
Modified: 2023-01-16 10:50 UTC (History)
5 users (show)

Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed: 2023-01-16 10:50:47 UTC
Type: Bug
Target Upstream Version:
Embargoed:

Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
Red Hat Issue Tracker RHELPLAN-137629 0 None None None 2022-10-26 10:35:10 UTC

Description liang cong 2022-10-26 09:29:46 UTC 
Description of problem:
Inconsistent error msg prompts when setting inexistent nodeset with restrictive numa tuning mode

Version-Release number of selected component (if applicable):
# rpm -q libvirt qemu-kvm
libvirt-8.5.0-7.el9_1.x86_64
qemu-kvm-7.0.0-13.el9.x86_64

How reproducible:
100%

Steps to Reproduce:
1.There are 2 numa nodes on host:
# numactl --hard
available: 2 nodes (0-1)
node 0 cpus: 0 1
node 0 size: 3671 MB
node 0 free: 1731 MB
node 1 cpus: 2 3
node 1 size: 4020 MB
node 1 free: 2215 MB
node distances:
node   0   1 
  0:  10  20 
  1:  20  10 

2.Set numa tuning with restrictive mode and inexistent numa nodeset 2
<numatune>
<memory mode='restrictive' nodeset='2'/>
</numatune>

3.Start the guest vm
# virsh start vm1
error: Failed to start domain 'vm1'
error: Invalid value '2' for 'cpuset.mems': Invalid argument

Actual results:
Error msg prompts:
error: Invalid value '2' for 'cpuset.mems': Invalid argument


Expected results:
If setting other numa tuning mode like "" then the error msg is:
error: unsupported configuration: NUMA node 2 is unavailable

The error msg should keep consistent. 


Additional info:
If setting numa topology like:
<numa>
   <cell id="0" cpus="0-1" memory="2097152" unit="KiB"/>
</numa>
then the error msg is consistent as "error: unsupported configuration: NUMA node 2 is unavailable", no matter what mode is set.
Comment 1 liang cong 2022-10-26 09:43:22 UTC 
Add some info:
If setting other numa tuning mode like "preferred", "strict" or "interleave" then the error msg is:
error: unsupported configuration: NUMA node 2 is unavailable
Comment 2 Michal Privoznik 2022-10-26 09:47:36 UTC 
This is because the check for host NUMA nodes presence is skipped in qemuBuildMemoryBackendProps() for VIR_DOMAIN_NUMATUNE_MEM_RESTRICTIVE and then the code proceeds to qemuProcessSetupPid() where the nodeset is set directly in CGroups, hence the difference in error messages.
Comment 3 Andrea Bolognani 2023-01-16 10:50:47 UTC 

*** This bug has been marked as a duplicate of bug 2156289 ***
Note You need to log in before you can comment on or make changes to this bug.