Return-Path: X-Original-To: apmail-cloudstack-issues-archive@www.apache.org Delivered-To: apmail-cloudstack-issues-archive@www.apache.org Received: from mail.apache.org (hermes.apache.org [140.211.11.3]) by minotaur.apache.org (Postfix) with SMTP id 9CB90101D5 for ; Tue, 15 Oct 2013 08:25:43 +0000 (UTC) Received: (qmail 49860 invoked by uid 500); 15 Oct 2013 08:25:43 -0000 Delivered-To: apmail-cloudstack-issues-archive@cloudstack.apache.org Received: (qmail 49693 invoked by uid 500); 15 Oct 2013 08:25:43 -0000 Mailing-List: contact issues-help@cloudstack.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: dev@cloudstack.apache.org Delivered-To: mailing list issues@cloudstack.apache.org Received: (qmail 49675 invoked by uid 500); 15 Oct 2013 08:25:42 -0000 Delivered-To: apmail-incubator-cloudstack-issues@incubator.apache.org Received: (qmail 49668 invoked by uid 99); 15 Oct 2013 08:25:42 -0000 Received: from arcas.apache.org (HELO arcas.apache.org) (140.211.11.28) by apache.org (qpsmtpd/0.29) with ESMTP; Tue, 15 Oct 2013 08:25:42 +0000 Date: Tue, 15 Oct 2013 08:25:42 +0000 (UTC) From: "Valery Ciareszka (JIRA)" To: cloudstack-issues@incubator.apache.org Message-ID: In-Reply-To: References: Subject: [jira] [Created] (CLOUDSTACK-4868) incorrect cpu usage values in dashboard MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: 7bit X-JIRA-FingerPrint: 30527f35849b9dde25b450d4833f0394 Valery Ciareszka created CLOUDSTACK-4868: -------------------------------------------- Summary: incorrect cpu usage values in dashboard Key: CLOUDSTACK-4868 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-4868 Project: CloudStack Issue Type: Bug Security Level: Public (Anyone can view this level - this is the default.) Components: Management Server Affects Versions: 4.2.0 Environment: KVM (CentOS 6.4) + CloudStack 4.2.0 Reporter: Valery Ciareszka If cpu.overprovisioning.factor for cluster is being changed, dashboard reports incorrect values, unless all vms are restarted (stop/start). I.e. I configured cluster and set cpu.overprovisioning.factor to 6 and started a number of VMS Current usage is reported correctly. change cpu.overprovisioning.factor to 12 at cluster settings Wait for 5-10 minutes and you will see that cpu usage was doubled. If you will stop/start all vms (including system vms/virtual routers), then you will see true CPU usage in dashboard. -- This message was sent by Atlassian JIRA (v6.1#6144)