Jump to content

Donk

Members
  • Content Count

    2,382
  • Joined

  • Last visited

  • Days Won

    3

Everything posted by Donk

  1. Unlocker 2.1 for latest VMware products. Important message - ESXi 6.x support has been removed from the Unlocker as it is too unreliable. Several methods have been tried but they cause random disconnects of vCenter and failure of the hostd daemon. Support will be added back if and when a reliable method is found. 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 Version 2.1.1 - http://www.insanelymac.com/forum/files/file/835-unlocker/ Please continue to use version 2.0.8 for ESXi 6.0. macOS Unlocker for VMware V2.1 ============================== +-----------------------------------------------------------------------------+ | 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 2 is designed for Workstation 11/12/14, Player 7/12/14, and Fusion 7/8/10. If you are using an earlier product please continue using Unlocker 1. Version 2 has been tested against: * Workstation 11/12/14 on Windows and Linux * Workstation Player 7/12/14 on Windows and Linux * Fusion 7/8/10 on macOS Sierra 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. The vmwarebase code does not need to be patched on macOS systems 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 written in Python as it makes the Unlocker easier to run and maintain on ESXi. 2. Prerequisites ---------------- The code requires Python 2.7 to work. Most Linux distros and macOS 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 using version 11, 12 or 13 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 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. macOS -------- On macOS 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 macOS. You may need to ensure the macOS scripts have execute permissions by running chmod +x against the 2 files. osx-install.sh - patches VMware osx-uninstall.sh - restores VMware 7. ESXi ------- ESXi is no longer supported as there are too many errors on newer versions due to VMware hardening the ESXi image. 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 and modified the unlocker code to run on Python 3 in the ESXi 6.5 environment. History ------- 10/10/17 2.1.0 - New version to support ESXi 6.5, Workstation/Player 14 and Fusion 10 - Removed support for ESXi 6.0 - Added ESXi boot option to disable unlocker (nounlocker) 11/10/17 2.1.1 - Removed all support for ESXi 6.x (c) 2011-2017 Dave Parsons
  2. 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.
  3. 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
  4. Version 3.0.0

    3,983 downloads

    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
  5. 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
  6. From previous post "VMware changed their VMware Tools website downloads format (file type) to a big compressed file, instead of directly downloadable, single small ISO file." FYI VMware are aware the tools are missing and the Fusion Product Manager is following it up. https://communities.vmware.com/thread/619357 The current core download is the entire Fusion app. If you need the tools I suggest logging into the VMware website and go here https://www.vmware.com/go/tools. If VMware does not re-instate the tools only download I will setup a mirror with tools only as I see no reason to download 500MB for 16MB of tools. At this point I'm not going to update the getools.py until I get an answer from VMware.
  7. There is no specific Catalina option in ESXi. You will have to use Mojave 10.14.
  8. I am planning to get back to the unlocker. I've been working on a work contract and so it's had to take a back seat. I have appointed another maintainer on github who is an ex-colleague of mine.
  9. There is no virus it's a false positive due to the use of Pyinstaller. It's happened before with the stub executable that is added to the zipped up Python code and interpreter.
  10. I will take a look at the new version. It shipped whilst I was on holiday and having a break from computers, internet etc.
  11. Trying an earlier Intel CPU from MacbookPro10,1. FreeBSD 64-bit.vmx.txt
  12. So this is the my next thoughts on this. I had to do a bit off checking because some things have changed in Workstation 14 & 15. I'm not sure if there is anythiong else we can do if this doesn't work apart from try and find a way to add an AMD kernel to the image. FreeBSD 64-bit.vmx.txt
  13. Sorry I missed following up on this. I will take a look and see if there is anything I can find but first guess is that an Intel instruction is being used and AMD does not implement it. Need to check the CPUID dumps for both processors.
  14. VMware will likely need to fix something or it's an issue with the beta. I wouldn't expect proper support until Catalina is released which is usually when VMware release a new version of Fusion/Workstation. September timeframe.
  15. Try this one first. again make a complete backup of the VM first. FreeBSD 64-bit.vmx.txt
  16. If you are using a version of VMware from 11 onwards the old method of patching the server check won't work as the code changed inside VMware. I did release some version of the unlocker 2 with a pre-patched BIOS but this causes issues as it would not match the currently version of the VMM monitor and may crash. For unlocker 3 there is no patcher built in but I released a separate tool the EFI Patcher that can work with Worsktation 14/15 and ESXi 6.5/6.7 that modifies a copy of the EFI BIOS/Firmware. That should be used now and there is a separate topic here
  17. Can you attach a copy of your VMX file to a post for the VM please? No guarantees but I havd found some old CPUID patching details that may work. Make sure you have a complete backup of this VM before we start.
  18. No use the new EFI Unlocker for Snow Leopard. The older version dfoesn't work anymore as VMware changed the code.
  19. Donk

    Unlocker

    Version 2.1.0

    26,957 downloads

    macOS Unlocker for VMware V2.1 ============================== +-----------------------------------------------------------------------------+ | IMPORTANT: | | ========== | | | | Always uninstall the previous version of the Unlocker before using a new | | version. Failure to do this could render VMware unusable especially ESXi. | | | +-----------------------------------------------------------------------------+ 1. Introduction --------------- Unlocker 2.1 is designed for Workstation 11/12/14, Player 7/12/14, ESXi 6.5 and Fusion 7/8/10. If you are using an earlier product please continue using Unlocker 1 and use Unlcoker 2.0 for ESXi 6.0 Version 2 has been tested against: * Workstation 11/12/14 on Windows and Linux * Workstation Player 7/12/14 on Windows and Linux * Fusion 7/8/10 on Sierra * ESXi 6.5U1 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 * Fix libvmkctl.so on ESXi 6 to allow use with vCenter * 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. The vmwarebase code does not need to be patched on macOS 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 written in Python as it makes the Unlocker easier to run and maintain on ESXi. 2. Prerequisites ---------------- The code requires Python 2.7 to work. Most Linux distros, ESXi and macOS 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 and ESXi products are OK and do not show this problem. +-----------------------------------------------------------------------------+ | IMPORTANT: | | ========== | | | | If you create a new VM using version 11, 12 or 13 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 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. macOS -------- On macOS 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 macOS. You may need to ensure the macOS 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 store and 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 There is a boot option for ESXi that disables the unlocker if there is a problem. At the ESXi boot screen press shift + o to get the boot options and add nounlocker. 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 needs to be re-run after an upgrade or patch is installed on the ESXi host. 3. The macOS VMwwre tools are no longer shipped in the image from ESXi 6.5. They have to be downloaded and installed manually onto the ESXi host. For additional details see this web page: https://blogs.vmware.com/vsphere/2016/10/introducing-vmware-tools-10-1-10-0-12.html 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 and modified the unlocker code to run on Python 3 in the ESXi 6.5 environment. History ------- 10/10/17 2.1.0 - New version to support ESXi 6.5, Workstation/Player 14 and Fusion 10 - Removed support for ESXi 6.0 - Added ESXi boot option to disable unlocker (nounlocker) © 2011-2017 Dave Parsons
  20. It may be possible to mask the CPU to look like Intel. Let me have a look. I did have a topic on this here but I can't find it now. Do you still have the machine with the CPU?
  21. Can you run chcp from the command line? You can also try chcp 850 and then running the installer.
  22. This has always been the case and I guess most folks knew it around here. So yes you have to re-run the unlocker after an upgrade to VMware.
  23. 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
  24. I did look at the files and then had a bad cold so forgot to reply. The bad news is there is nothing obvious about why it is not booting. I cannot re-create it with 15.0.2. So I at this stage I don't know what to look for next.
  25. Donk

    Threadripper ESXi and OSX VM

    macOS does not support AMD CPUs so you need to find an AMD kernel and build a setup using that, which is trickier than having an Intel CPU where macOS should just work in most cases. Unlocker cannot do anything about this.
×