This is an archived copy of the Xen.org mailing list, which we have preserved to ensure that existing links to archives are not broken. The live archive, which contains the latest emails, can be found at http://lists.xen.org/
Home Products Support Community News


[Xen-devel] Xen Domains scheduling parameters do not take effect before

To: xen-devel@xxxxxxxxxxxxxxxxxxx, xen-users@xxxxxxxxxxxxxxxxxxx
Subject: [Xen-devel] Xen Domains scheduling parameters do not take effect before rebooting
From: Priya <pbhat@xxxxxxxxxxxx>
Date: Mon, 19 Jul 2010 12:17:36 -0400
Delivery-date: Mon, 19 Jul 2010 09:18:28 -0700
Dkim-signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:mime-version:received:sender:received:date :x-google-sender-auth:message-id:subject:from:to:content-type; bh=+PSsnJ4Ym4ORNTLqoNWDmVeXg+0a628Y8ummstWmoYs=; b=pkSrQQ6Z/PHkbochQx1z7nXXx9CEL9A+IEqYAHq7m0PX0rJOn/ML/jHdGBhL0kdVAt HeD60YvrB+web9fVzojoobijTbljJsLsJDurr617YXjIpGWLI8X5Qk8cGy2a3Mvq0jsF x3Oshbo9GZ0oUki3RJkKZ743RNJ4Sc/w/AV44=
Domainkey-signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=mime-version:sender:date:x-google-sender-auth:message-id:subject :from:to:content-type; b=OWhK1FB7p2KYv82bEdFALzvRvOjtzEcGNeZUYEWzmGfPpJM4IwjuJj+qGfiBZ4pYNB Ib5H9u0Ze3bWGoQ77BGm0cGJIqennd2jjVHDhasbP4s01FJdpxsSRcG+9b5Nb2mJLc5t nwZEfJWCDiI09f4uOQUWEhZqb7H5mARy5v9AU=
Envelope-to: www-data@xxxxxxxxxxxxxxxxxxx
List-help: <mailto:xen-devel-request@lists.xensource.com?subject=help>
List-id: Xen developer discussion <xen-devel.lists.xensource.com>
List-post: <mailto:xen-devel@lists.xensource.com>
List-subscribe: <http://lists.xensource.com/mailman/listinfo/xen-devel>, <mailto:xen-devel-request@lists.xensource.com?subject=subscribe>
List-unsubscribe: <http://lists.xensource.com/mailman/listinfo/xen-devel>, <mailto:xen-devel-request@lists.xensource.com?subject=unsubscribe>
Sender: xen-devel-bounces@xxxxxxxxxxxxxxxxxxx
Dear all,

I am not observing a change in the performance of my hardware-assisted virtual machines (HVMs) when I change the scheduling parameters (weight and cap) associated with the HVMs unless they are rebooted. 

I am testing using 2 HVMs running Linux kernels (2.6.24-26-generic) in the guest operating system. My hardware is 1 x Intel(R) Core(TM)2 Duo CPU E8400 @ 3.00GHz. I have pinned my Domain-0 to physical CPU-0 and the 2 HVMs to physical CPU-1. In order create a load on my HVMs I run the "glxgears" API and monitor the performance using "xentop" (and from the movement of the gears, on the pop-up screen). I use the "xe" CLI to set and check the scheduling parameters.

I have experimented with setting the cap and weight of one domains to the least  possible value (1, 1 respectively) and that of the other to the maximum possible value (0 and 65536 respectively), the initial cap and weight of both domains being at the default setting of 0 and 256, but the processor utilization remains unchanged (at 50% for both domains) unless I reboot my HVMs. Once I do that, I can see the expected (enormous) difference in the performance.

Is it not possible to change processor utilization without having to reboot the HVMs? What am I missing here?
Please help!

Priya Bhat
Xen-devel mailing list
<Prev in Thread] Current Thread [Next in Thread>
  • [Xen-devel] Xen Domains scheduling parameters do not take effect before rebooting, Priya <=