Jump to content

ESXi 5 Mac OS X Unlocker

Donk

By Donk,
in Multi-booting and Virtualisation

 Share
817 posts in this topic

Recommended Posts

Donk
Donk
Posted
  • Author
Posted

Run through the steps you are doing please. Don't have enough information to see what may be wrong.

 

1. Version of ESXi?

2. Where are you running the patcher from?

3. Is this being done via vCenter or directly on ESXi host?

4. Output from the unlocker

 

I cannot guarantee anything as I don't have real ESXi box to test against, but I have tested against a nested ESXi guest on Workstation 9 and it all works.

Link to comment
Share on other sites
KBCNa
KBCNa
Posted
Posted

Run through the steps you are doing please. Don't have enough information to see what may be wrong.

 

1. Version of ESXi?

2. Where are you running the patcher from?

3. Is this being done via vCenter or directly on ESXi host?

4. Output from the unlocker

 

I cannot guarantee anything as I don't have real ESXi box to test against, but I have tested against a nested ESXi guest on Workstation 9 and it all works.

1. I'm running ESXi 5.1 (no update)

2. a folder named "scripts" in "/vmfs/volumes/datastore1/scripts" actually inside vms data store as described in readme file

3. I don't have vCenter, I SSHed directly to ESX Host

4. Output is the screenshot i've attached earlier on first post of this page - page 27.

 

thank u again my friend

Link to comment
Share on other sites
Donk
Donk
Posted
  • Author
Posted

1. I'm running ESXi 5.1 (no update)

2. a folder named "scripts" in "/vmfs/volumes/datastore1/scripts" actually inside vms data store as described in readme file

3. I don't have vCenter, I SSHed directly to ESX Host

4. Output is the screenshot i've attached earlier on first post of this page - page 27.

 

thank u again my friend

And that screenshot is from the reboot?

 

What was the output from the unlocker?

Link to comment
Share on other sites
KBCNa
KBCNa
Posted
Posted

And that screenshot is from the reboot?

 

What was the output from the unlocker?

that was just before the reboot!

you know after gathering necessary information it starts some thing like installing with that progress bar, and suddenly this error diag jumps out and then... reboot after pressing Enter...

or I can get what you have in mind, if so i'm sorry and can you make yourself more clear?!

Link to comment
Share on other sites
Donk
Donk
Posted
  • Author
Posted

Sorry I don't understand what you have done at the point you get the screenshot.

Please write down the exact steps you did and if possible show the screenshots of what the nested ESXi guest is doing at each step.

Link to comment
Share on other sites
KBCNa
KBCNa
Posted
Posted

Sorry I don't understand what you have done at the point you get the screenshot.

Please write down the exact steps you did and if possible show the screenshots of what the nested ESXi guest is doing at each step.

 

thanks buddy

I'll surely take snap shot step by step tomorow, cuase now I have to go...

regards and c u again ;)

Link to comment
Share on other sites
madburg
madburg
Posted
Posted

He's running 'install' there by executing esxi install... 

 

You should only have 3 files from the source (unlock-all-v111\esxi) in  "/vmfs/volumes/datastore1/scripts"

You need to "chmod +x" against the 3 files (in your case the  "scripts" folder in "/vmfs/volumes/datastore1/scripts")

Execute "./install.sh" (from in your case the  "scripts" folder in "/vmfs/volumes/datastore1/scripts")

Link to comment
Share on other sites
madburg
madburg
Posted
Posted

Hey guys, has anyone tried the latest patch for ESXi 5.1.0 and unlocker 1.1.1?

 

Name: ESXi510-201307001

Version: 5.1.0 Patch 5

Build: 1157734

I took the leap here and uninstalled unlocker 1.1.0, applied this esxi 5.1.0 patch 5 (rebooted) applied unlocker v1.1.1 (rebooted) my existing ML 10.8.3 came up, upgraded it to 10.8.4, all went well.

Link to comment
Share on other sites
KBCNa
KBCNa
Posted
Posted

Hi again

 

He's running 'install' there by executing esxi install... 

 

You should only have 3 files from the source (unlock-all-v111\esxi) in  "/vmfs/volumes/datastore1/scripts"

You need to "chmod +x" against the 3 files (in your case the  "scripts" folder in "/vmfs/volumes/datastore1/scripts")

Execute "./install.sh" (from in your case the  "scripts" folder in "/vmfs/volumes/datastore1/scripts")

Thanks but I have already done as you mentioned

# chmod +x install

# chmod +x Unlocker

# chmod +x uninstall

 

is it right?


here is the step by step process of upgrade:

2z4beyu.jpg

2yy9wy0.jpg

33bmpvc.jpg

24w83fr.jpg

invnn5.jpg

24bp3kk.jpg

2mot2qb.jpg

152hpup.jpg

1539ziw.jpg

1539ziw.jpg

2vbaivt.jpg

Link to comment
Share on other sites
MSoK
MSoK
Posted
Posted

Madburg,

 

As you have found the latest patch for ESXi 5.1.0 U1 which takes your installation to build 1157734 works fine once you have reinstalled the Unlocker now at v1.1.1, also works fine with Mavericks 10.9.0 DP6.

Link to comment
Share on other sites
MSoK
MSoK
Posted
Posted

KBCNa,

 

We seem to have some confusion, this thread is for discussion regarding installing the Unlocker now at version 1.1.1 on an ESXi 5 host and the subsequent troubleshooting in respect of installing a vanilla version of OS X. All you posts are related to upgrading ESXi, and looking at you last post you are doing an upgrade on a nested instance of ESXi, as you are showing no hardware virtualisation available, which is turned on by default in BIOS on HP DL380 G7 Servers. Unless you are able to pass-through a processor to your nested ESXi, vanilla OS X is not going to install.

 

We are not here to troubleshoot ESXi patching, you need to go the VMware forum.

 

However, ESXi upgrades normally works fine, are you running the vanilla version of ESXi or the HP version, you will need to patch accordingly, also it may be worth trying a manual esxcli of the relevant .zip file.

Link to comment
Share on other sites
Dmitry R
Dmitry R
Posted
Posted

Hi folks,

 

Does anybody know if it is possible to apply this patch somehow to amd system? I tried to apply it and it went without any errors. After reboot I can see modified /bin/vms* files like this:

 

~ # ls -l /bin/vmx*
-r-sr-xr-x    1 root     root      16890352 Aug 29 08:09 /bin/vmx
-r-xr-xr-x    1 root     root         18576 Mar 23 17:28 /bin/vmx-buildtype
-r-sr-xr-x    1 root     root      21347720 Aug 29 08:09 /bin/vmx-debug
-r-sr-xr-x    1 root     root      19607592 Aug 29 08:09 /bin/vmx-stats
~ #
 

But when I try to start OS X, vmware tells me that darwin10_64 is not supported, which means that patch doesn't work. Did I miss something?

 

Dmitry

Link to comment
Share on other sites
MSoK
MSoK
Posted
Posted

Dmitry,

 

While it is perfectly possible to install the Unlocker on an AMD host running VMware, Vanilla OS X does not support AMD processors hence the error, so installing the Unlocker has no benefit. If you want to get OS X up and running on an AMD system you will need an alternative kernel.

Link to comment
Share on other sites
Dmitry R
Dmitry R
Posted
Posted

Dmitry,

 

While it is perfectly possible to install the Unlocker on an AMD host running VMware, Vanilla OS X does not support AMD processors hence the error, so installing the Unlocker has no benefit. If you want to get OS X up and running on an AMD system you will need an alternative kernel.

MSoK, Of cause I know that and even don't try to run vanilla os x on my amd. I'm using amd kernel, but the problem is not that system craches after booting, vmware even doesn't allow me to power on the machine. When I try to do anything with it i.e. power on, or migrate, it says that darwin10_64 is not supported and rejected my command. That is the real problem.

 

Dmitry

Link to comment
Share on other sites
MSoK
MSoK
Posted
Posted

Dmitry,

 

Sorry for my misunderstanding of your issue, I think with all AMD kernels you will have to set the Guest operating system as "Other" and Version as "FreeBSD" or "FreeBSD 64-bit" rather than "Apple Mac OS X" and Version "Mac OS X 10.8 64-bit". In your .vmx file that might translate to guestOS = "freebsd" or "freebsd-64" rather than "darwin10-64".

Link to comment
Share on other sites
Donk
Donk
Posted
  • Author
Posted

Dmitry,

 

Sorry for my misunderstanding of your issue, I think with all AMD kernels you will have to set the Guest operating system as "Other" and Version as "FreeBSD" or "FreeBSD 64-bit" rather than "Apple Mac OS X" and Version "Mac OS X 10.8 64-bit". In your .vmx file that might translate to guestOS = "freebsd" or "freebsd-64" rather than "darwin10-64".

Dmitry - Are you using vCenter to power it on. If so you can't, you have to connect to the ESXi server directly for power operations.

Link to comment
Share on other sites
KBCNa
KBCNa
Posted
Posted

KBCNa,

 

We seem to have some confusion, this thread is for discussion regarding installing the Unlocker now at version 1.1.1 on an ESXi 5 host and the subsequent troubleshooting in respect of installing a vanilla version of OS X. All you posts are related to upgrading ESXi, and looking at you last post you are doing an upgrade on a nested instance of ESXi, as you are showing no hardware virtualisation available, which is turned on by default in BIOS on HP DL380 G7 Servers. Unless you are able to pass-through a processor to your nested ESXi, vanilla OS X is not going to install.

 

We are not here to troubleshoot ESXi patching, you need to go the VMware forum.

 

However, ESXi upgrades normally works fine, are you running the vanilla version of ESXi or the HP version, you will need to patch accordingly, also it may be worth trying a manual esxcli of the relevant .zip file.

 dear MSoK

 

actually I'm not here to ask how to enable hardware virtualization...

my issue is exactly the process of patching esxi i placed those screen shots, cause one of members requested. and my question is "could that virtualization warning be a point driving me into error?" as you may take  a second look over screen shots, there is a error dialogue as a result of running patcher script? what is possibly wrong with the process of patching? I'm using a general edition of esxi and all the things are well with my VMs and hardware...

could any body leave a step by step by step guide for me or do a favor, checking my screen shots to see if i'm not wrong through process?

thanks everybody

Link to comment
Share on other sites
Dmitry R
Dmitry R
Posted
Posted

Dmitry - Are you using vCenter to power it on. If so you can't, you have to connect to the ESXi server directly for power operations.

Yes, I was using vCenter. When I started the machine having connected directly to the ESXi host, everything became OK. I don't know where did I miss this point, but now all is OK. Thank you, Donk

Link to comment
Share on other sites
BzowK
BzowK
Posted
Posted

Hey Guys - 

 

Just installed ESX 5.1 on my old "home server" for dev testing and recently upgraded it with a 256GB SSD datastore (actually used 25 of it for host caching.)  I ran the unlocker on it, then used VMWare Converter 5.1 to transfer a fully working 10.8.3 OSX VM from VMWare Workstation to the ESX server.  I never got it to start up correctly on ESX, but finally was able to get it to by changing the Boot Firmware from EFI to BIOS.  After this, the VM booted normally (at first.)

 

I got to the first screen prompted for country without issue, but then realized that the mouse didn't work.  I tried using the keyboard (TAB) to switch between the windows which didn't work as I thought it should, but did provide some feedback at least on the screen.  The mouse never moved at all - even though the cursor appeared at the left side of the screen.

 

Any ideas for how to resolve this?  Thanks!

Link to comment
Share on other sites
MSoK
MSoK
Posted
Posted

Hey Guys - 

 

Just installed ESX 5.1 on my old "home server" for dev testing and recently upgraded it with a 256GB SSD datastore (actually used 25 of it for host caching.)  I ran the unlocker on it, then used VMWare Converter 5.1 to transfer a fully working 10.8.3 OSX VM from VMWare Workstation to the ESX server.  I never got it to start up correctly on ESX, but finally was able to get it to by changing the Boot Firmware from EFI to BIOS.  After this, the VM booted normally (at first.)

 

I got to the first screen prompted for country without issue, but then realized that the mouse didn't work.  I tried using the keyboard (TAB) to switch between the windows which didn't work as I thought it should, but did provide some feedback at least on the screen.  The mouse never moved at all - even though the cursor appeared at the left side of the screen.

 

Any ideas for how to resolve this?  Thanks!

BzowK,

 

Which version of Workstation are you using, and what is the hardware compatibility set for your OS X VM before conversion? I have yet to get an OS X VM to convert, especially if it was created in Workstation 9 with hardware compatibility set to version 9. If you install a new OS X VM in ESXi 5.1.0 U1 it uses hardware compatibility version 8, and any attempt to move it to version 9 stops the OS X VM from booting, and you cannot go back!

 

So I think you will have to create a new OS X VM in ESXi 5.1.0 U1, pending the imminent arrival of ESXi 5.5.

Link to comment
Share on other sites
 Share
Go to topic listing
×
×
  • Create New...