Could somebody hand me a lightbulb? The tool is used first by: extracting, patching and then injecting the ROM file though? Just installed a HP build ESXi 4.1 U1 build 348481 and connection is done successfully but: somewhere in the beginning it cannot copy: cp /vmfs/volumes/Hypervisor2/s.z /vmfs/volumes/volID#/vmvisor-sys/sys.gz cp: cannot stat '/vmfs/volumes/Hypervisor2/s.z': No such file or directory From that point... red... I'm going to reinstall with only 1 array known to the system...
bzzz.... also this one is a no-go... i'm out of options.. DL380G5 configured with 1 array. Set the password; Enabled SSH; but: cp /vmfs/volumes/Hypervisor2/s.z /vmfs/volumes/volID#/vmvisor-sys/sys.gz cp: cannot stat '/vmfs/volumes/Hypervisor2/s.z': No such file or directory
yeah, was about to do that.. have to make a RW-report for the phoenix tool still only important is file is S.Z?
Yes & no about the report. Latest update uses the SAME 3.15 BIOS like previos version & same like Workstation 7.1.3, so if you have that modded BIOS handy, you do not even need to mod it again! I believe s.z is the only file you need for ESXi sebus
few... worked ... Copying file S.Z from Hypervisor1 to Hypervisor2 Ran the tool to extract... Modded the file with phoenix tool. Renamed back to BIOS440.rom Injected the file.... crunch.. crunch ... Moved S.Z back to Hypervisor1 directory , ... ran tool again... crunch.. crunch ... and running,...
Thanks for providing a workaround sebus. It looks like the tool is not using the correct Hypervisor folder under certain circumstances though. godfather007 - can you post here or PM me with the boot.cfg files from your Hypervisor1 and 2 folders? I'll refine the code and get a new build up.
I tried the tool in ESXi 4.1 update 1 but I get some error. I'll attach some screenshot that are better than 1000 words. Can you give me some help?? Regards Alessio
So I have to copy all the contents of folder Hypervisor1 into Hypervisor2, then patching and after that copy again the file into Hypervisor1? Is that correct? And the file boot.cfg that I have in both folder? I have to backup it or it can be overwritten?? Regards Alessio
I tried........simply perfect!!!!!!! Thank you Just a curiosity.........so the file inside Hypervisor2 (in my case) are not useful and can be deleted after the mod?? Regards Alessio
I could do with getting a copy of the boot.cfg files before people overwrite the contents of their Hypervisor2 folders. I can get a new version up then so you won't need to use workarounds.
I did a fresh install of ESXi 4.1 U1 (non-HP) to a 4GB USB stick, and got the same hypervisor2 file copy error. I'll try the workaround..but a new version would be appreciated. Boot.cfg from Hypervisor1 folder: kernel=b.z kernelopt= modules=k.z --- s.z --- c.z --- oem.tgz --- license.tgz --- m.z build=4.1.0-348481 updated=1 bootstate=0 Boot.cfg from Hypervisor2 folder: kernel=b.z kernelopt= modules=k.z --- s.z --- c.z --- oem.tgz --- license.tgz --- m.z build=4.1.0-348481 updated=2 bootstate=3 Also, the tool was at first unable to connect to my freshly loaded ESXi 4.1 U1 server even though SSH was enabled. After a couple of failures I manually launched WinSCP, was able to connect (acknowledging a thumbprint warning), then the ESXi bios tool was able to connect. So I'm thinking it wouldn't connect because of the Thumbprint issue.
Thanks for your help - I've PM'd you a new build to try out. If it's working for you I'll put it up here. Dunno what's happening with WinSCP, I'll have to look into it.
Worked like a champ! This was a new ESXi 4.1 U1 server, and I didn't get the WinSCP issue. So maybe lastime was just a fluke.