I opened a ticket about this and vmware's canned answer is that there is no officially supported method to disable vmkernel modules on boot and they cannot guarantee that the removal of the VMFS2 vmkernel module from the boot process will not result in issues.
The reason being, the solution involving commenting out a line neglected to address this part of the script (line 315):
\# Check to see if we're doing the first boot after an upgrade,
\# and perform necessary post-boot upgrade tasks. At this time
\# that means upgrading multipathing config and cleaning up
\# old config files.
\#
\# Note that vmfs2 must be loaded in order to get the required
\# information, so this must be called after the late vmkernel config.
\#
check_for_upgrade() {
if \[ -f /etc/vmware/hwconfig ]; then
action " Upgrading SCSI Path config" esxcfg-upgrade -o
action " Loading upgraded SCSI Paths" /usr/sbin/esxcfg-mpath -r
fi
}
I don't know if this just applies to upgrades such as from 3.0.1 -> 3.0.2 or any patch installs as well. Although the solution works, seems to be too risky if further down the line (when you have forgotten about this change), you do an upgrade and don't get the additional actions above.
For this reason, I can only recommend the solution suggested by rubensluque and Mike_Laverick.
