From mboxrd@z Thu Jan  1 00:00:00 1970
From: Dominik Klein <dk@in-telegence.net>
Subject: Set cpu_weight and cpu_cap at boot time
Date: Tue, 05 Jun 2007 13:35:01 +0200
Message-ID: <46654A65.2080902@in-telegence.net>
Mime-Version: 1.0
Content-Type: text/plain; charset=ISO-8859-15; format=flowed
Content-Transfer-Encoding: 7bit
Return-path: <xen-devel-bounces@lists.xensource.com>
List-Unsubscribe: <http://lists.xensource.com/cgi-bin/mailman/listinfo/xen-devel>,
	<mailto:xen-devel-request@lists.xensource.com?subject=unsubscribe>
List-Post: <mailto:xen-devel@lists.xensource.com>
List-Help: <mailto:xen-devel-request@lists.xensource.com?subject=help>
List-Subscribe: <http://lists.xensource.com/cgi-bin/mailman/listinfo/xen-devel>,
	<mailto:xen-devel-request@lists.xensource.com?subject=subscribe>
Sender: xen-devel-bounces@lists.xensource.com
Errors-To: xen-devel-bounces@lists.xensource.com
To: xen-devel@lists.xensource.com
List-Id: xen-devel@lists.xenproject.org

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?

This is xen 3.1.0

Regards
Dominik