vSphere VM vCPU to ESXi host CPU core allocation – Curated Article

December 15th, 2014 by

Guest Contributor VCDX56-Magnus AnderssonThis article is being curated in about:virtualization from guest author Magnus Andersson, published on his blog VCDX56.com:

There has been quite a lot of discussion regarding resource utilization and resource allocation in vSphere environments lately. There are a lot of tools around doing analysis (some better than others) of your environment and gives suggestions if you need to e.g.:

  • Add more resources (CPU, RAM, Disk, Network) to your vSphere cluster.
  • Down size one or more virtual machines (VMs)
  • Give one or more VMs more resources.

In some products you can also schedule a potential VM reconfiguration task which can be very useful if you are allowed to perform such tasks automatically.

Well this post was suppose to cover the VM vCPU to ESXi host CPU core allocation and since i receive questions about that topic at least every other week so i thought it was time to create a blog post about my experiences in this topic. The below figures are actual figures i have collected over the years from my customers. …

Read the rest of the article – including the script that Magnus created to generate the vSphere VM vCPU to ESXi host core allocation report on a daily, weekly, monthly, or yearly basis – on his blog at http://vcdx56.com/2014/06/01/vsphere-vm-vcpu-to-esxi-host-cpu-core-allocation/

One response to “vSphere VM vCPU to ESXi host CPU core allocation – Curated Article

  1. An anonymous poestr stated that this “did not work” and gave no details to go with that. I assure you, this *does* work. I have ESXi 4.1 VMs all running with these changes in effect and I can copy-and-paste just fine between them (where I could not before making these changes). If you have made the changes described here and it “does not work”, can you give more details? Perhaps there is another conflicting setting or perhaps you did not reboot a VM or something?

Leave a Reply

Your email address will not be published. Required fields are marked *