If you have the same controller then you can add support for it by running the following commands in an ESXi shell:Įsxcli software acceptance set -level=CommunitySupportedĮsxcli network firewall ruleset set -e true -r httpClientĮsxcli software vib install -d -n sata-xahci I was able to verify this method with the help of someone who tried to get his ASMedia ASM1062 Controller (PCI ID 1b21:0612) working with ESXi 5.5. You just need to create another map file with the PCI IDs of these devices and a reference to the ahci driver. I always thought that whenever an ESXi driver is loaded then it would detect and configure any PCI devices that it supports, but the ahci driver of ESXi 5.5 behaves differently: Even if manually loaded (with vmkload_mod ahci) it will only configure the devices that are explicitly listed with their PCI IDs in its map file ( /etc/vmware//ahci.map).īut once you realize this it is easy to add support for other SATA AHCI controllers that are not listed there.

For the NICs the problem could easily be solved by using the old ESXi 5.1 drivers with ESXi 5.5, but - until recently - I had no idea how to fix the issue for the SATA controllers. In ESXi 5.5 VMware removed driver support not only for some commodity network cards, but also for lots of SATA controllers that have never been on the HCL, but worked fine with the generic ahci driver of ESXi 5.0 and 5.1 (provided that they support and are configured for AHCI mode).

Samsung rapid mode not supported