![]() ![]() Let's set MaxVcpusPerClusterPct to 0 so we are saying to allow 0 : 1 vCPU / pCPU ratio. Now let's do some test to understand real behavior. See different behavior in screenshots belowĦ.5 U1c (build 7119157) vSphere Web Client (Flash/Flex) sets MaxVcpusPerClusterPctĦ.5 U1c (build 7119157) vSphere Client (HTML5) sets MaxVCPUsPerCore Therefore, it is good to know what you would like to achieve and double check DRS Advanced Options. However, in vSphere Client (HTML5) it sets MaxVCPUsPerCore so it is per ESXi host. If I set "CPU Over-Commitment" in vSphere Web Client (Flash/Flex) it sets MaxVcpusPerClusterPct so it is the setting per the whole vSphere Cluster. In my lab, I have VCSA 6.5 U1c (build 7119157) so I did some tests. It is good to know how GUI setting of " CPU Over-Commitment" is mapped to DRS cluster advanced options. It is worth to mention a little bit tricky setting of these additional options via GUI. However, it is good to know that there are two different advanced DRS options (configuration parameters) how to specify vCPU:pCPU ratio and each setting behaves differently. It limits the number of vCPUs per pCPU in particular DRS cluster. VSphere 6.5 DRS has introduced additional option to set maximum CPU over-commitment. Some time ago I have blogged how to achieve it with PowerCLI and LogInsight - ESXi host vCPU/pCPU reporting via PowerCLI to LogInsight. Before vSphere 6.5 we have to monitor it externally by vROps or some other monitoring tool. ![]()
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |