mkesxiaio.sh not working for (4.0) update2 and (4.1) update1

[GoogleCodeExporter]

Structure/format of oem.tgz is different

What steps will reproduce the problem?
1. See attached screenshots:

Varazir-1: 4.0u2: *.tgz not in correct format (vmtar, not tar)
. FAIL to decompress

Varazir-2: 4.1u1: ISO created, oem.tgz format different.  PSOD on boot:
"The system has found a problem on your machine and cannot continue.
Could not populate the filesystem: Bboot image is corrupted.

"Escape" for local debugger." See attached vmkernel_debugger*.txt

Varazir-3: Structure of 2nd partition from imagedd (imagedd.bz2)

What is the expected output? What do you see instead?
4.0.0-U2: Fail.
4.1.0-U1: PSOD, boot corrupted.

What version of the product are you using? On what operating system?
Autodeploy.zip (CentOS 5.3) from 
http://labs.vmware.com/flings/vmware-auto-deploy

Please provide any additional information below.

http://mirrors.kernel.org/centos/5.5/os/x86_64/CentOS/ for updated RPMS:
syslinux-3.86-3.x86_64.rpm
perl-Crypt-PasswdMD5-1.3-1.2.1.noarch.rpm
perl-Digest-SHA1-2.11-1.2.1.x86_64.rpm
mtools-3.9.10-2.fc6.x86_64.rpm
tcsh-6.14-17.el5.x86_64.rpm
parted-1.8.1-27.el5.x86_64.rpm

CommunityUnifiedDriverPack_v1.1.0_U3-123629.oem.gz

Updated simple.map and pci.ids in custom-esx

Original issue reported on code.google.com by alpha_s...@msn.com on 23 Mar 2011 at 8:05

Attachments:

• Varazir-1.jpg
• vmkernel_debugger_4.1.0_348481.txt
• Varazir-2.jpg
• Varazir-3.jpg

[GoogleCodeExporter]

As I posted on the forum, test the 
VMware-VMvisor-Installer-4.1.0.update1-348481.x86_64.iso from vmware.com 

Make sure the oem ok too. 

Original comment by daniel.s...@gmail.com on 23 Mar 2011 at 4:17

• Changed state: Accepted

[GoogleCodeExporter]

[deleted comment]

[GoogleCodeExporter]

Please us the correct iso from VMwaresite 

Original comment by daniel.s...@gmail.com on 2 Apr 2011 at 12:16

• Changed state: Invalid