cloudstack-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "prashant kumar mishra (JIRA)" <j...@apache.org>
Subject [jira] [Closed] (CLOUDSTACK-1646) user VMs with equal cpu speed and different number of vcpus getting same weight on xenserver
Date Fri, 26 Jul 2013 12:41:49 GMT

     [ https://issues.apache.org/jira/browse/CLOUDSTACK-1646?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]

prashant kumar mishra closed CLOUDSTACK-1646.
---------------------------------------------


as per comment it is expected nature ,so closing
                
> user VMs with equal cpu speed and different number of vcpus getting same weight on xenserver
> --------------------------------------------------------------------------------------------
>
>                 Key: CLOUDSTACK-1646
>                 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-1646
>             Project: CloudStack
>          Issue Type: Bug
>      Security Level: Public(Anyone can view this level - this is the default.) 
>    Affects Versions: 4.2.0
>            Reporter: prashant kumar mishra
>            Assignee: Harikrishna Patnala
>            Priority: Critical
>             Fix For: 4.2.0
>
>         Attachments: access_log.2013-03-12.txt, apilog.log, catalina.out, management-server.log
>
>
> Deployed two vms having cpu speed 2GHZ  with different number of  vcpus .they are getting
assign same weight on xen .
> VM1
> --------
> SO>>vcpus:2 , speed 2 GHZ
> VM2
> --------
> SO>>VCPU:4 speed 2 GHZ
> EXPECTED
> ------------------
> VM should get different weight(vm2 should get 2 times wight of vm1)
> ACTUAL
> --------------
> VM1 and vm2  both are got assign  same weight(105)
> ======================================
> [root@Rack1Pod1Host7 ~]# xl sched-credit
> Name                                ID Weight  Cap
> Domain-0                             0      8    0
> s-1-VM                             102     26    0
> v-2-VM                             103     26    0
> r-30-VM                            110     26    0
> i-2-55-VM                          116    105    0
> i-2-56-VM                          117    105    0
> DB
> ===========
> mysql> select * from vm_instance where id >54\G;
> *************************** 1. row ***************************
>                  id: 55
>                name: cpu3
>                uuid: 7996cdf4-f392-42d1-97c9-dc0d08f234f9
>       instance_name: i-2-55-VM
>               state: Running
>      vm_template_id: 5
>         guest_os_id: 12
> private_mac_address: 02:00:44:12:00:35
>  private_ip_address: 10.1.1.209
>              pod_id: 1
>      data_center_id: 1
>             host_id: 1
>        last_host_id: 1
>            proxy_id: NULL
>   proxy_assign_time: NULL
>        vnc_password: FuFeyogwp1RDb8r0psJfUItB/ggQxoKMlR8gPuCdVns=
>          ha_enabled: 0
>       limit_cpu_use: 0
>        update_count: 3
>         update_time: 2013-03-12 12:47:49
>             created: 2013-03-12 12:47:24
>             removed: NULL
>                type: User
>             vm_type: User
>          account_id: 2
>           domain_id: 1
> service_offering_id: 25
>      reservation_id: b64c5832-88aa-4087-896c-a25af1771da5
>     hypervisor_type: XenServer
>    disk_offering_id: 3
>                 cpu: NULL
>                 ram: NULL
>               owner: 2
>               speed: 2000
>           host_name: cpu3
>        display_name: cpu3
>       desired_state: NULL
> *************************** 2. row ***************************
>                  id: 56
>                name: cpu4
>                uuid: ac25c63b-74c5-4460-bc6e-ef9e068e1c98
>       instance_name: i-2-56-VM
>               state: Running
>      vm_template_id: 5
>         guest_os_id: 12
> private_mac_address: 02:00:14:3a:00:36
>  private_ip_address: 10.1.1.114
>              pod_id: 1
>      data_center_id: 1
>             host_id: 1
>        last_host_id: 1
>            proxy_id: NULL
>   proxy_assign_time: NULL
>        vnc_password: QZeAyOPBJtCLEfu0bZeBf10N4FpFEhkz8K9G8Gzn4E4=
>          ha_enabled: 0
>       limit_cpu_use: 0
>        update_count: 3
>         update_time: 2013-03-12 12:48:57
>             created: 2013-03-12 12:48:33
>             removed: NULL
>                type: User
>             vm_type: User
>          account_id: 2
>           domain_id: 1
> service_offering_id: 26
>      reservation_id: 6db43dfc-e054-4842-8496-afeeed955442
>     hypervisor_type: XenServer
>    disk_offering_id: 3
>                 cpu: NULL
>                 ram: NULL
>               owner: 2
>               speed: 2000
>           host_name: cpu4
>        display_name: cpu4
>       desired_state: NULL
> 2 rows in set (0.00 sec)
> ERROR:
> No query specified
> =========Service offering details============
> mysql> select  id, uuid, name,display_text,cpu,speed, ram_size from service_offering_view
where id >24\G;
> *************************** 1. row ***************************
>           id: 25
>         uuid: f826a9ec-63ae-4e6b-882e-c16ffd172039
>         name: cpu3
> display_text: cpu3
>          cpu: 2
>        speed: 2000
>     ram_size: 1024
> *************************** 2. row ***************************
>           id: 26
>         uuid: 6cdb4d46-570f-49a1-b99f-22ff35c063d6
>         name: cpu4
> display_text: cpu4
>          cpu: 4
>        speed: 2000
>     ram_size: 1024
> 2 rows in set (0.00 sec)
> ERROR:
> No query specified

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

Mime
View raw message