Workstation 8/9/10, Player 4/5/6 and Fusion 4/5/6 Mac OS X Unlocker

[thecrazy]

VMware Workstation Tech Preview 2 available: http://blogs.vmware.com/vsphere/2012/06/vmware-workstation-tech-preview-2-available.html

[Donk]

1.1.0 works with July 2012 preview.

[sebus]

Seems like the July preview has again the same problem of VERY LOOOOONG boot (like W8 did) if smc.present = "TRUE" exists

 

sebus

[Donk]

Seems like the July preview has again the same problem of VERY LOOOOONG boot (like W8 did) if smc.present = "TRUE" exists

 

sebus

What version of OS X are you running? I am not seeing any delays with Mountain Lion GM or Lion 10.7.4.

[DislikeYou]

I have problems installing VMware Tools on ML in both Workstation 1 and

Tech Preview 2.

 

When i have the vm configured with 1 GB ram and 1 cpu with 1 core then the tools installer hangs and never finishes installing.

 

When i change to 2gb ram and 2 cpu's with 2 cores, it finishes but gives an error that it could not be installed.

 

I tried darwin.iso from this thread. Also tried some VMware Tools for

Tech Preview 2 on mediafire. None works. Help please. Need to change resolutions.

[sebus]

What version of OS X are you running? I am not seeing any delays with Mountain Lion GM or Lion 10.7.4.

 

 

Ops, I forgot to run unlocker when I installed the update to latest Preview...

Hence it was staying on the PCI configuration line...

 

My bad!

[kup]

I'm getting black screens with the Tech Preview. The mouse cursors are there and I can network in to the VM but nothing is showing up on screen..

 

Any ideas?

[kevintap]

I'm not sure if this is the best place to post this, but I'm using VMWare Player 4.0.4 build-744019 (for linux). The libvmwarebase.so.0 file was not patched by the unlocker, and the unlocker reported no specific errors for this file. After I saw that the Mac OS X choices did not get enabled when creating a new VM, I dug into the source code for the unlocker (thanks for including it!). The signatures in my copy of libvmwarebase.so.0 are slightly different than what's hard-coded in the unlocker. I manually fixed up the lib and now I see the Mac OS X choices enabled when creating a new VM.

 

The signature to look for in my copy of libvmwarebase.so.0 is just 4 bytes shorter. I've commented the missing bytes below:

0x00, 0xA0, 0x00, 0x00, 0x00, 0x00, 0x00, 0x00, 0x10, 0x00, 0x00, 0x00, 0x08, 0x00, 0x00, 0x00,

0x02, 0x00, 0x00, 0x00, /*0x00, 0x00, 0x00, 0x00,*/ 0xDE, 0x00, 0x19, 0x00, 0x00, 0x00, 0x00, 0x00

[victrl2]

VMWare Workstation 9 with unlocker 1.1.0 works for me only after upgrade a VM hardware up to version 9.

Without VM update I have been seeing black screen.

 

PS: Lion 10.7.4

[Donk]

Version 1.1.0 worked with the Tech Previews and will work with Workstation 9. Make sure you update the virtual hardware to the version 9 compatibility level for maximum performance.

[thecrazy]

Version 1.1.0 worked with the Tech Previews and will work with Workstation 9. Make sure you update the virtual hardware to the version 9 compatibility level for maximum performance.

I confirm. Works perfect

[wizdude]

Version 1.1.0 worked with the Tech Previews and will work with Workstation 9. Make sure you update the virtual hardware to the version 9 compatibility level for maximum performance.

 

workstation 9 doesn't appear to be able to boot from a DMG file, however.

 

i have one machine with workstation 8 + 1.1.0 unlocker and I can build a new 10.7 VM and use the InstallESD.DMG from the Lion install mounted as a CD and it will boot directly and install the operating system.

 

if I try the same thing with workstation 9 + 1.1.0 unlocker, I can can configure the VM but when it goes to start up, EFI doesn't appear to find any valid boot source.

 

EFI shows:

 

Attempting to start up from:

-> EFI VMware Virtual IDE Hard Drive (IDE 0:0) ... unsuccessful

-> EFI VMware Virtual IDE CDROM Drive (IDE 1:0) ... unsuccessful

 

and it eventually goes into an EFI shell.

 

I have an ISO for Snow Leopard that I took from my original media and as an ISO file it starts up fine.

 

does anyone know an easy way to work around this? or am I going to have to convert my DMG images into ISO's?

 

cheers, wizdude.

[wizdude]

 

workstation 9 doesn't appear to be able to boot from a DMG file, however.

 

...

 

does anyone know an easy way to work around this? or am I going to have to convert my DMG images into ISO's?

 

just as a quick followup to this problem - i used the evaluation version of UltraISO to convert the DMG images into ISOS fairly easily on my PC and I can now boot directly from those ISO images with no problems.

 

i haven't yet done a full install, but the fact that the installer actually boots up and runs looks very promising

 

you can grab a trial version (not sure how long it lasts for, but I only needed it for a few hours :wink2:)

 

http://www.ezbsystems.com/ultraiso/

 

i've successfully converted my leopard, lion and mountain lion DMG's into ISO's.

 

for reference, I did also try vu1tur's dmg2img but it only worked on the leopard DMG. the other ones came up with an "ERROR: Inflation failed". I assume these DMG's contain a format unsupported by dmg2img. the leopard DMG I converted using this tool had the identical size and MD5/SHA1 hash to the one I converted using ultraiso.

 

cheers, wizdude

[darkmas]

I'm not sure if this is the best place to post this, but I'm using VMWare Player 4.0.4 build-744019 (for linux). The libvmwarebase.so.0 file was not patched by the unlocker, and the unlocker reported no specific errors for this file. After I saw that the Mac OS X choices did not get enabled when creating a new VM, I dug into the source code for the unlocker (thanks for including it!). The signatures in my copy of libvmwarebase.so.0 are slightly different than what's hard-coded in the unlocker. I manually fixed up the lib and now I see the Mac OS X choices enabled when creating a new VM.

 

The signature to look for in my copy of libvmwarebase.so.0 is just 4 bytes shorter. I've commented the missing bytes below:

0x00, 0xA0, 0x00, 0x00, 0x00, 0x00, 0x00, 0x00, 0x10, 0x00, 0x00, 0x00, 0x08, 0x00, 0x00, 0x00,

0x02, 0x00, 0x00, 0x00, /*0x00, 0x00, 0x00, 0x00,*/ 0xDE, 0x00, 0x19, 0x00, 0x00, 0x00, 0x00, 0x00

 

Thanks for this, as it also applies to: vmware-workstation 8.0.4.744019

 

Also (for donk/Zenith432/whomever) there is a bug that hides the issue - the "found" boolean is never initialized. That's why the unlocker reported no error for this file, see:

 

--- old/Unlocker.cpp	2012-09-18 05:43:44.628551015 -0700
+++ new/Unlocker.cpp	2012-09-18 05:49:47.762413836 -0700
@@ -1,4 +1,4 @@
-/*
+man/*
 *  Unlocker.cpp
 *
 *  Created by Zenith432 on September 25 2011.
@@ -224,7 +224,7 @@
 };
 unsigned char *p, *q;
 size_t l;
-	bool found;
+	bool found = false;

 p = static_cast<unsigned char*>(base);
 q = p + length;

 

-darkmas

[NickThompson]

I just updated to VMWare Player 5 (Windows 7 host) and my working 10.7.3 Lion guest stopped booting. I have reinstalled 4.0.4 and 5.0 several times, each time with and without the patcher. Has anyone else experienced this?

 

Is the patcher compatible with VMWare Player 5?

 

Ok - just managed to get 4.0.4 back up and running. Clean install, then ran install.cmd within the patcher inside a cmd.exe window which I ran as administrator. Now. Do I dare try the 5.0 update again

 

 

On a side note - I've updated to 10.7.4 once and it broke horribly. Anyone else had any luck? Is 10.7.5 better/safer? I use the VM for XCode stuff so really need to be on the latest 10.7.x or 10.8...

[MSoK]

I just updated to VMWare Player 5 (Windows 7 host) and my working 10.7.3 Lion guest stopped booting. I have reinstalled 4.0.4 and 5.0 several times, each time with and without the patcher. Has anyone else experienced this?

 

Is the patcher compatible with VMWare Player 5?

 

Ok - just managed to get 4.0.4 back up and running. Clean install, then ran install.cmd within the patcher inside a cmd.exe window which I ran as administrator. Now. Do I dare try the 5.0 update again

 

 

On a side note - I've updated to 10.7.4 once and it broke horribly. Anyone else had any luck? Is 10.7.5 better/safer? I use the VM for XCode stuff so really need to be on the latest 10.7.x or 10.8...

Nick,

 

The latest Unlocker (1.1.0) works fine with Workstation 9, Player 5 and ESXi 5.1, and is required to support OS X on non Apple hardware. With the latest versions Unlocked 10.7.4 and 10.7.5 work fine as well as 10.8.2, and both Lion and Mountain lion appear to perform much faster and boot quickly using the new VMware v9 products.

[ThinkpadFan]

[...]

The latest Unlocker (1.1.0) works fine with Workstation 9, [...] both Lion and Mountain lion appear to perform much faster and boot quickly using the new VMware v9 products.

 

Thank you very much for this information, MSoK!

Like Nick, I'm using VMware to develop iOS-apps in my virtual machine - so this is a somewhat mission critical application for me. I wanted to wait until this (WS v9 & OS X) is stable and proven working with a current OS X version, which seems to be the case now. I'm especially thrilled to read that it's supposed to perform better. Nice! :-)

[ElCoyote_]

Please also remember to upgrade the virtual hardware to the latest version (Fusion 5 or Workstation 9) for best results.

On Linux I'm still on 8.0.4 but on native MBP (10.7.5) with Fusion 5.0.1 and your unlocker allowed me to upgrade my Lion VM (10.7.3) to the latest patches (10.7.5) without any issue.

Note that I had upgraded the virtual hardware prior to applying the VM's OSX patches..

 

@Donk: Did you have a chance to take a look at darkmas' patch for Linux? I have not yet researched the issue either but that could maybe explain the differences I saw between choices for non-shared VMs and shared VMs...

 

Thank you once again for this great tool and for including the source too.

 

Nick,

 

The latest Unlocker (1.1.0) works fine with Workstation 9, Player 5 and ESXi 5.1, and is required to support OS X on non Apple hardware. With the latest versions Unlocked 10.7.4 and 10.7.5 work fine as well as 10.8.2, and both Lion and Mountain lion appear to perform much faster and boot quickly using the new VMware v9 products.

[NickThompson]

Nick,

 

The latest Unlocker (1.1.0) works fine with Workstation 9, Player 5 and ESXi 5.1, and is required to support OS X on non Apple hardware. With the latest versions Unlocked 10.7.4 and 10.7.5 work fine as well as 10.8.2, and both Lion and Mountain lion appear to perform much faster and boot quickly using the new VMware v9 products.

Thanks for the response - I just tried a clean uninstall (remove product, delete folder from Program files, reboot), clean install of Player 5 (install and reboot), then installed the unlocker using a command prompt running with admin prvieleges (right click, run as admin) to execute the install.sh.

 

My 10.7.3 VM booted first time, no errors. Gonna try the 10.7.5 combo update now. Will also try making a 10.8 VM later!

 

Cheers for the unlocker - nice work! Much appreciated.

[Donk]

@Donk: Did you have a chance to take a look at darkmas' patch for Linux? I have not yet researched the issue either but that could maybe explain the differences I saw between choices for non-shared VMs and shared VMs...

 

Not yet - work has been very busy. I will as soon as I can find some time to check thinks through I also need to update the tools and a couple of other ideas I want to checkout. I have a simple way of creating the ISO from InstallESD.dmg on Windows, something that has caused problems in the past.

[ElCoyote_]

@Donk: No problem at all, take your time and all the best with the work.

I'm not too fluent into ASM, opcodes or hexadecimal readings but you can count on me in testing whatever you need when you'll be ready.

Thanks,

[Sandro M. V.]

Thanks for the response - I just tried a clean uninstall (remove product, delete folder from Program files, reboot), clean install of Player 5 (install and reboot), then installed the unlocker using a command prompt running with admin prvieleges (right click, run as admin) to execute the install.sh.

 

My 10.7.3 VM booted first time, no errors. Gonna try the 10.7.5 combo update now. Will also try making a 10.8 VM later!

 

Cheers for the unlocker - nice work! Much appreciated.

 

Same for me, but whenever i restart the vm, it crashes, on apple's report after restarting it says something like:

 

I upgraded to 10.8.2 today, and i'm using vmware plyer 5.0 with unlocker 1.10.

 

Backtrace continues...

Kernel Extensions in backtrace:

com.apple.driver.AppleEFIRuntime(1.6.1)[b10B7564-7C23-3BCF-9836-2376AF7C3537]@0xffffff7f956b1000->0xffffff7f956b5fff

com.apple.driver.AppleSMC(3.1.3d11)[7064D9BE-B74C-3170-A097-0C5869B4E2CF]@0xffffff7f94b85000->0xffffff7f94b91fff

dependency: com.apple.iokit.IOACPIFamily(1.4)[A35915E8-C1B0-3C0F-81DF-5515BC9002FC]@0xffffff7f94574000

 

Does someone knows about this error?

 

Thank you.

[RealNC]

Unlocker.cpp needs a minor fix. It needs to:

 

#include <unistd.h>

 

Otherwise it won't compile with GCC 4.7.2:

 

Unlocker.cpp: In function 'int {anonymous}::map_file(const char*, void**, size_t*)':
Unlocker.cpp:515:11: error: 'close' was not declared in this scope
Unlocker.cpp:521:11: error: 'close' was not declared in this scope
Unlocker.cpp:524:10: error: 'close' was not declared in this scope
Unlocker.cpp: In function 'int main(int, char**)':
Unlocker.cpp:628:14: error: 'geteuid' was not declared in this scope

 

However, when running it, it looks for libvmwarebase.so.0 in the wrong place:

 

$ sudo ./Unlocker.Linux /opt/vmware/lib/vmware/bin
Patching /opt/vmware/lib/vmware/bin/vmware-vmx
File mapped @0x7f3c6801b000 length 14494800
Found OSK0 @ 0x7f3c688609b5
Found OSK1 @ 0x7f3c688609ed
Found SRVR @ 0x7f3c6888470e
Patching /opt/vmware/lib/vmware/bin/vmware-vmx-debug
File mapped @0x7f3c67bd8000 length 18960552
Found OSK0 @ 0x7f3c685626d5
Found OSK1 @ 0x7f3c6856270d
Found SRVR @ 0x7f3c68586c76
Patching /opt/vmware/lib/vmware/bin/vmware-vmx-stats
File mapped @0x7f3c67d8c000 length 17177920
Found OSK0 @ 0x7f3c6860ad75
Found OSK1 @ 0x7f3c6860adad
Found SRVR @ 0x7f3c6863052e
Patching /opt/vmware/lib/vmware/bin/libvmwarebase.so.0
open failed No such file or directory

 

The actual place of that file is:

 

$ find /opt/vmware -type f -name libvmwarebase.so.0
/opt/vmware/lib/vmware/lib/libvmwarebase.so.0/libvmwarebase.so.0

 

This is true for both VMWare Workstation 8.0.4 and 9.0.0.

[rob12357]

Hey Guys,

 

I just attempted to upgrade from 10.7.3 which was working perfectly on my workstation 8 running on an i7 to Mountain Lion (10.8). Once the files copied over and the OSX restarted, the boot process got stuck on the grey EFI screen with the following errors:

 

EFI VMWare Virtual SCSI Hard Drive )0,0) ... unsuccessful

EFI Vmware Virtual IDE CDROM Drive (IDE 1:0) ... unsuccessful

EFI Network ...

 

After which it goes into the EFI Shell version 2.30 [1.0] showing the Shell> prompt

 

Unlocker Version: 1.1.0

VM Workstation Version: Tried both 8.0.2 and 9.0.0. Currently on 9.0.0 build-812388

OS: Windows 7 64bit

Currently running OSX: Lion 10.7.3

Trying to upgrade to OSX: Mountain Lion 10.8

Errors: Unable to boot after the installer copies OSX upgrade files. Shows EFI VMWare ... unsuccessful messages

 

 

I apologize if this is an old issue that has already been resolved. I did do a considerable amount of searching around before posting here. I would appreciate any help on this. Thanks!

 

-Rob

 

Any idea on how to tackle this one? Thanks

[Sandro M. V.]

Same for me, but whenever i restart the vm, it crashes, on apple's report after restarting it says something like:

 

I upgraded to 10.8.2 today, and i'm using vmware plyer 5.0 with unlocker 1.10.

 

Backtrace continues...

Kernel Extensions in backtrace:

com.apple.driver.AppleEFIRuntime(1.6.1)[b10B7564-7C23-3BCF-9836-2376AF7C3537]@0xffffff7f956b1000->0xffffff7f956b5fff

com.apple.driver.AppleSMC(3.1.3d11)[7064D9BE-B74C-3170-A097-0C5869B4E2CF]@0xffffff7f94b85000->0xffffff7f94b91fff

dependency: com.apple.iokit.IOACPIFamily(1.4)[A35915E8-C1B0-3C0F-81DF-5515BC9002FC]@0xffffff7f94574000

 

Does someone knows about this error?

 

Thank you.

 

Solved: I've removed fakesmc/ from S/L/E and it's working fine now...