In my scenario, I am running the Virtual Machine locally on DAS storage, therefore the TRIMP/UNMAP feature won’t work automatically. So you’ll need to check with the storage vendor to know if this will work or not. Why I said theoretically because the hardware needs to specifically support this. So in the scenario above, the disk would initially expand from 15GB to 45GB but when the large files are deleted inside the guest, this would theoretically (automatically) be able to drop back down the VHDX file to ~15GB size. The VM’s VHD or VHDX file tunnels the UNMAP request to the class driver stack of the Windows Hyper-V host. When a large file is deleted from the file system of a VM guest operating system, the guest operating system sends a file delete request to the virtual machine’s virtual hard disk file. In Windows Server 2012 and above, Microsoft introduced the TRIM/UNMAP feature. ![]() However, if we look at the host, we can see that this VM is occupying 45GB of disk space, this is odd
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |