Original Message:
Sent: Oct 10, 2024 06:33 AM
From: Honor Chief
Subject: CPU Topology - Assigned at power on
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!
Original Message:
Sent: Oct 10, 2024 06:01 AM
From: SagiKr
Subject: CPU Topology - Assigned at power on
Thanks for the quick response.
Original Message:
Sent: Oct 10, 2024 04:54 AM
From: Luc Dekens
Subject: CPU Topology - Assigned at power on
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
Original Message:
Sent: Oct 10, 2024 03:11 AM
From: SagiKr
Subject: CPU Topology - Assigned at power on
Hi,
can you determine from a vm with powercli whether the CPU topology is "Assigned at power on" or not?
Original Message:
Sent: Feb 06, 2024 01:37 AM
From: terencewklau
Subject: CPU Topology - Assigned at power on
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.