Bug 1238614
Summary: | numad restricts memory zones causing numademo to throw errors | ||
---|---|---|---|
Product: | Red Hat Enterprise Linux 7 | Reporter: | Milos Vyletel <milos> |
Component: | numad | Assignee: | Jan Synacek <jsynacek> |
Status: | CLOSED ERRATA | QA Contact: | Petr Sklenar <psklenar> |
Severity: | medium | Docs Contact: | |
Priority: | unspecified | ||
Version: | 7.1 | CC: | bgray, jscotka, mrdest |
Target Milestone: | rc | ||
Target Release: | 7.3 | ||
Hardware: | Unspecified | ||
OS: | Unspecified | ||
Whiteboard: | |||
Fixed In Version: | numad-0.5-17.20150602git.el7 | Doc Type: | Bug Fix |
Doc Text: | Story Points: | --- | |
Clone Of: | Environment: | ||
Last Closed: | 2016-11-04 06:09:38 UTC | Type: | Bug |
Regression: | --- | Mount Type: | --- |
Documentation: | --- | CRM: | |
Verified Versions: | Category: | --- | |
oVirt Team: | --- | RHEL 7.3 requirements from Atomic Host: | |
Cloudforms Team: | --- | Target Upstream Version: | |
Embargoed: |
Description
Milos Vyletel
2015-07-02 09:41:26 UTC
Note on rhel6 Thu Jul 2 05:50:11 2015: Advising pid 7221 (numademo) move from nodes (0-1) to nodes (0) Thu Jul 2 05:50:11 2015: Making new cpuset: /cgroup/cpuset/numad.7221 Thu Jul 2 05:50:12 2015: PID 7221 moved to node(s) 0 in 0.89 seconds ^C [root@ibm-x3850x5-1 ~]# ls /cgroup/cpuset/numad.7221 cgroup.event_control cpuset.mem_hardwall cpuset.mems cgroup.procs cpuset.memory_migrate cpuset.sched_load_balance cpuset.cpu_exclusive cpuset.memory_pressure cpuset.sched_relax_domain_level cpuset.cpus cpuset.memory_spread_page notify_on_release cpuset.mem_exclusive cpuset.memory_spread_slab tasks [root@ibm-x3850x5-1 ~]# cat /cgroup/cpuset/numad.7221/cpuset.mem cpuset.mem_exclusive cpuset.memory_pressure cpuset.mems cpuset.mem_hardwall cpuset.memory_spread_page cpuset.memory_migrate cpuset.memory_spread_slab [root@ibm-x3850x5-1 ~]# cat /cgroup/cpuset/numad.7221/cpuset.mems 0-1 [root@ibm-x3850x5-1 ~]# cat /cgroup/cpuset/numad.7221/cpuset.cpus 0-5,12-17 in this case we do not seem to be limiting memory zones only cpus 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. https://rhn.redhat.com/errata/RHBA-2016-2414.html |