You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@cloudstack.apache.org by "Nitin Mehta (JIRA)" <ji...@apache.org> on 2013/05/14 13:27:15 UTC

[jira] [Resolved] (CLOUDSTACK-187) CloudStack reports incorrect CPU & RAM usage values for hosts in Basic zone

     [ https://issues.apache.org/jira/browse/CLOUDSTACK-187?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Nitin Mehta resolved CLOUDSTACK-187.
------------------------------------

    Resolution: Invalid
    
> CloudStack reports incorrect CPU & RAM usage values for hosts in Basic zone
> ---------------------------------------------------------------------------
>
>                 Key: CLOUDSTACK-187
>                 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-187
>             Project: CloudStack
>          Issue Type: Bug
>      Security Level: Public(Anyone can view this level - this is the default.) 
>          Components: Management Server, Usage, XenServer
>    Affects Versions: pre-4.0.0
>         Environment: CloudStack: version 2.2.14.20120210101530
> Hypervisors:  XenServer 5.6.100-47101p
> Zones: one Basic and one Advanced zones are defined, each consisting of single XenServer host.
>            Reporter: Vladimir Ostrovsky
>            Assignee: Nitin Mehta
>             Fix For: 4.1.0
>
>
> CloudStack reports incorrect CPU & RAM usage values for hosts in Basic zone.
> CPU usage is reported about 90%, when "top", XenCenter and other tools report that actual usage is about 1%.
> The "command=listCapacity&zoneid=1&type=1" returns something like "<percentused>90.49</percentused>".
> The only way I found to get rid of this, is to:
> * place the host into Maintenance mode,
> * remove it from its Cluster,
> * add the host again.
> After this procedure, correct values are reported.
> Interesting that in my practice it happens thrice for hosts in Basic zone, and never - for hosts in Advanced.

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira