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

Re: [Xen-users] One domU locks up entire system? Scheduling?


  • To: tim Doyle <tim@xxxxxxxxxxxx>
  • From: Anand <xen.mails@xxxxxxxxx>
  • Date: Thu, 26 Jan 2006 04:13:26 +0530
  • Cc: Dirk Estreng <dirk.estreng@xxxxxx>, xen-users@xxxxxxxxxxxxxxxxxxx
  • Delivery-date: Wed, 25 Jan 2006 22:52:22 +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:references; b=dmMJGdjxHwgRoexBhtiwSw7Yy0Tl+VGvyWSDfx+lK8we0cuKY4At+jUJkFKhiwOBw6MvJFzbpChT1a4qdHnCrN6jJT3E4Mgk8G6XFIV3LLr8wYx33XT4SKwhxE+CaYkOq9JQBTC9SbOkxr0/DotY31xXBAGFrLSQJhKq54wZUuM=
  • List-id: Xen user discussion <xen-users.lists.xensource.com>


On 1/26/06, tim Doyle <tim@xxxxxxxxxxxx> wrote:
Does this help?

echo "cfq" > /sys/block/sda/queue/scheduler

Alternatively you can use elevator=cfq as the command line option for both the dom0 and domU kernels in grub.conf and domU config file respectively. This will force the use of cfq as the default scheduler.

By default anticipatory is the scheduler in dom0 and noop in domU.

You can also try to do cpu scheduling for the domU's which will allow other domains to get the cpu share they deserve.

--

regards,

Anand
_______________________________________________
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®.