Re: [Xen-devel] [PATCH][xend] Fix handling of scheduler params

[Masaki Kanno <kanno.masaki@xxxxxxxxxxxxxx>]

Hi Jim,

If the patch is applied, I think that "cpu_weight" and "cpu_cap" 
disappear from information of xm list.  Is my thought right? 

Best regards,
 Kan

>When creating domains that specify scheduler parameters with XenAPI, the
>specified parameters are not used when starting the domain.  As an
>example, here is a snippet of internal config for a domain created via
>XenAPI that contains scheduling params:
>
>(domain
>    (domid 6)
>    (vcpus_params ((cap 100) (weight 512)))
>    ...
>    (cpu_weight 256)
>    (cpu_cap 0)
>    ...
>)
>
>Starting the domain results in following scheduler settings:
>
>jfehlig4:/home/jfehlig/cim/cimxml # xm sched-credit -d sles10_nographic
>Name                              ID Weight Cap
>sles10_nographic                   6    256    0
>
>The attached patch collapses cpu_weight and cpu_cap in XendConfig into
>the vcpus_params dictionary.  The patch has been tested using xm and
>XenAPI on config with and without scheduler parameters.
>
>Regards,
>Jim
>
>Signed-off-by: Jim Fehlig <jfehlig@xxxxxxxxxx>
>
>
>
>-------------------------------text/plain-------------------------------
>_______________________________________________
>Xen-devel mailing list
>Xen-devel@xxxxxxxxxxxxxxxxxxx
>http://lists.xensource.com/xen-devel


_______________________________________________
Xen-devel mailing list
Xen-devel@xxxxxxxxxxxxxxxxxxx
http://lists.xensource.com/xen-devel