Jump to content

1 Screenshot

About This File

Mac OS X Unlocker for VMware

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

 

1. Introduction

---------------

 

The package is a combination of the Unlocker code written by Zenith432 plus some

fixes and scripts written by myself that wrap the actual unlocker code.

 

It has been tested against:

 

* Workstation 8/9/10 on Windows and Linux (32 & 64-bit versions)

* Player 4/5/6 on Windows and Linux (32 & 64-bit versions)

* Fusion 4/5/6 on Snow Leopard, Lion, Mountain Lion and Mavericks

* ESXi 5.0/5.1/5.5

 

The patch code carries out the following modifications dependent on the product

being patched:

 

* Fix vmware-vmx and derivatives to allow Mac OS X to boot

* Fix vmwarebase .dll or .so to allow Apple to be selected during creation

* Copy darwin.iso if needed to VMware folder

 

Note that not all products recognise the darwin.iso via install tools menu item.

You will have to manually mount the darwin.iso for example on Workstation.

 

Also Player is missing vmware-vmx-debug and vmware-vmx-stats files and so an

error is shown during patching as the files are not found. This can be safely

ignored.

 

OS X guests on ESXi patched hosts cannot be controlled from vCenter, only from

the ESXi host itself. This means power operations have to be run directly on

the server.

 

The vmwarebase code does not need to be patched on ESXi or OS X so you will see a

message on those systems telling you that it will not be patched.

 

In all cases make sure VMware is not running, and any background guests have

been shutdown.

 

2. Windows

----------

On Windows you will need to either run cmd.exe as Administrator or using

Explorer right click on the command file and select "Run as administrator".

 

install.cmd - patches VMware and copies darwin.iso tools image to VMware

uninstall.cmd - restores VMware and removes darwin.iso tools image from VMware

 

3. Linux

---------

On Linux you will need to be either root or use sudo to run the scripts.

 

You may need to ensure the contents of the linux folder have execute permissions

by running chmod +x against the 4 files.

 

install.sh - patches VMware and copies darwin.iso tools image to VMware

uninstall.sh - restores VMware and removes darwin.iso tools image from VMware

 

4. Mac OS X

-----------

On Mac OS X you will need to be either root or use sudo to run the scripts.

This is really only needed if you want to use client versions of Mac OS X.

 

You may need to ensure the contents of the osx folder have execute permissions

by running chmod +x against the 3 files.

 

install.sh - patches VMware

uninstall.sh - restores VMware

 

5. ESXi

-------

You will need to transfer the zip file to the ESXi host either using vSphere client or SCP.

 

Once uploaded you will need to either use the ESXi support console or use SSH to

run the commands. Use the unzip command to extract the files.

 

<<< WARNING: use a datastore volume to run the scripts >>>

 

Please note that you will need to reboot the host for the patches to become active.

The patcher is embbedded in a shell script local.sh which is run at boot from /etc/rc.local.d.

 

You may need to ensure the contents of the esxi folder have execute permissions

by running chmod +x against the 3 files.

 

install.sh - patches VMware

uninstall.sh - restores VMware

 

Note:

1. System should have a persistent scratch partition - should be OK except for stateless

and USB boot on drives less than 4GB

http://kb.vmware.com/selfservice/microsites/search.do?language=en_US&cmd=displayKC&externalId=1033696

http://www-01.ibm.com/support/docview.wss?uid=isg3T1013015

http://www.vreference.com/2011/04/28/check-for-esxi-scratch-persistence/

2. Any changes you have made to local.sh will be lost. If you have made changes to

that file, you will need to merge them into the supplied local.sh file.

3. This option runs at boot time to patch the releavant files and it now survives

an upgrade or patch to ESXi as local.sh is part of the persisted local state.

 

6. Zenith432's Unlocker

-----------------------

 

In all cases the unlocker can be run without the scripts but you would need to

carry out additional actions which the scripts encapsulate for you especially on

ESXi. If you want to run the unlocker directly the parameters are:

 

Usage: Unlocker [-h] [-u] [target_directory]

-h: print help

-u: remove the patch

target_directory: customize location of vmx executables

 

On all platforms you must run it with administrator or root privileges.

The source code is provided and Zenith432 makes it freely available for

modification. I have modified the code and it is available as per Zenith432's

original statement.

 

 

Thanks to Zenith432 for building the unlocker and Mac Son of Knife for all

the testing and support.

 

 

History

-------

11/10/11 1.0.0 - First release

07/11/11 1.0.1 - Fixed typo in Windows command files

07/12/11 1.0.2 - Updated patcher and tools for latest release WKS 8.0.1 & FUS 4.1.1

10/05/12 1.1.0 - Changed the patching mechanism for vmwarebase .dll or .so

& tested against ESXi 5.0 U1 and Tech Previews.

13/07/13 1.1.1 - Changed ESXi scripts to ensure not deleting root /bin folder

- Fixed vmwarebase patching on 32-bit Linux

- Some other code clean-up in Unlocker.cpp

18/09/13 1.2.0 - Updated vmwarebase pattern matching for WKS 10.0.0 & FUS 6.0.0

25/03/14 1.3.0 - New method to run patcher on ESXi

- Fixes crashes when using vCenter

- Tested against ESXi 5.5

- Darwin guest tools from Fusion 6.0.2

- Zip file preserves file attributes for Posix based systems

 

© 2011-2014 Dave Parsons


What's New in Version 1.3.0   See changelog

Released

No changelog available for this version.




User Feedback



Recommended Comments

Just a word of CAUTION with running this script on ESX: DO NOT RUN THIS IN / as all of ./bin will be deleted & you'll need to re-install ESX! I did this by mistake & an currently re-installing. IMHO: the script for ESX should at least check & inform you before deleting /bin & suggest this be done.

Share this comment


Link to comment
Share on other sites

Just a word of CAUTION with running this script on ESX: DO NOT RUN THIS IN / as all of ./bin will be deleted & you'll need to re-install ESX! I did this by mistake & an currently re-installing. IMHO: the script for ESX should at least check & inform you before deleting /bin & suggest this be done.

This is fixed in version 1.1.1.

Share this comment


Link to comment
Share on other sites

Hmm. Not sure why this is not working. Is there any log files I can look at? 

 

VMkernel orca 5.1.0 #1 SMP Release build-1065491

 

/vmfs/volumes/4eccd6b6-7191d638-26d6-bc305bd549e8/unlock-all-v111/esxi # ./install.sh
VMware ESXi 5.x Unlocker 1.1.1
==============================
Copyright: Dave Parsons 2011-13
Patching files...
Patching bin/vmx
File mapped @0x3ffd30cc010 length 16890352
Found OSK0 @ 0x3ffd3acb205
Found OSK1 @ 0x3ffd3acb23d
Found SRVR @ 0x3ffd3b0f2c6
Patching bin/vmx-debug
File mapped @0x3ffd30cc010 length 21347720
Found OSK0 @ 0x3ffd3bf4a45
Found OSK1 @ 0x3ffd3bf4a7d
Found SRVR @ 0x3ffd3c39406
Patching bin/vmx-stats
File mapped @0x7416d0 length 19607592
Found OSK0 @ 0x1160b25
Found OSK1 @ 0x1160b5d
Found SRVR @ 0x11a63e6
Patching vmwarebase is not supported on this platform
Setting permissions...
Creating darwin.tgz...
bin/
bin/vmx
bin/vmx-debug
bin/vmx-stats
addr: 0, sz: 10442140, flags: 5
addr: 0x9f7044, sz: 2206780, flags: 6
bin/vmx: textPgs: 2549, fixUpPgs: 0
Aligning executable bin/vmx
addr: 0, sz: 11667172, flags: 5
addr: 0xb2277c, sz: 2242564, flags: 6
bin/vmx-debug: textPgs: 2848, fixUpPgs: 0
Aligning executable bin/vmx-debug
addr: 0, sz: 10575212, flags: 5
addr: 0xa1665c, sz: 2371908, flags: 6
bin/vmx-stats: textPgs: 2581, fixUpPgs: 0
Aligning executable bin/vmx-stats
Adding darwin.tgz to boot.cfg...
Acquiring lock /tmp/bootbank.lck
Copying darwin.vgz to /bootbank/darwin.vgz
Editing /bootbank/boot.cfg to add module darwin.vgz
/vmfs/volumes/4eccd6b6-7191d638-26d6-bc305bd549e8/unlock-all-v111/esxi
Please now reboot the host system!
 
Rebooted but still says OS is not supported!

Share this comment


Link to comment
Share on other sites

I have the same problem on esxi 5.1 running on amd system from usb flash drive. I'm wondering if enabler make it possible to run osx under vmware on amd or on intel only?

Share this comment


Link to comment
Share on other sites

As far as I know you can't run this on a ESXi USB stick, so we just have to wait.

 

I did contact the author a good while back, and he said he would try to look into the issue when he had some time. So I'm just crossing my fingers that he has the time soon.

Share this comment


Link to comment
Share on other sites

Windows patch does *not* work for me, VMWare Workstation 10.0.0 build 1295980. The problem seems to be:

Patching C:\Program Files (x86)\VMware\VMware Workstation\vmwarebase.dll
File mapped @008D0000 length 4772944
Pattern not found in vmwarebase.dll

Any ideas?

Share this comment


Link to comment
Share on other sites

It's actually compatible with the new version of VMware (10), it just doesn't show OSX as an option to create a new VM. Past VMs with OSX work with the patch.

Share this comment


Link to comment
Share on other sites

It's actually compatible with the new version of VMware (10), it just doesn't show OSX as an option to create a new VM. Past VMs with OSX work with the patch.

thanks, I'll test this and see

Share this comment


Link to comment
Share on other sites

Just to be sure, does anyone of you guys (who got it working) boot ESXi from USB?

I do, has worked for me for the last 3 versions of unlocker. Currently on Esxi 5.1.0 U1 patch 5 and unlocker v1.1.1

Share this comment


Link to comment
Share on other sites

I did clean instalation of windows 8 + workstation 10 and just open previously installled mountain lion machine and it just start and work without unlocker..

WTF?

i am crazy or what?

Share this comment


Link to comment
Share on other sites

I installed the latest version of this patch in the latest version of ESX 5.1, it worked great and allowed me to spin up a Mac OS virtual machine in my ESX environment.  After I installed it, I am unable to vMotion any virtual machines to this host.  To test, I uninstalled it and vMotion began to work.  My goal is to patch one host at a time without occurring any downtime to the virtual machines.  This occurred when my hosts were on different versions.  I upgraded all hosts to the latest and greatest for 5.1 and I still encounter the same issue.  I can vMotion a few servers to this host with the unlocker installed, but after that vMotion breaks.  The error I get is Operation timed out.  It gets to 14%, Migrating active state of virtual machine.  I am running VMware ESX Enterprise Plus 5.1.1157734.  Any ideas why vMotion stops working with this patch installed?

Share this comment


Link to comment
Share on other sites

I installed the latest version of this patch in the latest version of ESX 5.1, it worked great and allowed me to spin up a Mac OS virtual machine in my ESX environment. After I installed it, I am unable to vMotion any virtual machines to this host. To test, I uninstalled it and vMotion began to work. My goal is to patch one host at a time without occurring any downtime to the virtual machines. This occurred when my hosts were on different versions. I upgraded all hosts to the latest and greatest for 5.1 and I still encounter the same issue. I can vMotion a few servers to this host with the unlocker installed, but after that vMotion breaks. The error I get is Operation timed out. It gets to 14%, Migrating active state of virtual machine. I am running VMware ESX Enterprise Plus 5.1.1157734. Any ideas why vMotion stops working with this patch installed?

The unlocked is only really working for standalone ESXi and there are known issues with vCenter including vMotion problems. I would post in the forum thread for ESXi and ask the folks there for advice http://www.insanelymac.com/forum/topic/267296-esxi-5-mac-os-x-unlocker/

Share this comment


Link to comment
Share on other sites

×