SophiaSupport
Your entitlement on PowerCLI with a free version of ESXi will be limited to read-only operations (most Get- cmdlets). You could be encountering a bug, what version of PowerCLI are you using?
For your first issue you can use a script very similar to the one for a VM:
$result = @()
$vmhosts = Get-view -ViewType hostSystem
foreach ($vmh in $vmhosts) {
$obj = new-object psobject
$obj | Add-Member -MemberType NoteProperty -Name name -Value $vmh.Name
$obj | Add-Member -MemberType NoteProperty -Name CPUType -Value $vmh.hardware.CPUPkg[0].Description
$obj | Add-Member -MemberType NoteProperty -Name NumPhysCPU -Value $vmh.hardware.cpuinfo.NumCpuPackages
$obj | Add-Member -MemberType NoteProperty -Name NumPhysCores -Value $vmh.hardware.cpuinfo.NumCPUCores
$obj | Add-Member -MemberType NoteProperty -Name NumThreads -Value $vmh.hardware.cpuinfo.NumCPUThreads
$obj | Add-Member -MemberType NoteProperty -Name Memory -Value ([Math]::Round($vmh.hardware.MemorySize/1GB)).ToString()
$result += $obj
}
$result
For your second question, bear in mind that with regards to a virtual machine, the total virtual cores and virtual CPUs are the same thing. The line "$vm.config.hardware.NumCPU/$vm.config.hardware.NumCoresPerSocket" was in response to a specific need for the number of sockets the vCPUs were divided up into which is important for some OS licensing purposes. For instance you can give a guest running Windows 2008 R2 Standard 16 vcpu's but you must divide that up into some number of cores per socket, if left at the default of 1 core per socket, Windows will only use 4 vcpu due to licensing of the OS, but divided up, the OS will use all cores assigned.
For the additional properties on the VMs. Modify the script as follows and you should be good to go:
$result = @()
$vms = Get-view -ViewType VirtualMachine
foreach ($vm in $vms) {
$obj = new-object psobject
$obj | Add-Member -MemberType NoteProperty -Name name -Value $vm.Name
$obj | Add-Member -MemberType NoteProperty -Name vCPUs -Value $vm.config.hardware.NumCPU
$obj | Add-Member -MemberType NoteProperty -Name vSockets -Value ($vm.config.hardware.NumCPU/$vm.config.hardware.NumCoresPerSocket)
$obj | Add-Member -MemberType NoteProperty -Name Persocket -Value $vm.config.hardware.NumCoresPerSocket
$obj | Add-Member -MemberType NoteProperty -Name Memory -Value $vm.config.hardware.MemoryMB
$obj | Add-Member -MemberType NoteProperty -Name OS -Value $vm.config.GuestFullName
$result += $obj
}
$result
Getting the parameters is a bit more difficult, but definitely worth exploring. If you've already gotten PowerShell ISE set up to run powercli commands, then find an add-on that allows you to explore variables. Alternatively you can do this from the command prompt. For instance, from above typing in $vms | Get-member after running the script will show you the methods and properties (and their types) that were returned, but only the top level (Objects are hierarchical and some properties contain other objects with their own properties) you'll see some that have a property type of vmware.vim.something (vmware.vim.VimClient, Vmware.vim.VirtualMachineConfigInformation, etc). These you'll have to dig into, for instance $vms.config | get-member will return methods and properties on the virtual machine config, again with some properties that are objects as well with their own properties.
Cheers!
