Jump to content

ESXi 5 Mac OS X Unlocker


  • Please log in to reply
729 replies to this topic

#141
sebus

sebus

    InsanelyMac Sage

  • Members
  • PipPipPipPipPip
  • 261 posts
  • Gender:Male
  • Location:UK
Unlocker is NOT being installed. It only patches few files (you should understand it if you want to use it!)

As to the error? Any problems with Google where you live?

sebus

#142
Justin Juneau

Justin Juneau

    InsanelyMac Protégé

  • Members
  • Pip
  • 4 posts

Unlocker is NOT being installed. It only patches few files (you should understand it if you want to use it!)

As to the error? Any problems with Google where you live?

sebus


I'd really like to understand this Unlocker to fully utilize it, however, the first post doesn't offer any information on what it is nor how to accurately install it. Do you have any better instructions on how to install on ESXi other than "run install.sh" ? I do appreciate your feedback about the Unlocker not being installed... Maybe you can elaborate? --- As for the error message, it's probably displaying that error because the unlocker isn't patching (according to your statement). I look forward to a reply.

Thank you kindly,

#143
sebus

sebus

    InsanelyMac Sage

  • Members
  • PipPipPipPipPip
  • 261 posts
  • Gender:Male
  • Location:UK
How about trying to understand what the install.sh actually does? (pretty easy to read line by line in notepad)

As to what it does?

Why dont you just hex compare original file & one that has been patched by unlocker?

It will give you an answer

As to the error? Unrelated to the unlocker (seems you did not even follow the link I posted)

sebus

#144
MSoK

MSoK

    InsanelyMac Legend

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

I'd really like to understand this Unlocker to fully utilize it, however, the first post doesn't offer any information on what it is nor how to accurately install it. Do you have any better instructions on how to install on ESXi other than "run install.sh" ? I do appreciate your feedback about the Unlocker not being installed... Maybe you can elaborate? --- As for the error message, it's probably displaying that error because the unlocker isn't patching (according to your statement). I look forward to a reply.

Thank you kindly,

Justin,
To answer your original question, ESXi installed on to a local HD or a USB stick, this is separate to any of the datastores. So it should not matter where you copy the "unlock-all-v101.zip" ESXi files, any of the datastores should be fine, I normally create an unlocker directory on the root of one of the datastores, by the way I also create an iso directory to upload iso images of guestOS's I intend to install.

With no guestOS's running, from the ESXi console, not putty, etc. change the permissions of your unlocker files, as per Donk's readme file included in the .zip with the latest unlocker, but see the link below for some additional details, and run the ./install.sh, again from the ESXi console. You can run the Unlocker.ESXi directly, check relevant install parameters, however the install script has been extensively tested and refined, so it is the recommended route for all but the very experienced.

http://www.insanelym...p...t&p=1751068

Reboot your ESXi Server, and from your vSphere Client see if you can select OS X as a guestOS when creating a new virtual machine, if you can then the unlocker has most likely worked.

Although I would recommend creating a new OS X guestOS, you should be able to convert an existing OS X guestOS, but note the term "convert", copying the .vmdk will not work as the defualt disk presentation between Workstation / Player and ESXi are different. You can download the Converter from VMware for free, see link below, or install it from the Workstation 8 Home Page.

http://www.vmware.co...ucts/converter/

If the converter works, I have not tried it but will when I get a chance, check your new .vmx file, to ensure it has OS X 10.7 "Lion" selected as the guestOS, this can be done in the GUI or checked directly in the .vmx file the entry should be as follows:

guestOS = "darwin11-64" or "darwin11"

Good luck, we are here to help, MSoK.

#145
Justin Juneau

Justin Juneau

    InsanelyMac Protégé

  • Members
  • Pip
  • 4 posts

Justin,
To answer your original question, ESXi installed on to a local HD or a USB stick, this is separate to any of the datastores. So it should not matter where you copy the "unlock-all-v101.zip" ESXi files, any of the datastores should be fine, I normally create an unlocker directory on the root of one of the datastores, by the way I also create an iso directory to upload iso images of guestOS's I intend to install.

With no guestOS's running, from the ESXi console, not putty, etc. change the permissions of your unlocker files, as per Donk's readme file included in the .zip with the latest unlocker, but see the link below for some additional details, and run the ./install.sh, again from the ESXi console. You can run the Unlocker.ESXi directly, check relevant install parameters, however the install script has been extensively tested and refined, so it is the recommended route for all but the very experienced.

http://www.insanelym...p...t&p=1751068

Reboot your ESXi Server, and from your vSphere Client see if you can select OS X as a guestOS when creating a new virtual machine, if you can then the unlocker as most likely worked.

Although I would recommend creating a new OS X guestOS, you should be able to convert an existing OS X guestOS, but note the term "convert", copying the .vmdk will not work as the defualt disk presentation between Workstation / Player and ESXi are different. You can download the Converter from VMware for free, see link below, or install it from the Workstation 8 Home Page.

http://www.vmware.co...ucts/converter/

If the convertor works, I have not tried it but will when I get a chance, check your new .vmx file, to ensure it has OS X 10.7 "Lion" selected as the guestOS.

Good luck, we are here to help, MSoK.


FINALLY! An intelligent and HELPFUL response. Thank you MSoK. I truly appreciate you taking the time to clarify. I'm sure others in my predicament will stumble across this site (through google) and be just as thankful as I am. If I had known "everything" about this unlocker and how it works, I wouldn't be wasting my time "trolling" the forums looking to sabotage people looking for help. So again, I applaud you for your help and I will go the ISO route as you suggested above.

Happy Holidays,

-Justin

#146
Justin Juneau

Justin Juneau

    InsanelyMac Protégé

  • Members
  • Pip
  • 4 posts

FINALLY! An intelligent and HELPFUL response. Thank you MSoK. I truly appreciate you taking the time to clarify. I'm sure others in my predicament will stumble across this site (through google) and be just as thankful as I am. If I had known "everything" about this unlocker and how it works, I wouldn't be wasting my time "trolling" the forums looking to sabotage people looking for help. So again, I applaud you for your help and I will go the ISO route as you suggested above.

Happy Holidays,

-Justin


Got it working! MSoK was correct, the unlocker DID install even though I ran it from a different data store than where I installed ESXi. (Thanks for the wrong information Sebus, maybe you should try using google). All I had to do was use the VMware converter on the VMDK file and point the converter to upload the resulting file to my ESXi server (sorry if that sounds confusing). I then went into Vsphere client, edited the new VM settings to reflect the guest O.S. was/is OSX 10.6 (64bit), booted the machine and presto!

Thanks again MSoK for this valuable tool and for your HELPFUL response!

#147
MSoK

MSoK

    InsanelyMac Legend

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

Got it working! MSoK was correct, the unlocker DID install even though I ran it from a different data store than where I installed ESXi. (Thanks for the wrong information Sebus, maybe you should try using google). All I had to do was use the VMware converter on the VMDK file and point the converter to upload the resulting file to my ESXi server (sorry if that sounds confusing). I then went into Vsphere client, edited the new VM settings to reflect the guest O.S. was/is OSX 10.6 (64bit), booted the machine and presto!

Thanks again MSoK for this valuable tool and for your HELPFUL response!

Justin,
Glad to hear you have solved your issue, of course, just for general information, the converter needs to point at a server, in your case ESXi, but the server can also be your local copy of Workstation, for doing P2V's or V2V's from a different environment.

Also gentlemen can we move on, sebus is a valued member of the InsanelyMac forum, and has provided help and solutions over an extended period.

#148
Donk

Donk

    InsanelyMac Deity

  • Members
  • PipPipPipPipPipPipPipPipPipPip
  • 1,941 posts
  • Gender:Male
  • Location:Manchester UK
Updated 7th December
Updated for Workstation 8.0.1 and Fusion 4.1.0
http://goo.gl/5CZVn

#149
sebus

sebus

    InsanelyMac Sage

  • Members
  • PipPipPipPipPip
  • 261 posts
  • Gender:Male
  • Location:UK
Has anybody experienced any problems with VMotion (while using unlocker on ESX5i)
On ESX 4.1 I never had any problems, same hardware with patched latest ESX5i behaves odd (migrates fine a couple of machines & then times out on another)
services.sh restart always clears the problem
Just wonder if it could be unlocker (most likely not, but worth eliminating before I involve Vmware Support)

Thanks

sebus

#150
MSoK

MSoK

    InsanelyMac Legend

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

Has anybody experienced any problems with VMotion (while using unlocker on ESX5i)
On ESX 4.1 I never had any problems, same hardware with patched latest ESX5i behaves odd (migrates fine a couple of machines & then times out on another)
services.sh restart always clears the problem
Just wonder if it could be unlocker (most likely not, but worth eliminating before I involve Vmware Support)

Thanks

sebus

sebus,
I am not aware of any issues regarding the unlocker and vCenter Server based operations, but be aware the unlocker is not vCenter aware, and should only be used with OS X guestOS's accessed via vSphere client connected directly to the relevant ESXi host and not via vCenter.
If you do intend to contact VMware support, ensure you uninstall the unlocker first, it is very definately outside the support envelope.

#151
sebus

sebus

    InsanelyMac Sage

  • Members
  • PipPipPipPipPip
  • 261 posts
  • Gender:Male
  • Location:UK
Ofcourse I am not talking about OSX guests (as VMotion is not possible)
And yes, will have to get unlocker off, I know how (little mindedly) support works

sebus

#152
Donk

Donk

    InsanelyMac Deity

  • Members
  • PipPipPipPipPipPipPipPipPipPip
  • 1,941 posts
  • Gender:Male
  • Location:Manchester UK
Sebus - somebody else sent me a PM with a similar problem. Not sure what is happening but one question do you have the unlocker on both machines that are being used for vMotion? My suspicion is that vCenter is getting a checksum of the core monitor program (vmx) which we patch and decided it is not compatible. The guy on the PM removed the unlocker an vMotion worked again.

#153
sebus

sebus

    InsanelyMac Sage

  • Members
  • PipPipPipPipPip
  • 261 posts
  • Gender:Male
  • Location:UK
I could understand if it does NOT work ALWAYS. That would be easy. But no, it works for one or two or three moves (never consistent number) & then it times out.
Restarting services on the host makes it all work again (for a random number of times)

It just does not make sense...

sebus

#154
Eric Gravel

Eric Gravel

    InsanelyMac Protégé

  • Members
  • Pip
  • 3 posts
  • Gender:Male
  • Location:Qc, Canada
Is there anyway the Unlocker could be one day compatible with vCenter ?
I have a 3 Host cluster and don't really feel like managing everything separately.

If any help is needed in testing i'll be my pleasure to help.


@Those who still try to install on a vCenter configuration, not only it won't work to boot up but it will give you problem with any Linux/Unix VM and you won't be able to start Fault Tolerance or start some of you VM.

#155
sebus

sebus

    InsanelyMac Sage

  • Members
  • PipPipPipPipPip
  • 261 posts
  • Gender:Male
  • Location:UK

@Those who still try to install on a vCenter configuration, not only it won't work to boot up but it will give you problem with any Linux/Unix VM and you won't be able to start Fault Tolerance or start some of you VM.


Would you elaborate?

Unlikely that it would ever happen, as hacking vCenter files would be required

sebus

#156
Eric Gravel

Eric Gravel

    InsanelyMac Protégé

  • Members
  • Pip
  • 3 posts
  • Gender:Male
  • Location:Qc, Canada

Would you elaborate?

Unlikely that it would ever happen, as hacking vCenter files would be required

sebus


Ok.... why hacking ESXi is ok but not vCenter ? What are the difference ?

I haven't tested the patch during days since my important VM were affected.

Trixbox VM: Wouldn't start at all, i would receive a "general system error", even with vCenter Server and all host reboot.... the VM never wanted to boot after the patch.

All VM: FaultTolerance is "ON" but secondary VM won't start, again the "general system error" occur (0xbad0007).

I haven't push it further since up start pfSense and Trixbox are two of my most important VM in my cluster, first thing that came to my mind was the patch i just applied so i decided to uninstall it, as soon it was off everything started working back again like it was used to.

#157
Donk

Donk

    InsanelyMac Deity

  • Members
  • PipPipPipPipPipPipPipPipPipPip
  • 1,941 posts
  • Gender:Male
  • Location:Manchester UK
Because the change on the ESXi host came directly from the work done on Workstation. vCenter, vSphere, vMotion, SRM plus all the other parts of a vSphere deployment are hugely complex, and just trying to find what is happening is a challenge. On top of that I don't have access to enough kit to even try and find out what is going. I have virtualized ESXI, vCenter system (vPod in VMware terms) but nothing I do allows me to run a nested Mac OS X guest, which means I can't trace anything. Finally I have no time to do this as my work schedule is vey heavy until at least March.

If anyone else wants to take up the challenge feel free, but for now the patch is for ESXi 5 only.

#158
Eric Gravel

Eric Gravel

    InsanelyMac Protégé

  • Members
  • Pip
  • 3 posts
  • Gender:Male
  • Location:Qc, Canada

Because the change on the ESXi host came directly from the work done on Workstation. vCenter, vSphere, vMotion, SRM plus all the other parts of a vSphere deployment are hugely complex, and just trying to find what is happening is a challenge. On top of that I don't have access to enough kit to even try and find out what is going. I have virtualized ESXI, vCenter system (vPod in VMware terms) but nothing I do allows me to run a nested Mac OS X guest, which means I can't trace anything. Finally I have no time to do this as my work schedule is vey heavy until at least March.

If anyone else wants to take up the challenge feel free, but for now the patch is for ESXi 5 only.


If i had half of your knowledge i would probably be up for it.
I totally understand the complexity it would inquired.

I was mainly wondering if it was on the roadmap for the future. Again i can't be more help that testing it but if it can help i'll be more that happy to.

#159
sebus

sebus

    InsanelyMac Sage

  • Members
  • PipPipPipPipPip
  • 261 posts
  • Gender:Male
  • Location:UK
I also got few "general system error" on VM start, but this one was always clear with services restart (not even host reboot)
Will have to test hostd only restart next time...
Also will have to test starting VM from host only (and not vCenter)

sebus

#160
strannik6

strannik6

    InsanelyMac Protégé

  • Members
  • Pip
  • 3 posts

Sebus - somebody else sent me a PM with a similar problem. Not sure what is happening but one question do you have the unlocker on both machines that are being used for vMotion? My suspicion is that vCenter is getting a checksum of the core monitor program (vmx) which we patch and decided it is not compatible. The guy on the PM removed the unlocker an vMotion worked again.


Hi to everybody.
I'm "someone else" :) just needed time to understand how to post here))

So the problem was when your ESXi had been connected to vCenter and you patcher it with Unlocker.
You successfully run Lion, for example.
But after day or two, when you try to create a new VM (windows, for example) or just(!!) switch off Lion and then try to turn on it again, you get an error:
"A general system error occurred: The virtual machine could not start"

The interesting moment is that I managed to vMotion to this host one of my Win2k3 VM and it works well (and turn on too), but another VMs and win2k3 too don't work. So some VMs work...

Reboot of ESXi doesn't help, reboot of vCenter doesn't help.
The decision is to uninstall and install Unlocker again.

If someone has more information and can test it with more VMs, post it here. It can help to understand the dependence if it exists...





2 user(s) are reading this topic

1 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