The Mysterious Case of Insufficient Resources: A Lesson in DRS Troubleshooting
As a seasoned IT professional, I have encountered my fair share of mysterious errors and unexpected behavior in virtualized environments. However, a recent case involving a DRS-enabled cluster left me stumped for a while. In this blog post, I will delve into the details of the issue, the troubleshooting process, and the solution that was eventually found.
The Case: Insufficient Resources? But Why?!
One day, one of my customers contacted me with an urgent request to troubleshoot an issue they were experiencing with their DRS-enabled cluster. When attempting to start a virtual machine, they were met with the generic error “Insufficient resources.” However, further checking revealed that there were plenty of resources available on all hosts in the cluster. This was puzzling, to say the least.
The usual questions that come to mind in such situations – “Is the host running out of memory?”, “Are there any resource contention issues?” – were all ruled out. The customer had already checked these and ensured that there were no obvious reasons for the error. That’s when I decided to dive into the Advanced Options of DRS, which is often overlooked but can provide valuable insights into unexpected behavior.
The Solution: A Less-Known Setting with Unintended Consequences
As I explored the Advanced Options of DRS, I stumbled upon a setting called “LimitVMsPerESXHostPercent.” This setting, which is not well-known and is often set to 0 by default, controls the maximum number of virtual machines that can be running on any given ESXi host. In this customer’s environment, the setting was still set to 0, which seemed to be causing the issue.
Removing the setting for testing purposes allowed the virtual machine to power on successfully, and DRS behavior returned to normal. It turned out that this setting had been causing unexpected side effects in the customer’s environment for quite some time!
The Takeaway: Check Those Advanced Options!
As IT professionals, we often overlook certain settings or options in our haste to troubleshoot issues. The case of LimitVMsPerESXHostPercent is a perfect example of this. It’s essential to remember that even the most obscure settings can have a significant impact on the behavior of our virtualized environments.
In conclusion, when encountering unexpected behavior in your DRS-enabled cluster, never hesitate to explore all available options and settings. You never know what hidden gem you might discover!
About the Author: Patrik Kernstock
Hello there! My name is Patrik Kernstock, and I’m a 25-year-old perfectionist born in Austria and living in Ireland, Cork. As a tech and security enthusiast, I enjoy exploring Linux, container solutions, and software offerings from Microsoft, Veeam, and VMware. When not working or troubleshooting, you can find me binge-watching series and movies or indulging in my love for Linux and open-source projects.