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

Re: [Xen-devel] XEN Proposal

  • To: "Juergen Gross" <juergen.gross@xxxxxxxxxxxxxxxxxxx>
  • From: "George Dunlap" <George.Dunlap@xxxxxxxxxxxxx>
  • Date: Thu, 11 Dec 2008 19:38:53 +0000
  • Cc: Chris <hap10@xxxxxxxxxxxxxx>, "Tian, Kevin" <kevin.tian@xxxxxxxxx>, xen-devel@xxxxxxxxxxxxxxxxxxx, Keir Fraser <keir.fraser@xxxxxxxxxxxxx>
  • Delivery-date: Thu, 11 Dec 2008 11:39:16 -0800
  • Domainkey-signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=message-id:date:from:sender:to:subject:cc:in-reply-to:mime-version :content-type:content-transfer-encoding:content-disposition :references:x-google-sender-auth; b=XjXaVs40j2kB5S+ZJespAXc+48tPWy3Zw73lO6r+Pq8sdIGN1o2eGp0JrDBTJ9z/PH LFZZfBy8IQOivo19cGDX5FeQZyGIs6mBJ9YSmdb3huKtmvHHxYN8o1WThRkL6hUP9p9n 5X/qFbYVjAkZWoJ5+AcraI9mtZ4I5AIhFacoc=
  • List-id: Xen developer discussion <xen-devel.lists.xensource.com>

On Thu, Dec 11, 2008 at 3:13 PM, George Dunlap <dunlapg@xxxxxxxxx> wrote:
> It seems like what you really want is to cap the number of credits the
> VMs can get, and then take them offline when their credits go negative
> (instead of competing for resources in a "best-effort" fashion).  :-)

Actually, it turns out this functionality is already present.

xm sched-credit -d [domid] -c 30

will "cap" the domain to 30% of one cpu, even if there are no other
cpus running.  You should be able to utilize that directly, no
development needed.


Xen-devel mailing list



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