Any chance of this fix being rolled into 4.0.1?
-----Original Message-----
From: Koushik Das (JIRA) [mailto:j...@apache.org]
Sent: Tuesday, December 11, 2012 9:31 AM
To: cloudstack-dev@incubator.apache.org
Subject: [jira] [Commented] (CLOUDSTACK-605) Host physical CPU is incorrectly
calculated for Vmware hosts
[
https://issues.apache.org/jira/browse/CLOUDSTACK-605?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13529005#comment-13529005
]
Koushik Das commented on CLOUDSTACK-605:
----------------------------------------
The fix for CS-16863 is not yet merged into CS Apache branch.
> Host physical CPU is incorrectly calculated for Vmware hosts
> ------------------------------------------------------------
>
> Key: CLOUDSTACK-605
> URL: https://issues.apache.org/jira/browse/CLOUDSTACK-605
> Project: CloudStack
> Issue Type: Bug
> Security Level: Public(Anyone can view this level - this is the
> default.)
> Components: VMware
> Affects Versions: pre-4.0.0, 4.0.0
> Reporter: Koushik Das
> Assignee: Koushik Das
>
> There is a mismatch in host CPU count displayed in CS UI (displayed under the
> 'Statistics' tab when a host is selected) compared to that in vCenter. The
> mismatch happens for ESX hosts having > 1 cpu package. This will affect VM
> allocation logic.
> Currently host CPU is computed based on below logic
> (HostHardwareSummary is defined in Vmware library) HostHardwareSummary
> hardwareSummary = getHostHardwareSummary();
> summary.setCpuCount(hardwareSummary.getNumCpuCores()*hardwareSummary.g
> etNumCpuPkgs()); The correct logic is to use
> hardwareSummary.getNumCpuCores() only.
--
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
