You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@cloudstack.apache.org by "prashant kumar mishra (JIRA)" <ji...@apache.org> on 2013/07/31 09:41:49 UTC

[jira] [Created] (CLOUDSTACK-3970) vms with cpu=2GHz getting less weight (52) compare to vms with cpu=1.5GHz (158)

prashant kumar mishra created CLOUDSTACK-3970:
-------------------------------------------------

             Summary: vms with cpu=2GHz getting less weight (52) compare to vms with cpu=1.5GHz (158)
                 Key: CLOUDSTACK-3970
                 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-3970
             Project: CloudStack
          Issue Type: Bug
      Security Level: Public (Anyone can view this level - this is the default.)
         Environment: hyp:xenserver6.1
            Reporter: prashant kumar mishra
            Priority: Critical
         Attachments: XEN_DB_MS.rar

Weight
A domain with a weight of 512 will get twice as much CPU as a domain with a weight of 256 on a contended host. Legal weights range from 1 to 65535 and the default is 256
--> http://wiki.xen.org/wiki/Credit_Scheduler


Steps to reproduce
===============
1-prepare a CS setup with xen6.1
2-create  service offerings say cpu15(cpu=1.5GHz,vcpu=1,ram=512),cpu2(cpu=2GHz,vcpu=1,ram=512)
3-deploy vms  vm1 using cpu15 and vm2 using cpu2
4-check weight of vm on xen hypervisor using   #xe vm-list params=all uuid=    |grep weight

Expected
--------------
vm1 should get less weight compare to vm2

Actual
----------
vm1(158) getting more weight than vm2(52) 


details
=======
[root@Rack1Pod1Host7 ~]# xe vm-list
uuid ( RO)           : 3119bbdf-9d0c-019f-e3f6-58cc20c76e37
     name-label ( RW): i-2-37-VM
    power-state ( RO): running


uuid ( RO)           : b992ea8b-c08a-1730-3461-717f8b4f0220
     name-label ( RW): r-4-VM
    power-state ( RO): running


uuid ( RO)           : e7d05be1-13d5-c9ed-e3dd-27ad8de4326e
     name-label ( RW): v-2-VM
    power-state ( RO): running


uuid ( RO)           : 5650439d-7951-cdc4-a05e-52c5b108cd37
     name-label ( RW): s-1-VM
    power-state ( RO): running


uuid ( RO)           : d36d336e-800a-4363-a248-8ded70080eae
     name-label ( RW): Control domain on host: Rack1Pod1Host7
    power-state ( RO): running


uuid ( RO)           : ee434e8f-b912-0cb0-59e5-9c7d1d8a87a4
     name-label ( RW): i-2-38-VM
    power-state ( RO): running




[root@Rack1Pod1Host7 ~]# xe vm-list params=all uuid=5650439d-7951-cdc4-a05e-52c5b108cd37  |grep weight
                  VCPUs-params (MRW): weight: 52; cap: 0


[root@Rack1Pod1Host7 ~]# xe vm-list params=all uuid=ee434e8f-b912-0cb0-59e5-9c7d1d8a87a4 |grep weight
                  VCPUs-params (MRW): weight: 158; cap: 0

[root@Rack1Pod1Host7 ~]# xe vm-list params=all uuid=5650439d-7951-cdc4-a05e-52c5b108cd37  |grep weight
                  VCPUs-params (MRW): weight: 52; cap: 0




my observation
----------------------
VM with cpu=2GHz is getting same weight as vm with cpu=500MHz




--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira