Jump to content

ESXi 5 Mac OS X Unlocker


  • Please log in to reply
728 replies to this topic

#61
cfrogjump

cfrogjump

    InsanelyMac Protégé

  • Members
  • Pip
  • 4 posts

I have checked and there is no code checking for Xserve that I can see and it booted fine on my 2010 iMac and 2011 Macbook Pro. The Apple SMC driver loaded fine which is what the patch changes. However if you need to rely on Mac OS X, pick a supported solution! This is just an exercise in interest for me and would not rely on it to make money.

BTW new patch possibly tomorrow which works with ESXi500-201109001. I have it working just need to make a couple of changes to the scripts to fix a small problem with folders created.


You are correct. There is no code checking for the Xserve specifically. Possible driver issues and support from VMware is the only real problem with running in on something other than the Xserve. The only thing limiting ESXi on Apple Hardware is the SMC check, which your patch fixes.

Thanks for your hard work on this, it's so nice to be able to run OS X virtualized on ESXi and on non-Apple hardware. Now I can sell my old Mac Pro!

#62
Justinlu

Justinlu

    InsanelyMac Protégé

  • Members
  • Pip
  • 2 posts
Hi Donk,

Do you think is it possible to bypass the SMC check by inserting SMC device emulating code into DSDT?

Please refer to following topic:

http://www.insanelym...howtopic=170384

If it is possible, we may keep the ESXi binaries untouched.

Thank you for your hard working on Mac OS X visualization!

#63
Donk

Donk

    InsanelyMac Deity

  • Members
  • PipPipPipPipPipPipPipPipPipPip
  • 1,941 posts
  • Gender:Male
  • Location:Manchester UK

Hi Donk,

Do you think is it possible to bypass the SMC check by inserting SMC device emulating code into DSDT?

Please refer to following topic:

http://www.insanelym...howtopic=170384

If it is possible, we may keep the ESXi binaries untouched.

Thank you for your hard working on Mac OS X visualization!

Nope that technique doesn't work, you still need to emulate the device as it uses IO ports to read the haiku.

#64
sebus

sebus

    InsanelyMac Sage

  • Members
  • PipPipPipPipPip
  • 261 posts
  • Gender:Male
  • Location:UK
It seems that for Workstation 8 only fakesmc.kext is needed - http://www.insanelym...owtopic=268027#

Would not be the same for ESX5i ?

sebus

#65
Donk

Donk

    InsanelyMac Deity

  • Members
  • PipPipPipPipPipPipPipPipPipPip
  • 1,941 posts
  • Gender:Male
  • Location:Manchester UK

It seems that for Workstation 8 only fakesmc.kext is needed - http://www.insanelym...owtopic=268027#

Would not be the same for ESX5i ?

sebus

Yes but the patch means you do not need to hack the installation media.

#66
MSoK

MSoK

    InsanelyMac Legend

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

UPDATED 19/09/11

Here is the unlocker for the new VMware ESXi 5.0 updated for latest patch from VMware.

History
-------
1.0.0 - First release for ESXi 5.0 Build 469512
1.0.1 - Upate for Build 474610 and fixed a bug in shell scripts

Links:

ESXi 5.0.0 Build 469512 - http://goo.gl/mjhKo
ESXi 5.0.0 Build 474610 - http://goo.gl/nx8Xg

Donk has provided an updated "ESXi 5 Unlocker" which supports ESXi 5 updated with patch ESXi500-201109001.zip which takes ESXi 5.0.0 to build 474610.

The recommendation is to un-install the "ESXi 5 Unlocker (469512)", do a re-boot and then install the new version of the "ESXi 5 Unlocker (474610)" , again a re-boot will be required for the "Unlocker" to be activated.

Special thanks to Donk for the original "ESXi 5 Unlocker" and the updated version.

#67
HydroPhil

HydroPhil

    InsanelyMac Protégé

  • Members
  • Pip
  • 1 posts
This is great news! Thanks a lot to Donk for his continued efforts and time invested into giving us a feasible path towards deploying Mac OS X Server onto other hardware than Mac Pro or Mac mini...

The top notch feature would be to use vSphere vCenter Server to manage those VMs and/or migrate them from one ESXi to another.

Looking forward to see such a patch, and kudos again!
HydroPhil.

#68
crazyx

crazyx

    InsanelyMac Protégé

  • Members
  • Pip
  • 2 posts

ESXi 5.0.0 Build 474610 - http://goo.gl/nx8Xg

Thank you very much.....! Works great!

bye crazyx

#69
sebus

sebus

    InsanelyMac Sage

  • Members
  • PipPipPipPipPip
  • 261 posts
  • Gender:Male
  • Location:UK
Thank you!

sebus

#70
23adam23

23adam23

    InsanelyMac Protégé

  • Members
  • Pip
  • 3 posts
Help

Im getting an "invalid gzip magic" error when following the instructions.

see below
~ # cd /vmfs/volumes/datastore1/
/vmfs/volumes/4e7a5aaa-c372a8e3-9fe7-1078d2717a18 # tar -xzvf unlock-esxi500-469512.tgz
tar: invalid gzip magic

does it have anything to do with the datastore1 folder appearing renamed to the "4e7a....a18" string

thanks in advance
adam

#71
MSoK

MSoK

    InsanelyMac Legend

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

Help

Im getting an "invalid gzip magic" error when following the instructions.

see below
~ # cd /vmfs/volumes/datastore1/
/vmfs/volumes/4e7a5aaa-c372a8e3-9fe7-1078d2717a18 # tar -xzvf unlock-esxi500-469512.tgz
tar: invalid gzip magic

does it have anything to do with the datastore1 folder appearing renamed to the "4e7a....a18" string

thanks in advance
adam

Adam,

I had exactly the same problem, not sure why, the tgz appeared fine when I used winrar on my local Windows 7 PC.

So to resolve the problem I did the following:

Copy the unrared folder on to the ESXi 5 datastore, via vSphere Client or WinSCP. Then go to the console on the ESXi host ALT F1 log in as root and navigate to the copied folder. We need to change the permissions of the files, so use "chmod +rwx *.*" and also "chmod +rwx *", this will make all the files in the folder read, write, executable and they will be green if you do an "ls" (this may be overkill in terms of permissons but it works).

You should now be able to run the "./install.sh" command and get the output as described in Donk's readme.txt file.

Hope this helps, MSoK.

#72
pocopico1

pocopico1

    InsanelyMac Protégé

  • Members
  • Pip
  • 19 posts

Help

Im getting an "invalid gzip magic" error when following the instructions.

see below
~ # cd /vmfs/volumes/datastore1/
/vmfs/volumes/4e7a5aaa-c372a8e3-9fe7-1078d2717a18 # tar -xzvf unlock-esxi500-469512.tgz
tar: invalid gzip magic

does it have anything to do with the datastore1 folder appearing renamed to the "4e7a....a18" string

thanks in advance
adam



Just do a

# tar xvf unlock-esxi500-469512.tgz

it might be that its not gzip-ed at all.

#73
Donk

Donk

    InsanelyMac Deity

  • Members
  • PipPipPipPipPipPipPipPipPipPip
  • 1,941 posts
  • Gender:Male
  • Location:Manchester UK

Just do a

# tar xvf unlock-esxi500-469512.tgz

it might be that its not gzip-ed at all.

It is gzipped!

#74
pocopico1

pocopico1

    InsanelyMac Protégé

  • Members
  • Pip
  • 19 posts

I've tried everything I can think of, but all I get is the gray apple screen.
How can I boot mac os x into verbose mode with EFI? In the past, I could input the "-x" option in the darwin bootloader.

EDIT: tried a different lion installer. It gets stuck here now. I also tried booting my old vanilla snow leopard installer and all I get is the gray apple logo. (same behavior as the first lion installer)

EDIT2: this is a whitebox esxi with a Celeron E3200 cpu (very cheap, I know, but its only for my personal home use). Also, my snow leopard server used to work perfectly on esxi 4.1 with Donk's old patch.


Hey i was also trying to find how i could boot in verbose mode ... after a lot of searching and a little imagination i found the way...

Power on the VM and when you reach the at VMware logo press F8 this will drop you to the EFI menu

Select "Boot Manager" and then "EFI Internal Shell" you will be presented with a Device Mapping Table focus at fsX: line that should say "Removable Hard Disk" in my case it was fs0:

So at EFI shell type

Shell> fs0:
fs0\:> cd \usr\standalone\i386
fs0:\usr\standalone\i386> dir

there you should find the boot.efi executable to boot just type

fs0:\usr\standalone\i386> boot -v npci=0x2000

or whatever other options you might want to pass to the kernel (-x -f etc etc)

#75
pocopico1

pocopico1

    InsanelyMac Protégé

  • Members
  • Pip
  • 19 posts

It is gzipped!


Maybe it is but this is how i extracted the tar myself ...

#76
twood

twood

    InsanelyMac Protégé

  • Members
  • Pip
  • 5 posts

Hey i was also trying to find how i could boot in verbose mode ... after a lot of searching and a little imagination i found the way...

Power on the VM and when you reach the at VMware logo press F8 this will drop you to the EFI menu

Select "Boot Manager" and then "EFI Internal Shell" you will be presented with a Device Mapping Table focus at fsX: line that should say "Removable Hard Disk" in my case it was fs0:

So at EFI shell type

Shell> fs0:
fs0\:> cd \usr\standalone\i386
fs0:\usr\standalone\i386> dir

there you should find the boot.efi executable to boot just type

fs0:\usr\standalone\i386> boot -v npci=0x2000

or whatever other options you might want to pass to the kernel (-x -f etc etc)


Thanks that was so useful. :thumbsup_anim:
Sadly it still gets stuck on an hp microserver proliant server (AMD neo) during initial loading :D

#77
Cr0n_J0b

Cr0n_J0b

    InsanelyMac Protégé

  • Members
  • PipPip
  • 71 posts
thanks for the patch.

I'm on a fresh esx 5.0 install (no patches on the host) and i ran the install path but got errors with the .bsdiff files.



/vmfs/volumes/4d3a272c-2878edf8-3274-001cc469991e/unlock-esxi500-474610/unlock-esxi500-474610 # ./vmx-debug.bsdiff
./vmx-debug.bsdiff: line 1: syntax error: word unexpected (expecting ")")
/vmfs/volumes/4d3a272c-2878edf8-3274-001cc469991e/unlock-esxi500-474610/unlock-esxi500-474610 # ./vmx-stats.bsdiff
./vmx-stats.bsdiff: line 1: syntax error: ")" unexpected
/vmfs/volumes/4d3a272c-2878edf8-3274-001cc469991e/unlock-esxi500-474610/unlock-esxi500-474610 # ./vmx.bsdiff
./vmx.bsdiff: line 1: syntax error: ")" unexpected



It might be that I'm misreading the directions but what i do is:

1) position the patch folder (unzipped and executable) in a datastore folder

2)run the uninstall.sh and then the install.sh -- nothing was installed before, so I'm not sure why I run the uninstall...but that's what it says. :-)

2b) run through the bspatch and .bsdiff lines getting errors. One note is that the bspatch command seems to be looking for an input and an output, which isn't listed in the readme.

bspatch: usage: ./bspatch oldfile newfile patchfile


3) then the readme says to install the patch again...which i did above??

the output from the patch above seemed to be correct, so I'll see what happens on a reboot.

#78
23adam23

23adam23

    InsanelyMac Protégé

  • Members
  • Pip
  • 3 posts

Maybe it is but this is how i extracted the tar myself ...



Thanks for that, I successfully got the files unzipped using pocopico1's tip

Unfortunately after running the ./install.sh

the respone was

"VMWare ESXI 5.0 Unlocker 1.0.1

=========================

Patching files ...

Killed"



Any ideas on whats happening here



once again

thanks in advance

Adam

#79
Cr0n_J0b

Cr0n_J0b

    InsanelyMac Protégé

  • Members
  • PipPip
  • 71 posts
thanks to Donk.

I ignored the errors in the patch install and just went ahead and tried loading the OS. It worked after a couple of attempts. for some reason the screen kept freezing during the install...and it took a REALLY long time...but in the end it loaded up and I'm running.

Loaded VMware tools just fine, the mouse works great, graphics are...ok...but I'm not really concerned about that. The only other item that would be nice would be audio...but I can wait to figure that out.



thanks

#80
MSoK

MSoK

    InsanelyMac Legend

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

thanks for the patch.

I'm on a fresh esx 5.0 install (no patches on the host) and i ran the install path but got errors with the .bsdiff files.

/vmfs/volumes/4d3a272c-2878edf8-3274-001cc469991e/unlock-esxi500-474610/unlock-esxi500-474610 # ./vmx-debug.bsdiff

Cr0n,

Glad you got this running, as we move further away from the base 469512 build the less likely that later Unlocker's will work.

For information if you are running an unpatched ESXi 5.0.0 then you need Donk's Unlocker "unlock-esxi500-469512", ONLY use "unlock-esxi500-474610" if you have updated your ESXi 5.0.0 with the VMware patch "ESXi500-201109001.zip". Using the right correct unlocker will ensure you do not get errors and guarantee smooth running of your OS X guestOS's.





2 user(s) are reading this topic

0 members, 2 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