Jump to content
Donk

macOS Unlocker V3.0 for VMware ESXi

By Donk, in Multi-booting and Virtualisation

21 posts in this topic

Recommended Posts

Donk    443

Donk
Posted (edited)

Verision 3 of the macOS Unlocker for VMware ESXi. Supports versions:

 

  • ESXi 6.5 and 6.7

 

https://www.insanelymac.com/forum/files/file/964-macos-unlocker-v30-for-vmware-esxi/

https://github.com/DrDonk/esxi-unlocker/releases/download/3.0.0/esxi-unlocker-300.tgz

https://github.com/DrDonk/esxi-unlocker/

 

readme.txt

 

Please note that this will not work if Secure Boot is enabled on the ESXi host. This is by design where VMware restricts what can be run when booted using Secure Boot.

Edited by Donk
Cybernut and nle reacted to this

Share this post

Link to post
Share on other sites
Advertisement

MSoK    117

MSoK
Posted

Donk,

 

Thanks for releasing the new ESXi unlocker, apologies for not keeping you updated, has been working fine for me since you sent me the pre-release version.

 

Cheers,
MSoK.

Share this post

Link to post
Share on other sites

youme    1

youme
Posted

I did update to 6.7U1 just yesterday and 3.0 continues to work.

 

I shut down my macos VMs, uninstalled unlocker, rebooted, updated ESXI, rebooted, re-installed unlocker again, rebooted and finally ... macos Mojave VM is back running ;)

 

Thanks

Balamut reacted to this

Share this post

Link to post
Share on other sites

sunborn    1

sunborn
Posted

This doesn't allow booting of new or migrated Mac OS X VMs on AMD machines even though the check script works.

 

It seems that AMD boards were never supported by unlocker. Will this change in the near future or am I SOL?

Share this post

Link to post
Share on other sites

Donk    443

Donk
Posted

The unlocker cannot make this work. AMD macOS kernels are needed because macOS does not support AMD CPUs. You will find the details on the forums for setting up an AMD Hackintosh.

 

I may add a warning to the unlocker installer but it is still useful if you have AMD macOS setup available.

Share this post

Link to post
Share on other sites

sunborn    1

sunborn
Posted (edited)
1 hour ago, Donk said:

The unlocker cannot make this work. AMD macOS kernels are needed because macOS does not support AMD CPUs. You will find the details on the forums for setting up an AMD Hackintosh.

 

I may add a warning to the unlocker installer but it is still useful if you have AMD macOS setup available.

I have had hackintoshes in the past, I am not a fan. The reason I am using VMware is to load it without hacks (at least no Mac hacks).

Are there any Intel chipsets that also don't agree? I am thinking in the server dual socket arena.

Edited by sunborn
grammar

Share this post

Link to post
Share on other sites

Donk    443

Donk
Posted

Intel chipsets shopuld not matter as VMware has a "virtual chassis" that it emulates, unklike the CPU which iit virtualises. Just make sure you get a CPU with VMX Unrestricted Guest mode, as that is a new dependency for VMware products. Of course needs, VT-x and EPT as well.

 

Share this post

Link to post
Share on other sites

i.r.    0

i.r.
Posted

@Donk Please add to readme chmod +x "filename". And most importantly a small bugreport: if you run ESXi on a server with Secure Boot ON, the scripts won't work.

Share this post

Link to post
Share on other sites

Donk    443

Donk
Posted (edited)
50 minutes ago, i.r. said:

@Donk Please add to readme chmod +x "filename". And most importantly a small bugreport: if you run ESXi on a server with Secure Boot ON, the scripts won't work.

What is missing +x? I just took a look at the archive and it was OK.

 

Yep - none of this will work with secure boot, which is a VMware design decision. No way around it but will add to readme for next release.

Edited by Donk

Share this post

Link to post
Share on other sites

i.r.    0

i.r.
Posted
28 minutes ago, Donk said:

What is missing +x? I just took a look at the archive and it was OK. 

  

Yep - none of this will work with secure boot, which is a VMware design decision. No way around it but will add to readme for next release.

 

I mean in the readme, before this step


"Run the command from the terminal:

    ./esxi-install.sh"

 

there should be

 

"chmod +x esxi-install.sh"

Share this post

Link to post
Share on other sites

Donk    443

Donk
Posted
56 minutes ago, i.r. said:

 

I mean in the readme, before this step


"Run the command from the terminal:

    ./esxi-install.sh"

 

there should be

 

"chmod +x esxi-install.sh"

 

I am still confused. The readme is correct you should not need the chmod command. The archive is uploaded to ESXi and use SSH or Tech Support Console to login and extract the contents. The permissions are correctly set in the gzipped tar file. Don't extract on another system and upload.

  

[root@vm-esxi670:/vmfs/volumes/5b41f592-268e512b-943f-000c29347f00] tar tzvf esxi-unlocker-300.tgz 
-rw-r--r-- dave/staff      4125 2018-09-27 07:02:45 unlocker.tgz
-rwxr-xr-x dave/staff       336 2018-09-27 07:02:45 esxi-install.sh
-rwxr-xr-x dave/staff       341 2018-09-27 07:02:45 esxi-uninstall.sh
-rwxr-xr-x dave/staff       189 2018-09-27 07:02:45 esxi-smctest.sh
-rw-r--r-- dave/staff      2629 2018-09-27 07:02:45 readme.txt

[root@vm-esxi670:/vmfs/volumes/5b41f592-268e512b-943f-000c29347f00/esxi-unlocker-300] ll esxi-*.sh
-rwxr-xr-x    1 501      20           336 Sep 27 07:02 esxi-install.sh
-rwxr-xr-x    1 501      20           189 Sep 27 07:02 esxi-smctest.sh
-rwxr-xr-x    1 501      20           341 Sep 27 07:02 esxi-uninstall.sh

 

 

Share this post

Link to post
Share on other sites

i.r.    0

i.r.
Posted
On 11/9/2018 at 9:58 PM, Donk said:

I am still confused. The readme is correct you should not need the chmod command. The archive is uploaded to ESXi and use SSH or Tech Support Console to login and extract the contents. The permissions are correctly set in the gzipped tar file. Don't extract on another system and upload.

 

Yeah you are right, i must have read the readme for the different version that also includes windows executables

Share this post

Link to post
Share on other sites

Donk    443

Donk
Posted

That's fine. I deliberately split ESXi fromn Windows/Linux so can have separate release schedules if needed.

Share this post

Link to post
Share on other sites

rteiouyr    0

rteiouyr
Posted

I am reporting that this fails for me when trying to apply to ESXI 6.7 U1 specifically ESXi-6.7.0-20181104001-standard

 

  • Testing with esx-smctest.sh returns smcPresent = false
  • It appears that ex-install.sh runs cleanly with no errors, the fixup just does not appear to be loaded
  • esxcli system visorfs tardisk list | grep custom.vgz returns nothing

 

@Donk, let me know what you need to troubleshoot. 

Share this post

Link to post
Share on other sites

gr4z    0

gr4z
Posted
On 11/20/2018 at 2:06 PM, Donk said:

I will take a look when I have some time, but unfortunately not at the moment.

Fresh install of 6.7u1, same problem for me. smcPresent=false

 

Works fine on another host which was 6.7 upgraded to 6.7u1.

Share this post

Link to post
Share on other sites

rteiouyr    0

rteiouyr
Posted (edited)

I figured out the problem. 

 

It turns out the previous install of Unlocker (208) was still on the system despite my having run the uninstall script. After running the 208 uninstall script, rebooting, running the 300 install script then rebooting, things appear to be working again. This is with a Mojave VM.

 

PS. I upgraded from 6.0 to 6.7...

Edited by rteiouyr

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
Go To Topic Listing Multi-booting and Virtualisation

  • Recently Browsing   0 members

    No registered users viewing this page.

  • Similar Content

    • MSoK
      VMware Tools for OS X (darwin.iso)
      By MSoK
      This is the current version of VMware Tools for OS X / macOS from the VMware CDS repository for Fusion 11.0.2
       
      Please note: In the latest VMwareGfx.kext from Fusion 8.5.5 onwards VMware have discontinued the 2D-Acceleration code, and graphics performance is better now, thanks to Zenith432 for the update.
       
      To check for the latest version visit http://softwareupdate.vmware.com/cds/vmw-desktop/fusion/. The various VMware Tools downloads are located under the packages folder for each version.
       
      Instructions for extracting darwin.iso
      - Download the file above
      - Extract com.vmware.fusion.tools.darwin.zip.tar
      - darwin.iso is located in the "payload" folder
      com.vmware.fusion.tools.darwinPre15.zip.tar
      com.vmware.fusion.tools.darwin.zip.tar
    • Donk
      macOS EFI Unlocker V1.0 for VMware
      By Donk
      Here is a new utility to patch the EFI firmware in VMware Workstation and Fusion to allow the non-server versions of Mac OS X 10.5 (Leopard) and 10.6 (Snow Leopard) to run. Yoiu will need macOS unlocker 3 if you are using Workstation on non-Apple hardware. I still have to find a way to do this on ESXi as the UEFIPatch utility will not run in the ESXi console.
      This currently supports:
       
      Workstation 11/12/14/15 on Windows and Linux Workstation Player 7/12/14/15 on Windows and Linux Fusion 10/11 on macOS  
      https://github.com/DrDonk/efi-unlocker/releases/download/1.0.0/efi-unlocker100.zip
      https://github.com/DrDonk/efi-unlocker
       
      Please read the readme.txt file for details.
      readme.txt
    • Donk
      macOS Unlocker V3.0 for VMware Workstation
      By Donk
      Verision 3 of the macOS Unlocker for VMware Workstation and Player. Supports versions:
       
      Workstation 11/12/14/15 on Windows and Linux Workstation Player 7/12/14/15 on Windows and Linux  
      https://www.insanelymac.com/forum/files/file/963-macos-unlocker-v30-for-vmware-workstation/
      https://github.com/DrDonk/unlocker/releases/download/3.0.2/unlocker302.zip
      https://github.com/DrDonk/unlocker/
      readme.txt
    • Donk
      macOS Unlocker V3.0 for VMware Workstation
      By Donk
      macOS Unlocker V3.0 for VMware Workstation ========================================== +-----------------------------------------------------------------------------+ | IMPORTANT: | | ========== | | | | Always uninstall the previous version of the Unlocker before using a new | | version. Failure to do this could render VMware unusable. | | | +-----------------------------------------------------------------------------+ 1. Introduction --------------- Unlocker 3 is designed for VMware Workstation 11-15 and Player 7-15. If you are using an earlier product please continue using Unlocker 1. Version 3 has been tested against: * Workstation 11/12/14/15 on Windows and Linux * Workstation Player 7/12/14/15 on Windows and Linux The patch code carries out the following modifications dependent on the product being patched: * Fix vmware-vmx and derivatives to allow macOS to boot * Fix vmwarebase .dll or .so to allow Apple to be selected during VM creation * Download a copy of the latest VMware Tools for macOS 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. In all cases make sure VMware is not running, and any background guests have been shutdown. The code is written in Python. 2. Prerequisites ---------------- The code requires Python 2.7 to work. Most Linux distros ship with a compatible Python interpreter and should work without requiring any additional software. Windows Unlocker 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 products are OK and do not show this problem. +-----------------------------------------------------------------------------+ | IMPORTANT: | | ========== | | | | If you create a new VM 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 macOS 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 macOS guest tools 6. 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 and modified the unlocker code to run on Python 3 in the ESXi 6.5 environment. History ------- 27/09/18 3.0.0 - First release 02/10/18 3.0.1 - Fixed gettools.py to work with Python 3 and correctly download darwinPre15.iso 10/10/18 3.0.2 - Fixed false positives from anti-virus software with Windows executables - Allow Python 2 and 3 to run the Python code from Bash scripts (c) 2011-2018 Dave Parsons  
    • Donk
      macOS Unlocker V3.0 for VMware ESXi
      By Donk
      macOS Unlocker V3.0 for VMware ESXi =================================== 1. Introduction --------------- Unlocker 3 for ESXi is designed for VMware ESXi 6.5 and 6.7. The patch code carries out the following modifications dependent on the product being patched: * Fix vmware-vmx to allow macOS to boot * Fix libvmkctl to allow vSphere to control the guest The code is written in Python as it makes the Unlocker easier to run and maintain on ESXi. +-----------------------------------------------------------------------------+ | IMPORTANT: | | ========== | | | | Always uninstall the previous version of the Unlocker before using a new | | version. Failure to do this could render VMware unusable. | | | +-----------------------------------------------------------------------------+ 2. Installation --------------- Copy the distribution file to the ESXi host datastore using scp or some other data transfer system. Decompress the file from the ESXi console or via SSH: tar xzvf esxi-unlocker-xxx.tgz (xxx - will be the version number, for example, 300) Run the command from the terminal: ./esxi-install.sh Finally reboot the server. 3. Uninstallation ----------------- Open the ESXi console or login via SSH and chnage to the folder where the files were extracted. Run the command from the terminal: ./esxi-uninstall.sh Finally reboot the server. 4. Notes -------- A. There is a command added called esxi-smctest.sh which can show if the patch is successful. It must be run from a terminal or SSH session. The output should be: /bin/vmx smcPresent = true custom.vgz false 38725560 B B. The unlocker can be temporarily disabled during boot by editing the boot options and adding "nounlocker". 5. 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 and modified the unlocker code to run on Python 3 in the ESXi 6.5 environment. The code is available at https://github.com/DrDonk/esxi-unlocker History ------- 26/09/18 3.0.0 - First release (c) 2011-2018 Dave Parsons  
×