From 9156563314f5efc8ffb5d6f49ef5fc06f89d73fa Mon Sep 17 00:00:00 2001 From: Jason Azze Date: Thu, 27 Aug 2020 15:10:33 -0400 Subject: [PATCH] Update HardwareConfig-not-required.mdx I've tested the behavior of CPUs and cpu_cores against both vSphere 5.5 and 6.7. In both cases, CPUs gives you virtual cores, not sockets. For example, I want 6 cores per socket across 2 sockets for 12 total cores. Based on the wording of this doc, I set CPUs to 2 and cpu_cores to 6. The documentation implies that will give me 2 sockets with 6 cores each. The actual behavior is you get 2 cores, and when you crack open the VMs configuration, you see that cores per socket is set to 6 -- which is meaningless. Setting CPUs to 12 and cpu_cores to 6 gives me what I wanted. So the wording I propose is ``` - `CPUs` (int32) - Number of CPU cores. ``` --- .../builder/vsphere/common/HardwareConfig-not-required.mdx | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/website/pages/partials/builder/vsphere/common/HardwareConfig-not-required.mdx b/website/pages/partials/builder/vsphere/common/HardwareConfig-not-required.mdx index 1d1ae824f..ccc4f5e90 100644 --- a/website/pages/partials/builder/vsphere/common/HardwareConfig-not-required.mdx +++ b/website/pages/partials/builder/vsphere/common/HardwareConfig-not-required.mdx @@ -1,6 +1,6 @@ -- `CPUs` (int32) - Number of CPU sockets. +- `CPUs` (int32) - Number of CPU cores. - `cpu_cores` (int32) - Number of CPU cores per socket.