WARNING - OLD ARCHIVES

This is an archived copy of the Xen.org mailing list, which we have preserved to ensure that existing links to archives are not broken. The live archive, which contains the latest emails, can be found at http://lists.xen.org/
   
 
 
Xen 
 
Home Products Support Community News
 
   
 

xen-devel

[Xen-devel] XenAPI: why we implement VM_metrics.VCPUs_utilisation as pro

To: xen-devel@xxxxxxxxxxxxxxxxxxx
Subject: [Xen-devel] XenAPI: why we implement VM_metrics.VCPUs_utilisation as proportion?
From: Zhigang Wang <zhigang.x.wang@xxxxxxxxxx>
Date: Wed, 03 Sep 2008 17:20:14 +0800
Delivery-date: Wed, 03 Sep 2008 02:20:42 -0700
Envelope-to: www-data@xxxxxxxxxxxxxxxxxxx
List-help: <mailto:xen-devel-request@lists.xensource.com?subject=help>
List-id: Xen developer discussion <xen-devel.lists.xensource.com>
List-post: <mailto:xen-devel@lists.xensource.com>
List-subscribe: <http://lists.xensource.com/mailman/listinfo/xen-devel>, <mailto:xen-devel-request@lists.xensource.com?subject=subscribe>
List-unsubscribe: <http://lists.xensource.com/mailman/listinfo/xen-devel>, <mailto:xen-devel-request@lists.xensource.com?subject=unsubscribe>
Sender: xen-devel-bounces@xxxxxxxxxxxxxxxxxxx
User-agent: Thunderbird 2.0.0.16 (X11/20080707)
hi all,

why we implement VM_metrics.VCPUs_utilisation as the proportion of all cpu time?

Then XenAPI client (xm) can not get the accumulated cpu_time of each vcpu.

I recommend we make VM_metrics.VCPUs_utilisation just the cpu_time which is
maintained by hypervisor.

Then XenAPI client (xm) not only can get the accumulated cpu_time of each vcpu,
but also can calculate the proportion by getting twice the
VM_metrics.VCPUs_utilisation.

Am I missing something?

thanks,

zhigang

_______________________________________________
Xen-devel mailing list
Xen-devel@xxxxxxxxxxxxxxxxxxx
http://lists.xensource.com/xen-devel

<Prev in Thread] Current Thread [Next in Thread>
  • [Xen-devel] XenAPI: why we implement VM_metrics.VCPUs_utilisation as proportion?, Zhigang Wang <=