Bug 1267027
Summary: | numad consumes too much CPU, especially when incorrectly selecting assigned device VM | ||
---|---|---|---|
Product: | Red Hat Enterprise Linux 7 | Reporter: | Alex Williamson <alex.williamson> |
Component: | numad | Assignee: | Jan Synacek <jsynacek> |
Status: | CLOSED WONTFIX | QA Contact: | qe-baseos-daemons |
Severity: | unspecified | Docs Contact: | |
Priority: | unspecified | ||
Version: | 7.2 | CC: | bgray |
Target Milestone: | rc | ||
Target Release: | 7.3 | ||
Hardware: | Unspecified | ||
OS: | Unspecified | ||
Whiteboard: | |||
Fixed In Version: | Doc Type: | If docs needed, set a value | |
Doc Text: | Story Points: | --- | |
Clone Of: | Environment: | ||
Last Closed: | 2019-02-19 08:52:53 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
Alex Williamson
2015-09-28 20:56:53 UTC
Now I've seen this behavior with absolutely no special configuration, my guest effectively hung, so I run top and see numad consuming 100% cpu. The guest was only 4G in this case, so the hang was substantially shorter than above. Wed Sep 30 13:16:08 2015: Nodes: 2 Min CPUs free: 651, Max CPUs: 714, Avg CPUs: 682, StdDev: 31.504 Min MBs free: 7661, Max MBs: 15236, Avg MBs: 11448, StdDev: 3787.5 Node 0: MBs_total 16307, MBs_free 15236, CPUs_total 720, CPUs_free 714, Distance: 10 20 CPUs: 0-5,12-17 Node 1: MBs_total 12288, MBs_free 7661, CPUs_total 720, CPUs_free 651, Distance: 20 10 CPUs: 6-11,18-23 Wed Sep 30 13:16:08 2015: Processes: 432 Wed Sep 30 13:16:08 2015: Candidates: 1 132068: PID 13333: (qemu-kvm), Threads 8, MBs_size 5143, MBs_used 4276, CPUs_used 63, Magnitude 269388, Nodes: 0-1 Wed Sep 30 13:16:08 2015: PICK NODES FOR: PID: 13333, CPUs 74, MBs 6050 Wed Sep 30 13:16:08 2015: PROCESS_MBs[0]: 154 Wed Sep 30 13:16:08 2015: PROCESS_MBs[1]: 4122 Wed Sep 30 13:16:08 2015: PROCESS_CPUs[0]: 1 Wed Sep 30 13:16:08 2015: Node[0]: mem: 88520 cpu: 1233 Wed Sep 30 13:16:08 2015: PROCESS_CPUs[1]: 42 Wed Sep 30 13:16:08 2015: Node[1]: mem: 77699 cpu: 1211 Wed Sep 30 13:16:08 2015: MBs: 6050, CPUs: 74 Wed Sep 30 13:16:08 2015: Sorted magnitude[0]: 115966732 Wed Sep 30 13:16:08 2015: Sorted magnitude[1]: 99974332 Wed Sep 30 13:16:08 2015: Node[0]: mem: 28020 cpu: 641 Wed Sep 30 13:16:08 2015: Advising pid 13333 (qemu-kvm) move from nodes (0-1) to nodes (0) Wed Sep 30 13:16:08 2015: Writing 1 to: /sys/fs/cgroup/cpuset/machine.slice/machine-qemu\x2dwin8.1\x2d2.scope/emulator/cpuset.memory_migrate Wed Sep 30 13:16:08 2015: Writing 0 to: /sys/fs/cgroup/cpuset/machine.slice/machine-qemu\x2dwin8.1\x2d2.scope/emulator/cpuset.mems Wed Sep 30 13:16:50 2015: Including PID: 13333 in cpuset: /sys/fs/cgroup/cpuset/machine.slice/machine-qemu\x2dwin8.1\x2d2.scope/emulator Wed Sep 30 13:16:50 2015: Writing 0-5,12-17 to: /sys/fs/cgroup/cpuset/machine.slice/machine-qemu\x2dwin8.1\x2d2.scope/emulator/cpuset.cpus Wed Sep 30 13:16:50 2015: Writing 1 to: /sys/fs/cgroup/cpuset/machine.slice/machine-qemu\x2dwin8.1\x2d2.scope/emulator/cpuset.memory_migrate Wed Sep 30 13:16:50 2015: Writing 0 to: /sys/fs/cgroup/cpuset/machine.slice/machine-qemu\x2dwin8.1\x2d2.scope/emulator/cpuset.mems Wed Sep 30 13:16:50 2015: Writing 0-5,12-17 to: /sys/fs/cgroup/cpuset/machine.slice/machine-qemu\x2dwin8.1\x2d2.scope/emulator/cpuset.cpus Wed Sep 30 13:16:50 2015: Writing 1 to: /sys/fs/cgroup/cpuset/machine.slice/machine-qemu\x2dwin8.1\x2d2.scope/vcpu0/cpuset.memory_migrate Wed Sep 30 13:16:50 2015: Writing 0 to: /sys/fs/cgroup/cpuset/machine.slice/machine-qemu\x2dwin8.1\x2d2.scope/vcpu0/cpuset.mems Wed Sep 30 13:17:00 2015: Writing 0-5,12-17 to: /sys/fs/cgroup/cpuset/machine.slice/machine-qemu\x2dwin8.1\x2d2.scope/vcpu0/cpuset.cpus Wed Sep 30 13:17:00 2015: Writing 1 to: /sys/fs/cgroup/cpuset/machine.slice/machine-qemu\x2dwin8.1\x2d2.scope/vcpu1/cpuset.memory_migrate Wed Sep 30 13:17:00 2015: Writing 0 to: /sys/fs/cgroup/cpuset/machine.slice/machine-qemu\x2dwin8.1\x2d2.scope/vcpu1/cpuset.mems Wed Sep 30 13:17:09 2015: Writing 0-5,12-17 to: /sys/fs/cgroup/cpuset/machine.slice/machine-qemu\x2dwin8.1\x2d2.scope/vcpu1/cpuset.cpus Wed Sep 30 13:17:09 2015: Writing 1 to: /sys/fs/cgroup/cpuset/machine.slice/machine-qemu\x2dwin8.1\x2d2.scope/vcpu2/cpuset.memory_migrate Wed Sep 30 13:17:09 2015: Writing 0 to: /sys/fs/cgroup/cpuset/machine.slice/machine-qemu\x2dwin8.1\x2d2.scope/vcpu2/cpuset.mems Wed Sep 30 13:17:19 2015: Writing 0-5,12-17 to: /sys/fs/cgroup/cpuset/machine.slice/machine-qemu\x2dwin8.1\x2d2.scope/vcpu2/cpuset.cpus Wed Sep 30 13:17:19 2015: Writing 1 to: /sys/fs/cgroup/cpuset/machine.slice/machine-qemu\x2dwin8.1\x2d2.scope/vcpu3/cpuset.memory_migrate Wed Sep 30 13:17:19 2015: Writing 0 to: /sys/fs/cgroup/cpuset/machine.slice/machine-qemu\x2dwin8.1\x2d2.scope/vcpu3/cpuset.mems Wed Sep 30 13:17:29 2015: Writing 0-5,12-17 to: /sys/fs/cgroup/cpuset/machine.slice/machine-qemu\x2dwin8.1\x2d2.scope/vcpu3/cpuset.cpus Wed Sep 30 13:17:29 2015: PID 13333 moved to node(s) 0 in 80.65 seconds Explanation? Move to RHEL8? The needinfo request[s] on this closed bug have been removed as they have been unresolved for 1000 days |