Code of Conduct

• I have read and agree to the project's Code of Conduct.
• Vote on this issue by adding a 👍 reaction to the original issue initial description to help the maintainers prioritize.
• Do not leave "+1" or other comments that do not add relevant information or questions.
• If you are interested in working on this issue or have submitted a pull request, please leave a comment.

Description

When I create a vsphere_virtual_machine, the num_cores_per_socket value defaults to 1, which is not the same as the GUI default of "Assigned at power on". Stopping the VM, setting the value to automatic by hand, works. But the next time I terraform apply the value is reset.

Use Case(s)

vSphere 8 documentation added this topology feature for performance reasons, but it is not available via automation at this time. Supporting "Assigned at power on" will optimize performance and utilization

Potential Configuration

resource "vsphere_virtual_machine" "vm01" {
  name                 = each.value.vmname
  num_cpus             = var.num_cores
  num_cores_per_socket = 0
}

References

https://www.vmware.com/docs/vsphere8-virtual-topology-perf