|
VMware ESX Server 2.1
Features | Documentation | Knowledge Base | Discussion Forums You can customize the loading of VMkernel device driver modules during bootup by editing one of the following files:
Caution: Editing these files are recommended for advanced users only. If you have any questions, be sure to contact your authorized service provider before editing these files. Caution: Do not modify the /etc/vmware/hwconfig file other than to add extra parameters, as described in this section. Instead, use the VMware Management Interface to manage your hardware. You can supply extra parameters to be passed to a driver when it is loaded during bootup. You do this by editing the file /etc/vmware/hwconfig. This file contains information about the hardware on your system, including device driver modules. As an example of passing a parameter to the Emulex device driver, first identify the bus, slot and function holding the first (or only) Emulex card. (You can find this information by looking at the Startup Profile page in the Options tab of the VMware Management Interface.) Then add a line with the format device.vmnix.6.14.0.options = "lpfc_delay_rsp_err=0" to the end of /etc/vmware/hwconfig. Here, the numbers 6.14.0 specify the bus, slot and function where the Emulex card is located. If you have more than one Emulex card, you should have only a line referencing the first card. You can completely customize the loading of modules at bootup time by editing the /etc/vmware/vmkmodule.conf file. By adding or removing entries from this file, you can add or prevent a device driver module from loading. Also, by rearranging the order of the device driver modules in this file, you can specify the order in which these modules are loaded during bootup. You can also supply extra parameters to a driver when it is loaded on bootup. Note: If you use this file to customize the loading of device driver modules, then you must manually update this file whenever you add new hardware. Consequently, we recommend using the VMware Management Interface to manage your hardware, or if you need to add extra parameters, then editing the hwconfig file as described in the previous section. The vmkmodule.conf file takes effect only if it contains a comment line containing the keyword MANUAL-CONFIG. Otherwise, the configuration is obtained automatically from the management interface. Each non-blank line that does not begin with # should contain the name of a module file, the tag to be associated with the module in the VMkernel and possibly a sharing specification (the argument specified with the -d flag above). The module file should just be the base file name, without the /usr/lib/vmware/... path. A sample vmkmodule.conf file is:
# MANUAL-CONFIG
|
