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

I'm on win7 x64, i have UAC disabled.

 

used unlocker202, removed lines 8-11 from win-install.cmd to make it run.

upgraded the 10.9 virtual machine, i added smc.version = 0 in the mavericks .vmx

 

all good, thanks!

Share this post


Link to post
Share on other sites
Advertisement

With hardware compatible mode for workstation11, I added vmx smc.version = "0" in .vmx.

Mavericks and Yosemite work good.

But, Snow Leopard (not Server) occurred boot time error "The guest operating system is not MAC OS X Server" and turn off.

Anyone have a good idea?

 

Workstation11, patched unlocker 2.0.2.

Share this post


Link to post
Share on other sites

With hardware compatible mode for workstation11, I added vmx smc.version = "0" in .vmx.

Mavericks and Yosemite work good.

But, Snow Leopard (not Server) occurred boot time error "The guest operating system is not MAC OS X Server" and turn off.

Anyone have a good idea?

 

Workstation11, patched unlocker 2.0.2.

 

As per the readme file, I haven't found how to bypass the OS X Server check..

Share this post


Link to post
Share on other sites

Hello,

 

I previously had VMware Workstation 10 on a Ubuntu Linux 12.04 LTS and upgraded (by uninstalling the reinstalling everything from scratch) to VMware Workstation 11 with Unlocker 2.0.2 yesterday. However, I can't properly use my OSX virtual machine from now on. Indeed, the VM crashes every 5 or 10 minutes and the following error message appears:

 
VMware Workstation unrecoverable error: (vcpu-0)
Unexpected signal: 11.
A log file is available in /home/...

post-1362041-0-04118400-1419270019_thumb.png

 

Do you have any idea about this kind of bug ? I attached here the error message and some logs.

 

Kind regards,

 

Extracted from vmware.log:

2014-12-22T18:06:51+01:00[+0.010]| vcpu-0| W110: Caught signal 11 -- tid 9424 (addr 0)
2014-12-22T18:06:51+01:00[+0.010]| vcpu-0| I120: SIGNAL: rip 0x0 rsp 0x7fbb3c44abc8 rbp 0x4
2014-12-22T18:06:51+01:00[+0.010]| vcpu-0| I120: SIGNAL: rax 0x0 rbx 0x1edef58 rcx 0x18 rdx 0xc9b860 rsi 0x7fbb3c44ac70 rdi 0x7fbae0021210
2014-12-22T18:06:51+01:00[+0.010]| vcpu-0| I120:         r8 0x1ec4398 r9 0x24d0 r10 0x0 r11 0x3246 r12 0x164 r13 0x7fbb4365eec0 r14 0x1a76e50 r15 0x7fbb4365eec0
2014-12-22T18:06:51+01:00[+0.010]| vcpu-0| I120: SIGNAL: stack 7FBB3C44ABC8 : 0x0000000000738a2d 0x0000000000000000
2014-12-22T18:06:51+01:00[+0.010]| vcpu-0| I120: SIGNAL: stack 7FBB3C44ABD8 : 0x0000000000000000 0x000000044361df00
2014-12-22T18:06:51+01:00[+0.011]| vcpu-0| I120: SIGNAL: stack 7FBB3C44ABE8 : 0x0000000001edaa00 0x0000000001edaa00
2014-12-22T18:06:51+01:00[+0.011]| vcpu-0| I120: SIGNAL: stack 7FBB3C44ABF8 : 0x00007fbb4362f3c0 0x0000000000000004
2014-12-22T18:06:51+01:00[+0.011]| vcpu-0| I120: SIGNAL: stack 7FBB3C44AC08 : 0x0000000400b13c16 0x00007fbb4365eec0
2014-12-22T18:06:51+01:00[+0.011]| vcpu-0| I120: SIGNAL: stack 7FBB3C44AC18 : 0x00007fbae001af00 0x0000000000000000
2014-12-22T18:06:51+01:00[+0.011]| vcpu-0| I120: SIGNAL: stack 7FBB3C44AC28 : 0x0000000000000000 0x00007fbb4362f3c0
2014-12-22T18:06:51+01:00[+0.011]| vcpu-0| I120: SIGNAL: stack 7FBB3C44AC38 : 0x00007fbb4361df00 0x00000000013cd400
2014-12-22T18:06:51+01:00[+0.011]| vcpu-0| I120: Backtrace:
2014-12-22T18:06:51+01:00[+0.012]| vcpu-0| I120: Backtrace[0] 00007fbb3c44a520 rip=00000000004f306e rbx=00000000004f2e40 rbp=0000000000000000 r12=00007fbb3c44b690 r13=00007fbb3c44ac48 r14=00007fbb3c44ac48 r15=000000000000000b
2014-12-22T18:06:51+01:00[+0.013]| vcpu-0| I120: Backtrace[1] 00007fbb3c44a550 rip=0000000000462c89 rbx=000000000000000b rbp=0000000000000004 r12=00007fbb3c44b690 r13=00007fbb3c44ac48 r14=00007fbb3c44ac48 r15=000000000000000b
2014-12-22T18:06:51+01:00[+0.013]| vcpu-0| I120: Backtrace[2] 00007fbb3c44a640 rip=00007fbb42e55cb0 rbx=0000000001edef58 rbp=0000000000000004 r12=0000000000000164 r13=00007fbb4365eec0 r14=0000000001a76e50 r15=00007fbb4365eec0
2014-12-22T18:06:51+01:00[+0.013]| vcpu-0| I120: Backtrace[3] 00007fbb3c44abc8 rip=0000000000000000 rbx=0000000001edef58 rbp=0000000000000004 r12=0000000000000164 r13=00007fbb4365eec0 r14=0000000001a76e50 r15=00007fbb4365eec0
2014-12-22T18:06:51+01:00[+0.013]| vcpu-0| I120: SymBacktrace[0] 00007fbb3c44a520 rip=00000000004f306e in function (null) in object /usr/lib/vmware/bin/vmware-vmx loaded at 0000000000400000
2014-12-22T18:06:51+01:00[+0.013]| vcpu-0| I120: SymBacktrace[1] 00007fbb3c44a550 rip=0000000000462c89 in function (null) in object /usr/lib/vmware/bin/vmware-vmx loaded at 0000000000400000
2014-12-22T18:06:51+01:00[+0.013]| vcpu-0| I120: SymBacktrace[2] 00007fbb3c44a640 rip=00007fbb42e55cb0 in function (null) in object /lib/x86_64-linux-gnu/libpthread.so.0 loaded at 00007fbb42e46000
2014-12-22T18:06:51+01:00[+0.014]| vcpu-0| I120: SymBacktrace[3] 00007fbb3c44abc8 rip=0000000000000000
2014-12-22T18:06:51+01:00[+0.014]| vcpu-0| I120: Unexpected signal: 11.
2014-12-22T18:06:51+01:00[+0.014]| vcpu-0| W110:
2014-12-22T18:06:51+01:00[+0.014]| vcpu-0| W110+ The core dump limit is set to ZERO; no core dump should be expected
2014-12-22T18:06:51+01:00[+0.200]| vcpu-0| W110: Core dumped.
2014-12-22T18:06:51+01:00[+0.201]| vcpu-0| I120: Core dump pipes to process /usr/share/apport/apport %p %s %c, core file unreliable
2014-12-22T18:06:51+01:00[+0.201]| vcpu-0| W110: A core file is available in "/home/psaxl/Machines virtuelles/OS X Mavericks/core"
2014-12-22T18:06:51+01:00[+0.201]| vcpu-0| W110: Writing monitor corefile "/home/psaxl/Machines virtuelles/OS X Mavericks/vmmcores.gz"
2014-12-22T18:06:51+01:00[+0.204]| vcpu-0| W110: Dumping core for vcpu-0
2014-12-22T18:06:51+01:00[+0.204]| vcpu-0| I120: Beginning monitor coredump
2014-12-22T18:06:51.892+01:00| mks| W110: Panic in progress... ungrabbing
2014-12-22T18:06:51.892+01:00| mks| I120: MKS: Release starting (panic).
2014-12-22T18:06:51.895+01:00| mks| I120: MKS: Release finished (panic).
2014-12-22T18:06:51.895+01:00| mks| W110: Panic in progress... ungrabbing
2014-12-22T18:06:51.895+01:00| mks| I120: MKS: Release starting (panic).
2014-12-22T18:06:51.895+01:00| mks| I120: MKS: Release finished (panic).
2014-12-22T18:06:51+01:00[+0.688]| vcpu-0| I120: End monitor coredump
2014-12-22T18:06:51+01:00[+0.688]| vcpu-0| W110: Dumping core for vcpu-1
2014-12-22T18:06:51+01:00[+0.688]| vcpu-0| I120: Beginning monitor coredump
2014-12-22T18:06:51+01:00[+1.442]| vcpu-0| I120: End monitor coredump
2014-12-22T18:06:51+01:00[+1.964]| vcpu-0| I120: Coredump encountered overflow 2075:2075 (350 duplicates)
2014-12-22T18:06:51+01:00[+2.192]| vcpu-0| I120: Backtrace:
2014-12-22T18:06:51+01:00[+2.192]| vcpu-0| I120: Backtrace[0] 00007fbb3c44a020 rip=00000000004f306e rbx=00000000004f2e40 rbp=0000000000000000 r12=0000000000000001 r13=00007fbb3c44ac48 r14=00007fbb3c44ac48 r15=000000000000000b
2014-12-22T18:06:51+01:00[+2.192]| vcpu-0| I120: Backtrace[1] 00007fbb3c44a050 rip=00000000004ce229 rbx=00007fbb3c44a070 rbp=00000000014c4260 r12=0000000000000001 r13=00007fbb3c44ac48 r14=00007fbb3c44ac48 r15=000000000000000b
2014-12-22T18:06:51+01:00[+2.192]| vcpu-0| I120: Backtrace[2] 00007fbb3c44a550 rip=0000000000462cd8 rbx=000000000000000b rbp=00007fbb3c44a580 r12=00007fbb3c44b690 r13=00007fbb3c44ac48 r14=00007fbb3c44ac48 r15=000000000000000b
2014-12-22T18:06:51+01:00[+2.192]| vcpu-0| I120: Backtrace[3] 00007fbb3c44a640 rip=00007fbb42e55cb0 rbx=0000000001edef58 rbp=0000000000000004 r12=0000000000000164 r13=00007fbb4365eec0 r14=0000000001a76e50 r15=00007fbb4365eec0
2014-12-22T18:06:51+01:00[+2.192]| vcpu-0| I120: Backtrace[4] 00007fbb3c44abc8 rip=0000000000000000 rbx=0000000001edef58 rbp=0000000000000004 r12=0000000000000164 r13=00007fbb4365eec0 r14=0000000001a76e50 r15=00007fbb4365eec0
2014-12-22T18:06:51+01:00[+2.193]| vcpu-0| I120: SymBacktrace[0] 00007fbb3c44a020 rip=00000000004f306e in function (null) in object /usr/lib/vmware/bin/vmware-vmx loaded at 0000000000400000
2014-12-22T18:06:51+01:00[+2.193]| vcpu-0| I120: SymBacktrace[1] 00007fbb3c44a050 rip=00000000004ce229 in function (null) in object /usr/lib/vmware/bin/vmware-vmx loaded at 0000000000400000
2014-12-22T18:06:51+01:00[+2.193]| vcpu-0| I120: SymBacktrace[2] 00007fbb3c44a550 rip=0000000000462cd8 in function (null) in object /usr/lib/vmware/bin/vmware-vmx loaded at 0000000000400000
2014-12-22T18:06:51+01:00[+2.193]| vcpu-0| I120: SymBacktrace[3] 00007fbb3c44a640 rip=00007fbb42e55cb0 in function (null) in object /lib/x86_64-linux-gnu/libpthread.so.0 loaded at 00007fbb42e46000
2014-12-22T18:06:51+01:00[+2.193]| vcpu-0| I120: SymBacktrace[4] 00007fbb3c44abc8 rip=0000000000000000
2014-12-22T18:06:51+01:00[+2.193]| vcpu-0| I120: Msg_Post: Error
2014-12-22T18:06:51+01:00[+2.193]| vcpu-0| I120: [msg.log.error.unrecoverable] VMware Workstation unrecoverable error: (vcpu-0)
2014-12-22T18:06:51+01:00[+2.193]| vcpu-0| I120+ Unexpected signal: 11.
2014-12-22T18:06:51+01:00[+2.193]| vcpu-0| I120: [msg.panic.haveLog] A log file is available in "/home/psaxl/Machines virtuelles/OS X Mavericks/vmware.log".  
2014-12-22T18:06:51+01:00[+2.193]| vcpu-0| I120: [msg.panic.requestSupport.withoutLog] You can request support.  
2014-12-22T18:06:51+01:00[+2.193]| vcpu-0| I120: [msg.panic.requestSupport.vmSupport.windowsOrLinux]
2014-12-22T18:06:51+01:00[+2.193]| vcpu-0| I120+ To collect data to submit to VMware support, choose "Collect Support Data" from the Help menu.
2014-12-22T18:06:51+01:00[+2.193]| vcpu-0| I120+ You can also run the "vm-support" script in the Workstation folder directly.
2014-12-22T18:06:51+01:00[+2.193]| vcpu-0| I120: [msg.panic.response] We will respond on the basis of your support entitlement.
2014-12-22T18:06:51+01:00[+2.193]| vcpu-0| I120: ----------------------------------------
2014-12-22T18:06:51+01:00[+92.433]| vcpu-0| I120: Exiting

post-1362041-0-04118400-1419270019_thumb.png

vmware.txt

OS X Mavericks.vmx.txt

Share this post


Link to post
Share on other sites

 

Hello,

 

I previously had VMware Workstation 10 on a Ubuntu Linux 12.04 LTS and upgraded (by uninstalling the reinstalling everything from scratch) to VMware Workstation 11 with Unlocker 2.0.2 yesterday. However, I can't properly use my OSX virtual machine from now on. Indeed, the VM crashes every 5 or 10 minutes and the following error message appears:

 

 

Can you add smc.vrsion = "0"  to vmx file as documented in readme.txt or downgrade virtual hardware to version 10.

Share this post


Link to post
Share on other sites

I've just tried this (downgrading to VM10 the virtual hardware and setting smc.version to value "0") but the same problem still occurs unfortunately... Here are some logs

 

You are running a distro from ZackehSoul. We don't support anything other than vanilla OS X as there is usually a load of kexts and other things that interfere with running OS X on VMware. Can you re-try using a clean installation of OS X  so we can rule that in or out of the problem please? .

I can confirm psaxl's crash (running on F20, x64, kernel 3.17.4-200). largely identical backtrace, trying to run any of 10.9 or 10.10

 

Can you attach a vmware.log to a post please? I should point out that the unlocker actually does very little to the core VMX executable, and there are reports of signal 11 errors for Workstation on Linux not related to unlocking VMX..

 

 

Can you both ensure you do not have 3D graphic s acceleration selected for the VM? This is a known issue for Workstation on Linux, and can cause signal 11.

Share this post


Link to post
Share on other sites

I have same problem with unexpected signal:

 

 

VMware Workstation unrecoverable error: (vcpu-0)
Unexpected signal: 11.

 

Running Ubuntu 14.04 as host OS and OS X 10.9 as guest. Seems to be linux host specific problem. However I found workaround, just disable sound card in virtal machine preferences and this error will go away. Crash happens when OS X trying to make sound.

Share this post


Link to post
Share on other sites

Okay, I'm very reluctant to post, because I'm sure I've messed something up or misread, but aren't there supposed to be OSX options when creating a new VM? I have none. Also, one of my VMs got switched away when I was investigating and I can't change it back. Not sure what to check next.

 

Host OS: Windows 8.1 Pro

VMware Workstation 11.0 (reinstalled clean to check)

Unlocker 2.0.2 (reapplied after clean reinstall of VMware Workstation)

 

Argh. As I feared, opened my mouth and removed all doubt.

 

Reinstalling VMW did nothing, as did repairing, but I did a full on complete remove, reboot, manual check for leftover bits, reboot, install, reboot, unlocker, reboot, launch VMW cycle, and now the OSX guest options are back. Sorry for the trouble.

Share this post


Link to post
Share on other sites

You are running a distro from ZackehSoul. We don't support anything other than vanilla OS X as there is usually a load of kexts and other things that interfere with running OS X on VMware. Can you re-try using a clean installation of OS X  so we can rule that in or out of the problem please? .

 

Can you attach a vmware.log to a post please? I should point out that the unlocker actually does very little to the core VMX executable, and there are reports of signal 11 errors for Workstation on Linux not related to unlocking VMX..

 

 

Can you both ensure you do not have 3D graphic s acceleration selected for the VM? This is a known issue for Workstation on Linux, and can cause signal 11.

 

Weiredly im running a distro from ZackehSoul, but putting smc.version to value "0" Worked for me, Thanks a Lot donk for your unlocker. but im wondering, Yosemite is running slower on the vm11 than vm10, did i overlook anything?

Share this post


Link to post
Share on other sites

Hello

 

Firstly, thank you Donk for your amazing project! I really apreciate it!

 

 

I need help (i'm a begginer)

 

 

So, i'm trying to install Yosemite 10.10.1 (host is Win8.1 Pro VL x64 with a Haswell 4770K)

 

 

I'm using OS X Yosemite 10.10.1 (14B25) bootable USB (DMG File) [5.29 GB]

 

I installed VMware WS 11 > ran unlocker 2.0.3 > converted 'OS X Base System.dmg' to .iso using http://vu1tur.eu.org/tools/ > create a vm using default settings > smc.version = "0" added to .vmx file

 

 

When i power up, it gives this:

 

Error: http://i.imgur.com/aYREYH9.png ||| http://i.imgur.com/cyHZ0CP.png

Log: http://pastebin.com/hKvsHvBx

 

When '2015-01-06T15:41:42.632-02:00| vmx| I120: GuestRpcSendTimedOut: message to toolbox-dnd timed out.' pops in the log the error come out

 

 

 

What can it be?

 

 

 

Sorry for my bad english

 

 

Thanks :)

Share this post


Link to post
Share on other sites

Thanks Donk for the software! I am new to Mac and please help, everyone..

 

After installed Unlocker203, my Yosemite VM successfully boot up in VMware Workstation 11, but the resolution is limited to 1024x768, and a reminder for VMware Tools pop up. I tried to install the VMware Tools, but got the following error message instead:

 

"Could not find component on update server. Contact VMware Support or your system administrator".

 

The host PC is a 64-bit Ubuntu 14.10 with Xeon E3-1230v3 CPU/16GB/Nvidia Video Card/BenQ 1920x1080 Monitor. My Windows 7 Professional VM works fine under Workstation 11 for full screen 1920x1080 resolution.

 

The Guest Yosemite VM was made on a new MacBook Air Laptop that just purchased 2 days ago. I installed VMware Fusion 7 and no other updates or software installations on the laptop. The VM was created using Recovery Partition as VMware documentation indicated. Works perfectly on the laptop inside the Fusion 7.

 

I copied the VM across to the host PC, applied the Unlocker203 script with no issues. The VM boot up ok, but just resolution is restricted to 1024x768, and can't install VMware Tools. I did the software update and it works fine. I tried attach the 'vmware.log' file to this post, but the forum said "You aren't permitted to upload this kind of file".

 

Thanks in advance for the help...

Share this post


Link to post
Share on other sites

Thanks Donk for the software! I am new to Mac and please help, everyone..

 

After installed Unlocker203, my Yosemite VM successfully boot up in VMware Workstation 11, but the resolution is limited to 1024x768, and a reminder for VMware Tools pop up. I tried to install the VMware Tools, but got the following error message instead:

 

"Could not find component on update server. Contact VMware Support or your system administrator".

 

The host PC is a 64-bit Ubuntu 14.10 with Xeon E3-1230v3 CPU/16GB/Nvidia Video Card/BenQ 1920x1080 Monitor. My Windows 7 Professional VM works fine under Workstation 11 for full screen 1920x1080 resolution.

 

The Guest Yosemite VM was made on a new MacBook Air Laptop that just purchased 2 days ago. I installed VMware Fusion 7 and no other updates or software installations on the laptop. The VM was created using Recovery Partition as VMware documentation indicated. Works perfectly on the laptop inside the Fusion 7.

 

I copied the VM across to the host PC, applied the Unlocker203 script with no issues. The VM boot up ok, but just resolution is restricted to 1024x768, and can't install VMware Tools. I did the software update and it works fine. I tried attach the 'vmware.log' file to this post, but the forum said "You aren't permitted to upload this kind of file".

 

Thanks in advance for the help...

you need to manually install VMware Tools, pointing to the image VMware tools - Use iso image file - in the virtual cd device, when starting VM OS X.

Share this post


Link to post
Share on other sites

Thanks Donk for the software! I am new to Mac and please help, everyone..

 

After installed Unlocker203, my Yosemite VM successfully boot up in VMware Workstation 11, but the resolution is limited to 1024x768, and a reminder for VMware Tools pop up. I tried to install the VMware Tools, but got the following error message instead:

 

"Could not find component on update server. Contact VMware Support or your system administrator".

 

The host PC is a 64-bit Ubuntu 14.10 with Xeon E3-1230v3 CPU/16GB/Nvidia Video Card/BenQ 1920x1080 Monitor. My Windows 7 Professional VM works fine under Workstation 11 for full screen 1920x1080 resolution.

 

The Guest Yosemite VM was made on a new MacBook Air Laptop that just purchased 2 days ago. I installed VMware Fusion 7 and no other updates or software installations on the laptop. The VM was created using Recovery Partition as VMware documentation indicated. Works perfectly on the laptop inside the Fusion 7.

 

I copied the VM across to the host PC, applied the Unlocker203 script with no issues. The VM boot up ok, but just resolution is restricted to 1024x768, and can't install VMware Tools. I did the software update and it works fine. I tried attach the 'vmware.log' file to this post, but the forum said "You aren't permitted to upload this kind of file".

 

Thanks in advance for the help...

Tony,

11Al beat me to the draw, in Workstation 11 you cannot install the VMware Tools from the menu, it needs to be done manually. The tools are installed from the darwin.iso, which needs to be mounted via the CD/DVD drive, the iso is located in the tools directory of the unlocker203 and in the VMware Workstation installation directory. Once installed you should be able to change resolution.

Hello

 

Firstly, thank you Donk for your amazing project! I really apreciate it!

I need help (i'm a begginer)

So, i'm trying to install Yosemite 10.10.1 (host is Win8.1 Pro VL x64 with a Haswell 4770K)

 

I'm using OS X Yosemite 10.10.1 (14B25) bootable USB (DMG File) [5.29 GB]

 

I installed VMware WS 11 > ran unlocker 2.0.3 > converted 'OS X Base System.dmg' to .iso using http://vu1tur.eu.org/tools/ > create a vm using default settings > smc.version = "0" added to .vmx file

 

When i power up, it gives this:

 

Error: http://i.imgur.com/aYREYH9.png ||| http://i.imgur.com/cyHZ0CP.png

Log: http://pastebin.com/hKvsHvBx

 

When '2015-01-06T15:41:42.632-02:00| vmx| I120: GuestRpcSendTimedOut: message to toolbox-dnd timed out.' pops in the log the error come out

 

What can it be?

Sorry for my bad english

 

Thanks :)

lllFATAL1TY,

 

You need to create a DMG file which includes the Base System, have a look at the following topic it has all the steps required to install Yosemite in VMware Workstation 11:

 

http://www.insanelymac.com/forum/topic/290949-how-to-install-os-x-10x-snow-leopard-lion-mountain-lion-mavericks-and-yosemite-in-vmware-workstation-1011-or-player-67/

Share this post


Link to post
Share on other sites

post-1239015-0-87417400-1420622352_thumb.png

 

Hi 11Al and MSoK,

 

Thanks for the reply. After mapping drive to that .iso file, installation of the VMware Tools can be started but can not be finished. Please see attached the screen snapshot for detail. Just before I could click 'restart' button, the error message window pop up, and close that window will close the Workstation 11 window as well. 

 

I must missed something here..

 

 

Share this post


Link to post
Share on other sites

tonyyz05,

Try turning off the sound card before starting the VM. Chaosmaster, pointed out that the error comes up everytime OS X tries to make a sound. His solution worked for me and I am now running the VM without a hitch (and without sound, also).

Still, I would like to find a fix for this bug as I would like to run GarageBand in the VM if possible.

 

Cheers.

Share this post


Link to post
Share on other sites

Hello everyone.

 

First thanks to Donk and everyone one who comtribute to the unlocker.

 

Quick questions :

 

  • Can this be used on Esxi 5.5U2 ?

 

Ps: I am running Maverick in esxi, whit GPU passtrough in vtd, (unlocker V1) and looking foward to upgrade to Yosemite.

Share this post


Link to post
Share on other sites

Hello everyone.

 

First thanks to Donk and everyone one who comtribute to the unlocker.

 

Quick questions :

 

  • Can this be used on Esxi 5.5U2 ?

 

Ps: I am running Maverick in esxi, whit GPU passtrough in vtd, (unlocker V1) and looking foward to upgrade to Yosemite.

 

No - use 1.3.1 for ESXi.

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.

Announcements

  • 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.
×