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 did a clean install of Win7 x64 and I was able to load up OS X Mountain Lion in VM10 without using this or any other unlocker. So what would be the point of using the unlocker in VM10? Just wondering how it could be working now without using an unlocker.

Share this comment


Link to comment
Share on other sites

Dears, trying to patch a standalone ESXi 5.5 with v120 I'm returned this:

 

Immagine_1.png

 

ESXi has standard configuration, with 2 datastores.

 

Should I enter maintainance mode before to patch?

 

Any other suggestions?

 

 

Thanks and best regards

Share this comment


Link to comment
Share on other sites

I run ESX 5.5 from a SD card slot inside of a Dell PowerEdge R810. Can I assume this is why the installer is failing? 

 

VMware ESXi 5.x Unlocker 1.2.0
===============================
Copyright: Dave Parsons 2011-13
Patching files...
Patching bin/vmx
File mapped @0x3ffdfa04010 length 22929216
Found OSK0 @ 0x3ffe095c265
Found OSK1 @ 0x3ffe095c29d
Found SRVR @ 0x3ffe09ec1f6
Patching bin/vmx-debug
File mapped @0x3ffdfa04010 length 27924264
Found OSK0 @ 0x3ffe0ad68e5
Found OSK1 @ 0x3ffe0ad691d
Found SRVR @ 0x3ffe0b681f6
Patching bin/vmx-stats
File mapped @0x32002740 length 25723136
Found OSK0 @ 0x32f7cb15
Found OSK1 @ 0x32f7cb4d
Found SRVR @ 0x3300d926
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: 16065572, flags: 5
addr: 0xf54e3c, sz: 3416524, flags: 6
bin/vmx: textPgs: 3922, fixUpPgs: 0
Aligning executable bin/vmx
addr: 0, sz: 17618636, flags: 5
addr: 0x10ce47c, sz: 3529484, flags: 6
bin/vmx-debug: textPgs: 4301, fixUpPgs: 0
Aligning executable bin/vmx-debug
addr: 0, sz: 16203932, flags: 5
addr: 0xf7643c, sz: 3653996, flags: 6
bin/vmx-stats: textPgs: 3956, 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
cp: error writing to '/bootbank/darwin.vgz': No space left on device
Copying darwin.vgz to /bootbank/darwin.vgz failed: 1

Share this comment


Link to comment
Share on other sites

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


Copyright: Dave Parsons 2011-13


Patching files...


/vmfs/volumes/datastore1/osxen/unlock-all-v120/esxi/install.sh: line 27: ./Unlocker.ESXi: Permission denied


/vmfs/volumes/52180278-4dc75e9c-6a9e-10604b924c50/osxen/unlock-all-v120/esxi # c


hmod +x /vmfs/volumes/datastore1/osxen/unlock-all-v120/esxi/install.sh


/vmfs/volumes/52180278-4dc75e9c-6a9e-10604b924c50/osxen/unlock-all-v120/esxi # /


vmfs/volumes/datastore1/osxen/unlock-all-v120/esxi/install.sh


VMware ESXi 5.x Unlocker 1.2.0


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


Copyright: Dave Parsons 2011-13


Patching files...


/vmfs/volumes/datastore1/osxen/unlock-all-v120/esxi/install.sh: line 27: ./Unlocker.ESXi: Permission denied


/vmfs/volumes/52180278-4dc75e9c-6a9e-10604b924c50/osxen/unlock-all-v120/esxi # cd /


 


Does that look right to you people? ;)


Share this comment


Link to comment
Share on other sites

For anyone interested I was able to get this working on a USB stick with a bit of a hack. I did have to install it on a hard drive at first to get the unlock to work but once I did that I was able to remove the extra VMFS partition on the drive using partedUtil from the esxi commandline and then using clonezilla to clone all the partitions to a USB drive. You could technically do this on something as small as a 1GB USB drive if you get rid of the scratch partition too and then recreate it on another drive (which is advisable since you don't want the system writing to your USB on a regular basis). If you use clonezilla use the advanced mode and dont install grub, don't resize partitions, and ignore the size difference as options, then just use the existing partition table from the source drive.

Share this comment


Link to comment
Share on other sites

Did you make sure to run unlocker from a Administrator level CMD window?  I have the same setup (Win 8.1 Pro with VMware 10.0.1) and just finished installing OSX 10.8.5.  No issues...

Share this comment


Link to comment
Share on other sites

When I try to patch "unlocker v120" on ESXi, the message "segmentation fault" was prompt out. Seem that the patch was not complete. After that, I have successfully patched and install the OSX used the "unlocker v1.1.0".

My ESXi version is "5.0.0,914586". Thanks.

Share this comment


Link to comment
Share on other sites

In Introduction for ESXi, it should add wording similar to: Please note that you will need to reboot the host [and create new VM] for the patches to become active.

Apparently, this patch will not apply to existing VMs.

Share this comment


Link to comment
Share on other sites

Ya esta confirmado amigos la versión 1.3 no soporta VMWare Workstation 10.0.2, sera necesaria una actualización del Unlocker para poder ejecutar maquinas con Mac OS X.

 

Already this confirmed friends version 1.3 does not support VMWare Workstation 10.0.2, required an update of the Unlocker to run machines with Mac OS X.

Share this comment


Link to comment
Share on other sites

Did you make sure to run unlocker from a Administrator level CMD window?  I have the same setup (Win 8.1 Pro with VMware 10.0.1) and just finished installing OSX 10.8.5.  No issues...

 

I just did a clean install of vmware and tried installing the unlocker as admin and via a cmd with admin privs, doesnt work

Share this comment


Link to comment
Share on other sites

Ya esta confirmado amigos la versión 1.3 no soporta VMWare Workstation 10.0.2, sera necesaria una actualización del Unlocker para poder ejecutar maquinas con Mac OS X.

 

Already this confirmed friends version 1.3 does not support VMWare Workstation 10.0.2, required an update of the Unlocker to run machines with Mac OS X.

 

I can confirm that VMware Workstation 10.0.2 running under Windows 8.1 Pro 64 bit unlocks fine with unlock-all-v130.

Share this comment


Link to comment
Share on other sites

Hi,

 

first a big thanks für this very great unlocker! It work like a charm on my HP ProLiant ML110 G7 with OSX 10.9.2 server!

 

My questions: Can I use it with esxi 5.5 U1?

 

BR

crypted

Share this comment


Link to comment
Share on other sites

HI everyone~

VMware Unlocker 1.3.0  not work on ESXi5.0 build 914586(ESXi 5.0 U2) server.

ESXI5.0 has rc.local file but not  local.sh .

someone can help me ?

thanks~

 

 

VMware Unlocker 1.3.0
===============================
Copyright: Dave Parsons 2011-14
Installing local.sh
cp: cannot remove '/etc/rc.local.d/local.sh': No such file or directory
 

Share this comment


Link to comment
Share on other sites

ok just playing around and here is where I am at:

clean install 5,5 base on dell 1950

esxi running from internal usb 4gb.  scratch is located on main drive

upgrade - now 5.5.0, 1746018

 

created folder and copied unlocker directory to store

execute install.sh from esxi directory

completed without errors, reported success and to reboot.

reboot server

create vm    osx 10.6 64bit

power on vm - fails standard error not supported.

 

ran through it a second time - same issue. ran again on clean 2950 - same thing.

if this works for others I have to be missing a step.

 

will play with system more after Hawks game but since I am not getting any errors on install (permissions etc) then really don't know where to start. 

Share this comment


Link to comment
Share on other sites

ok so - access the same 1950 clean install from client and not center - vm powers up.

This follows the earlier posts about issues with vcenter vs stand alone esxi.

 

will work with install tonight and post again

Share this comment


Link to comment
Share on other sites

First, think you very much for making this script.  I look forward to being to run OSX on my ESXi environment at work.

 

I have just preformed a fresh install on a fully firmware patched HP DL360p G8 server with 4 - 500GB HDDs in RAID 60 mode (this gives me 1 TB of space on the server).  I am booting the HP Customer ESXi 5.5.0 Image file from the disks mentioned above.  I have follow your instructions but I am getting the error message:

    vmkfstools failed with message: create fs

   deviceName:'/vmfs/devices/disks/naa.600508b1001ca4cb71a1a956750c5c3e:2',fsShortName:'vfat',fsName:'(null)'

   deviceFullPath:/dev/disks/naa.600508b1001ca4cb71a1a956750c5c3e:2

   deviceFile:naa.600508b1001ca4cb71a1a956750c5c3e:2

   Checking if remote hots are using this device as a valid file system. This may take a few seconds....

   Creating vfat file system on "naa.600508b1001ca4cb71a1a956750c5c3e:2"with block size 1048576 and volume label "none"

   Error: Device or respirce busy

 

May I ask what are your suggestions to get this to work.

 

I don't think that this should matter but I am running this script from datastore1.

 

Thanks Again

Share this comment


Link to comment
Share on other sites

Is the "Unlocker.ESXi" file not needed any more? If it is, I cannot find it in this package. When i run install.sh it does not seem to patch any files, if it does - the silent switch must be on. When the machine boots up, it seems to be some built-in EFI system that I did not intend to use. Any ideas?

 

Running on ESXi 5.5 u1 on an Intel Q6600 with 6GB RAM.

Share this comment


Link to comment
Share on other sites

Hello the download seems not to work any more. I am using VMWare Player 6.0.3 build 1895310 on Windows 7. I had Mac Osx maverick. installed and run sucessfully before. But it stopped working 2-3 days ago and I am also not succesfull in a new instalation.

 

I keep on reciving "EFI Network..." messeage on the initial gray screen and then dropping to boot manager screen...

 

Any comments

Share this comment


Link to comment
Share on other sites

Thanks for this VM Unlocker its successfully unlock VMware Workstation 10 OSX flavor, running on Windows 8.1 Pro x64.

Share this comment


Link to comment
Share on other sites

Unfortunately, the unlocker doesn't seem to work on the latest version of VMware Fusion, version 7.0. The Terminal output indicates that it sucessfully patched vmware-vmx, -vmx-debug, and -vmx-stats, but "Patching vmwarebase is not supported on this platform."

Share this comment


Link to comment
Share on other sites

×