Red Hat Bugzilla – Bug 800367
3.1 - vdsm does not report the system and user cpu usage separately for vms.
Last modified: 2012-12-04 13:54:30 EST
+++ This bug was initially created as a clone of Bug #800366 +++
Description of problem:
In RHEVM 3.0 the history database vm system cpu usage is always 0. This is because libvirt do not report the system and user cpu usage separately and vdsm sends all the vm cpu usage as user cpu only. Need to add this separation to vdsm.
System usage is an important statistic to troubleshoot various performance
related problems. So i think it's very important to have this.
Since RHEL 6.3 External Beta has begun, and this bug remains
unresolved, it has been rejected as it is not proposed as
exception or blocker.
Red Hat invites you to ask your support representative to
propose this request, if appropriate and relevant, in the
next release of Red Hat Enterprise Linux.
A burocratic question may be, but why is this bug registered to RHEL 6? :)
since it is a feature enhancement request, can we move it to oVirt and let a wider community discuss the question?
(In reply to comment #5)
> since it is a feature enhancement request, can we move it to oVirt and let a
> wider community discuss the question?
Or make the bug public.
(In reply to comment #4)
> A burocratic question may be, but why is this bug registered to RHEL 6? :)
because a customer does not like the cpuSys==0 that we currently report, and our product management decided that it should go into rhev-3.1. The bug is a means to track this fact, so please keep it here in rhel-6.
Removed the improvement from the keywords, as this is simply a bug fix (to get the right data from the host).
Currently everything exists in place (also engine's side) but VDSM is reporting 0 all the time.
merged upstream 43675686c0b41891a9f78bef71fbe1866c6d409b
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.