Is there anyone that is using vCenter server that IS NOT having issues like most people? If so please provide details on your setup. (vCenter standalone or appliance? Hardware? etc..)
How not compatible is it? Should ESXi hosts patched with Unlocker not even be added to a vCenter server? Or is it just that the OS X VMs shouldn't be created, modified, or connected to through the console while connected to a vCenter server?
Is anyone looking into making it compatible with vCenter? Anyone know if it's even possible or impossible? Interested in knowing why it won't work with vCenter.
My thoughts are:
1. Everyone has these issues as unless you are running ESXi on real Apple hardware, certain HOST variables are incorrectly set. To get around that currently the ESXi Host BIOS and Apple SMC driver would need to be hacked. There may well be other checks that vCenter makel.
2. I definitely wouldn't add it to vCenter. Had some reports that vCenter can mess up the unlocker especially if using vMotion.
3. At this point I persoanlly don't have the time or interest in hacking this any further. Whilst I do use VMware vCenter, this was actually a project I started to run on Workstation on Windows To be honest all my work and personal machines are now Macs so I don't need this patcher, but continue to help out because it was useful to me in the past, and is useful to others now.
Hey, guys. New here and having trouble trying to unlock vmware 9.0.1 with unlocker 1.1.0 (linux x86)
:$ uname -a
Linux 2.6.32-5-686 #1 SMP Mon Feb 25 01:04:36 UTC 2013 i686 GNU/Linux
VMware Unlocker 1.1.0
Copyright: Dave Parsons 2011-12
File mapped @0xb686c000 length 15339496
Found OSK0 @ 0xb71919ad
Found OSK1 @ 0xb71919dd
Found SRVR @ 0xb71a964a
File mapped @0xb6434000 length 19759872
Found OSK0 @ 0xb6e9384d
Found OSK1 @ 0xb6e9387d
Found SRVR @ 0xb6eab94e
File mapped @0xb65f3000 length 17930716
Found OSK0 @ 0xb6f3c24d
Found OSK1 @ 0xb6f3c27d
Found SRVR @ 0xb6f54d9a
File mapped @0xb70b6000 length 6646660
`../tools/darwin.iso' -> `/usr/lib/vmware/isoimages/darwin.iso'
`../tools/darwin.iso.sig' -> `/usr/lib/vmware/isoimages/darwin.iso.sig'
So far so good, I think. But when I open VMware Workstation 9.0.1 there is no "Mac OS" or "Server" option and does not recognize the iso image converted from a retail dmg using poweriso (wine hehe)
Am I missing something?
One more question:
I've downloaded a vmware image of Mountain Lion
the one with this description
OS X 10.8 Mountain Lion Retail
Courtesy of ZackehSoul
Last thing, when I install and unistall the unlocker, the addresses change
for instance (real one):
First time: Found OSK0 @ 0xb71bb9ad
Second time: Found OSK0 @ 0xb71919ad
Is that OK?
Tried to unlock two different ways: stopping vmware daemons and not stopping (/etc/init.d/vmware[-workstation-server, -USBArbitrator] stop)
Thanks in advance for helping me ^^
1. No entry in dialog is my fault it is a bug in unlocker when running on 32-bit Linux which is what you have. It is fine on 64-bit Linux and VMware. I will look at it (again as I forgot about it!), but not until weekend due to work commitments.
2. Any "distro" isn't really supported as we don't know what has been added to it. You can create an ISO from the DMG or APP but the instructions are on my desktop machine. Will update later.
3. Address changes are fine as it is the loaded address of the executable not the file offset.