Jump to content

1 Screenshot

About This File

Mac OS X Unlocker for VMware V2.0

 

Please ask questions in this thread http://www.insanelymac.com/forum/topic/303311-workstation-1112-player-712-fusion-78-and-esxi-6-mac-os-x-unlocker-2/

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 hardware VMware will 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

 

© 2011-2015 Dave Parsons


What's New in Version 2.0.8   See changelog

Released

  • 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



User Feedback

Recommended Comments



Trying "El Capitan" Beta3 on Workstation 11.1.2 on Scientific Linux 7.0 host, with unlocker 2.0.5

 

Followed instructions at http://pastebin.com/6pWGSB5bto create bootable ISO from OS_X_10.11b3 download

 

Created new VM with defaults (hardware version 11, so set smc.version = "0" in vmx file)

 

Booted to and ran installer OK, but at end of installation:

"The bless tool was unable to set the current boot disk"

 

Retrying with VM hardware version 10...

Share this comment


Link to comment
Share on other sites

I just wanted to say thank you for these tools!  Ive got 10.10 running on 2 developer machines for iOS.  I almost cracked and bought a used MBP.  I kinda game up on the entire hackintosh thing.  Updates breaking things, wasting time to rebuild it all, etc.  I got too annoyed by it.  This solution is the perfect.  :)

Share this comment


Link to comment
Share on other sites

I am afraid I am a bit lost,

when I add the line "efi64.filename = "efi64-srvr.rom"" to my vmx file, VMWARE complains the virtual machine is corrupt.

I did patch the vmware using 2.0.6 using the provided patch script for windows. No error reported as far as I can see.

 

VMWare player 7.1.2 build-2780323, Mac Os X 10.10 installed via VMWare Fusion, (They are interoperable, since I copy an image of my Centos VM on both without any conversion whatsoever) 

 

"Edit"

 

For some reason, after reinstalling the VMWare, applying the patch again, and skipping the modification to vmx file, it works perfectly now.

 

I am so much grateful for this, If you ever visit Germany, I will offer the developers all the beer you can drink.

Share this comment


Link to comment
Share on other sites

Thank You for these tool. When will you release new release for Workstation 12 Pro. I want to be a first. Thanks for your work.

 

Regards.

Share this comment


Link to comment
Share on other sites

Just a heads up... unlocker 2.0.6 doesn't work with Workstation 12 Pro on Linux.  

 

I get an error of missing library:  /usr/lib/vmware/lib/libvmwarebase.so.0/libvmwarebase.so.0

Share this comment


Link to comment
Share on other sites

2.0.6 is working for VMware Workstaion 12 (confirmed) 

 

Running El Capitan 

 

I confirmed as well. I also installed the new version of darwin.iso.

 

running Yosemite & Mavericks.

Share this comment


Link to comment
Share on other sites

I get the missing library: /usr/lib/vmware/lib/libvmwarebase.so.0/libvmwarebase.so.0 message and VMware Workstation 12 doesn't recognise OSX as a option. Running "official version" VMware Workstation 12 on Fedora 22 x86_64...

Share this comment


Link to comment
Share on other sites

I'm having problems in linux with VMware Workstation Pro 12, it says:

 

VMware Unlocker 2.0.6
===============================
Copyright: Dave Parsons 2011-15
Creating backup folder...
‘/usr/lib/vmware/bin/vmware-vmx’ -> ‘./backup/vmware-vmx’
‘/usr/lib/vmware/bin/vmware-vmx-debug’ -> ‘./backup/vmware-vmx-debug’
‘/usr/lib/vmware/bin/vmware-vmx-stats’ -> ‘./backup/vmware-vmx-stats’
cp: cannot stat ‘/usr/lib/vmware/lib/libvmwarebase.so.0/libvmwarebase.so.0’: No such file or directory
 

Any help?

Share this comment


Link to comment
Share on other sites

It's easy to fix unlocker 2.0.6 for linux to be compatible with Vmware Workstation 12:

substitute ‘/usr/lib/vmware/lib/libvmwarebase.so.0/libvmwarebase.so.0’ with

'/usr/lib/vmware/lib/libvmwarebase.so/libvmwarebase.so' in the following two files :
 
lnx-install.sh
unlocker.py
 
then rerun lnx-install.sh and enjoy :-)

Share this comment


Link to comment
Share on other sites
Hello to all,

I confirm that unlocker 2.0.6 works with vwmware 12, I installed OS X Yosemite, and I upgraded to El Capitan.

I have only one problem, but actually I had before, I can not install the vm tools (darwin.iso version 8) me: open but do not see any files in the folder.

Share this comment


Link to comment
Share on other sites

I solved the problem, I was able to install the VMTools, then confirm that VMware 12 works well with Mac OS X El Capitan 10.11 Beta 7

Share this comment


Link to comment
Share on other sites

 

It's easy to fix unlocker 2.0.6 for linux to be compatible with Vmware Workstation 12:

substitute ‘/usr/lib/vmware/lib/libvmwarebase.so.0/libvmwarebase.so.0’ with

'/usr/lib/vmware/lib/libvmwarebase.so/libvmwarebase.so' in the following two files :
 
lnx-install.sh
unlocker.py
 
then rerun lnx-install.sh and enjoy :-)

 

Great!, it worked!. Thanks!

Share this comment


Link to comment
Share on other sites

 

It's easy to fix unlocker 2.0.6 for linux to be compatible with Vmware Workstation 12:

substitute ‘/usr/lib/vmware/lib/libvmwarebase.so.0/libvmwarebase.so.0’ with

'/usr/lib/vmware/lib/libvmwarebase.so/libvmwarebase.so' in the following two files :
 
lnx-install.sh
unlocker.py
 
then rerun lnx-install.sh and enjoy :-)

 

Hi Thanks for this. lnx-install works.

However after installing VMWare-Player (free) 12, and applying unlocker 2.0.6 (after patching it), my OSX 10.10 virtual machine doesn't work anymore. It hangs at about 50% of the loading (apple logo and progress bar). It behaves the same as I had not installed the locker....

That was working with VMPlayer 7 and unlocker 2.0.3.

Any idea??

Share this comment


Link to comment
Share on other sites

I'm having the same problem. It stucks at boot screen almost at 50% and it never ends.

 

Any idea about this?

 

However, I had a previous snapshot and I can use it but sometimes I need to restart the machine and it never boots again.

 

Hi Thanks for this. lnx-install works.

However after installing VMWare-Player (free) 12, and applying unlocker 2.0.6 (after patching it), my OSX 10.10 virtual machine doesn't work anymore. It hangs at about 50% of the loading (apple logo and progress bar). It behaves the same as I had not installed the locker....

That was working with VMPlayer 7 and unlocker 2.0.3.

Any idea??

Share this comment


Link to comment
Share on other sites

Yes, in fact i have the same behavior with hanging just below 50%

 

I'm afraid we have to wait for unlocker to be updated to be VM12 compatible.

 

Alexandre

Share this comment


Link to comment
Share on other sites

:(

 

Yes, in fact i have the same behavior with hanging just below 50%

 

I'm afraid we have to wait for unlocker to be updated to be VM12 compatible.

 

Alexandre

Share this comment


Link to comment
Share on other sites

×