New answers tagged cpu
0
I would check to make sure that the KVM guests are provisioned so that they're able to make use of all the host's resources (CPU, RAM, etc.). Typically KVM guests are only allocated say 1-2 CPUs (cores) on a system that may contain many more.
This would mean you're not comparing the exact same thing when looking at the host's resources vs. the internals of ...
2
Being cynical I could say that is "normal" for Windows guests but not for Linux guests (at least I never saw one behave like that).
With Windows it depends a lot on the applications running (near idle). A plain XP or W2K (I have no experience with newer versions in KVM yet) causes 10% to 20% on the host (being shown about 0% within) but MS SQL server gets ...
1
These messages can also be false positives, under very specific conditions: http://tech.ryancox.net/2010/11/diagnosing-throttled-or-slow-systems.html
1
CPUs are pretty robust. They are designed to become slower (“throttle”) or stop altogether if they detect that they are overheating. There is pretty much zero risk that you damage your CPU by overheating. The only consequence of this overheat is that your system became slower for a while, as the message indicates.
You should see about cleaning or upgrading ...
7
I don't think so. It just means that the CPU is overheating. And your building of a huge program probably is the cause (I'm assuming that after the build finishes things get back to normal, and if you repeat the build the message appears again).
You might want to check your system cooling (eg. fans, dust), as the message suggests.
0
It might help you:
#!/bin/bash
total_mem=0
printf "%-10s%-10s\n" User MemUsage
while read u m
do
[[ $old_user != $u ]] && { printf "%-10s%-0.1f\n" $old_user $total_mem;
total_mem=0; }
total_mem="$(echo $m + $total_mem | bc)"
old_user=$u
done < <(ps --no-headers -eo user,%mem| sort ...
Top 50 recent answers are included
