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 966341 - Failed to run numatune with specified node
Summary: Failed to run numatune with specified node
Keywords:
Status: CLOSED CURRENTRELEASE
Alias: None
Product: Red Hat Enterprise Linux 7
Classification: Red Hat
Component: libvirt
Version: 7.0
Hardware: Unspecified
OS: Unspecified
low
low
Target Milestone: rc
: ---
Assignee: Libvirt Maintainers
QA Contact: Virtualization Bugs
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2013-05-23 06:04 UTC by Luwen Su
Modified: 2014-06-13 09:46 UTC (History)
7 users (show)

Fixed In Version: libvirt-1.1.1-18.el7
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2014-06-13 09:46:15 UTC
Target Upstream Version:
Embargoed:

Attachments (Terms of Use)

Description Luwen Su 2013-05-23 06:04:29 UTC 
Description of problem:
Since Bug 920406 just fix the error messeg when fail to write into cpuset.mems , and it's a kernel issue about fail to run numatune with specified node , so file this one to track in libvirt field.



Version-Release number of selected component (if applicable):
libvirt-1.0.5-2.el7.x86_64
kernel-3.9.0-0.55.el7.x86_64


How reproducible:
100%

Steps to Reproduce:
1.A guest and a numa host
# virsh list
 Id    Name                           State
----------------------------------------------------
 2     test                           running


# virsh nodeinfo
CPU model:           x86_64
CPU(s):              12
CPU frequency:       800 MHz
CPU socket(s):       1
Core(s) per socket:  6
Thread(s) per core:  1
NUMA cell(s):        2
Memory size:         32686424 KiB



2.
# virsh numatune test --nodeset 0
error: Unable to change numa parameters
error: unable to set numa tunable: Device or resource busy

# virsh numatune test --nodeset 0-1

# virsh numatune test --nodeset 1
error: Unable to change numa parameters
error: unable to set numa tunable: Device or resource busy

# virsh numatune test --nodeset 99
error: Unable to change numa parameters
error: unable to set numa tunable: Invalid argument


#echo 0 > /sys/fs/cgroup/cpuset/machine/test.libvirt-qemu/cpuset.mems 
-bash: echo: write error: Device or resource busy


Actual results:
Fail to write into cpuset.mems

Expected results:
Success
Comment 2 Wayne Sun 2013-11-20 07:21:50 UTC 
Depend bug 955489 is still new, waiting for it to be resolved.
Comment 4 Ján Tomko 2014-03-28 09:38:58 UTC 
This was not a kernel issue and has been fixed in upstream libvirt by
commit 81fae6b95cfe72d0f5a987b6b5cd4bf86e32798c
Author:     Shivaprasad G Bhat <shivaprasadbhat>
AuthorDate: 2013-12-03 06:30:26 -0500
Commit:     Martin Kletzander <mkletzan>
CommitDate: 2013-12-04 13:32:07 +0100

    qemu: fix live pinning to memory node on NUMA system
    
    Ever since the subcpusets(vcpu,emulator) were introduced, the parent
    cpuset cannot be modified to remove the nodes that are in use by the
    subcpusets.
    The fix is to break the memory node modification into three steps:
     1. assign new nodes into the parent,
     2. change the nodes in the child nodes,
     3. remove the old nodes on the parent node.
    
    Resolves: https://bugzilla.redhat.com/show_bug.cgi?id=1009880
    
    Signed-off-by: Shivaprasad G Bhat <sbhat.ibm.com>
    Signed-off-by: Martin Kletzander <mkletzan>

git describe: v1.2.0-43-g81fae6b contains: v1.2.1-rc1~208
Comment 6 Jincheng Miao 2014-03-31 09:01:53 UTC 
in latest libvirt-1.1.1-29.el7.x86_64, the operation of specify nodeset is working.

# rpm -q libvirt kernel
libvirt-1.1.1-29.el7.x86_64
kernel-3.10.0-115.el7.x86_64

# virsh nodeinfo
CPU model:           x86_64
CPU(s):              32
CPU frequency:       1064 MHz
CPU socket(s):       1
Core(s) per socket:  8
Thread(s) per core:  2
NUMA cell(s):        2
Memory size:         131908736 KiB

# virsh start r7
Domain r7 started

# virsh numatune r7 --nodeset 1

# cat /sys/fs/cgroup/cpuset/machine.slice/machine-qemu\\x2dr7.scope/cpuset.mems 
1

# virsh numatune r7 --nodeset 0

# cat /sys/fs/cgroup/cpuset/machine.slice/machine-qemu\\x2dr7.scope/cpuset.mems 
0

# virsh numatune r7 --nodeset 0-1

# cat /sys/fs/cgroup/cpuset/machine.slice/machine-qemu\\x2dr7.scope/cpuset.mems 
0-1

# virsh numatune r7 --nodeset 2
error: Unable to change numa parameters
error: Unable to write to '/sys/fs/cgroup/cpuset/machine.slice/machine-qemu\x2dr7.scope/vcpu0/cpuset.mems': Invalid argument
Comment 7 Jincheng Miao 2014-04-08 06:55:06 UTC 
As comment 6, this bug is fixed in the latest libvirt-1.1.1-29.el7.x86_64, so change the status to VERIFIED.
Comment 9 Ludek Smid 2014-06-13 09:46:15 UTC 
This request was resolved in Red Hat Enterprise Linux 7.0.

Contact your manager or support representative in case you have further questions about the request.
Note You need to log in before you can comment on or make changes to this bug.