WARNING - OLD ARCHIVES

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/
   
 
 
Xen 
 
Home Products Support Community News
 
   
 

xen-devel

RE: [Xen-devel] Set cpu_weight and cpu_cap at boot time

To: "Dominik Klein" <dk@xxxxxxxxxxxxxxxx>, xen-devel@xxxxxxxxxxxxxxxxxxx
Subject: RE: [Xen-devel] Set cpu_weight and cpu_cap at boot time
From: "Petersson, Mats" <Mats.Petersson@xxxxxxx>
Date: Tue, 5 Jun 2007 14:15:46 +0200
Delivery-date: Tue, 05 Jun 2007 05:14:17 -0700
Envelope-to: www-data@xxxxxxxxxxxxxxxxxx
In-reply-to: <46654A65.2080902@xxxxxxxxxxxxxxxx>
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/cgi-bin/mailman/listinfo/xen-devel>, <mailto:xen-devel-request@lists.xensource.com?subject=subscribe>
List-unsubscribe: <http://lists.xensource.com/cgi-bin/mailman/listinfo/xen-devel>, <mailto:xen-devel-request@lists.xensource.com?subject=unsubscribe>
Sender: xen-devel-bounces@xxxxxxxxxxxxxxxxxxx
Thread-index: AcenZaQMlvoWWQlgS/mFgI7xJsa2kAABX4Qg
Thread-topic: [Xen-devel] Set cpu_weight and cpu_cap at boot time
 

> -----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