-
Notifications
You must be signed in to change notification settings - Fork 18
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
vm cpu util in kvmtop unequal top inside vm #33
Comments
@MyungChi Can you please do some further tests to analyse this behavior? |
I checked my server as you mentioned. kvmtop result
top in host
|
So you're seeing 210.0% CPU utilisation for this VM in top on the host, but no CPU utilisation inside the VM? The 210% and 52% in top vs. kvmtop differences are probably because kvmtop computes the 100% relative to the amount of cores, hence I assume these two tools measure the same. Hence I'm not so sure yet that this is a bug of kvmtop. |
My server has 88 core, It means 8,800%. 210% is just 2.3% of total cpu capability. |
What CPU architecture do you have? Can you name the Model of the CPU? |
This is my server cpu info. server is "HPE DL380 G10" processor : 87 |
Hi. As I know %CPU on top is core * usage in linux. This is CPU usage when I type top -p $PID
This is CPU usage after chage Irix module (shift + i).
|
Hi. Is there any update for this ? |
@MyungChi as stated in my previous comment, I cannot reproduce nor understand this issue. To fix it, please provide a more intense problem analysis and provide a sketch for a proper solution, which I can then integrate. This is an open source project - so your support is as important as my own contribution. |
Hi.
I reinstall kvmtop latest release(2.1.3) in my system.
Total number of CPU is fixed.
But, There are issue usage of CPU usage of VM is not collect.
As you see below, VM name "vedge" is shown "52%" CPU usage.
So, I checked with top after login vedge VM. CPU usage is less than 1%.
kvmtop --cpu --mem
top in vedge vm
=====================================================
The text was updated successfully, but these errors were encountered: