vSphere

Windows Server 2016 Really slow on ESXI 6.5 |VMware Communities


Here are some resolution but it’s not a VMware’s official one.

 

Windows Server 2012 or above can support In-Guest unmap and trim.

That function cause a problem with VMware’s new In-Guest unmap support.

 

This function works well under Hyper-V environment but doesn’t works well with VMware’s one.

 

01. Use a VM Hardware verwion 10 (ESXi 5.5 compatible) that doesn’t support In-Guest unmap.

      If you downgrade VM hardware version 10 you will escape from high disk usage.

      But you can’t never use In-Guest unmap function.

 

02. Use fsutil command in Windows Guest OS – Windows Server 2012 or above –

 

     In Windows command shell with administrative right then execute belows.

     These commands will disable Windows In-Guest unmap and trim on NTFS, ReFS v1, v2.

   

     — disable unmap and trim on NTFS & ReFS v1

     fsutil behavior set DisableDeleteNotify NTFS 1

 

     — disable unmap and trim on ReFS v2

     fsutil behavior set DisableDeleteNotify ReFS 1

 

     If you want to rollback to Windows unmap function execute belows

 

     fsutil behavior set DisableDeleteNotify NTFS 0

     fsutil behavior set DisableDeleteNotify ReFS 0

 

 

Plus ~

If you disable In-Guest unmap but you can unmap on VMFS with vmfstools command manually…:)

 

Best Regard,

Jaehoon Choi



Source link

 

To see the full content, share this page by clicking one of the buttons below

Related Articles

Leave a Reply