Bug 1112820
| Summary: | Failed to run numatune with specified node | ||
|---|---|---|---|
| Product: | Red Hat Enterprise Linux 6 | Reporter: | Jan Kurik <jkurik> |
| Component: | libvirt | Assignee: | Ján Tomko <jtomko> |
| Status: | CLOSED ERRATA | QA Contact: | Virtualization Bugs <virt-bugs> |
| Severity: | high | Docs Contact: | |
| Priority: | high | ||
| Version: | 6.4 | CC: | acathrow, cwei, dyuan, gsun, honzhang, jiahu, jmiao, jsvarova, jtomko, lsu, mtessun, mzhan, pm-eus, tdosek |
| Target Milestone: | rc | Keywords: | Upstream, ZStream |
| Target Release: | --- | ||
| Hardware: | Unspecified | ||
| OS: | Unspecified | ||
| Whiteboard: | |||
| Fixed In Version: | libvirt-0.10.2-29.el6_5.10 | Doc Type: | Bug Fix |
| Doc Text: |
Prior to this update, the libvirt library was trying to pin the domain's parent thread to another CPU even if its vCPU threads were not allowed to run on that CPU. As a consequence, the pinning process failed. To fix this bug, the child threads repin to the old and new CPUs first before only pinning them to the new ones. As a result, pinning now works even if the new CPU list is not a subset of the old CPUs.
|
Story Points: | --- |
| Clone Of: | 857312 | Environment: | |
| Last Closed: | 2014-08-04 08:14:05 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: | |||
| Bug Depends On: | 857312 | ||
| Bug Blocks: | |||
|
Description
Jan Kurik
2014-06-24 18:12:01 UTC
This bug is fix in latest libvirt-0.10.2-29.el6_5.10: # virsh start a Domain a started # virsh numatune a numa_mode : strict numa_nodeset : 1 # virsh numatune a --nodeset 0 # virsh numatune a numa_mode : strict numa_nodeset : 0 # virsh start a # virsh numatune a --live numa_mode : strict numa_nodeset : 0 here umount the cgroup cpuset, check the error msg: # umount /cgroup/cpuset/ # virsh numatune a --nodeset 0 --live error: Unable to change numa parameters error: unable to get numa nodeset: No such file or directory So I change the status to VERIFIED. 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. http://rhn.redhat.com/errata/RHBA-2014-0911.html |