CPU Topology - Assigned at power on

[terencewklau]

Hi,

In vSphere 8, using the GUI to create a VM defaults to "Assigned at power on" for CPU Topology.

I've been using powercli's (version 13.1) New-VM with -NumCpu but this configures the VM with "Manual" for CPU Topology.  Using the same integer with -NumCpu and -CoresPerSocket still creates the VM as "Manual" for CPU Topology.

Is there any option with powercli to create the VM with "Assigned at power on" for CPU Topology?

Thanks.

 

 

[LucD]

Afaik, not with the current version

[terencewklau]

Bummer ... but thanks for the update.

[LucD]

You can't do it with the New-VM cmdlet, but you can change the setting after the VM has been created.

$vmName = 'MyVM'

$vm = Get-VM -Name $vmName
$spec = New-Object VMware.Vim.VirtualMachineConfigSpec
$spec.NumCoresPerSocket = 0
$vm.ExtensionData.ReConfigVM($spec)

------------------------------

Blog: lucd.info  Twitter: @LucD22  Co-author PowerCLI Reference

------------------------------

[mpac]

Keep in mind that you only can apply changes of the cpu topology in powered off state.  I am not sure if a script is useful in this case.

-------------------------------------------

[SagiKr]

Hi, 
can you determine from a vm with powercli whether the CPU topology is "Assigned at power on" or not?

[LucD]

Yes, if the AutoCoresPerSocket property is set to $true

Get-VM |
Select Name,
    @{N='autoCoresPerSocket';E={$_.ExtensionData.Config.Hardware.AutoCoresPerSocket}}

------------------------------

Blog: lucd.info  Twitter: @LucD22  Co-author PowerCLI Reference

------------------------------

[SagiKr]

Thanks for the quick response.

[Honor Chief]

Hey there!

It seems like you're running into a quirk with PowerCLI when setting the CPU topology. Unfortunately, as of now, PowerCLI defaults to "Manual" for CPU topology when specifying CPU options like -NumCpu and -CoresPerSocket. There isn't a built-in parameter to force "Assigned at power on" during VM creation via PowerCLI.

A possible workaround is to create the VM first, then use the Set-VM cmdlet after the fact to modify the topology settings or use the vSphere Client GUI to adjust it manually post-creation. Hopefully, a future version of PowerCLI might address this gap!

Cheers!

[LucD]

Did you even read the replies in this thread?

------------------------------

Blog: lucd.info  Twitter: @LucD22  Co-author PowerCLI Reference

------------------------------