Jump to content

Workstation 11/12, Player 7/12, Fusion 7/8 and ESXi 6 Mac OS X Unlocker 2


Donk
 Share

688 posts in this topic

Recommended Posts

I'm hoping someone can accelerate me here with the following questions(s):

 

I'm currently running ESX 5.5 on an older PE2900III server.  I'm running a basic vSphere 6.0 setup from a hosted appliance image (VCSA).

 

I'd like to upgrade to the latest supported versions while still being able to maintain this unlocker to boot OSX.

 

Can I upgrade both my ESXi server and vSphere VM to 6.5?

 

I see there is a newer version of the unlocker that doesn't support 6.x.  What am I losing by not going to that unlocker on ESXi?

 

If I can't upgrade to the latest, what is the last version I can go to and safely use the tool?

 

I will be doing a full rebuild on the server(s).

 

Thanks!


  • 1 month later...

Hi everyone!

 

I noticed that VMware Workstation 15 has been released. Do you know if unlocker 2.0.9 (is there any higher version) is working properly with that new release?

 

Any info would be great!

 

Thank you in advance!

Edited by mihha
wrong unlocker version mentioned

On 9/25/2018 at 8:40 AM, mihha said:

Hi everyone!

 

I noticed that VMware Workstation 15 has been released. Do you know if unlocker 2.0.9 (is there any higher version) is working properly with that new release?

 

Any info would be great!

 

Thank you in advance!

According to the README file on his GitHub (last updated two days ago as of this posting), Workstation 15 support is present in v3.0. As far as I am aware, v3.0 has not been released yet, but at least we know that it is being worked on. Has anybody tried using the current latest version on 15?

Edited by David-B

Yes ity does work. V3 splits ESXi support out from Workstation. I am dropping patching Fusion as it is completely redundant as SMC is always present either physically or using FakeSMC.

  • Like 1

  • 4 months later...

Hi, thanks for making this!

Just executed win-install and was distracted by something and couldn't see if the command was successful before cmd closed... is there a way to know? Should I run it again? Should I run win-uninstall and then start over?


  • 1 month later...
On 12/13/2014 at 11:27 AM, Donk said:

This version is now only supported for ESXi 6.0 for the latest version please visit http://www.insanelymac.com/forum/topic/328285-macos-unlocker-21-for-vmware-workstation-111214-player-71214-fusion-7810-and-esxi-65/

 

 

Support Request
Please, please, please do NOT copy vmx or log files inline in a post. Always attach the log file as an attachment. It slows down the forum editor and puts a lot of junk in the actual post, and I cannot analyse unless it is a separate file. Alternatively post a link to a Gist.
 
Download Links
 
InsanelyMac: http://www.insanelymac.com/forum/files/file/339-unlocker/

 

14/11/15 - Version 2.0.8
  • Player 12 on Linux fixes
  • Get latest VMware tools command
  • Removed firmware files
  • Moved to PyInstaller 3.0

16/09/15 - Version 2.0.7

  • Workstation 12 on Linux fixes

20/06/15 - Version 2.0.6

  • ESXi 6 patch for smcPresent vCenter compatibility. Thanks Sam!

18/06/15 - Version 2.0.5
 
ESXi 6 work was greatly helped by Sam B. Thanks to Sam for helping me out and finding the last piece of the puzzle.

  • ESXi 6 working
  • Latest tools from Fusion 7.1.2

24/01/15 - Version 2.0.4
 
Couple of quick fixes:

  • Added stop and start of VMware View USB Service to Windows batch files
  • Fixed broken GOS Table patching on Linux

03/01/15 - Version 2.0.3
 
Added new EFI firmware files to remove Server check for 10.5 and 10.6.
 
If you are using a 32-bit installation of OS X:

1. Copy efi32-srvr.rom to guest folder.
2. Edit the vmx file and add:

 

 

 


efi32.filename = "efi32-srvr.rom"

If you are using a 64-bit installation of OS X:
 
1. Copy efi64-srvr.rom to guest folder.
2. Edit the vmx file and add:


efi64.filename = "efi64-srvr.rom"

14/12/14 - Version 2.0.2
 
Uploaded a new version, 2.0.2, which removes need for Python on Windows. Packaged using PyInstaller. If you have already used 2.0.0 successfully then you do not need this as there are no other changes. Also added darwin.iso back into the zip file.
 
http://www.insanelymac.com/forum/files/file/339-unlocker/
 
For installation queries please read MSoK's excellent post http://www.insanelymac.com/forum/topic/290949-how-to-install-os-x-10x-snow-leopard-lion-mountain-lion-mavericks-and-yosemite-in-vmware-workstation-10-or-player-6/.
 


Mac OS X Unlocker for VMware V2.0
=================================


1. Introduction
---------------


Unlocker 2 is designed for Workstation 11, Player 7, ESXi 6 and Fusion 7.


If you are using an earlier product please continue using Unlocker 1 


Version 2 has been tested against:


* Workstation 11/12 on Windows and Linux
* Player 7 & Workstation Player 12 on Windows and Linux
* Fusion 7/8 on Mavericks and Yosemite
* ESXi 6.0


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 VM creation
* Fix libvmkctl.so on ESXi 6 to allow use with vCenter
* Download a copy of the latest VMware Tools for OS X


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 11 and Player 7.


The vmwarebase code does not need to be patched on OS X or ESXi 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.


The code is now Python as it makes the Unlocker easier to run and maintain on ESXi.
There are some challenges to write the code as ESXi has a subset of Python 2.7 which
constrains some modules that can be used.


2. Prerequisites
----------------


The code requires Python 2.7 to work. Most Linux distros, ESXi and OS X ship with a compatible
Python interpreter and should work without requiring any additional software.


Windows has a packaged version of the Python script using PyInstaller, and so does not
require Python to be installed.


3. Limitations
--------------


If you are using VMware Player or Workstation on Windows you may get a core dump.


Latest Linux and ESXi products are OK and do not show this problem.


+-----------------------------------------------------------------------------+
| IMPORTANT:                                                                  |
| ==========                                                                  |
|                                                                             |
| If you create a new VM using version 11 or 12 hardware VMware may stop and  |
| create a core dump. There are two options to work around this issue:        |
|                                                                             |
| 1. Change the VM to be HW 10 - this does not affect performance.            |
| 2. Edit the VMX file and add:                                               |
|    smc.version = "0"                                                        |
|                                                                             |
+-----------------------------------------------------------------------------+


4. 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".


win-install.cmd   - patches VMware
win-uninstall.cmd - restores VMware
win-update-tools.cmd - retrieves latest OS X guest tools


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


You may need to ensure the Linux scripts have execute permissions
by running chmod +x against the 2 files.


lnx-install.sh   - patches VMware
lnx-uninstall.sh - restores VMware
lnx-update-tools.cmd - retrieves latest OS X guest tools


6. 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 OS X scripts have execute permissions
by running chmod +x against the 2 files.


osx-install.sh   - patches VMware
osx-uninstall.sh - restores VMware


7. 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 ESXi scripts have execute permissions
by running chmod +x against the 2 files.


esxi-install.sh   - patches VMware 
esxi-uninstall.sh - restores VMware 


Note:
1. 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.
2. The unlocker runs at boot time to patch the relevant files and it now survives 
   an upgrade or patch to ESXi as local.sh is part of the persisted local state.
   
8. Thanks
---------


Thanks to Zenith432 for originally building the C++ unlocker and Mac Son of Knife
(MSoK) for all the testing and support.


Thanks also to Sam B for finding the solution for ESXi 6 and helping me with
debugging expertise. Sam also wrote the code for patching ESXi ELF files.




History
-------
12/12/14 2.0.0 - First release
13/13/14 2.0.1 - Removed need for Python for Windows
13/13/14 2.0.2 - darwin.iso was missing from zip file
02/01/15 2.0.3 - Added EFI firmware files to remove Server check
               - Refactored Python code
07/01/15 2.0.4 - Added View USB Service to Windows batch files
               - Fixed broken GOS Table patching on Linux
18/06/15 2.0.5 - ESXi 6 working
               - Latest tools from Fusion 7.1.2
20/06/15 2.0.6 - ESXi 6 patch for smcPresent vCenter compatibility
16/09/15 2.0.7 - Workstation 12 on Linux fixes
14/11/15 2.0.8 - Player 12 on Linux fixes
               - Get latest VMware tools command
               - Removed firmware files
               - Moved to PyInstaller 3.0


(c) 2011-2015 Dave Parsons

 


On 8/12/2018 at 6:09 PM, bengalih said:

I'm hoping someone can accelerate me here with the following questions(s):

 

I'm currently running ESX 5.5 on an older PE2900III server.  I'm running a basic vSphere 6.0 setup from a hosted appliance image (VCSA).

 

I'd like to upgrade to the latest supported versions while still being able to maintain this unlocker to boot OSX.

 

Can I upgrade both my ESXi server and vSphere VM to 6.5?

 

I see there is a newer version of the unlocker that doesn't support 6.x.  What am I losing by not going to that unlocker on ESXi?

 

If I can't upgrade to the latest, what is the last version I can go to and safely use the tool?

 

I will be doing a full rebuild on the server(s).

 

Thanks!

According to the VMware Compatibility Guide you are running latest support ESXi version at 5.5, see below:

 

image.thumb.png.c030f2949ed883f822773a15a0324338.png


  • 4 weeks later...
On 4/24/2019 at 7:29 PM, KdeAssassin said:

im trying to run the unlocker in my pc but.. for some reason its not working i still dont see the mac os option in vmware

and i dont even think my code runs properly

 

 

Can you run chcp from the command line? You can also try chcp 850 and then running the installer.


  • 1 year later...
  • 2 weeks later...
On 9/19/2020 at 4:01 PM, David-B said:

I cannot seem to find the unofficial patcher for VMware Workstation 15.5 here now, but for anyone who is curious, I can confirm that it works perfectly with with the new Workstation 16 release!

 

Thanks, with that info I found this thread that has a patcher which works on VMware Workstation 16 in Windows.

 


 Share

×
×
  • Create New...