Mailing-List: contact issues-help@cloudstack.apache.org; run by ezmlm
Precedence: bulk
Reply-To: dev@cloudstack.apache.org
Date: Sat, 7 Dec 2013 00:30:36 +0000 (UTC)
From: "ASF subversion and git services (JIRA)" <jira@apache.org>
To: cloudstack-issues@incubator.apache.org
Message-ID: <JIRA.12682447.1386093801161.90192.1386376236690@arcas>
In-Reply-To: <JIRA.12682447.1386093801161@arcas>
References: <JIRA.12682447.1386093801161@arcas>
Subject: [jira] [Commented] (CLOUDSTACK-5352) CPU cap calculated incorrectly
 for VMs on XenServer hosts
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: quoted-printable


    [ https://issues.apache.org/jira/browse/CLOUDSTACK-5352?page=3Dcom.atla=
ssian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=
=3D13841942#comment-13841942 ]=20

ASF subversion and git services commented on CLOUDSTACK-5352:
-------------------------------------------------------------

Commit 275537e9280ae3deab472fe34b276f3ca3dc71bb in branch refs/heads/4.2 fr=
om [~nitinme]
[ https://git-wip-us.apache.org/repos/asf?p=3Dcloudstack.git;h=3D275537e ]

CLOUDSTACK-5352:
CPU cap calculated incorrectly for VMs on XenServer hosts. It should not be=
 limited by the overprovisioning and should set the cap as service offering


> CPU cap calculated incorrectly for VMs on XenServer hosts
> ---------------------------------------------------------
>
>                 Key: CLOUDSTACK-5352
>                 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-535=
2
>             Project: CloudStack
>          Issue Type: Bug
>      Security Level: Public(Anyone can view this level - this is the defa=
ult.)=20
>    Affects Versions: 4.2.0, 4.3.0
>            Reporter: Nitin Mehta
>            Assignee: Nitin Mehta
>            Priority: Critical
>             Fix For: 4.3.0
>
>
> The CPU cap assigned to VMs on XenServer hosts (via VCPUs-params paramete=
r) is not calculated correctly. The assigned values are too low and can res=
ult in performance problems. This seems related to CPU overprovisioning. Th=
e assigned CPU cap is approximately the expected cap / CPU overprovisioning=
 value. The customer is using CloudStack 4.2.0 with XenServer 6.1. On the c=
ustomer environment they have several VMs that were created before upgradin=
g to 4.2.0 from 3.0.6 and never rebooted, and those VMs appear to have the =
expected CPU cap.
> I see similar results on a CS 4.2.1 setup with a XS 6.2 host with 1x E312=
20L CPU =E2=80=93 2x physical cores / 4x logical cores (with hyperthreading=
) at 2.20GHz =E2=80=93 8800 MHz total (confirmed in op_host_capacity), a Co=
mpute Offering with 2200 MHz and 4 cores gives a VM with:
> [root@csdemo-xen2 ~]# xe vm-list params=3Dname-label,uuid,VCPUs-params na=
me-label=3Di-2-87-VM
> uuid ( RO) : 7cd5893e-728a-a0f3-c2cf-f3464cb8b9cb
> name-label ( RW): i-2-87-VM
> VCPUs-params (MRW): weight: 84; cap: 131
> And with a Compute Offering with 2200 MHz and 1 core gives a VM with:
> [root@csdemo-xen2 ~]# xe vm-list params=3Dname-label,uuid,VCPUs-params na=
me-label=3Di-2-87-VM
> uuid ( RO) : c17cd63a-f6d5-8f76-d7f1-eb34d574e0dd
> name-label ( RW): i-2-87-VM
> VCPUs-params (MRW): weight: 84; cap: 32
> The configured cap does not make sense in either example. In this environ=
ment, cpu.overprovisioning.factor is 3 for the cluster and 1 in Global Sett=
ings. In example 1 the cap should be:
> 2200 * 0.99 * 4 / 2200 * 100
> =3D 396
> But it is:
> 2200 * 0.99 * 4 / (3*2200) * 100
> =3D 132
> For example 2 it should be:
> 2200 * 0.99 * 1 / 2200 * 100
> =3D 99
> But it is:
> 2200 * 0.99 * 1 / (3*2200) * 100


--
This message was sent by Atlassian JIRA
(v6.1#6144)