My feedback is that this asset has gotten many, many hits from my customers as well as colleagues and team in our efforts to build Master images for projects and labs.
I'd be interested to see how many hits this gets, 'Daily'
Top marks for sure!
Maybe add something about why certain choices are made, I know when I refer people to it and they ask questions there are some choices I don't know how to explain every time. Its probably general image management best practices but I keep getting asked why are we generalizing when it works fine when you don't.
9-12.6K hits per month in the last 12 months and we had somewhere around 20 remarks/questions on the guide. A large portion of those are praises, and we had 9 people that couldn’t get it working.
7 of those deviated from the guide (and had no issues when following it to the letter) 2 didn’t respond to follow up questions. The others where textual changes which we adjusted.
Which choices would you like to see explained?
The VM Tools section is either new, or I totally overlooked it.
Does installing tools without those custom options have any known performance impact?
It was in there before, but from the UI. The video driver is done to ease updates (no sequence dependency between Horizon Agent and VMware Tools), the other removed features came from earlier recommendation, but I haven’t measured it.
That makes a lot of sense, my other question was about updated VMtools as I saw later in this documentation where they just update with no regard for sequence! Back to the base image for those changes.
Why are is it suggested to export the VM, I'm assuming its to recover the space savings. Why not instead run the vmktools command to recover the space like in the below kb. I'm assuming its because its easier, but I'm seeing people here and there have issues with the export and import of ovf files through the webclient like in Re: Invalid response code: 500 so I'm wondering if the vmkfstools command is better.
- Ensure that the disk has no Snapshots.
- In a Windows virtual machine, run the
SDeletecommand (or a tool with similar functionality) to zero out all unused space. The syntax for the SDelete command is SDelete -z driveletter. If you use
SDelete, ensure that you use version 1.6 or later.
Note: Zeroing all unused blocks inflates the disk to its full size as if it was an eagerzeroed disk. Ensure that there is sufficient space on the datastore to allow the disk to grow to its full size. For more information, see Determining if a VMDK is zeroedthick or eagerzeroedthick (1011170).
- Shut down the virtual machine or temporarily remove the virtual disk from the virtual machine to ensure that it is not in use.
- Erase all unused blocks by running the command:
vmkfstools -K /path/to/disk-name.vmdk
1 person found this helpful
Both methods will work to reclaim unused space. Using Export to OVF also helps if you need to copy and use the VM in a different vCenter environment.
vmkfstools only works on VMFS storage, plus not everyone has SSH access.