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

Re: [Xen-devel] dom0 starves guests off CPU

  • To: "Rik van Riel" <riel@xxxxxxxxxx>
  • From: "Molle Bestefich" <molle.bestefich@xxxxxxxxx>
  • Date: Tue, 21 Feb 2006 14:51:15 +0100
  • Cc: James Harper <james.harper@xxxxxxxxxxxxxxxx>, xen-devel@xxxxxxxxxxxxxxxxxxx
  • Delivery-date: Tue, 21 Feb 2006 14:04:30 +0000
  • Domainkey-signature: a=rsa-sha1; q=dns; c=nofws; s=beta; d=gmail.com; h=received:message-id:date:from:to:subject:cc:in-reply-to:mime-version:content-type:content-transfer-encoding:content-disposition:references; b=ElWcuirrGeVfNWuAL++472fL9q6Fya/pEtwZrvFJPQcbCWqqM1RMUzt7wM+kWCL01sNNTYwyJRQHzQ/2oFdcow5j/u0+46UYM397e1Vdh2SpC8Z8HIeprNnWEu9ldknV6kT+nNiQy1ySHhgyPns/tpqEoKA28P2N6puPod100yI=
  • List-id: Xen developer discussion <xen-devel.lists.xensource.com>

Rik van Riel wrote:
> > At a guess, the default scheduling assumes that all of dom0's work is
> > going to be related to serving data (block and network) to domU's, so it
> > makes sense to give it priority.
> That's not a safe assumption.  People will be running CPU
> intensive things in dom0, if only things like apt-get, yum
> or recompiling a new package after a security bug was found.
> Also, some people will want to use dom0 as their desktop,
> with a few guest domains as test machines...
> I believe that the default should be safe, even if it's not
> the most high performance setting for some configurations.

Another point.

Using dom0 for backup purposes must be common, since you can snapshot
the devices that the domUs use.  Backups can be long-running
CPU-gobbling monsters which you wouldn't want to shove all your CPU
time at just because they happen to sit in dom0...

Xen-devel mailing list



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