From e1e4642d678a62c28a1d73046a6717b448e6f2fe Mon Sep 17 00:00:00 2001 From: Sateesh Chodapuneedi Date: Thu, 8 Aug 2013 08:54:00 +0530 Subject: [PATCH] CLOUDSTACK-4181 [upgrade][2.2.14 to 4.2][vmware]After upgrade the system vms fail to start number of cores per socket for ESXi4.1 is 1. Signed-off-by: Sateesh Chodapuneedi --- .../src/com/cloud/hypervisor/vmware/mo/VirtualMachineMO.java | 5 +++++ 1 file changed, 5 insertions(+) diff --git a/vmware-base/src/com/cloud/hypervisor/vmware/mo/VirtualMachineMO.java b/vmware-base/src/com/cloud/hypervisor/vmware/mo/VirtualMachineMO.java index 7d77a8d0125..6c33eea496d 100644 --- a/vmware-base/src/com/cloud/hypervisor/vmware/mo/VirtualMachineMO.java +++ b/vmware-base/src/com/cloud/hypervisor/vmware/mo/VirtualMachineMO.java @@ -2200,6 +2200,11 @@ public class VirtualMachineMO extends BaseMO { } public int getCoresPerSocket() throws Exception { + // number of cores per socket is 1 in case of ESXi. It's not defined explicitly and the property is support since vSphere API 5.0. + String apiVersion = HypervisorHostHelper.getVcenterApiVersion(_context); + if (apiVersion.compareTo("5.0") < 0) { + return 1; + } return (Integer)_context.getVimClient().getDynamicProperty(_mor, "config.hardware.numCoresPerSocket"); }