4 people found this helpful
welcome to the forums!
ESXi 6.5 includes a new native driver (vmw_ahci) for SATA AHCI controllers, but that introduces performance problems with a lot of controllers and/or disks.
Try to disable the native driver and revert to the older sata-ahci driver by running
esxcli system module
in an ESXi shell. Reboot the host to make the change effective.
This fixed it for me.
Was experiencing Latency of > 1000ms and Write Speed of 1Mbps on my M.2 SSD (Transcend 2260). Motherboard is a H110T/CSM.
Thanks for the advice.
I was also having this issue, after 3 days trying to troubleshoot found this solution on a blog post.
One issue I still have is that my 4 port Syba PCIe controller card now vanishes after disabling vmw_ahci and I am restricted to using the SATA ports on the motherboard. Is there also a workaround for this?
Thanks peetz, you saved me: I spent hours trying to determine why my 1TB Crucial MX300 M.2 2280 SSD had such abysmal performance (updating BIOS on my skull canyon, updating ESXi, etc...), and now, thanks to your post, I'm getting ~500MB/s read write.
Does this or something like it apply to ESXi 5.5 ?
I have an IBM X3550M5 and boot ESXi off an internal SD card.
The ESXi was installed from the latest download of 5.5 (U3?)
There is a single SSD drive for VMware View desktops -
But actions like clone to replica take well more than the 90-minute limit for a simple Win7 VM.
Even creating the clone files (not replica) for View desktops was impossible.
Trying to migrate a 36GB Win2012R2 Terminal server to the SSD is about 50% done after 3 hours.
The SSD is unusable...
What is the permanent fix for this issue, should we expect a corrected native driver from VMware, or will this require a firmware upgrade on the part of the drive vendors?
I can confirm that this works for me to increase SSD access speed on my Intel NUC (BOXNUC7I7BNH).
This was my problem as well.
WARNING: Doing this at least for me erases all the VMs on the aforementioned drive. Migrate as needed.
Please tell the noob, does this problem affect ESXi 6.7? And how can I check, does it affect my system?
And what will happen with my ESXi, installed on one of the SSD's?