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 846894 - Error occurs when start domain with cpuset on numa machine
Summary: Error occurs when start domain with cpuset on numa machine
Keywords:
Status: CLOSED DUPLICATE of bug 838070
Alias: None
Product: Red Hat Enterprise Linux 6
Classification: Red Hat
Component: libvirt
Version: 6.4
Hardware: Unspecified
OS: Unspecified
medium
high
Target Milestone: rc
: ---
Assignee: Peter Krempa
QA Contact: Virtualization Bugs
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2012-08-09 03:35 UTC by hongming
Modified: 2012-08-27 12:15 UTC (History)
7 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2012-08-27 12:15:21 UTC
Target Upstream Version:
Embargoed:


Attachments (Terms of Use)
NUMA topology (10.09 KB, text/plain)
2012-08-09 03:35 UTC, hongming
no flags Details

Description hongming 2012-08-09 03:35:55 UTC
Created attachment 603158 [details]
NUMA topology

Description of problem:
If the domain's  xml includes cpuset attribute of  vcpu element , it is failed to start domain and the following errors occur.
error: Failed to start domain rhel6q
error: internal error cannot set CPU affinity on process 0: Invalid argument

But if remove the cpuset attribute from  vcpu element  of domain xml , it can successfully start. And it can't be reproduced machine without NUMA. Attached NUMA -topology .


Version-Release number of selected component (if applicable):
libvirt-0.10.0-0rc0.el6.x86_64
qemu-kvm-0.12.1.2-2.295.el6.x86_64
numad-0.5-4.20120522git.el6.x86_64
kernel-2.6.32-279.el6.x86_64


How reproducible:
100% 

Steps to Reproduce:
1. # virsh dumpxml rhel6q

<domain type='kvm'>
.....
<vcpu placement='static' cpuset='1-2,4,6'>10</vcpu>
......
</domain>


2. # virsh start rhel6q
error: Failed to start domain rhel6q
error: internal error cannot set CPU affinity on process 0: Invalid argument



3. Edit domain xml -  delete the cpuset attribute.
 # virsh edit rhel6q
Domain rhel6q XML configuration edited.

4.# virsh dumpxml rhel6q
<domain type='kvm'>
.....
<vcpu placement='static'>10</vcpu>
......
</domain>

# virsh start rhel6q
Domain rhel6q started


Actual results:
It is failed to start domain when domain's  xml includes cpuset attribute of  vcpu element


Expected results:
It can start successfully 

Additional info:

Comment 7 hongming 2012-08-24 09:25:29 UTC
Please ignore above Comment 6. It is right. The same error is not related with the bug.

Comment 8 Peter Krempa 2012-08-27 12:15:21 UTC
The problem you observed is most probably related to misconfigured cpuset cgroups that occurs when you disable (offline) and enable host processors. The cgroup setting is not restored when the processor is enabled again. I'm closing this as a dupe of 838070 that deals specifically with cgroup-related problems. 

If you reproduce this bug with working cpuset cgroup (/sys/fs/cgroup/cpuset/libvirt/cpuset.cpus contains all processors) please re-open this bug.

*** This bug has been marked as a duplicate of bug 838070 ***


Note You need to log in before you can comment on or make changes to this bug.