Maybe but I'm a C# / Windows man and don't fancy the learning curve... Also, more people have windows boxes than linux on this forum and modding will utimately take place on a windows box. It would be fairly trivial to write a linux script to do all this - just look at the commands that are being executed in the log, it's all there.
I'm a Windows guys as well, so doing it in Linux would be a PITA. But if that didn't require SSH, it would be a bonus. However, like you said, the BIOS mod isn't supported anyway so what's the harm in turning on SSH anyways.
Hello, I am trying to inject a modified bios into my ESXI 4.0 update 1 machine. I have version 1.0.0.3, but it is crashing when I try to inject my bios. Where can I download the latest version of this tool? Thanks.
ESX(i) bios tools v1.0.1 fails on ESXi 3.5.0 update 5 Hi, I intend to extract the bios from ESXi 3.5.0. update 5 using ESX(i) bios tools v 1.0.1. This however does not work. In the output of the tool I can see: 1) succesfull login 2) succesfull change directory to /usr/lib/vmware/bin 3) failing get vmware-vmx I logged in as root manually using putty and tried manually. The vmware-vmx file is not in the directory. In an attempt to locate the file I did a search of the entire file system for vmware-vmx by: cd / find . | grep -i vmware-vmx with no result. It seems like this file does not exist on the file system. Anybody has ideas or even a solution?
Update 2 has been released for VmWare 4.0 esx(i). Did anyone try apply it to the patched esx(i)? Does it work then? Does it require re-patch it again?
vSphere ESX version 261974 (update 2) ESX Clean install - Running on a dell Optiplex 745 with 8gb of memory...Installed Windows XP vm to run Rw. Installed Windows server 2008 R2 to test activation Steps: (I used software posted already on this thread) First: IMPORTANT: ssh to the vmware server and allow root ssh login: change from "no" to "yes": PermitRootLogin yes # vi /etc/ssh/sshd_config # ps -ef | grep ssh # kill <pid_id> (to kill running ssh service) # /usr/sbin/sshd (to restart service) Second: Software used: EsxBiosTools1001 to extract rom bios from vmware. RwV1.4 Install rw everything on a vmware machine. Press acpi button, wait and press save all (ctrl+F2) it will give you acpitbls.rw which you use in the phoenix tool. phoenixtool100 to edit bios using the above files (acptables.rw, dell certificate, dell .bin (from SLIC21 folder)). To Test open the new rom with winhex.exe (I used version15.4 evaluation) to verify the slic number. Third: Run tool to inject back the new rom to vmware esx 4 "BIOS440_SLIC.ROM" When you inject the bios using ESX Bios Tools, the original vmx file is backed up so you can restore if it goes wrong. You don't need to rename the bios. The whole process took me less than 10 minutes (not counting winXP and Server installs). Activate windows 2008 R2 std 1.- Copy DELL.XRM-MS to C:\ 2.- run SLMGR.vbs -ILC C:\DELL.XRM-MS slmgr.vbs -ipk xxxxx-xxxxx-xxxx-xxxxx-xxxxx-xxxxx It should be activated now... Cheers!
probably you could just publish moded bios? because I didn't understand what are RwV1.4 and phoenixtool100 tools. is exs bios the same as for esxi for upd2? (bioses were the same in esx and esxi 4.0 up 1) thank you!
I would like to say great Thanks, to all they make it possible to help frustrated noobs (like me) with such easy to use Tools. I know it is a hard job to find out new method against much complexe technics. Thanks
In ESXi 4.1 the file sys.vgz has become s.z in folder hypervisor1. It is still possible to get the vm file. But this one is no longer a elf32 format but a elf64. It seems the version of objdump can not handel this format.