So, I'm going to write a quick info about ESXis most famous oem.tgz.
\nThe oem.tgz is an file supplied by two sources:
\na) the \"install\" oem.tgz which does sit in the root of your install medium (like pxe tftpboot, or cdrom root)
\nthis is ONLY used DURING the installation
\nb) the \"installed\" oem.tgz which does sit in the file install.tgz
\nthis file gets copied during the installation and is therefore active AFTER the installation.
\ndetailed path is in
\nusr\\lib\\vmware\\installer\\Core\\VMware-VMvisor-big-3.5.0_Update_4-153875.i386.dd.bz2
\nunziped to VMware-VMvisor-big-3.5.0_Update_4-153875.i386.dd
\nand there in Partition 5 the oem.tgz
\n(AccessData FTK Imager Lite to access)<\/p>\n
Do you want to change the oem.tgz of an running ESXi System?
\nJust enable SSH, use Winscp and copy your oem.tgz to the folder \/bootbank and replace the old, empty oem.tgz<\/p>\n
The oem.tgz enables you to change the way the installation works.
\nYou can for example add drivers, or add Vendor\/Device Codes to the driver table<\/p>\n
Mostly used:
\n- add Vendor \/ Device code:
\n\/etc\/vmware\/simple.map<\/p>\n
- driver
\n\/mod<\/p>\n
Look up driver in ESXi:
\nlspci -v<\/p>\n
Watch which device does load which driver:
\nlspci -p<\/p>\n
Is an HDD recognized?
\nfdisk -l<\/p>\n
Just some quick infos<\/p>\n