I just had a discussion about an upgrade from 3.0.x to 3.5. During that conversation the new HBA drivers that VMware uses came up. After an upgrade it seems that the queue depth settings are lost. Thinking about it I can understand why. ESX 3.5 uses different driver for most HBA’s. For instance Emulex, their driver for the LP11002 used to be the “lpfcdd_732″ and now is the “lpfc_740″. After an upgrade the new driver/module doesn’t get the options you provided with “esxcfg-module” because it was specified for that specific “old” module. This means that you have to set these options again!
You won’t be able to set the queue depths using Emulex HBAs with the lpfc_740 driver. That means you’re stuck with a default queue depth of 30 per LUN. T
This capability doesn’t work with 3.5 and Emulex cards. In fact ,it is stated in the Emulex documentation that being able to set queue depths will be available on different driver release.
Nick
okay, that’s new to me… although i hardly ever set the queuedepth for emulex cards. but that’s probably because qlogic seems to be the card that’s sold mostly in the netherlands. thanks for the additional info,
In Emulex documentation I can see the following;
“The lpfc_hba_queue_depth described in table 2 is not settable as a module parameter in this release.Emulex is targeting a subsequent release to address this issue.”
It is lpfc_hba_queue_depth, not lpfc_lun_queue_depth.
I reached here, after I failed to set LUN queue depth for ESX 3.5 with lpfc_740 driver.
I followed the methods from emulex & vmware articles.
Is there any other wat?