Jump to content


  • Content count

  • Joined

  • Last visited

About Rubyducky

  • Rank
    InsanelyMac Protégé
  1. FWIW, Sierra installed and runs fine on 6.0 with the "Mac OS X 10.10" guest OS setting, which I think is the highest it goes on VM version 11
  2. Thanks so much! Looking forward to the new release. FWIW, the fix that allowed vCenter to start VMs appears to no longer work with vCenter 6.5 as well. It errors out with "darwin64 guest OS is not supported" before (or instead of) hitting the Transport VMDB error -45.
  3. I would be cautious upgrading to ESXi 6.5. I'm getting "Transport (VMDB) error -45: Failed to connect to peer process" when trying to start ANY VM with the Unlocker installed (from vCenter and the local vSphere Web Client since there's no C# client anymore). Running the Unlocker uninstall script lets non Mac VMs boot up again. Reinstalling the Unlocker (and I even did a clean install of ESXi 6.5) did not fix the error. Maybe I'm doing something terribly wrong, but can some one else verify this?
  4. El Capitan on VMWare

    I just tried installing the El Capitan public beta on ESXi 6.0 and subjectively, it looks like beamoff isn't working. Still getting jittery motion
  5. Status of Unlocker 2.0

    Really nice job!!! One tip, "beamoff" works wonders at improving graphics performance in Yosemite. Using the new VMRC for access, performance is almost the same as a real Mac!
  6. ESXi 5 Mac OS X Unlocker

    I just upgraded my hosts to 5.5 U2 and everything still seems to work with 1.3.0, 10.9.5, and vCenter. I did uninstall and reinstall the patch after upgrading, however.
  7. ESXi 5 Mac OS X Unlocker

    Ok yeah, it was the Workstation conversion. I had to create a new VM on ESXi and use Carbon Copy Cloner to clone the Workstation vmdk over to ESXi. Looks good so far, vCenter seems to still be working! Thanks so much for your work!
  8. ESXi 5 Mac OS X Unlocker

    1. Server CPU being used -Xeon E3-1245v3 2. Version of OS X being used -10.9.2 3. How you created the OS X bootable media -This is actually a converted Workstation 10 VM (I used the built-in ESXi converter). Currently I'm running nested virtualization with Workstation 10 inside a Windows VM. 4. Attach a copy of vmware.log from the guest folder (Please do NOT post inline on the reply) -http://pastebin.com/raw.php?i=EgztRNiM 5. Login to the support console and run: ls -la vmx and post output -No such file or directory, should I be running it in "/"? Thanks for your help! EDIT: Actually, I booted from the install ISO and it worked. Something must have not transferred from Workstation properly. I believe you can create a "SATA" type disk in Workstation now (and that's what I did), and it may not transfer to ESXi properly...
  9. ESXi 5 Mac OS X Unlocker

    My bad! In any case, I ran the patch from a datastore (and verified a scratch partition existed), restarted, but I'm stuck at the Apple logo and spinner...
  10. ESXi 5 Mac OS X Unlocker

    So does 1.4.0 fix the issues that come up when an ESXi server is managed by vCenter?
  11. ESXi 5 Mac OS X Unlocker

    Not sure if this has been mentioned...not even sure if it's worth mentioning! Since the unlocker isn't compatible with vCenter managed hosts, there's a very kludgey workaround: nested virtualization! If your hardware is compatible, you can bring up a Windows or Linux VM in ESXi, install Workstation or Player, apply the unlocker to Workstation or Player, and install Mac OS X in Workstation or Player. Here's a guide to see if your hardware is compatible and to enable nested virtualization support: http://www.virtuallyghetto.com/2012/08/how-to-enable-nested-esxi-other.html I was able to install Mavericks in Workstation in a Windows Server 2012 R2 VM, and it runs with no issues that I can tell. It's not even slow! Definitely not an ideal solution but it seems to work
  12. ESXi 5 Mac OS X Unlocker

    Quick note, I also could not get the console to work reliably similar to ipas. I am on ESXi 5.5 and am also using vCenter (5.5?). The console would work for a while, but then it would give the "Unable to connect" error on all VMs. I could not connect to the console through the web client, vSphere connected to vCenter, or even vSphere connected directly to the host. Restarting the VMs would bring the console back, but it would stop connecting again after a while. The host would also sporadically disconnect and reconnect to vCenter. Uninstalling the unlocker seems to have resolved everything. However, my other host running ESXi 5.1 and the unlocker but connected to the same vCenter server does not have these console connection issues.
  13. iDeneb v1.4 10.5.6 Released!

    Are the video drivers or kexts for the ATI X1650 71c6 available in a standalone installer?