We have decided to delete all accounts on the site because the way we have collected the data to create your account did not comply with the General Data Protection Regulation (GDPR) law. This means that the existing comments and bugs will be anonymized.

We have updated our site, so please use the sign up page to create a new account on our website. The old account cannot be reinstated, so your old comments or bugs will have to remain anonymous.

We apologize for any inconvenience!


This fling has been deprecated.

VMware vCenter has provided sophisticated resource management controls (to set resource reservations, limits, shares, etc.) for virtual machines since vCenter 2.0. However, we have noticed that not everyone uses these controls due to confusion about how these features can affect other virtual machines in the resource pool. For instance, what happens when you increase the CPU size of a VM? How does that affect the other VMs in the same cluster?

This Fling attempts to make this easier by providing resource management recommendations based on inventory dumps of the existing environment. It compares the current resource demands of a VM and suggests changes to the resource allocation settings to achieve the performance you are looking for. It will also let you know how it impacts the other VMs.

For more details, please see the How to Run file or this blog post by Frank Denneman, titled "There is a new fling in town: DRMdiagnose".

This fling has been deprecated.

It is best to run it on the same OS type as vCenter - a recent 64-bit version of windows for vCenter windows and a recent 64-bit version of Linux for the VCVA. This has been tested on Windows 2008 64-bit, ubuntu 11.10 (oneric) and CentOS release 6.2 (Final), and the tar files have been tested for Red Hat Enterprise Linux.

This fling has been deprecated.

How to Run has instructions for each tar and also how to diagnose the sample pre-packaged drmdumps.

To get diagnostic recommendations, simply  get the tar for the vSphere/VC version for the drmdump. Follow the steps/instructions mentioned in the HowToRun.txt for that particular tar, replacing the drmdump with your version of dump file.

Additional instructions can be found in the README file located within the zip file.


Unzip the download and run "drmdiagnose.exe" through the command-line.


Unzip the download and run "run-drmdiagnose.sh" through a terminal.

Usage drmdiagnose <dump_file_name> [options]:
  -h [ --help ]           this help message
  -a [ --auto ]           Auto mode  - DrmDiagnose will pick top distressed VM
                          NOTE: -v, -m, -c options and -a option are mutually 
  -v [ --vmid ] arg       VM ID to adjust
  -m [ --mem ] arg        required memory entitlement
  -c [ --cpu ] arg        required CPU entitlement
  -s [ --static ]         adjust static entitlement. default is dynamic
  -d [ --disallowed ] arg disallowed actions string

                           possible disallowed actions are :
                                l increase limit
                                s increase size
                                h increase shares
                                r increase resevarion
                                o decrease others resevarion
                                c increase resource pool capacity
                                t decrease migration threshold
This fling has been deprecated.

The binary tars are created to diagnose Dumps using DrmDiagnose utility. These tar files have self-sufficient directory structures and shell scripts to run the utility.

This change comprises of following files:

  • vsphere51.tar
  • vc55u3.tar
  • vsphere60.tar
This fling has been deprecated. New comments are disabled.
This fling has been deprecated. New bug reports are disabled.