Invalid CPU settings are not prevented

[perlfisch]

When editing the CPU settings of a VM, both the cores attached and the vCPUs actually usable can be configured independently of each other. The Web UI prevents setting the vCPUs to a greater value than cores * sockets, but seemingly neither the API nor this provider does so.

For example a configuration like the following deploys fine, but actually results in a broken, unbootable VM, which won't even tell you what the problem is:

resource "proxmox_vm_qemu" "this" {

  cores   = 24
  vcpus   = 32

Instead, a check in the provider should prevent configurations in which vcpus is greater than sockets * cores

[Tinyblargon]

@perlfisch Which version of the provider are you using?

I am a little confused as this situation gets explicitly tested upstream
https://github.com/Telmate/proxmox-api-go/blob/master/proxmox%2Fconfig_qemu_cpu_test.go#L204-L209