> -----Original Message-----
> From: xen-devel-bounces@xxxxxxxxxxxxxxxxxxx
> [mailto:xen-devel-bounces@xxxxxxxxxxxxxxxxxxx] On Behalf Of
> Dominik Klein
> Sent: 05 June 2007 12:35
> To: xen-devel@xxxxxxxxxxxxxxxxxxx
> Subject: [Xen-devel] Set cpu_weight and cpu_cap at boot time
>
> Hi
>
> "xm create --help_config" gives:
> ...
> cpu_cap=CAP Set the maximum amount of cpu.
> CAP is a percentage that fixes the
> maximum amount
> of cpu.
> cpu_weight=WEIGHT Set the cpu time ratio to be allocated
> to the domain.
> ...
>
> As it does not work I looked at the py Files and found this:
>
> /usr/lib/python/xen/xend/XendConfig.py :
> ...
> # List of legacy configuration keys that have no equivalent in the
> # Xen API, but are still stored in XendConfig.
> LEGACY_UNSUPPORTED_BY_XENAPI_CFG = [
> # roundtripped (dynamic, unmodified)
> 'shadow_memory',
> 'security',
> 'vcpu_avail',
> 'cpu_weight',
> 'cpu_cap',
> 'features',
> # read/write
> 'on_xend_start',
> 'on_xend_stop',
> # read-only
> 'domid',
> 'start_time',
> 'cpu_time',
> 'online_vcpus',
> # write-once
> 'cpu',
> 'cpus',
> ]
> ...
>
> So it looks like it cannot work yet. Are there any plans to
> change/fix this?
But that only means that they can't be used by XenAPI - as far as I
know, "xm create" doesn't use XenAPI - at least it didn't a week or two
ago...
--
Mats
>
> This is xen 3.1.0
>
> Regards
> Dominik
>
> _______________________________________________
> 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
|
Home