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

Re: [Xen-users] Disk Usages


  • To: Jonathan Tripathy <jonnyt@xxxxxxxxxxx>
  • From: Florian Heigl <florian.heigl@xxxxxxxxx>
  • Date: Thu, 16 Jun 2011 23:14:00 +0200
  • Cc: Xen Users <xen-users@xxxxxxxxxxxxxxxxxxx>
  • Delivery-date: Thu, 16 Jun 2011 14:20:38 -0700
  • Domainkey-signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :cc:content-type; b=Snfd7CmXTKyOZm1W+LAcll5IMzU91rex9//JTuRUs7VsDm7xDyjL4TQGwYXTLWiR8u HcIOGBd2hs4kSPwpluopzAACIIOdNQ1M8JyeP6ZydnuTTXF7fm0Ziw31STI2t/NQeGnO JghT1neIZFfL2Cz8C4HySRVBzClVFXWsFdUJ4=
  • List-id: Xen user discussion <xen-users.lists.xensource.com>

Hi,

> I am aware that I can throttle a DomU's disk usage by using ionice in the
> Dom0 against the correct blkback process. However, how does one actually
> find out what the "offending" DomU is?

if it's enough to find out "after" the fact - meaning, when there
already IS excessive disk IO, then iotop is the very best thing since
sliced bread.
imho even better than top :)

Can  you also give
https://bitbucket.org/darkfader/black-magic/src/d14a84157990/usr/local/bin/blksched
a test run in this situation and let me know if it helps for you?

Florian


-- 
the purpose of libvirt is to provide an abstraction layer hiding all
xen features added since 2006 until they were finally understood and
copied by the kvm devs.

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


 


Rackspace

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