Next steps for customizing OEM.TGZ
Page 1 of 1

Author:  kaizenwerks [ Tue Sep 15, 2009 11:57 am ]
Post subject:  Next steps for customizing OEM.TGZ

I apologize ahead of time for being new to this whole thing so my questions are probably elementary. I hope someone will be able to shed some light so I can better understand how this works. Thanks!

I was able to get ftp working on ESXi 3.5 and am now trying to figure out how to survive the reboot.

I reviewed the http://www.vm-help.com/esx40i/customize ... hp#Example instructions but am not sure what to do next.

I am using IBM Blade HS21 XM hardware with the USB Flash drive it was shipped with.

From the "http://www.vm-help.com/esx40i" I'm assuming that I'm referring to the "Modifyng oem.tgz when booting from a USB flash drive" section since I am using a USB Flash drive that is supported by IBM. It then references an example in the "Instructions to modify oem.tgz if you're booting from a USB flash drive to add support for an unrecognized device" section.

If I follow that, then I need to get the PCI ids.

I run the lspci command and got:
~ # lspci
00:00.00 Bridge: Intel Corporation
00:02.00 Bridge: Intel Corporation
00:03.00 Bridge: Intel Corporation
00:04.00 Bridge: Intel Corporation
00:05.00 Bridge: Intel Corporation
00:06.00 Bridge: Intel Corporation
00:07.00 Bridge: Intel Corporation
00:08.00 Generic system peripheral: Intel Corporation I/OAT DMA controller (1a38)
00:16.00 Bridge: Intel Corporation
00:16.01 Bridge: Intel Corporation
00:16.02 Bridge: Intel Corporation
00:17.00 Bridge: Intel Corporation
00:19.00 Bridge: Intel Corporation
00:21.00 Bridge: Intel Corporation
00:22.00 Bridge: Intel Corporation
00:28.00 Bridge: Intel Corporation
00:29.00 Serial bus controller: Intel Corporation
00:29.01 Serial bus controller: Intel Corporation
00:29.02 Serial bus controller: Intel Corporation
00:29.07 Serial bus controller: Intel Corporation
00:30.00 Bridge: Intel Corporation 82801BA/CA/DB/EB PCI Bridge
00:31.00 Bridge: Intel Corporation
00:31.02 Mass storage controller: Intel Corporation 31xESB/632xESB/3100 Chipset SATA Storage Controller IDE [vmhba0]
01:01.00 Display controller: ATI Technologies Inc
02:00.00 Mass storage controller: LSI Logic / Symbios Logic LSI1064E [vmhba1]
03:00.00 Bridge: ServerWorks
04:00.00 Network controller: Broadcom Corporation Broadcom NetXtreme II BCM5708 1000Base-SX [vmnic0]
05:00.00 Bridge: ServerWorks
06:00.00 Network controller: Broadcom Corporation Broadcom NetXtreme II BCM5708 1000Base-SX [vmnic1]
07:00.00 Bridge: Intel Corporation
07:00.03 Bridge: Intel Corporation
08:01.00 Serial bus controller: QLogic Corp ISP2422-based 4Gb Fibre Channel to PCI-X HBA [vmhba2]
08:01.01 Serial bus controller: QLogic Corp ISP2422-based 4Gb Fibre Channel to PCI-X HBA [vmhba3]
09:00.00 Bridge: Intel Corporation
09:01.00 Bridge: Intel Corporation

I also ran the lspci -p command and got:

~ # lspci -p
Bus:Sl.F Vend:Dvid Subv:Subd ISA/irq/Vec P M Module Name
Spawned bus
00:00.00 8086:25d8 8086:8086 0/ / A V
00:02.00 8086:25f7 0000:0000 007 V
00:03.00 8086:25e3 0000:0000 015 V
00:04.00 8086:25e4 0000:0000 012 V
00:05.00 8086:25e5 0000:0000 014 V
00:06.00 8086:25e6 0000:0000 003 V
00:07.00 8086:25e7 0000:0000 005 V
00:08.00 8086:1a38 1014:02dd 5/ 5/0x79 A V ioat
00:16.00 8086:25f0 1014:02dd V
00:16.01 8086:25f0 8086:8086 V
00:16.02 8086:25f0 8086:8086 V
00:17.00 8086:25f1 8086:8086 V
00:19.00 8086:25f3 8086:8086 V
00:21.00 8086:25f5 8086:8086 V
00:22.00 8086:25f6 8086:8086 V
00:28.00 8086:2690 0000:0000 0/ 0/0x79 A V
00:29.00 8086:2688 1014:02dd 11/ 11/0x81 A V usb-uhci
00:29.01 8086:2689 1014:02dd 7/ 7/0x89 B V usb-uhci
00:29.02 8086:268a 1014:02dd 5/ 5/0x91 C V usb-uhci
00:29.07 8086:268c 1014:02dd 7/ 7/0x99 D V ehci-hcd
00:30.00 8086:244e 0000:0000 001 V
00:31.00 8086:2670 0000:0000 V
00:31.02 8086:2680 1014:02dd 0/ 0/0x99 B V vmhba0
01:01.00 1002:515e 1014:0305 11/ / A V
02:00.00 1000:0056 1014:0306 5/ 5/0x79 A V mptscsi_2xx vmhba1
03:00.00 1166:0103 0000:0000 004 V
04:00.00 14e4:16ac 1014:0327 7/ 7/0xa1 A V bnx2 vmnic0
05:00.00 1166:0103 0000:0000 006 V
06:00.00 14e4:16ac 1014:0327 7/ 7/0x91 A V bnx2 vmnic1
07:00.00 8086:3500 0000:0000 009 V
07:00.03 8086:350c 0000:0000 008 V
08:01.00 1077:2422 1077:014d 7/ 7/0xa9 A V qla2300_707_vmw vmhba2
08:01.01 1077:2422 1077:014d 11/ 11/0xb1 B V qla2300_707_vmw vmhba3
09:00.00 8086:3510 0000:0000 011 V
09:01.00 8086:3514 0000:0000 010 V

Am I on the right track here? Can you point out what I should be looking for? In addition, is there an example of what the oem.tgz syntax should look like? Thanks for the newb questions.

Author:  Dave.Mishchenko [ Tue Sep 15, 2009 5:50 pm ]
Post subject:  Re: Next steps for customizing OEM.TGZ

If you go here there's a sample oem.tgz file that you can download for this - http://www.vm-help.com/esx/esx3i/customize_oem_tgz.php.

But basically the oem.tgz file will contain the files you want with the proper folder structure. When ESXi boots it will extract the file and the other tgz (or vgz for ESXi 4) files, and you can use oem.tgz to add or overwrite files.

If I want to modify /etc/inetd.conf, I would create the folder structure .etc/ and add my modified inet.conf file into it. Then you compress it and add it to /bootbank.

But one things to note. In the order of files that ESXi extracts, oem.tgz comes second last. The last file is state.tgz, so if you run a fresh install of ESXi then modify inetd.conf, it will get copied into state.tgz (or local.tgz for ESXi Embedded). In that case, the /etc/inetd.conf file you would add to oem.tgz would always get overwritten by the copy in state.tgz. Does that make it clear as mud :)?

Page 1 of 1 All times are UTC - 8 hours
Powered by phpBB © 2000, 2002, 2005, 2007 phpBB Group