What happens if we add the PCI ID of the Dell H700 to the list of IDs supported by the lsi_mr3 driver? After all, if the VCG is anything to go by, the lsi_mr3 driver used to support LSI 2108 based cards… These files are driver.map and driver.ids. SubDevice ID (SDID) = 1f18 (Dell PERC H700 Modular)Īfter lots and lots of reading, a bit more reading and a bit of testing in a VM, it looks like VMware drivers potentially reference PCI hardware IDs located in two files for each driver present in the O/S. SubDevice ID (SDID) = 1f17 (Dell PERC H700 Integrated) SubDevice ID (SDID) = 1f16 (Dell PERC H700 Adapter) Taking the H700 for example, we can see from the VMware VCG (after pulling all the entries together): Many modern operating systems use PCI card hardware identifiers (aka PCI IDs) to identify and to ensure that the correct driver is loaded for the hardware present. Wait, when did the VMKlinux Driver Stack Deprecation start? ESXi5.5! Hmmm, so back in the ESXi 5.5 days, LSI 2108 based cards used the native lsi_mr3 driver…!?! Check out the above VCG entry for the LSI MegaRAID SAS 9260-8i for yourself HERE I even found the LSI 2015 Product Guide that contains something like thirteen LSI 2108 chipset based cards if you fancy spending a couple of hours on VMware Compatibility Guide!! Clutching at StrawsĬhecking the VCG with the first five above, straight away I noticed something:
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |