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



having the same issue here. 

unlocker 2.0.8 running with workstation 12.1 pro build-3272444 on windows 10 x64 10240

For those having the issue with the bar getting stuck half way across, starting win-install.cmd as an Administrator BUT FROM a folder copied to C:\ did the trick for me ! I'm using Windows 10 Pro x64 1511, VMWare Workstation Pro 12.1.1 build-3770994 and Unlocker 2.08.

Share this comment


Link to comment
Share on other sites

I've ran this against the latest ESXi 6.0 update 2 version, build 3620759, and I get the following output

 

VMware Unlocker 2.0.8

===============================
Copyright: Dave Parsons 2011-15
Installing local.sh
cp: can't stat 'local-template.sh': No such file or directory
 
 
Any idea's?
 
 
______________________________________
 
 
Fixed it, the full unlocked folder hadn't copied to the ESX host, I was looking at the tree's and not the wood on this one, trying to figure out what had changed between update 1 and update 2 in terms of the file structure etc

Share this comment


Link to comment
Share on other sites

I had VMWare Player 6 running Mac OS 10.10.5 Yosemite. I tried upgrading to 10.11 El Capitan but it got stuck at some point, even leaving it throughout the night.

 

So I forcefully stopped the VM, installed the latest VMWare Workstation Player 12 and Unlocker 2.0.8, then restarted the VM, and the update went through without a hitch.

 

Thanks a lot!

Share this comment


Link to comment
Share on other sites

one more pre-requisite - be connected to the internet when you run this up so you can DL VMware tools etc. :)

thanks heaps for this, really REALLY helps!

Share this comment


Link to comment
Share on other sites

Here is the software I'm running... Windows 10 x64 build 14393, VMware Workstation Pro 12.1.1 build 3770994, and Unlocker 2.0.8.  I have a Mac OS X virtual machine that I'm trying to install the latest updates on as well as a Windows 10 virtual machine that I'm trying to install the updates on.  Both virtual machines keep crashing.  They were working fine before I reinstalled everything on my computer.  I was just wondering if anyone knows if there are any known issues using Unlocker on VMware 12.1.1 or on Windows 10 build 14393.  I think I might've been running a slightly older version of VMware before I reformatted my computer.  The Mac OS X virtual machine does have smc.version = "0" in the configuration file.  Any ideas why my virtual machines would be crashing?

 

Update:  I tried removing the Sound Card, USB Controller, and CD/DVD Drive from both virtual machines.  The Windows virtual machine seems to be stable so far but the mouse wouldn't work on the OS X VM.  I added a USB 1.1 controller back into the OS X VM and I'm going to see if it's more stable with that one.  It was set to USB 2.0 before.

 

Nevermind... none of that helped much.  The virtual machines still keep crashing a lot.  Maybe Unlocker 2.0.8 is causing VMware 12.1.1 to be unstable.  I ran WhoCrashed in the Windows VM and it says the crash is due to a memory error... I wonder if Unlocker could be causing a memory issue in the VMs or if there is a memory bug in VMware 12.1.1.

Share this comment


Link to comment
Share on other sites

I think I'm going to try a slightly older build of VMware Workstation.  What was the latest build of VMware Workstation tested with Unlocker 2.0.8?

Share this comment


Link to comment
Share on other sites

Still works like a charm with Fusion 8.5! So I think it would be reasonable to infer it should work with Win/Lin 12.5.

 

8.5/12.5 really is NOT a major upgrade, pretty much some long overdue patches...

Share this comment


Link to comment
Share on other sites

I can confirm, it's working with 12.5 (Win). I forgot to uninstall the unlocker patch before updating, but that wasn't a problem at all... uninstalled and reinstalled it after updating to 12.5.

Share this comment


Link to comment
Share on other sites

Anyone able to get a 10.12 install running using the 2.0.8 unlocker on an ESXi 6U2?

10.11 is working fine, but even updating an existing 10.11 to 10.12 won't let it boot afterwards.

Share this comment


Link to comment
Share on other sites

Anyone able to get a 10.12 install running using the 2.0.8 unlocker on an ESXi 6U2?

10.11 is working fine, but even updating an existing 10.11 to 10.12 won't let it boot afterwards.

 

I was getting the prohibitory sign in 10.12 on esxi 6U2 after a reboot or two.  Booting off the Sierra iso and reinstalling, got it booting again, but it would start having the same issue again afterwards.
 
I changed the hw.model from default VMware7,1 to something else (used Macmini6,2) as well as the s/n and board-id. I followed: http://daveparsons.net/blog/2013/12/30/pass-real-mac-details-to-vm/
Not sure if this fixed it, I only tested it for a few hours but it hasn't acted up on me yet.

Share this comment


Link to comment
Share on other sites

Hi, Thanks for this great piece of software. Is there a torrent / link version? My http download keeps failing/ corrupt: Missing files: unlocker.exe gettools.exe Thanks in advance.

Running Windows 10, VMWare 12.5.2 -> intention osx 10.11

Share this comment


Link to comment
Share on other sites

Anyone try ESXi 6.5 yet?

 

I was not able to get the unlocker working on 6.5 and it seems like it actually affects other VM's from starting, not just mac VMs. Uninstall fixed other VMs but mac VM's won't boot still.

Share this comment


Link to comment
Share on other sites

nzalog - thanks for that comment. I upgraded to 6.5 and couldnt' start any VM and got the error 'failed - transport (vmdb) error -45: failed to connect to peer process.'. Couldn't find any troubleshooting help until I came across your comment and realized I had the unlocker installed. Once I uninstalled it VMs started successfully.

 

I should note that I was able to resume my OSX VM successfully. I'm not going to reboot or power it off though. =) 

Share this comment


Link to comment
Share on other sites

Hi,

 

I'm having issues with the unlocker 2.0.8 and ESXi 6.5 on PowerEdge 2950III.

 

With the patch, which i need to run OSX, none of my vm would start

I keep receiving this message;

 

Key

haTask-8-vim.VirtualMachine.powerOn-170465547

State

Failed - Transport (VMDB) error -45: Failed to connect to peer process.

Errors

  • Transport (VMDB) error -45: Failed to connect to peer process.

 

 

Now, I had these VM working fine under 5.5 using unlocker 1.3.0, unfortunately this older version did not allow me to connect USB devices from the host to the guests.

Now with 6.5 I can do this but then I lost the ability to launch my OSX VM's.

 

I was wondering if anyone of you guys knew how to get OS X guests to run on 6.5 ?

 

Actually, I had few machines which were on Suspend and those works fine as long as I dont reboot.

After reboot they just freeze on the wheel...

 

 

Any help would be appreciated.

Share this comment


Link to comment
Share on other sites

Same error here with unlocker 2.0.8 and HPE ESXi 6.5 on microserver Gen8: 

 

Transport (VMDB) error -45: Failed to connect to peer process

 

Any recommendation?

Share this comment


Link to comment
Share on other sites

Transport (VMDB) error -45: Failed to connect to peer process

seems to always occur if a buggy system trashes the (swap) space with logs :)

 

The esxi-uninstall.sh luckily fixes the Problem for now.

 

Interresting is, that an OSX-Install will start without the unlocker (adding cpuid.1.eax = "----:----:----:0010:----:----:1010:0111" of course) and proceed to 50% until it hangs.

Share this comment


Link to comment
Share on other sites

Does not appear to work in Wayland on Fedora 25:

 

[root@xps13 unlocker207]# ./lnx-install.sh
VMware Unlocker 2.0.7
===============================
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'
'/usr/lib/vmware/lib/libvmwarebase.so/libvmwarebase.so' -> './backup/libvmwarebase.so'
Patching...
Traceback (most recent call last):
  File "./unlocker.py", line 402, in <module>
    main()
  File "./unlocker.py", line 352, in main
    vmx_version = subprocess.check_output(["vmware", "-v"])
  File "/usr/lib64/python2.7/subprocess.py", line 567, in check_output
    process = Popen(stdout=PIPE, *popenargs, **kwargs)
  File "/usr/lib64/python2.7/subprocess.py", line 711, in __init__
    errread, errwrite)
  File "/usr/lib64/python2.7/subprocess.py", line 1343, in _execute_child
    raise child_exception
OSError: [Errno 2] No such file or directory
 

[root@xps13 unlocker208]# ./lnx-install.sh
VMware Unlocker 2.0.8
===============================
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'
'/usr/lib/vmware/lib/libvmwarebase.so/libvmwarebase.so' -> './backup/libvmwarebase.so'
Patching...

(vmplayer:11376): Gtk-WARNING **: cannot open display:
Traceback (most recent call last):
  File "./unlocker.py", line 413, in <module>
    main()
  File "./unlocker.py", line 361, in main
    vmx_version = subprocess.check_output(["vmplayer", "-v"])
  File "/usr/lib64/python2.7/subprocess.py", line 574, in check_output
    raise CalledProcessError(retcode, cmd, output=output)
subprocess.CalledProcessError: Command '['vmplayer', '-v']' returned non-zero exit status 1
 

[root@xps13 unlocker208]# vmplayer -v

(vmplayer:11409): Gtk-WARNING **: cannot open display:

 

I've had some issues with a few other applications, something about the :0 display I presume.
 

Share this comment


Link to comment
Share on other sites

DrDonk/Dave has a release candidate available for ESXi 6.5 on his GitHub page (https://github.com/DrDonk/unlocker)! For those that can't wait for it to be posted here, go download the master branch from GitHub and run that on ESXi. I can confirm that it is working on a white box ESXi 6.5 instance! Thanks for your awesome work Dave and all those that have helped on the project!

Share this comment


Link to comment
Share on other sites

This might be a dumb question but what does unlocking vmware fusion do?

Is it for hackintoshes only?

I'm just asking because I've ran OSX in Fusion on my macbook without any unlockers.

Share this comment


Link to comment
Share on other sites

×