Mailing-List: contact issues-help@cloudstack.apache.org; run by ezmlm
Precedence: bulk
Reply-To: dev@cloudstack.apache.org
Date: Thu, 3 Nov 2016 11:55:58 +0000 (UTC)
From: "Nux (JIRA)" <jira@apache.org>
To: cloudstack-issues@incubator.apache.org
Message-ID: <JIRA.12929442.1452593465000.171704.1478174158350@Atlassian.JIRA>
In-Reply-To: <JIRA.12929442.1452593465000@Atlassian.JIRA>
References: <JIRA.12929442.1452593465000@Atlassian.JIRA> <JIRA.12929442.1452593465776@arcas>
Subject: [jira] [Commented] (CLOUDSTACK-9226) Wrong number of sockets
 reported
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit
archived-at: Thu, 03 Nov 2016 11:56:00 -0000


    [ https://issues.apache.org/jira/browse/CLOUDSTACK-9226?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15632522#comment-15632522 ] 

Nux commented on CLOUDSTACK-9226:
---------------------------------

Hi Andrija,

Unless the number of sockets is not reported correctly, then I don't think this is the right place for your issue.
It looks more like an issue of how CPU is reported by OS/libvirt.

> Wrong number of sockets reported
> --------------------------------
>
>                 Key: CLOUDSTACK-9226
>                 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-9226
>             Project: CloudStack
>          Issue Type: Bug
>      Security Level: Public(Anyone can view this level - this is the default.) 
>          Components: KVM
>    Affects Versions: 4.6.0, 4.7.0
>         Environment: KVM, CentOS 7 mgmt + HV
>            Reporter: Nux
>              Labels: dashboard, kvm, sockets, statistics
>
> Hello,
> My current setup includes a dual cpu, quad core + HT, however in the ACS dashboard the "CPU sockets" says only one.
> This value is wrong and as I undestand it, it is taken from "virsh nodeinfo" which is known to give misleading information, as it reports stuff "per NUMA cell"
> As per the man page of virsh, the number of real physical sockets should be calculated as "NUMA cell" multiplied by "CPU sockets".
> e.g.
> virsh nodeinfo
> CPU model:           x86_64
> CPU(s):              16
> CPU frequency:       2393 MHz
> CPU socket(s):       1
> Core(s) per socket:  4
> Thread(s) per core:  2
> NUMA cell(s):        2
> physical cpus = "CPU socket(s):       1"  *  "NUMA cell(s):        2" = 2 (correct)
> Additional information can be taken from "virsh capabilities|grep socket_id" (xml output) e.g.:
> virsh capabilities|grep socket_id
>             <cpu id='0' socket_id='1' core_id='0' siblings='0,8'/>
>             <cpu id='2' socket_id='1' core_id='1' siblings='2,10'/>
>             <cpu id='4' socket_id='1' core_id='9' siblings='4,12'/>
>             <cpu id='6' socket_id='1' core_id='10' siblings='6,14'/>
>             <cpu id='8' socket_id='1' core_id='0' siblings='0,8'/>
>             <cpu id='10' socket_id='1' core_id='1' siblings='2,10'/>
>             <cpu id='12' socket_id='1' core_id='9' siblings='4,12'/>
>             <cpu id='14' socket_id='1' core_id='10' siblings='6,14'/>
>             <cpu id='1' socket_id='0' core_id='0' siblings='1,9'/>
>             <cpu id='3' socket_id='0' core_id='1' siblings='3,11'/>
>             <cpu id='5' socket_id='0' core_id='9' siblings='5,13'/>
>             <cpu id='7' socket_id='0' core_id='10' siblings='7,15'/>
>             <cpu id='9' socket_id='0' core_id='0' siblings='1,9'/>
>             <cpu id='11' socket_id='0' core_id='1' siblings='3,11'/>
>             <cpu id='13' socket_id='0' core_id='9' siblings='5,13'/>
>             <cpu id='15' socket_id='0' core_id='10' siblings='7,15'/>


--
This message was sent by Atlassian JIRA
(v6.3.4#6332)