VMware Template and CPU Cores

I'm running Foreman 1.9.3 and it looks like Foreman is fine when changing
the number of CPUs, however the Cores per Socket seem to always get set to
1 regardless of what I set on the virtual machine tab.

Bug #10873: "cores per socket" field should be disabled for Virtual H/W Version 10 when creating VMware VM - Foreman may be related.

··· On 04/01/16 21:38, Christopher Pisano wrote: > I'm running Foreman 1.9.3 and it looks like Foreman is fine when > changing the number of CPUs, however the Cores per Socket seem to always > get set to 1 regardless of what I set on the virtual machine tab.


Dominic Cleal
dominic@cleal.org

Dominic, I think I'm using Virtual H/W version 8. But I was also unaware
that VMware removed the cores per socket option in Virtual H/W version 10.
I think I might rethink how I'm setting my resources.

··· On Tuesday, January 5, 2016 at 3:05:39 AM UTC-5, Dominic Cleal wrote: > > On 04/01/16 21:38, Christopher Pisano wrote: > > I'm running Foreman 1.9.3 and it looks like Foreman is fine when > > changing the number of CPUs, however the Cores per Socket seem to always > > get set to 1 regardless of what I set on the virtual machine tab. > > http://projects.theforeman.org/issues/10873 may be related. > > -- > Dominic Cleal > dom...@cleal.org >

I have been doing a lot of deleting and creating of VM's on VMware and I thing the fog could do with a few updates, doesn't seam to handle multiple nic's very well. I am running foreman 1.10, ESXi 6.0u1 direct with no vcentre and also see the CPU issue too.