Jump to content
Donk

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

686 posts in this topic

Recommended Posts

2.0.9 from the GitHub repo now works on my upgraded exsi 6.5 install.  OS X Sierra installed just fine with no smc entries...and other operating systems powered up just fine...  looks like official release should happen soon.

Share this post


Link to post
Share on other sites
Advertisement

2.0.9 from the GitHub repo now works on my upgraded exsi 6.5 install.  OS X Sierra installed just fine with no smc entries...and other operating systems powered up just fine...  looks like official release should happen soon.

 

Please do not use the GitHub code. We have significant issues on some real servers which can make them unusable. They can only be recovered if you have physical access to th keyboard and screen.

Share this post


Link to post
Share on other sites

Unlocker 2.0.8 is for ESXi6 and does not work on ESXi 5/5.5. Also it is very likely that you need the specific 10.12 setting in VMware to be available to make Sierra run. The guest OS settings enable/disable specific OS optimisations in the core VMware code.

 

FWIW, Sierra installed and runs fine on 6.0 with the "Mac OS X 10.10" guest OS setting, which I think is the highest it goes on VM version 11

Share this post


Link to post
Share on other sites

Hello again,

 

thanks for the reply, unluckily ive made a little typo in my first statement. Of course i am running esxi 6.0 und not 5 while using Unlocker 2.0.8, but there is no 10.12 OS version available.

Share this post


Link to post
Share on other sites

Hello again,

 

thanks for the reply, unluckily ive made a little typo in my first statement. Of course i am running esxi 6.0 und not 5 while using Unlocker 2.0.8, but there is no 10.12 OS version available.

 

OK. There would not be an entry for it as 10.12 came out after ESXi 6. VMware would need to add it to an ESXi 6.0 update for it to be selectable as a guest OS type. The unlocker just makes VMware hidden options visible when it comes to the guest OS type.

Share this post


Link to post
Share on other sites

so why isnt Sierra working for me, when other users dont have this isue ?

 

So we need more information to help out. 

 

1. What is the host machine specification? CPUs and Memory?

2. How did you create the installation media for creating the guest?

3. Attach to a post the vmx file for the guest 

4. Attach to a post the vmweare.log file for the guest

 

(Please make sure you attach them as files and do not post inline as makes following the thread very difficult)

Share this post


Link to post
Share on other sites

1.    16 CPUs x Intel® Xeon® CPU E5-2620 v4 @ 2.10GHz       128 GB Ram

2.      Media downloaded as .dmg from appstore, coverted on Mac and testet on Workstation 12

 

Thanks. Try adding these 2 lines to your VMX file:

ich7m.present = "TRUE"
smc.present = "TRUE"

Share this post


Link to post
Share on other sites

VM is booting now, but my ESXI WebUI keeps crashing when editing that machine.

 

Edit: Created 120GB Harddisk for VM, but Installation just shows DVD Device

Share this post


Link to post
Share on other sites

VM is booting now, but my ESXI WebUI keeps crashing when editing that machine.

 

I use Workstation or Fusion to manage ESX so try it from one of those products and see if it still causes a problem. It could be there is something else missing. I can have a look but not until tomorrow.

Share this post


Link to post
Share on other sites

OK. There would not be an entry for it as 10.12 came out after ESXi 6. VMware would need to add it to an ESXi 6.0 update for it to be selectable as a guest OS type. The unlocker just makes VMware hidden options visible when it comes to the guest OS type.

 

Can confirm there is no option for OS X 10.12 when running unlocker 2.0.8.... but if you un-install unlocker which defeats it's purpose, OS X 10.12 will be available from the drop down menu assuming you have the latest VMware exsi patches so this confirms that unlocker 2.0.8 is the limiting factor.   Given that I used the GitHub 2.0.9 code(frowned upon by Donk) which did work on my dell R610 server without any issues, OS X 10.12 is available on EXSI 6.5.  I updated to this since simply editing my OS X install on exsi 6.0 using unlocker 2.0.8 hung my system and gave me an operating system not found when booting OS X... all I did was increase the core from 1 to 4 cpu's and that killed it.

Share this post


Link to post
Share on other sites

I will have to check this but the unlocker is not touching anything in this area. It only does 2 things. It adds the Apple haiku for the SMC controller and tells vCenter that OS X is supported by a simple string replace.

 

The 2.0.9 issue is now sorted but the code is not fully tested so please wait until I flag the code as done in a release and a commit to GitHub.

 

There have been issues with VMware and the number of cores in a macOS guest. The recommendation from VMware is 1 CPU/2 cores.

Share this post


Link to post
Share on other sites

Hey Donk. I know we shouldn't be using the 2.0.9 release yet, but I was just playing around with it and I wanted to make you aware of a problem I am seeing.

 

I installed ESXi 6.5 a few days ago, patched it with 2.0.9 and everything worked great. I decided to re-create the host with some bigger hard drives, so I upgraded the drives, reinstalled, and re-patched with the unlocker.

 

Now whenever I go to start ANY VM on that host, I get this error:

"The available Memory resources in the parent resource pool are insufficient for the operation"

When I un-install the unlocker, everything works again (windows VM's that is).

 

If you are already aware of this, great, I look forward to 2.0.9, if not let me know if I can get you any logs or anything.

 

Share this post


Link to post
Share on other sites

Hey Donk. I know we shouldn't be using the 2.0.9 release yet, but I was just playing around with it and I wanted to make you aware of a problem I am seeing.

 

I installed ESXi 6.5 a few days ago, patched it with 2.0.9 and everything worked great. I decided to re-create the host with some bigger hard drives, so I upgraded the drives, reinstalled, and re-patched with the unlocker.

 

Now whenever I go to start ANY VM on that host, I get this error:

"The available Memory resources in the parent resource pool are insufficient for the operation"

When I un-install the unlocker, everything works again (windows VM's that is).

 

If you are already aware of this, great, I look forward to 2.0.9, if not let me know if I can get you any logs or anything.

 

Thanks for the report. This is something new and not sure why this has happened. Could you tell me a bit more of your setup please?

 

1. How is ESXi installed?

2. USB key, hard drive?

3. Stateless or stateful?

4. Did you do a complete reinstall or upgrade install?

5. Host specification especially RAM?

 

If you don't mind could you zip or tar the /var/log folder and put it somewhere so I can download it. If you don't want others to have it email me via the address in the readme file.

 

I will be honest it is looking more likely that the unlocker will not be working reliably on ESXi. VMware have made some changes that seem to be beginning to restrict this sort of overlay. Probably related to the push into secure boot for ESXi. The question is do I release what I have with a big warning? I have to say I am reluctant to do so as I don't want someone running something critical on an ESXi host in a production environment with unreliable code.

Share this post


Link to post
Share on other sites

I will have to check this but the unlocker is not touching anything in this area. It only does 2 things. It adds the Apple haiku for the SMC controller and tells vCenter that OS X is supported by a simple string replace.

 

The 2.0.9 issue is now sorted but the code is not fully tested so please wait until I flag the code as done in a release and a commit to GitHub.

 

There have been issues with VMware and the number of cores in a macOS guest. The recommendation from VMware is 1 CPU/2 cores.

 

 

I have been and checked ESXi 6.0 and 6.5 with and without unlocker. I used ESXi Host UI, Fusion 8.5.3 and Workstation 12.5.2 to create new macOS guests. (I don't have vCSA available just at the moment.)

 

 

          ESXi UI Fusion Workstation
ESXi 6.0  10.10   10.10  10.10
ESXi 6.5  10.12   10.12  10.11

The only anomaly is Workstation but this is consistent with and without unlocker running on the ESXi host.

Share this post


Link to post
Share on other sites

Thanks for the report. This is something new and not sure why this has happened. Could you tell me a bit more of your setup please?

 

1. How is ESXi installed?

2. USB key, hard drive?

3. Stateless or stateful?

4. Did you do a complete reinstall or upgrade install?

5. Host specification especially RAM?

 

If you don't mind could you zip or tar the /var/log folder and put it somewhere so I can download it. If you don't want others to have it email me via the address in the readme file.

 

I will be honest it is looking more likely that the unlocker will not be working reliably on ESXi. VMware have made some changes that seem to be beginning to restrict this sort of overlay. Probably related to the push into secure boot for ESXi. The question is do I release what I have with a big warning? I have to say I am reluctant to do so as I don't want someone running something critical on an ESXi host in a production environment with unreliable code.

 

 

Donk,

 

1. The first time, I THINK I upgraded from 5.5 to 6.5 and that was when it worked. I have however re-installed 5-6 times with all kinds of combinations. Fresh install, re-install 5.5 and upgrade again.

2. I am installing from a CD, and running from the hard drives (Raid 5 to be exact)

3. Im not sure what you mean from this, but i'm pretty sure it's sateful. This is a standard ESXi install on a Dell R610

4. I have tried both. It was working with 6 146gb hard drives, I replaced them with 6, 1TB SSDs and re-installed and it breaks

5. Dell Inc. PowerEdge R610, 2x E5620 @ 2.40GHz, 192gb RAM, 4 NICs, 6 1TB SSD in Raid 5

 

Log file are here: https://www.dropbox.com/s/u6kpyxvtu7kclz0/logs.tar.gz?dl=0

Share this post


Link to post
Share on other sites

Hi Donk

 

I have home server. It is Asrock C2750D4I motherboard with Intel Avoton C2750 Octa-Core Processor and 32 GB RAM.

It has Vmware ESXi 6.0 update 2 installed.

 

I install unlock 2.08 and ok but when I start to install OS X Sierra I get panic(cpu 1 caller...) error.

The ISO is perfect because I can install it in Vmware Workstation without any problem.

What is the problem? Is the CPU?

 

 

post-1220657-0-42422300-1482967374_thumb.png

Share this post


Link to post
Share on other sites

Hi Donk

 

I have home server. It is Asrock C2750D4I motherboard with Intel Avoton C2750 Octa-Core Processor and 32 GB RAM.

It has Vmware ESXi 6.0 update 2 installed.

 

I install unlock 2.08 and ok but when I start to install OS X Sierra I get panic(cpu 1 caller...) error.

The ISO is perfect because I can install it in Vmware Workstation without any problem.

What is the problem? Is the CPU?

pktman,

 

Not seen anyone running an Intel Atom processor and OS X / macOS, and not a processor used in any Apple product as far as I am aware, you might try the CPUID masks recommended in the following topic:

 

http://www.insanelymac.com/forum/topic/290949-how-to-install-os-x-10x-snow-leopard-to-el-capitan-in-vmware-workstation-1011-workstation-proplayer-12-player-67-esxi-56/?p=1936143

Share this post


Link to post
Share on other sites

pktman,

 

Not seen anyone running an Intel Atom processor and OS X / macOS, and not a processor used in any Apple product as far as I am aware, you might try the CPUID masks recommended in the following topic:

 

http://www.insanelymac.com/forum/topic/290949-how-to-install-os-x-10x-snow-leopard-to-el-capitan-in-vmware-workstation-1011-workstation-proplayer-12-player-67-esxi-56/?p=1936143

 

MSoK is probably correct in his analysis. Any chance you could attach a vmware.log file to a post (please do not copy the contents into the post) so I can check out the CPUID data.

Share this post


Link to post
Share on other sites

pktman,

 

Not seen anyone running an Intel Atom processor and OS X / macOS, and not a processor used in any Apple product as far as I am aware, you might try the CPUID masks recommended in the following topic:

 

http://www.insanelymac.com/forum/topic/290949-how-to-install-os-x-10x-snow-leopard-to-el-capitan-in-vmware-workstation-1011-workstation-proplayer-12-player-67-esxi-56/?p=1936143

Hi MSoK and Donk

 

You are the best. It works very well.

I added

cpuid.1.eax = "0000:0000:0000:0001:0000:0110:1010:0101"

in .vmx file and works fine.

 

I discovered that this also can be done editing options of virtual machine (CPUID Mask).

 

Thank you very much for your great work.

Knowing that now it works, the next step will be to update to ESXi 6.5 when unlocker 2.09 is prepared.

Share this post


Link to post
Share on other sites

I've not had any problems with 2.0.9RC2 on ESXi 6.5 running a freshly installed 10.12 Sierra VM.  I used a 10.10 VM on another KVM-based virtualization platform to create the ISO (not sure the previous platform matters much, just FYI).  This is in a 3 host cluster and I can vMotion the machine around, etc with no problems.

 

I did add the smc.version=0 to the VMX, though I had no problems before (but I didn't want to run the risk of a host crashing later).  You can use PowerCLI to add this setting so you don't have to edit the VMX by hand, reload the VM in a vCenter inventory, etc.  Here's how I did it:

 

Connect-VIServer (enter requested info)

New-AdvancedSetting -Entity (Get-VM -Name Name_Of_VM_Here) -Name smc.version -Value 0
 
Confirm the setting with:
 
Get-AdvancedSetting -Entity (Get-VM -Name Name_Of_VM_Here) -Name smc.version

 

Hope this helps someone.  Thanks for the great tool.

Share this post


Link to post
Share on other sites

Hello

I need help please.

I use win10, vmware player 12.5.2 build-4638234

 

I cant patch vmware player with unlocker 2.0.8 (run win-install.cmd as admin)

 

acces denied (see image)

 

post-1943192-0-13290600-1483815859_thumb.jpg

 

Why?

 

Can anybody help me? (preferably German)

 

Thanks

 

 

 

Share this post


Link to post
Share on other sites

Created 120GB Harddisk for VM, but Installation just shows DVD Device

 

 

Solution found: HDD Device was found, but no volume on it. Didnt know that OSX Installation came with tool to fix that.

 

Editing still causes UI to freeze.

Share this post


Link to post
Share on other sites

Just wanted to report that unlocker 2.0.8 worked correctly with the latest Workstation update, 12.5.2 build-4638234 on a Windows 10 host.

 

 

 

I use win10, vmware player 12.5.2 build-4638234

 

I cant patch vmware player with unlocker 2.0.8 (run win-install.cmd as admin)

 

acces denied (see image)

 

Make sure you running as Administrator and that you don't have any VMware application (like Player) running.

Share this post


Link to post
Share on other sites

Create an account or sign in to comment

You need to be a member in order to leave a comment

Create an account

Sign up for a new account in our community. It's easy!

Register a new account

Sign in

Already have an account? Sign in here.

Sign In Now

  • Recently Browsing   0 members

    No registered users viewing this page.

  • Similar Content

    • By fusion71au
      Run Vanilla OS X El Capitan, Sierra, High Sierra or Mojave in VMware Workstation on a Windows Host
       
      I wanted to make a simple guide on how to create a vanilla OS X El Capitan virtual machine running on a Windows host.  The virtual machine should be useful for testing El Capitan and also for creating installers for use on a real machine/hackintosh.
       
      There are many guides and videos on the net about running OS X on Windows machines using pre-made VMWare disk images but you can never guarantee what else is in there….
       
      I’ve gathered info for this guide from various threads in the Multibooting and Virtualisation section of this forum eg
       
      Workstation 11/12, Player 7/12, Fusion 7/8 and ESXi 6 Mac OS X Unlocker 2 by @Donk How to Install OS X 10.x from Snow Leopard to El Capitan in VMware Workstation 10/12, Player 6/8 or ESXi 5/6 by @MSOK HOW TO: Create a bootable El Capitan ISO for VMware Credit and thanks to @Donk, @Albert Nietsnie and @MSOK for all their hard work in creating and testing the VMware Unlocker program.
       
      Requirements
      Intel PC with four or more CPU cores running Windows 7 X64 or later OS (2 or more cores needed for OS X) 4GB or more RAM (2GB or more will be needed for OS X) Hard Disk with at least 40GB free for Virtual Machine VMware Workstation 12 or later VMware Unlocker 2.0.7 or later Install OS X El Capitan app and Mac or Hack to prepare installation iso <-- Now, no longer necessary to have previous access to a Mac or Hack by building the Installer.app from scratch - see post#41 16GB or larger exFAT formatted USB stick to transfer El Capitan iso from Mac/Hack to Host PC Prepare Installation ISO on your Mac or Hack
      1.  On your Mac or Hack, download "Install OS X El Capitan.app" from the App Store into your Applications folder.
      2.  Unmount any attached install image/InstallESD.dmg (if currently mounted) by rebooting the system or running the hdiutil unmount command in terminal eg
       
      3.  Download and unzip the CECI.tool (attached to this post) into your ~/Downloads folder. The commands in this executable script are shown below for informational purposes….
       
       
       
      4.  Open OS X terminal, then run the following commands to execute the script:
      cd downloads chmod +x CECI.tool ./CECI.tool 5.  At the end of the process, you will have an El Capitan iso on your desktop - copy this onto an exFAT formatted USB for use on the PC Host later.
       
      Updates:
      @shela has created an ISO generating script compatible with OS X 10.6-10.12: create_osx_iso post #362.
      See post#30 for macOS_iso_cim.tool script to create ISO for macOS 10.13+ using Apple's createinstallmedia utility.
       
      Install and Patch VMware Workstation 12 on your PC
      1.  Download and install VMWare Workstation Player 12 or later
      2.  Download and extract Unlocker 2.0.7 or later to your USB stick…
      3.  Run the win-install.cmd as administrator by right clicking the file in Windows explorer or run it from an Administrative Command Prompt.
       



       
      Create an El Capitan Virtual Machine
      1.  Double click on the VMware Workstation 12 Player icon on your desktop and click “Create a New Virtual Machine”.  Choose “I will install the operating system later” at the How will you install screen….
       

      2.  Select Apple Mac OS X as the Guest operating system and OS X 10.11 as the version.  By default, an OS X 10.11 folder will be created in your Documents\Virtual Machines folder.
       


      3.  Under Specify Disk Capacity, you can leave the default 40GB or set a larger value.  I personally store the virtual disk as a single file.  Click Finish and you will see OS X 10.11 on the Main Screen of Workstation 12.
       


      4.  Next, we need to edit the virtual machine settings to map the virtual SATA CD/DVD drive to the El Capitan installation iso we created earlier.
       


       
      5.  To prevent the virtual machine from crashing in Windows, the virtualHW.version set in the vmx configuration file needs to be changed from 12 to 10 (alternatively, the line smc.version = "0" can be added to the file).  The OS X 10.11.vmx file can be edited with the WordPad program (navigate to the OS X 10.11 virtual machine folder with Windows Explorer and right click on the file to open in WordPad).
       


       
      6.  For HW10, set USB compatibility to USB 2.0, otherwise your mouse and keyboard might not work in the virtual machine.
       

      7.  Finally click “Play virtual machine”
       

      Installation of El Capitan
      Installation should be relatively straight forward, just following the prompts of the OS X installer:
      1.  Select language, agree to legal terms
       

      2.  Use Disk Utility from the Utilities Menu to erase and format the virtual hard drive as a single partition GUID Mac OS X Extended.  I’ve named the drive Macintosh HD but you can enter whatever you like eg El_Capitan.
       



      3.  Quit DU and choose Macintosh HD to install El Capitan on.
       

      4.  After 20-30 min (depending on how fast your system is), the installation will complete and the VM will automatically reboot…
       

      5.  At the welcome screen, choose your country and keyboard layout.  You can skip transfer information, location services and logging in with your Apple ID if you wish…
       


      6.  Create a User Account and select your Time Zone.  You can skip sending diagnostics and usage data to Apple….
       


      7.  Finally, you will arrive at the El Capitan Desktop.  You should eject the Installation iso now by right clicking and selecting “Eject OS X Base System”.  This will allow you to install VMware Tools….
       



      8.  After rebooting, the VM can now be resized or run at full screen resolution.  Audio and network/internet should also work OOB.
       

       
      SMBIOS Customization and iMessage Vars
      To make the Virtual Machine more "Mac like", you can edit the vmx file to add unique identifiers from a real Mac's SMBIOS -
      eg for an iMac 11,3 SMBIOS, you can enter the following lines....
      smbios.reflectHost = "FALSE" board-id.reflectHost = "FALSE" board-id = "Mac-F2238BAE" hw.model.reflectHost = "FALSE" hw.model = "iMac11,3" serialNumber.reflectHost = "FALSE" serialNumber = "W80#######6" Refer How to spoof real Mac in VMware - Multi-booting and Virtualisation.
       
      The critical variables for iMessage/Facetime activation are MLB & ROM.  By default, VMware "reflects" the host's MLB and ROM since it assumes you are running the OSX guest on a real Mac host - see post#42 by @Donk.
       
      If the host is a Windows PC, the following lines need to be added to the vmx file (requires virtualHW.version 12 and smc.version = "0")....
      efi.nvram.var.ROM.reflectHost = "FALSE" efi.nvram.var.MLB.reflectHost = "FALSE" system-id.enable = "TRUE" and the MLB, ROM and optionally system-id entered manually eg
      efi.nvram.var.MLB = "W80######BA1A" (MLB can be 13 or 17 characters long, alphanumeric string) efi.nvram.var.ROM = "<=>?@A" (ROM is entered here as a 6 character ASCII string) uuid.bios = "## ## ## ## ## ## ## ##-## ## ## ## ## ## ## ##" <---Optional (if you want to inject a given system-id hexadecimal value) Note the output for ROM from imessage_debug is a 12 character hexadecimal that needs to be entered here as a 6 character ASCII string eg using an Hex to ASCII converter we find that "3c3d3e3f4041" hex is equivalent to   "<=>?@A".
       
      Vanilla Mavericks and Yosemite
      The same VM settings for El Capitan will also boot and run vanilla installations of OS X Mavericks and Yosemite .  Attached to this post are installer scripts to create bootable Mavericks (CMI.tool) and Yosemite (CYI.tool) ISOs for VirtualBox and VMware.
       
      With the respective OS X installer apps in the Applications folder, download and run the installer tools using terminal ie
       
      To create a Mavericks ISO on your desktop
      cd downloads chmod +x CMI.tool ./CMI.tool To create a Yosemite ISO on your desktop
      cd downloads chmod +x CYI.tool ./CYI.tool Here is a screenshot of the VM running Mavericks 10.9.5...
       

       
      Enjoy
       
      Update for macOS 10.12 Sierra
      The above settings still work for macOS Sierra after upgrading to VMware Workstation 12.5 and unlocker 2.0.8 - see post #13.
       
      Update for macOS 10.13 High Sierra and 10.14 Mojave
      See post#30 for macOS_iso_cim.tool script to create ISO for macOS using Apple's createinstallmedia utility.
      Post#41 describes how to build "Install macOS ******.app" on the fly from installer files downloaded beforehand in /SharedSupport folder.
       
      Update for macOS 10.15beta Catalina
      See post Update for macOS Catalina 10.15beta
       
      CECI.zip
      CYI.tool.zip
      CMI.tool.zip
    • By David-B
      This version of VMware Unlocker is modified to support VMware Workstation 14. It has not undergone extensive testing, but from the little I have used it, it appears to be working properly on VMware Workstation 14.
       
      The original VMware Unlocker is available here: http://www.insanelymac.com/forum/files/file/339-unlocker/
       
      The changes that were made to the code to enable this patcher to work are available here: http://www.insanelymac.com/forum/topic/303311-workstation-1112-player-712-fusion-78-and-esxi-6-mac-os-x-unlocker-2/?p=2503855. Other than this change, only the install scripts and the patcher exe for Windows was modified.
    • By Donk
      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
    • By phantom2000
      I'm tyring to run iATKOS S3 V2 on VMware Fusion 6(on Mavericks). I tried to set up Fusion with the iso file but when I start the VM, it says "The guest operating system is not MacOS X Server". Then I have downloaded the Fusion Unlocker v1.2.0 but I can't seem to get it to work. I have taken the execution permissions for the files install.sh, uninstall.sh and Unlocker.osx file by running the following commands,
      sudo chmod +x /Users/tim/Desktop/VMware/unlock-all-v120/osx/install.sh sudo chmod +x /Users/tim/Desktop/VMware/unlock-all-v120/osx/uninstall.sh sudo chmod +x /Users/tim/Desktop/VMware/unlock-all-v120/osx/unlocker.osx Then I tried to run the install.sh script using the command,
      sudo /Users/tim/Desktop/VMware/unlock-all-v120/osx/install.sh But I get this error message,
      TimBok:~ tim$ sudo /Users/tim/Desktop/VMware/unlock-all-v120/osx/install.sh Password: VMware Unlocker 1.2.0 =============================== Copyright: Dave Parsons 2011-13 Patching... /Users/tim/Desktop/VMware/unlock-all-v120/osx/install.sh: line 12: ./Unlocker.OSX: No such file or directory TimBok:~ tim$ I need to know what I can do here to get rid os this issue and run the VM.
×