You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
vmware-iso builder appears to be incorrectly dividing the cpus option value by the cores / cpuid.coresPerSocket option value.
Reproduction Steps
Create a template which uses the vmware-iso builder.
Set cpus option to 1.
Set cores option to 2.
Inititate Packer build.
In VMware Workstation, open the VM settings pane for the Packer VM and observe under 'Processors' that the number of processors / CPU sockets is Invalid: 0.5 (expect 1).
Same behaviour observed when cpus set to 2, cores set to 2. VMware shows number of processors as 1 (expect 2).
Same behaviour when using cpuid.coresPerSocket option under vmx_data.
I'm going to lock this issue because it has been closed for 30 days ⏳. This helps our maintainers find and focus on the active issues.
If you have found a problem that seems similar to this, please open a new issue and complete the issue template so we can capture all the details necessary to investigate further.
Overview of the Issue
vmware-iso
builder appears to be incorrectly dividing thecpus
option value by thecores
/cpuid.coresPerSocket
option value.Reproduction Steps
vmware-iso
builder.cpus
option to1
.cores
option to2
.Invalid: 0.5
(expect1
).Same behaviour observed when
cpus
set to2
,cores
set to2
. VMware shows number of processors as1
(expect2
).Same behaviour when using
cpuid.coresPerSocket
option undervmx_data
.Packer version
Packer v1.7.4
Simplified Packer Buildfile
Operating system and Environment details
Windows 10 20H2 (Build 19042.1165)
VMware Workstation Pro 16.1.2 (Build 17966106)
The text was updated successfully, but these errors were encountered: