Hi, after of the 3.0.1 upgrade...the Qlogic driver dont load at boot. I have to load manually with vmkload_module command. How load the module at boot?
Thanks.
Can you post your /etc/vmware/esx.conf file?
We can certainly load that VMkernel module manually in one of the startup scripts, but I'd rather find out why it isn't getting made persistent in the bootup configuration.
Paul
use esxcfg-module -l to see which modules are loaded.
then use esxcfg-module -e to enable a specific module
the module is loaded, but if i reboot the server...the module dont load...and the vi client dont see the HBA's...then..load the module manually...click on "rescan" button in vi client...and all work fine.
thanks
once you have loaded the module run the esxcfg-module -l command which will show you a list
you should see the qlogic module loaded but probably showing false against enabled (i.e. enabled at boot)
now run the esxcfg-module -e to enable it at boot
the module is ENABLED and LOADED....but dont load at boot...i have to do manually.
Other solution?
thanks
ok, not sure if you can do this in your environment but use esxcfg-module -d to disable and then reenable again using -e rather than the vmkmodule command and see if this corrects it
Try:
esxcfg-boot -p -b
Then reboot the system and see if the module loads on bootup.
Paul
I tried esxcfg-boot -p -b but the module dont load at boot.
Appear as "false" in the "Loaded" column. I have to load manually with vmkload_mod qla2300_707
Any other solutions? in the init.d can put something?... because if i reboot the ESX the qla modules dissappear
thanks
Can you post your /etc/vmware/esx.conf file?
We can certainly load that VMkernel module manually in one of the startup scripts, but I'd rather find out why it isn't getting made persistent in the bootup configuration.
Paul
how i can load the module manually in the init scripts?
i deleted the line "options" in the esx.conf and the module loaded fine
The bad line was "options=qla2x_lun_queue_depth=64"
Thanks
dd
Well done.