Prior to vSphere 5, it was not trivial to identify the particular disk format for a given virtual machine’s disk. Using the vSphere Client, you would see a virtual machine’s disk be displayed as either thin or thick. The problem with this is that the “thick” format can be either:
- zeroedthick – A thick disk has all space allocated at creation time and the space is zeroed on demand as the space is used
- eagerzeroedthick – An eager zeroed thick disk has all space allocated and wiped clean of any previous contents on the physical media at creation time. Such disks may take longer time during creation compared to other disk formats.
Users would not be able to distinguish the exact type using the vSphere Client or the vSphere 4 APIs. With the release of vSphere 4, VMware did introduce a new property in the vSphere 4 API called eagerlyScrub which was supposed to help identify whether a virtual disk was allocated as an eagerzeroedthick disk. Unfortunately there may have been a bug with the property as it never gets modified whether a disk is created as zeroedthick or eagerzeroedthick.
The only method that I was aware of to truly figuring out the disk format would be to manually parse the virtual machine’s vmware.log file to identify the disk type which I wrote a script for in 2009.
During the vSphere 5 beta, I had noticed the vSphere Client UI now properly displays all three virtual machine disk format: zeroedthick (displayed as flat), thin and eagerzeroedthick (displayed as thick).
Seeing that VMware now displays the three different formats, I wanted to see if it was possible to extract this using the vSphere 5 APIs and not have to rely on the hack of reading the vmware.log files. It turns out that the eagerlyScrub property is now functioning properly when a VMDK is provisioned or has been inflated/converted to the eagerzeroedthick format. I wrote a simple vSphere SDK for Perl script called getVMDiskFormat.pl which allows you to extract the disk formats of all virtual machines connecting to either vCenter or directly to an ESX(i) host.
The script allows for two types of output: console (directly on the console) or csv (creates .csv file)
If you select csv output, by default it will be stored in a file called “vmDiskFormat.csv”. You also have the option of specifying the filename by using the –filename flag and providing a name of your choosing.
You can then load the csv file into excel and easily sort through the various disk format types.
All this is already included in the latest version of the VMware vSphere Health Check Report 5.0 if you want a centralize report that includes virtual machine disk format.