Jump to content
InsanelyMac Forum
Donk

ESXi 5 Mac OS X Unlocker

Recommended Posts

Donk,

 

I tried your patch works great was able to start Lion install using usb stick. It is in the process of installing.

 

I am sure you have answered this before, my apologies in advance.

 

If you don't mind, I am interested to know how this patch works.

 

I see three binary files being patched, what are the changes made?

Share this post


Link to post
Share on other sites
Advertisement
Donk,

 

I tried your patch works great was able to start Lion install using usb stick. It is in the process of installing.

 

I am sure you have answered this before, my apologies in advance.

 

If you don't mind, I am interested to know how this patch works.

 

I see three binary files being patched, what are the changes made?

Hur,

 

I suspect the answer to your question is no, as we don't want to give VMware informtion for them to close the loophole in a future update, or remove it from the up coming Workstation 8 / 2011. Best to keep the detailed knowledge in safe hands like Donk's.

 

Please do not be offended,

Cheers MSoK!

Share this post


Link to post
Share on other sites

I was also going to ask how this worked, but really I'm just wondering if this might affect the stability of the ESXi host.

 

Does this patch the VMX binaries used by the entire system, or does it only patch binaries that the OS X host would use?

 

EDIT: Also, I'm having a problem installing Snow Leopard. I've patched my ESXi 5.0 system, rebooted, and created an "Apple OS X 10.6 (64-bit)" guest operating system. I'm using the host CD-ROM drive.

 

When the guest os boots, it boots my retail Snow Leopard DVD and I see the Apple logo, but then a second or two later I see a blinking cursor and the system reboots over and over...

Share this post


Link to post
Share on other sites
I was also going to ask how this worked, but really I'm just wondering if this might affect the stability of the ESXi host.

 

Does this patch the VMX binaries used by the entire system, or does it only patch binaries that the OS X host would use?

 

EDIT: Also, I'm having a problem installing Snow Leopard. I've patched my ESXi 5.0 system, rebooted, and created an "Apple OS X 10.6 (64-bit)" guest operating system. I'm using the host CD-ROM drive.

 

When the guest os boots, it boots my retail Snow Leopard DVD and I see the Apple logo, but then a second or two later I see a blinking cursor and the system reboots over and over...

It is a system wide patch, but can easily be removed. The patch will not alter anything for any other guest VMs and when remved the system is completely put back to the installed version as everything used RAM disks in ESXi. Basically the patch allows the SMC controller and MAC OS X checks to pass without any other CD etc., and is the equivalent to the code path inside VMware Fusion.

 

I understand your dilema and I would say to anyone who wants to use Mac OS X or any form of productive use buy a Mac or virtualize on a VMware approved platform such as Mac and Fusion or Xserve and ESXi. On that last note I see no code that checks for Xserve, and booting ESXi on my Macbook Pro showed all the ESXi Apple drivers correctly loaded.

 

For SL what is the CPU in the host and what version of SL? Do not forget that early SL version cannot support later CPUS e.g. Sandy Bridge until 10.6.7.

Share this post


Link to post
Share on other sites

Thanks for the information!

 

Also - I _greatly_ appreciate all of your efforts on brining OS X to VMware!

 

Anyways... why does the CPU matter for ESXi and OS X? Since the guest operating system is virtualized, I thought Snow Leopard wouldn't even know about the CPU in the host, etc.

Share this post


Link to post
Share on other sites

I migrated a working osx lion install, and its stuck on the apple logo, did smc=present, donk's patch, cpuid modification, it still hangs at apple logo screen, tried verbose startup didnt work, went to efi shell but it says boot is invalid command

Share this post


Link to post
Share on other sites
Thanks for the information!

 

Also - I _greatly_ appreciate all of your efforts on brining OS X to VMware!

 

Anyways... why does the CPU matter for ESXi and OS X? Since the guest operating system is virtualized, I thought Snow Leopard wouldn't even know about the CPU in the host, etc.

Virtualized systems pass the real CPU characteristics through to the guest. Emulation would allow any CPU to be specified. That's the reason virtualization is so quick compared to emulation.

 

You can mask certain features and it may be possible to do that for ESXi booting Mac OS X. MSoK can point you in the right direction for a CPUID mask that may help.

Share this post


Link to post
Share on other sites
Virtualized systems pass the real CPU characteristics through to the guest. Emulation would allow any CPU to be specified. That's the reason virtualization is so quick compared to emulation.

 

You can mask certain features and it may be possible to do that for ESXi booting Mac OS X. MSoK can point you in the right direction for a CPUID mask that may help.

Thanks very much for the explanation.

 

I'll continue my question in the other thread since the original post on that thread says it's meant for questions regarding installing OS X and this thread is more about the unlocker itself.

 

Thanks again so much!

Share this post


Link to post
Share on other sites

Donk,

 

I've written a bios extractor for ESXi:

 

http://forums.mydigitallife.info/threads/1...SXi-Bios-Tools/

 

which I'm currently updating to work with v5. I could include the code to automate patching of ESXi for OSX with your patch if you're happy for me to?

 

It unpacks the ramdisk image s.v00 from the active vmfs folder, mods the vmx file and repacks it, leaving boot.cfg unchanged.

 

If you're happy for me to do this, would your preference be to include your archive in my pack or force the user to pick it from a dialogue?

Share this post


Link to post
Share on other sites

Hi Guys

 

When I run unlocker I get the following permission denied error:

 

VMware ESXi 5.0 Unlocker 1.0.0

==============================

Patching files...

install.sh: line 13: ./bspatch: Permission denied

 

First time I've tried this so probably doing something silly, logging on via SSH using root if that matters.

 

Thanks

Share this post


Link to post
Share on other sites
Donk,

 

I've written a bios extractor for ESXi:

 

http://forums.mydigitallife.info/threads/1...SXi-Bios-Tools/

 

which I'm currently updating to work with v5. I could include the code to automate patching of ESXi for OSX with your patch if you're happy for me to?

 

It unpacks the ramdisk image s.v00 from the active vmfs folder, mods the vmx file and repacks it, leaving boot.cfg unchanged.

 

If you're happy for me to do this, would your preference be to include your archive in my pack or force the user to pick it from a dialogue?

Hi

 

Sorry I missed your PM as was busy over weekend. Actually I would rather do it my way based on feedback I have been given. No offence but I was asked to do something that was reversible and so took the root of using the bootbank to do this. Happy to discuss in more detail of you want, such as incorporating both sets of patches but delivering via a new tgz or vmtar file.

 

Donk

Share this post


Link to post
Share on other sites

hi folks,

 

i used a pre existing vm-image created on vmworkstation 7.x and converted it with vmconverter to esxi5. i have used the "unlock script" ( not sure if installing,reboot, deinstall, reboot is the right procedure )

 

I can start the VM, but it hangs on the gray Apple Logo Screen ... any ideas?

 

cheers

m

Share this post


Link to post
Share on other sites
hi folks,

 

i used a pre existing vm-image created on vmworkstation 7.x and converted it with vmconverter to esxi5. i have used the "unlock script" ( not sure if installing,reboot, deinstall, reboot is the right procedure )

 

I can start the VM, but it hangs on the gray Apple Logo Screen ... any ideas?

 

cheers

m

Please attach vmx file to a post. Do not copy it inline into the post.

Share this post


Link to post
Share on other sites

hi a3897431@nepwk.com,

 

you just install the patch and reboot. The deinstallation just removes the changes you have made previously and restores a plain vanillla esxi. So you do not want to deinstall as long as you want to run OSX natively ...

 

 

cheers,

oegie

Share this post


Link to post
Share on other sites

The readme for the unlocker says

 

Step 4 - Uninstall the patch ?

 

I assume this is only if you want to revert back to vanilla ESXi ?

Share this post


Link to post
Share on other sites
The readme for the unlocker says

 

Step 4 - Uninstall the patch ?

 

I assume this is only if you want to revert back to vanilla ESXi ?

In a word, Yes, LoL!

Share this post


Link to post
Share on other sites
Here is the unlocker for the new VMware ESXi 5.0.

 

http://goo.gl/UFbTZ

 

I will post more details later as for Lion there are still some challenges in getting installation media. Mac Son of Knife will help out with setting up and configuring Mac OS X guests. I will deal primarily with the patch itself. Please note that if there is an update or fix from VMware for the files patched I will have to issue a new patcher.

Please note there is a patch now available for ESXi 5.0 and this does update the files I patch. However the patcher still work with the new files which are build 474610.

Share this post


Link to post
Share on other sites
Please note there is a patch now available for ESXi 5.0 and this does update the files I patch. However the patcher still work with the new files which are build 474610.

Donk,

 

Just to confirm, I assume we need to re-apply the patch following the update to build 474610?

Share this post


Link to post
Share on other sites
Hi Guys

 

When I run unlocker I get the following permission denied error:

 

VMware ESXi 5.0 Unlocker 1.0.0

==============================

Patching files...

install.sh: line 13: ./bspatch: Permission denied

 

First time I've tried this so probably doing something silly, logging on via SSH using root if that matters.

 

Thanks

 

Anyone? ;)

Share this post


Link to post
Share on other sites
Donk,

 

Just to confirm, I assume we need to re-apply the patch following the update to build 474610?

Yes the best sequence is to uninstall and install.

 

First time I've tried this so probably doing something silly, logging on via SSH using root if that matters.

 

Thanks

 

Anyone? ;)

Not logged in with root permissions?

Share this post


Link to post
Share on other sites

Hi and Hello,

 

This is my first post here...

Yes the best sequence is to uninstall and install.

 

Your patch works great..Thanks a lot! Do you mean uninstall before ESXi patching and install after the ESXi patching is done?

 

Thanks a lot!

 

bye crazyx

Share this post


Link to post
Share on other sites

Maybe I'm missing something here, but i ran the ESXi unlocker patch (after the ESXi 5 patches), connected locally to the ESXi server itself (its in a cluster currently) and created a VM with Apple MAC OS X 10.6 64bit as the OS (also tried 10.5 and 10.7)... when i try to power it on i get this:

 

4vnwgz.jpg

 

Are there more modifications to make other than just installing the ESXi patch, rebooting, and creating an OS X VM?

Share this post


Link to post
Share on other sites

Create an account or sign in to comment

You need to be a member in order to leave a comment

Create an account

Sign up for a new account in our community. It's easy!

Register a new account

Sign in

Already have an account? Sign in here.

Sign In Now

  • Recently Browsing   0 members

    No registered users viewing this page.



×