Hi, I add the Xen Scheduler APIs to xenDaemonDriver. - xenDaemonGetSchedulerType - xenDaemonGetSchedulerParameters - xenDaemonSetSchedulerParameters We will have the following improvements by this patch: 1) xenDaemonDriver of Schedulr is usable when xenHypervisorDriver failed. 2) Show the Scheduler information with non-root user. 3) Set the Scheduler parameters for inactive domain. (Unfortunately not right now, because we need this fix. http://lists.xensource.com/archives/html/xen-devel/2008-03/msg00301.html) And I have a few things to note: - Currently, implemented for the Xen-credit scheduler only. - xenDaemonGetSchedulerType is supported in xendConfigVersion >= 4, because we can get "xen_scheduler" from xend after Cset13394 of Xen (i.e. xendConfigVersion is four or later). - For the above reason, xenDaemonGetSchedulerParameters and xenDaemonSetSchedulerParameters are also supported in xendConfigVersion >= 4, because they are using xenDaemonGetSchedulerType to get the scheduler type. - At xenDaemonSetSchedulerParameters, there are restrictions which depends on Xend-version. a) We cannot set the "cap" value by xend before Cset15476 of Xen, because xend does not support the "cap" value at xend/server/SrvDomain.py b) We cannot set the scheduler parameters for inactive domain without the following patch. http://lists.xensource.com/archives/html/xen-devel/2008-03/msg00301.html If the above patch is committed, this API will be available for inactive domain. Regards, Saori Fukuta

On Mon, Mar 24, 2008 at 02:12:25PM +0900, Saori Fukuta wrote: > How about the second one ? We can make some improvements for virsh > schedinfo command with the patch, so I want the patch to be committed > if it is OK. I had forgotten about it, sorry. It looks okay, though i have to clean a few problems raised by 'make syntax-check' (please try this in future patches). I commited it to CVS.

However, i don't see why it is needed, basically when running with Xen as root, the hypervisor access should be used, not xend, so this seems to indicate that you have problem using the hypervisor calls and that's probably something to worry about. But it's fine having a more complete xend driver surrport.