Set cpu_weight and cpu_cap at boot time

Set cpu_weight and cpu_cap at boot time

[Dominik Klein]

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

RE: Set cpu_weight and cpu_cap at boot time

[Petersson, Mats]

 

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

Re: Set cpu_weight and cpu_cap at boot time

[Dominik Klein]

> 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

RE: Set cpu_weight and cpu_cap at boot time

[Petersson, Mats]

 

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

[solved] Re: Set cpu_weight and cpu_cap at boot time

[Dominik Klein]

> 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

[solved] Re: Set cpu_weight and cpu_cap at boot time

[Volker Badziong]

Shouldn't RESTART be semantically the same as SHUTDOWN && CREATE ?!

Regards,
Volker


> 
> > 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
> 
> _______________________________________________
> Xen-devel mailing list
> Xen-devel@lists.xensource.com
> http://lists.xensource.com/xen-devel

-- 
Psssst! Schon vom neuen GMX MultiMessenger gehört?
Der kanns mit allen: http://www.gmx.net/de/go/multimessenger

[solved] Re: Set cpu_weight and cpu_cap at boot time

[Volker Badziong]

Hi, 

shouldn't RESTART be semantically the same as SHUTDOWN && CREATE ?!

Regards,
Volker


> 
> > 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
> 
> _______________________________________________
> Xen-devel mailing list
> Xen-devel@lists.xensource.com
> http://lists.xensource.com/xen-devel


-- 
GMX FreeMail: 1 GB Postfach, 5 E-Mail-Adressen, 10 Free SMS.
Alle Infos und kostenlose Anmeldung: http://www.gmx.net/de/go/freemail

RE: [solved] Re: Set cpu_weight and cpu_cap at boot time

[Petersson, Mats]

 

> -----Original Message-----
> From: xen-devel-bounces@lists.xensource.com 
> [mailto:xen-devel-bounces@lists.xensource.com] On Behalf Of 
> Volker Badziong
> Sent: 05 June 2007 15:13
> To: xen-devel@lists.xensource.com
> Subject: [solved] Re: [Xen-devel] Set cpu_weight and cpu_cap 
> at boot time
> 
> Hi, 
> 
> shouldn't RESTART be semantically the same as SHUTDOWN && CREATE ?!

Just like a system reboot is not exactly the same as powerdown and power
up, restart just WARM RESTARTS the guest - so it essentially just tells
the guest to start over from scratch. So it uses the stored
configuration of the guest, rather than re-reading the guest config
[note that a guest configuration isn't necessarily a file - you can
specify every single component as a command-line argument to the "xm
create" command, so "xm create" actually stores all the values given to
it, and any updates are also changing the stored values]. 

So they are not and can not be exactly the same. 

--
Mats
> 
> Regards,
> Volker
> 
> 
> > 
> > > 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
> > 
> > _______________________________________________
> > Xen-devel mailing list
> > Xen-devel@lists.xensource.com
> > http://lists.xensource.com/xen-devel
> 
> 
> -- 
> GMX FreeMail: 1 GB Postfach, 5 E-Mail-Adressen, 10 Free SMS.
> Alle Infos und kostenlose Anmeldung: http://www.gmx.net/de/go/freemail
> 
> _______________________________________________
> Xen-devel mailing list
> Xen-devel@lists.xensource.com
> http://lists.xensource.com/xen-devel
> 
> 
>