A few notes to my configuration in advance: system is 6.5.0 Update 1 (Build 5969303) vSphere host system installed on HP MicroSD STORAGE is a RAID-6 volume on HPE P222 controller STORAGE c...
See more...
A few notes to my configuration in advance: system is 6.5.0 Update 1 (Build 5969303) vSphere host system installed on HP MicroSD STORAGE is a RAID-6 volume on HPE P222 controller STORAGE contains VMs SWAP is a single WD RED 2,5 drive on HP smart array B120i each volume configuration is done via /vmfs/volumes/<UUID of drive/volume> due to MicroSD installation scratch folder (.locker) is default located on STORAGE (SWAP was installed subsequent) Default install of vSphere produces drive access even if no VM is running resulting in a harddisk click-clack access noise every 2-3 seconds that drives me insane :smileycool: (host machine is a HPE Proliant Microserver Gen8 located besides my desk). As written before I located scratch folder to self-generated folder on SWAP/.locker by editing <ScratchConfig.ConfiguredScratchLocation> path. The harddisk click-clack noise every 2-3 second is gone until one VM is started. Looking in the VM folder on STORAGE of a VM that has been started shows two .vswp files that are created as soon as the VM boots up. Adding sched.swap.dir in the advanced VM configuration parameters causes that at least one of the two .vdsk files is created on SWAP. But harddisk access click-clack noise remains… So, finally to answer your question "Does it work when you force the host using this parameter? Nice and quiet-ish now?" No, unfortunately not…:smileycry:
