Jump to content

ESXi 5 Mac OS X Unlocker


  • Please log in to reply
793 replies to this topic

#321
Cobretti

Cobretti

    InsanelyMac Protégé

  • Members
  • Pip
  • 6 posts
for anyone else in the same position I was - I just recently came across the thread and as I had already updated to ESX 5.1 and never ran Mac OS vm on it I jumped straight into the install without the patch since 5.1 was supposed to officially support it. I spent 2 days trying to get install going but would just get to the beach ball. I finally decided to use Donk's script and the install came up without issue at first start after reboot. So does not mean because 5.1 officially supports it that it will actually install (at least in my case it did not). I was using my Lion ESD install file. So run the patch if you stuck at that point instead of wasting time trying to get it going without the patch. Thanks Donk!

#322
MSoK

MSoK

    InsanelyMac Legend

  • Members
  • PipPipPipPipPipPipPip
  • 984 posts
  • Gender:Male
  • Location:Darlington UK
Just for clarification, VMware ESXi 5.1 Supports OS X including Mountain Lion, but ONLY on Apple hardware, in fact officially MacPro5,1 (Intel Xeon 56x Series) and Xserve3,1 (Intel Xeon 55xx Series), the MacPro was added with the release of 5.1.

So if you install ESXi 5.1 on any other hardware you will need the "Unlocker" currently v1.1.0, it removes the Apple hardware check amongst other things.

Hope this helps, MSoK.

#323
Lisecons

Lisecons

    InsanelyMac Protégé

  • Members
  • Pip
  • 1 posts
While reading trough some post I got the impression that installing Mountain Lion on ESX 5.1 would not be as straight forward as installing it on a regular mac. I originally came here to find out to install Mountain Lion on my Dell Poweredge 2900 server I keep at home for hobby and research purposes.
After reading some posts I decided to update my esxi 5.0 box to 5.1 and afterwards install unlocker 1.10 (you’re the man DONK!). This all went without a hitch. I subsequently and eagerly attached my Mountain Lion DMG image and started installing. Since I was warned that using an image would not work I was waiting for something to go wrong. It did not. The install went perfectly and, after a few reboots, I am confident enough to say is working without problems.
So just to let you all know installing and using Mountain Lion on a ESXi 5.1 box works. And as some have commented already it even works faster (suspend/restore) than before.
Thank you all for the valuable information you are all sharing on this forum. Keep it going.

#324
ekological

ekological

    InsanelyMac Protégé

  • Members
  • Pip
  • 1 posts
Here's an interesting situation I'm running into:

Asus P8B WS
Intel E3-1245 V2 Ivy bridge CPU
ESXi 5.1

- USB install drive created by restoring the base image, deleting the package link, copying the package files over, etc
- -v npci=0x2000 to boot
- The install under 5.1 seems to go a lot smoother (no insanely long waits) than under 5.0 or 5.0 update 1
- Once everything is installed and the system is running, I can reboot, shutdown, power up...no problem. I even updated the com.apple.Boot.plist to always do ncpi=0x2000 and installed VMWare tools or running a system update...not a problem
- If I touch anything....even create a backup of the virtual disk (vmkfstools -i <original vmdk>.vmdk -d thin <backup vmdk>.vmdk or change the size of the video RAM, the VM boots up fine, but I lose mouse and keyboard input to the console. It doesn't appear to be similar to the past where there was a wait of 10 - 15 minutes before the system becomes responsive as I see the cursor blinking (not sure if that happened before during the long wait periods). The keyboard and mouse do not function ever and I waited over a half an hour. VMWare tools appears to be running too (see it under the summary tab of the hypervisor client) and I'm able to click the power off button and it appears to shut down the VM gracefully.

Anyone else see this?

TIA,
Chester

#325
alexiskai

alexiskai

    InsanelyMac Protégé

  • Members
  • Pip
  • 11 posts
My install experience for 10.8: (this is on ESXi 5.1 on Dell R710 with unlocker 1.10 applied)

- First hurdle was how to create the VM as hardware version 9, since the vSphere desktop client doesn't support it. Had to go through vCenter Server's web client to create the empty VM.

- Once that was done, switched back to connecting directly to the host with the vSphere desktop client.

- Tried to boot from:
remotely attached 10.8 USB - nope
10.8 ISO mounted through virtual optical drive - nope
10.8 DMG mounted through virtual optical drive - nope
10.7.1 installer VMDK left over from previous adventures in ESX - yep

- Left the 10.8 ISO attached via the optical drive; installed 10.7.1 to empty VMDK; rebooted

- Installed 10.8.0 over 10.7.1; rebooted

- Installed VMware Tools (darwin.iso) that I pulled from Fusion 5; rebooted

- Installed 10.8.2 via Software Update; rebooted

Seems to be working fine now. Next hurdle, install Server and then migrate a bunch of stuff from the 10.7 VM that has a corrupted GUI.

#326
ddarvish

ddarvish

    InsanelyMac Protégé

  • Members
  • Pip
  • 2 posts
I did a seach and no luck so please dont blast me if it is somewhere in this thread but can i get step by step instructions on how to install the unlocker on esxi 5.1 and/or vcenter? if i connect the client directly to esxi i am able to boot osx no problem but when connected to vcenter server it gives me an error about not supporting darwin11 blah blah ... would i install the unlocker on the vcenter server or esxi or both? how would i go about doing it.. i iknow how to use putty and i know how to use scp but no where are there instructions on where to copy the files and what permissions i shoudl give them... i assume that after that i just type ./install.sh into the terminal but yeah.. i attempted to just copy them to root and run it but got some weird ran out of ROM memory etc and the whole server just crashed... please help (as a side note i worked hard right now taking those damn quizes to be able to post here so please be kind)

#327
Donk

Donk

    InsanelyMac Deity

  • Members
  • PipPipPipPipPipPipPipPipPipPip
  • 2,025 posts
  • Gender:Male
  • Location:Manchester UK

I did a seach and no luck so please dont blast me if it is somewhere in this thread but can i get step by step instructions on how to install the unlocker on esxi 5.1 and/or vcenter? if i connect the client directly to esxi i am able to boot osx no problem but when connected to vcenter server it gives me an error about not supporting darwin11 blah blah ... would i install the unlocker on the vcenter server or esxi or both? how would i go about doing it.. i iknow how to use putty and i know how to use scp but no where are there instructions on where to copy the files and what permissions i shoudl give them... i assume that after that i just type ./install.sh into the terminal but yeah.. i attempted to just copy them to root and run it but got some weird ran out of ROM memory etc and the whole server just crashed... please help (as a side note i worked hard right now taking those damn quizes to be able to post here so please be kind)


Firstly please use some capitals, carriage returns and punctuation. I find it hard to read posts like this.

1. Unlocker only works for ESXi and you cannot use vCenter to start the Mac VM. Known issue no workaround currently.
2. Please re-read the text file that comes with the unlocker - do NOT put in root of ESXi but copy and run from a datastore volume.

#328
Slonik

Slonik

    InsanelyMac Protégé

  • Members
  • Pip
  • 1 posts
Hi,
I got few problems with my ESXi. I'm using ESXi 5.1 and trying to run unlock downloaded from this forum. When I'm running it i got something as seen below.


/vmfs/volumes/505cacad-7c983265-ea01-000c29d08428/unlock-all-v110/esxi # ./insta
ll.sh
VMware ESXi 5.0 Unlocker 1.1.0
==============================
Copyright: Dave Parsons 2011-12
Patching files...
Patching bin/vmx
File mapped @0x3ffd31ae010 length 16877808
Found OSK0 @ 0x3ffd3bab225
Found OSK1 @ 0x3ffd3bab25d
Found SRVR @ 0x3ffd3bef2c6
Patching bin/vmx-debug
File mapped @0x3ffd31ae010 length 21344208
Found OSK0 @ 0x3ffd3cd7a65
Found OSK1 @ 0x3ffd3cd7a9d
Found SRVR @ 0x3ffd3d1c406
Patching bin/vmx-stats
File mapped @0x7416d0 length 19599544
Found OSK0 @ 0x115fb45
Found OSK1 @ 0x115fb7d
Found SRVR @ 0x11a53e6
Patching vmwarebase is not supported on this platform
Setting permissions...
Creating darwin.tgz...
bin/
bin/vmx
bin/vmx-debug
bin/vmx-stats
addr: 0, sz: 10439724, flags: 5
addr: 0x9f7094, sz: 2206732, flags: 6
bin/vmx: textPgs: 2548, fixUpPgs: 0
Aligning executable bin/vmx
addr: 0, sz: 11664156, flags: 5
addr: 0xb217b4, sz: 2242540, flags: 6
bin/vmx-debug: textPgs: 2847, fixUpPgs: 0
Aligning executable bin/vmx-debug
addr: 0, sz: 10573180, flags: 5
addr: 0xa1768c, sz: 2371892, flags: 6
bin/vmx-stats: textPgs: 2581, fixUpPgs: 0
Aligning executable bin/vmx-stats
Adding darwin.tgz to boot.cfg...
Acquiring lock /tmp/bootbank.lck
Copying darwin.vgz to /bootbank/darwin.vgz
Editing /bootbank/boot.cfg to add module darwin.vgz
Please now reboot the host system!

"Patching vmwarebase is not supported on this platform" this is my problem i think becouse I got the same problem on VM Workstation on my Win 7 x64 OS. When i managed to patch this file my OSX started to work. Can some one help me whit this problem?

And secound question I got my ESXi on the Supermicro PDSMI+ Mother Board. It got two sepered intel chips for the LAN: 82573V and 82573L. The problem is that the ESXi 5.1 is not working properli whit it. But the VMware HCL says that it is compatible whit it. I read somewher that the 5.0 works grate whit 82573V and 82573L. How I can change the drivers in the 5.1?

#329
alexiskai

alexiskai

    InsanelyMac Protégé

  • Members
  • Pip
  • 11 posts
We are having an issue with the unlocker. After the unlocker patch has been installed on an ESXi host, no non-Mac VMs can start on that host; in addition, non-Mac VMs created on that host will not easily start on other hosts - they have to be tinkered with first. Has anyone else seen this behavior and is there any fix?

#330
Donk

Donk

    InsanelyMac Deity

  • Members
  • PipPipPipPipPipPipPipPipPipPip
  • 2,025 posts
  • Gender:Male
  • Location:Manchester UK

Hi,
I got few problems with my ESXi. I'm using ESXi 5.1 and trying to run unlock downloaded from this forum. When I'm running it i got something as seen below.


"Patching vmwarebase is not supported on this platform" this is my problem i think becouse I got the same problem on VM Workstation on my Win 7 x64 OS. When i managed to patch this file my OSX started to work. Can some one help me whit this problem?

And secound question I got my ESXi on the Supermicro PDSMI+ Mother Board. It got two sepered intel chips for the LAN: 82573V and 82573L. The problem is that the ESXi 5.1 is not working properli whit it. But the VMware HCL says that it is compatible whit it. I read somewher that the 5.0 works grate whit 82573V and 82573L. How I can change the drivers in the 5.1?


There is no vmwarebase to patch on ESXi so that is the correct output. Only Workstation and Player vmwarebase libraries are patched with the unlocker.

We are having an issue with the unlocker. After the unlocker patch has been installed on an ESXi host, no non-Mac VMs can start on that host; in addition, non-Mac VMs created on that host will not easily start on other hosts - they have to be tinkered with first. Has anyone else seen this behavior and is there any fix?


No have had no problems. What do you mean "tinkered with"?

#331
AidanLinz

AidanLinz

    InsanelyMac Protégé

  • Members
  • Pip
  • 8 posts
  • Gender:Male
  • Location:Chapel Hill, NC

No have had no problems. What do you mean "tinkered with"?


Donk, in reference to alexiskai-- I've isolated the source of the problem down to this snippet from the logs:


2012-11-06T05:21:12.760Z [314F4B90 warning 'Libs'] VMHSSpawnVMXUW: unable to spawn /bin/vmx: Operation not permitted
2012-11-06T05:21:12.760Z [314F4B90 info 'Libs'] VigorClient_StartAndConnect Failed: Failed to launch peer process

 /bin/vmx
Error during version check: Failed to get vmkernel version: 0xffffffff

I can provide more of the logs if they'd be helpful. I cloned the machine in question and that was the first attempt to power it on (it's been 3 so far that have fallen victem to the no-power-on issue).

I don't remember what I did with migration to get the machines back on -- that was before I figured out what the cause was. As soon as I reverted unlocker, before rebooting, the machine powered on immediately.

#332
sebus

sebus

    InsanelyMac Sage

  • Members
  • PipPipPipPipPip
  • 276 posts
  • Gender:Male
  • Location:UK
I have seen this also happening on ESXi 5.0
That is why Unlocker best suits a single ESXi 5.x environment

sebus

#333
Donk

Donk

    InsanelyMac Deity

  • Members
  • PipPipPipPipPipPipPipPipPipPip
  • 2,025 posts
  • Gender:Male
  • Location:Manchester UK

Donk, in reference to alexiskai-- I've isolated the source of the problem down to this snippet from the logs:


2012-11-06T05:21:12.760Z [314F4B90 warning 'Libs'] VMHSSpawnVMXUW: unable to spawn /bin/vmx: Operation not permitted
2012-11-06T05:21:12.760Z [314F4B90 info 'Libs'] VigorClient_StartAndConnect Failed: Failed to launch peer process

/bin/vmx
Error during version check: Failed to get vmkernel version: 0xffffffff

I can provide more of the logs if they'd be helpful. I cloned the machine in question and that was the first attempt to power it on (it's been 3 so far that have fallen victem to the no-power-on issue).

I don't remember what I did with migration to get the machines back on -- that was before I figured out what the cause was. As soon as I reverted unlocker, before rebooting, the machine powered on immediately.


Is this a vCenter system? If so I am sorry to say the unlocker really doesn't work that well. Really only works with a standalone system as Sebus mentioned. I have tried to find what else is needed for vCenter and then vMotion etc., to work but haven't managed to find anything yet. (And I have been looking for a l long time!)

However these are the first logs I have seen on this so could you send me the vmx and vmware.log files from the original guest and a clone, please? And one other question you have you upgraded the ESXi version without re-running the unlocker?

#334
AidanLinz

AidanLinz

    InsanelyMac Protégé

  • Members
  • Pip
  • 8 posts
  • Gender:Male
  • Location:Chapel Hill, NC

Is this a vCenter system? If so I am sorry to say the unlocker really doesn't work that well. Really only works with a standalone system as Sebus mentioned. I have tried to find what else is needed for vCenter and then vMotion etc., to work but haven't managed to find anything yet. (And I have been looking for a l long time!)

However these are the first logs I have seen on this so could you send me the vmx and vmware.log files from the original guest and a clone, please? And one other question you have you upgraded the ESXi version without re-running the unlocker?


The vmware.log files for the machines themselves weren't written to by the power on attempts, so they won't be much use, that snippet came from hostd.log...I'll send it your way shortly.

I also just saw this in the kernel logs:

2012-11-06T04:30:40.418Z cpu0:6003)VmkAccess: 637: hostd-vix-poll: access denied:: dom:appDom(2), obj:vmxSys(66), mode:syscall_allow(2)
2012-11-06T04:37:19.983Z cpu0:6003)VmkAccess: 637: hostd-vix-poll: access denied:: dom:appDom(2), obj:vmxSys(66), mode:syscall_allow(2)
2012-11-06T05:21:12.758Z cpu5:6003)VmkAccess: 637: hostd-vix-poll: access denied:: dom:appDom(2), obj:vmxSys(66), mode:syscall_allow(2)
2012-11-06T05:36:40.141Z cpu5:1037388)VmkAccess: 637: vmx: access denied:: dom:appDom(2), obj:vmxSys(66), mode:syscall_allow(2)
2012-11-06T05:36:46.002Z cpu3:1041489)VmkAccess: 637: vmx: access denied:: dom:appDom(2), obj:vmxSys(66), mode:syscall_allow(2)

Yes, it is a cluster -- though that host just got kicked out of it. We upgraded, re-applied unlocker, unapplied unlocker, and re-applied unlocker. :)
Thanks for the swift response!

#335
mattclarkdotnet

mattclarkdotnet

    InsanelyMac Protégé

  • Members
  • Pip
  • 1 posts
I just installed Vsphere 5.1 and Mountain Lion, and the whole thing went exceptionally smoothly. The system is a Supermicro X8ST3-F with 12GB of RAM and a Xeon E5506.

Once Vsphere was installed I applied the patch, and used the hdiutil trick posted by Battmac to create the CD image for 10.8.2:

"The ISO image must be created from the Lion ‘InstallESD.dmg’ (you can open package contents and browse to the "ESD.dmg located in /Contents/Shared Support/InstallESD.dmg.) Using terminal on Mac OS: hdiutil convert InstallESD.dmg -format UDTO -o InstallESD.iso. This will result in a .cdr file (.iso.cdr). You simply remove the ".cdr" and keep the ".iso" I then copied the .iso to a "local" storage on my ESXi box, and pointed the installer to the iso... "

Booted the VM and Mountain Lion installed and is very happy.

Many thanks to every here!

#336
reebzor

reebzor

    InsanelyMac Protégé

  • Members
  • Pip
  • 16 posts
  • Gender:Male
Weird issue- I had everything set up and running on ESXi 5.0U1, updated to 5.1, reapplied the patch, rebooted and none of my Mac VMs will start. I get a Circle Slash, and they just sit there. All of my other VM's start up just fine. Any Ideas?

FYI I am using the HP customized ESXi image (but I also used the HP customized 5.0U1 and that worked just fine)

EDIT: Also, my host was in maintenance mode when I applied the patch, could this cause an issue?

UPDATE Uninstalled the patch, rebooted, re-installed the patch, rebooted- All my VM's boot up in under a minute, and it no longer asks me a question about multiple CPUs!

#337
Ormond

Ormond

    InsanelyMac Protégé

  • Members
  • Pip
  • 1 posts
Hi,

I've applied the unlocker to install OS X 10.6 on our ESXi 5. worked perfectly. But if I try to run the installer, I get a kernel panic as soon as the Apple-splash screen is visible:

The guest OS panicked. The first line of the panic report is: panic(cpu 0 caller 0x2a6ac2): Kernel trap at 0x1b5b4d25, type 6=invalid opcode, registers:

I've tried to set npci=0x2000, enabling / disabling NX/XD-Bit, tried the EFI Shell, set the Intel VT-x setting, but nothing seems to help.

Setting
cpuid.80000001.eax = "0000:0000:0000:0001:0000:0110:1010:0101"
or
cpuid.1.eax = "0000:0000:0000:0001:0000:0110:1010:0101"
Doesn't help either.

The ESXI runs on an Intel Xeon E5606 CPU and the installation image is a DMG of the 10.6 installation DVD.

Is this Host system incompatible with OX X?

I coudn't find any other hint on the net.

Attached Files



#338
MSoK

MSoK

    InsanelyMac Legend

  • Members
  • PipPipPipPipPipPipPip
  • 984 posts
  • Gender:Male
  • Location:Darlington UK

I just installed Vsphere 5.1 and Mountain Lion, and the whole thing went exceptionally smoothly. The system is a Supermicro X8ST3-F with 12GB of RAM and a Xeon E5506.

Once Vsphere was installed I applied the patch, and used the hdiutil trick posted by Battmac to create the CD image for 10.8.2:

"The ISO image must be created from the Lion ‘InstallESD.dmg’ (you can open package contents and browse to the "ESD.dmg located in /Contents/Shared Support/InstallESD.dmg.) Using terminal on Mac OS: hdiutil convert InstallESD.dmg -format UDTO -o InstallESD.iso. This will result in a .cdr file (.iso.cdr). You simply remove the ".cdr" and keep the ".iso" I then copied the .iso to a "local" storage on my ESXi box, and pointed the installer to the iso... "

Booted the VM and Mountain Lion installed and is very happy.

Many thanks to every here!

Just for completeness ESXi 5.1 will allow you to mount and install L or ML directly from the InstallESD.dmg file rather than converting to an ISO. However this is not the case for Workstation 9 and Player 5, they do not support mounting the DMG file, so converting to an ISO is still required for these platforms.

Hi,

I've applied the unlocker to install OS X 10.6 on our ESXi 5. worked perfectly. But if I try to run the installer, I get a kernel panic as soon as the Apple-splash screen is visible:

The guest OS panicked. The first line of the panic report is: panic(cpu 0 caller 0x2a6ac2): Kernel trap at 0x1b5b4d25, type 6=invalid opcode, registers:

I've tried to set npci=0x2000, enabling / disabling NX/XD-Bit, tried the EFI Shell, set the Intel VT-x setting, but nothing seems to help.

Setting
cpuid.80000001.eax = "0000:0000:0000:0001:0000:0110:1010:0101"
or
cpuid.1.eax = "0000:0000:0000:0001:0000:0110:1010:0101"
Doesn't help either.

The ESXI runs on an Intel Xeon E5606 CPU and the installation image is a DMG of the 10.6 installation DVD.

Is this Host system incompatible with OX X?

I couldn't find any other hint on the net.

OK, not sure why you are having a problem, firstly your processor appears to support VT-x, so ensure it is enabled in BIOS. Also I think ESXi 5.1 is the first non Fusion iteration of VMware to support mounting a DMG image, and I have always installed SL from either the original "Retail" DVD or an ISO image of the "Retail" version, not the rebuild version supplied with Mac hardware at the time. Secondly you need to create the VMX configuration file (which you appear to have done), and add the CPUID mask as per the original topic, as your Xeon 5600 series processor is not supported by the 10.6.3 installation media, before trying to boot your OS X VM, see below:

http://www.insanelym...r/#entry1551966

Finally installation will only work in your vSphere client if you are directly logged on to the specific ESXi host, not via vCenter Server.

I can confirm that SL installation on Xeon 5600 series hardware using both ESXi 5 and 5.1 with the latest 1.1.0 "Unlocker" is both possible and works fine.

#339
madmax14304

madmax14304

    InsanelyMac Protégé

  • Members
  • Pip
  • 6 posts
Is it safe to say that this unlocker will NOT work on an esxi 5 host that's running on an AMD processor? Those new 16-core AMD chips look enticing but not if I'm going to lose access to my guest OS X VM. Thanks

#340
MSoK

MSoK

    InsanelyMac Legend

  • Members
  • PipPipPipPipPipPipPip
  • 984 posts
  • Gender:Male
  • Location:Darlington UK

Is it safe to say that this unlocker will NOT work on an esxi 5 host that's running on an AMD processor? Those new 16-core AMD chips look enticing but not if I'm going to lose access to my guest OS X VM. Thanks

In a word no, it is nothing to do with the "Unlocker", it simply enables existing OS X support feature, disabled by VMware on non Apple hardware. It is that Apple only use Intel CPU's and therefore currently no code to support AMD CPU's. So no Vanilla OS X on AMD, the only workaround is to use a modified kernel, not ideal.





1 user(s) are reading this topic

0 members, 1 guests, 0 anonymous users

© 2014 InsanelyMac  |   News  |   Forum  |   Downloads  |   OSx86 Wiki  |   Mac Netbook  |   PHP hosting by CatN  |   Designed by Ed Gain  |   Logo by irfan  |   Privacy Policy