Semi-Open - Beyerdynamic DT880-600 - Fostex T50RP - *AKG K240 studioĬlosed-Back - Rode NTH-100 - Meze 99 Neo - AKG K361-BT - Blue Microphones Lola - * Beyerdynamic DT770-80 - *Meze 99 Noir - * Blon BL-B60 - *Hifiman R7dx Compatible: IO Device 'MegaRAID SAS GEN2 Controller (PCIID:1000:79:1000:9263)' is compatible for ESX 6.7.Open-Back - Sennheiser 6xx - Focal Elex - Phillips Fidelio X3 - Harmonicdyne Zeus - Beyerdynamic DT1990 - * HiFi-man HE400i (2017) - *Phillips shp9500 - *SoundMAGIC HP200 Vmhba1 - 0000:01:00.0: IO Device 'MegaRAID SAS GEN2 Controller' from Avago (LSI / Symbios Logic) Compatible: IO Device 'Cougar Point 6 port SATA AHCI Controller (PCIID:8086:1C02:8086:7270)' is compatible for ESX 6.7.0 Vmhba0 - 0000:00:1f.2: IO Device 'Cougar Point 6 port SATA AHCI Controller' from Intel Corporation It complained about my 10G nics possibly not being supported in 6.7 (but they still work), but the storage both reported compatible (the datastore works, but no hardware monitoring). Strangely, I found a Fling for ESXi compatibility checking. Going from 6.5->6.7 just makes me look at the other hypervisor solutions in the future.Įdit: Just found an updated document () showing 6.5 U2 as being latest for LSI provider. Going to v7.0, I'd expect to drop legacy stuff. I really, really hate it when hardware and feature deprecation happens in a point release like this. So now I'll have to reinstall ESXi 6.5 to get around this issue.
Unfortunately, when I discovered this and found the instructions to rollback to previous version, both bootbanks say they are 6.7 and cannot be downgraded or reverted. Search your raid card again, and see it probably says 6.7 supported.
Search "LSIprovider" on the compatibility check page to see the 6.5 U2. My raid card reports supporting 6.7, so you think all good, right? Nope, not if the LSI provider functionality is no longer supported. Messed around with different versions of the SMIS and lsi provider files, but ultimately I believe the issue is that the LSI Provider support has ended at 6.5 U2.
I just ran into this problem after upgrading from 6.5 to 6.7.
0 kommentar(er)
