Bug #10873
open
"cores per socket" field should be disabled for Virtual H/W Version 10 when creating VMware VM
Description
VMware has removed the "Cores per socket" configuration setting for Hardware version 10. Please grey out or remove the "Cores per socket" field when selecting Virtual H/W Version of 10.
Updated by Marek Hulán almost 9 years ago
- Subject changed from Virtual Machine creation: "cores per socket" field should be disabled for Virtual H/W Version 10 to "cores per socket" field should be disabled for Virtual H/W Version 10 when creating VMware VM
- Category set to Compute resources - VMware
Updated by Anonymous over 8 years ago
As we don't set the h/w version by default and just pass all the args to fog, I think it's time to remove the "cores per socket" field alltogether, as we have no possibility to check all the way down to the actual ESX server if the Compute Resource would accept it.
Updated by Chris Pisano over 8 years ago
If the "Cores per socket" field is removed will the CPUs field count increase from 8? In VMware I think it goes all the way up to 32 and with the cores per socket option disappearing I can see a need to be able to have more than 8 CPUs.
Updated by Anonymous about 8 years ago
- Assignee set to Timo Goebel
Timo, could you have a look onto this one?
Updated by Timo Goebel about 8 years ago
Michael Moll wrote:
Timo, could you have a look onto this one?
Sure, will do.
Updated by Anonymous about 8 years ago
- Related to Bug #14038: Selecting multiple cores per socket not working against vmware provider (image cloning) added
Updated by Anonymous almost 8 years ago
- Related to Bug #7177: Unable to create a new host against a vSphere 5.1.0 cluster. - 'InvalidProperty: ' added