Published by Ryan Mangan
Ryan Mangan works as the CTO at Systech IT Solutions. Systech Specialise in application delivery, and desktop virtualization specialist company based in the UK, where he focuses on end-user computing and emerging technologies. Ryan is an end-user computing specialist with a great passion for virtualization. A speaker and presenter, he has helped customers and technical communities with end-user computing solutions, ranging from small to global 30,000-user deployments.
He is the owner and author of ryanmangansitblog.com, where he posts articles about remote desktop services, VMware, Microsoft Azure, Parallels RAS, KEMP, and other products and technologies.
Ryan has been awarded VMware vExpert since 2014, has been a member of the NetApp United program since 2017, Parallels VIPP, and was awarded Technical Person of the Year in 2017 by KEMP Technologies.
Subject Matter Expert with Remote Desktop Services and Windows Virtual Desktop.
Ryan also wrote the Microsoft Ebook "Quickstart Guide to Windows Virtual Desktop"
View all posts by Ryan Mangan
Does the VM have to be powered off for this to work? I tried this with a running vm and got a lock error.
Hi, yes you would need to shutdown the VM to convert a VMDK.
Good Article with snapshots, very informative.
Hi, thx for this good instruction. Process is done and looking fine. But the disk with in the VM properties is still shown as lazy-zeroed!? Is this correct?
You will need to remove the disk from the virtual machine and then reattach.
Hi Christian,
You can check the type of VMDK by using the command “vmkfstools -D”
If the output appears similar to the following with tbz at zero, the VMDK is eagerzeroedthick. Otherwise it is zeroedthick.
I find that by starting the VM, it will re-register the VM and update the properties. You should see that the VM properties will show eager or Lazy. You can also reattach the disk to the VM as Reed mentioned.
Best Regards,
Thank you!
It showed the disk to be a lazy zeroed one. After reattaching the disk to the vm it now shows the correct format.
Best regards,
Thank you for the great article. For the benefit of anyone else viewing this article, there are a few errors. The instructions incorrectly state (last two lines):
ls vmfstools -k /vmfs/volumes/ESX01_Internal1/RDS2012/RDS2012.vmdk
Use “vmfstools -k” to convert a Lazy Zeroed disk to a Eagerly Zeroed disk.
Using the command listed here results in receiving the error “ls: vmfstools: No such file or directory”. As is correctly used in the screenshot, you should omit the “ls” and the command is “vmkfstools” and not “vmfstools”.
Dear Reed, Thank you for highlighting the Typos. This has now been altered to show “vmkfstools” as per my screenshot.
“ls” is used to list out files in the directory (List subregions), readers may use this when locating the VMDK they want to convert but its not used when running the conversion command.
Best Regards,