Re: [Xen-API] [BUG] Xenserver 6.2 and XCP 1.6 ignore cap parameter for VPUs-params

[Bob Ball <bob.ball@xxxxxxxxxx>]

Hi George,

I've heard of this before - it's an incorrect parsing of the cap and weight 
parameters - they must both be valid values, otherwise the parsing generates an 
internal exception and both are ignored.

Try setting a weight as well as the cap - even if the weight is the same for 
all VMs - and then the caps should be honored.

Bob
________________________________________
From: xen-api-bounces@xxxxxxxxxxxxx [xen-api-bounces@xxxxxxxxxxxxx] on behalf 
of George Shuklin [george.shuklin@xxxxxxxxx]
Sent: 12 September 2013 09:10
To: xen-api@xxxxxxxxxxxxxxxxxxx
Subject: [Xen-API] [BUG] Xenserver 6.2 and XCP 1.6 ignore cap parameter for     
VPUs-params

Good day.

Found bug in all 'xenops' versions (XCP 1.6, Xenserver 6.2).

Parameter 'cap' in  VCPUs-params is ignored. It mention in administrator
guide for XenServer 6.2/6.1, and worked in earlier version (XCP 1.1),
after upgrade it is ignored. Checked on fresh installation of Xenserver
6.2 and upgraded one.

Cap can be changed manually via xc library for python but lasts only
until migration.

Steps to reproduce:

Install vm

xe vm-set-param vm=... VPUs-params=cap:30
xe vm-shutdown vm=...
xe vm-start vm=...

run any cpu-intensive operation (f.e. cpuburn).

Expected: 30% CPU for domain at max
Actual: 100% or even more CPU


_______________________________________________
Xen-api mailing list
Xen-api@xxxxxxxxxxxxx
http://lists.xen.org/cgi-bin/mailman/listinfo/xen-api

_______________________________________________
Xen-api mailing list
Xen-api@xxxxxxxxxxxxx
http://lists.xen.org/cgi-bin/mailman/listinfo/xen-api