Project

General

Profile

Bug #10873

"cores per socket" field should be disabled for Virtual H/W Version 10 when creating VMware VM

Added by larry campbell almost 5 years ago. Updated almost 3 years ago.

Status:
New
Priority:
Normal
Assignee:
Category:
Compute resources - VMware
Target version:
-
Difficulty:
Triaged:
No
Bugzilla link:
Pull request:
Fixed in Releases:
Found in Releases:

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.


Related issues

Related to Foreman - Bug #14038: Selecting multiple cores per socket not working against vmware provider (image cloning)Closed2016-03-03
Related to Foreman - Bug #7177: Unable to create a new host against a vSphere 5.1.0 cluster. - 'InvalidProperty: 'New2014-08-20

History

#1 Updated by Marek Hulán almost 5 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

#2 Updated by Michael Moll over 4 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.

#3 Updated by Chris Pisano over 4 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.

#4 Updated by Michael Moll over 4 years ago

  • Assignee set to Timo Goebel

Timo, could you have a look onto this one?

#5 Updated by Timo Goebel over 4 years ago

Michael Moll wrote:

Timo, could you have a look onto this one?

Sure, will do.

#6 Updated by Michael Moll about 4 years ago

  • Related to Bug #14038: Selecting multiple cores per socket not working against vmware provider (image cloning) added

#7 Updated by Michael Moll almost 4 years ago

  • Related to Bug #7177: Unable to create a new host against a vSphere 5.1.0 cluster. - 'InvalidProperty: ' added

Also available in: Atom PDF