Bug 654540
Summary: | "error : cannot set CPU affinity on process 0: Invalid argument" | ||
---|---|---|---|
Product: | Red Hat Enterprise Linux 5 | Reporter: | yanbing du <ydu> |
Component: | libvirt | Assignee: | Jiri Denemark <jdenemar> |
Status: | CLOSED ERRATA | QA Contact: | Virtualization Bugs <virt-bugs> |
Severity: | high | Docs Contact: | |
Priority: | low | ||
Version: | 5.6 | CC: | berrange, dallan, dyuan, eblake, gren, jdenemar, llim, mjenner, virt-maint, xen-maint |
Target Milestone: | rc | ||
Target Release: | --- | ||
Hardware: | Unspecified | ||
OS: | Unspecified | ||
Whiteboard: | |||
Fixed In Version: | libvirt-0.8.2-13.el5 | Doc Type: | Bug Fix |
Doc Text: | Story Points: | --- | |
Clone Of: | Environment: | ||
Last Closed: | 2011-01-13 23:17:28 UTC | Type: | --- |
Regression: | --- | Mount Type: | --- |
Documentation: | --- | CRM: | |
Verified Versions: | Category: | --- | |
oVirt Team: | --- | RHEL 7.3 requirements from Atomic Host: | |
Cloudforms Team: | --- | Target Upstream Version: | |
Embargoed: |
Description
yanbing du
2010-11-18 07:05:22 UTC
https://www.redhat.com/archives/libvir-list/2010-November/msg00863.html is a starting point for a discussion on how to deal with this bug. > # virsh nodeinfo
> CPU model: x86_64
> CPU(s): 96
> CPU frequency: 2398 MHz
> CPU socket(s): 16
> Core(s) per socket: 6
> Thread(s) per core: 1
> NUMA cell(s): 4
> Memory size: 1006708712 kB
This tells us that there are 16*6*4 CPUs == 384.
THe virsh capabilities XML meanwhile says there are 96 CPUs.
When setting the CPU affinity, we use VIR_NODEINFO_MAXCPUS(). So what's happening is that we're probably telling the kernel to run the guest on 384 CPUs, when only 96 exist. Thus -EINVAL is returned
Fixed in libvirt-0.8.2-13.el5 Verified this bug. kernel-2.6.18-233.el5 libvirt-0.8.2-14.el5 An advisory has been issued which should help the problem described in this bug report. This report is therefore being closed with a resolution of ERRATA. For more information on therefore solution and/or where to find the updated files, please follow the link below. You may reopen this bug report if the solution does not work for you. http://rhn.redhat.com/errata/RHEA-2011-0060.html |