[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

[Xen-devel] qemu cpu utility too high as dom0 cpu stealtime's also high

  • To: xen-devel@xxxxxxxxxxxxxxxxxxx
  • From: alice wan <wanjia19870902@xxxxxxxxx>
  • Date: Fri, 10 Jun 2011 21:57:13 +0800
  • Delivery-date: Fri, 10 Jun 2011 06:59:20 -0700
  • Domainkey-signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=mime-version:date:message-id:subject:from:to:content-type; b=rFWu2w9rkCOwyKmDWUFTccoNDbSUYYDBly9/E90ADv8h7pgScmoiAq7PP+TQ2Ws0yM JK2ailvgfvmpDF6J9lynhnpKFLHfWZJOpAxqEx+nmefTjTCMgK4SRg75ZLAjkchxOkr3 Bh6TpczG8BCeFjS/7EI5RDp2VkVHld2IOIcsY=
  • List-id: Xen developer discussion <xen-devel.lists.xensource.com>

hi all,
       when i started 10 windows vms of 4 vcpu on the host with 8 cpu, dom0 has 4 shareble vcpu, i found qemu-dm cpu utility is too high, about 80-90%, lasting for more than half an hour. after a long period of time, the dom0 became normal.
        i observed that when qemu-dm %cpu's too high, the dom0 cpu's stealtime was also too high.
        when dom0 became normal, %st  and qemu %cpu also became low.
        high stealtime is reasonable as the cpu is too busy, the time vcpu wait for cpu scheduling  is too long.
        however, qemu high cpu utility is unreasonable,  the oprofile report of qemu seems normal.
        I doubt the granularity of task cpu time accounting seems too rough.
        It seems that task cpu accounting didn't distinguish virtual cpu time from cpu time so that  the qemu-dm cpu time = real cpu time+steal time
        Does the task cpu accounting is based on tick?
        the config about accounting 's like this:
        # CONFIG_IRQ_TIME_ACCOUNTING is not set
        Should i turn on the CONFIG_IRQ_TIME_ACCOUNTING ?
        Any advice is appreciated, thanks in advance.
Xen-devel mailing list



Lists.xenproject.org is hosted with RackSpace, monitoring our
servers 24x7x365 and backed by RackSpace's Fanatical Support®.