* Set cpu_weight and cpu_cap at boot time
@ 2007-06-05 11:35 Dominik Klein
2007-06-05 12:15 ` Petersson, Mats
0 siblings, 1 reply; 5+ messages in thread
From: Dominik Klein @ 2007-06-05 11:35 UTC (permalink / raw)
To: xen-devel
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
^ permalink raw reply [flat|nested] 5+ messages in thread* RE: Set cpu_weight and cpu_cap at boot time
2007-06-05 11:35 Set cpu_weight and cpu_cap at boot time Dominik Klein
@ 2007-06-05 12:15 ` Petersson, Mats
2007-06-05 12:19 ` Dominik Klein
0 siblings, 1 reply; 5+ messages in thread
From: Petersson, Mats @ 2007-06-05 12:15 UTC (permalink / raw)
To: Dominik Klein, xen-devel
> -----Original Message-----
> From: xen-devel-bounces@lists.xensource.com
> [mailto:xen-devel-bounces@lists.xensource.com] On Behalf Of
> Dominik Klein
> Sent: 05 June 2007 12:35
> To: xen-devel@lists.xensource.com
> 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@lists.xensource.com
> http://lists.xensource.com/xen-devel
>
>
>
^ permalink raw reply [flat|nested] 5+ messages in thread
* Re: Set cpu_weight and cpu_cap at boot time
2007-06-05 12:15 ` Petersson, Mats
@ 2007-06-05 12:19 ` Dominik Klein
2007-06-05 12:27 ` Petersson, Mats
0 siblings, 1 reply; 5+ messages in thread
From: Dominik Klein @ 2007-06-05 12:19 UTC (permalink / raw)
To: xen-devel
> 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...
Ok, maybe, I am not familiar with that.
Well that does not change that both configuration items do not work (for
my PV linux domains in xen 3.1.0)
Regards
Dominik
^ permalink raw reply [flat|nested] 5+ messages in thread
* RE: Set cpu_weight and cpu_cap at boot time
2007-06-05 12:19 ` Dominik Klein
@ 2007-06-05 12:27 ` Petersson, Mats
2007-06-05 13:22 ` [solved] " Dominik Klein
0 siblings, 1 reply; 5+ messages in thread
From: Petersson, Mats @ 2007-06-05 12:27 UTC (permalink / raw)
To: Dominik Klein, xen-devel
> -----Original Message-----
> From: xen-devel-bounces@lists.xensource.com
> [mailto:xen-devel-bounces@lists.xensource.com] On Behalf Of
> Dominik Klein
> Sent: 05 June 2007 13:20
> To: xen-devel@lists.xensource.com
> Subject: Re: [Xen-devel] Set cpu_weight and cpu_cap at boot time
>
> > 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...
>
> Ok, maybe, I am not familiar with that.
>
> Well that does not change that both configuration items do
> not work (for
> my PV linux domains in xen 3.1.0)
That may well be the case, but it probably takes a bit more digging
before that can be solved.
--
Mats
>
> Regards
> Dominik
>
> _______________________________________________
> Xen-devel mailing list
> Xen-devel@lists.xensource.com
> http://lists.xensource.com/xen-devel
>
>
>
^ permalink raw reply [flat|nested] 5+ messages in thread
* [solved] Re: Set cpu_weight and cpu_cap at boot time
2007-06-05 12:27 ` Petersson, Mats
@ 2007-06-05 13:22 ` Dominik Klein
0 siblings, 0 replies; 5+ messages in thread
From: Dominik Klein @ 2007-06-05 13:22 UTC (permalink / raw)
To: xen-devel
> That may well be the case, but it probably takes a bit more digging
> before that can be solved.
It actually works. It was my fault.
I tested it by setting cpu_weight in the config and the RESTARTING the
domain. This did not read the new value but use the last one.
SHUTDOWN and CREATE does recognize the new value in the config file.
Sorry to bother you.
Regards
Dominik
^ permalink raw reply [flat|nested] 5+ messages in thread
end of thread, other threads:[~2007-06-05 13:22 UTC | newest]
Thread overview: 5+ messages (download: mbox.gz follow: Atom feed
-- links below jump to the message on this page --
2007-06-05 11:35 Set cpu_weight and cpu_cap at boot time Dominik Klein
2007-06-05 12:15 ` Petersson, Mats
2007-06-05 12:19 ` Dominik Klein
2007-06-05 12:27 ` Petersson, Mats
2007-06-05 13:22 ` [solved] " Dominik Klein
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.