Today, I decided to uninstall unlocker v110, as esxi 5.1.0 U1 Health Status (CIM) and other hardware statuses (like hardware acceleration for storage statues) where all acting up all this time. And since the moment I upgraded from 5.0 U1 to 5.1.0 U1 I installed unlocker v110 I could not be sure if it was a compatibility issue with my hardware and this new version of esxi or unlocker causing it. I can confirm it was indeed unlocker v110 causing it. Everything is perfect now that unlocker v110 is uninstalled.
I just took a screenshot of what the esxi Health Status (CIM) looks like when unlocker is not installed and esxi 5.1.0 U1 works properly. WIth unlocker v110 installed all statuses displayed "unknown" (no fan speeds etc...) as well as miss-reporting in other areas via the vSphere client. There were also lags in vm guest consoles when powering up vm's, this too is now functioning properly.
Re-running the tests on the osx 10.8.3 guest with the mounted dmg gave the exact behavior (with the unlocker v110 uninstalled), so this version of unlocker is not working properly under esxi 5.1.0 U1 and unfortunately causes other stability (for a lack of better words at the moment) issue with the base esxi.
To verify with you, all I did is copy the 3 files (install.sh, uninstall.sh, Unlocker.ESXi) to a folder in my datastore (no other files), than ran chmod +x against the 3 files (they turned green color via putty once that was done) and executed ./install.sh from the path in which they reside on the datastore. The output I posted in a previous post, Donk verified.
Your thoughts are appreciated.
Sorry for the lack of response to you problem, I cannot see anything obviously wrong, your method for installing the "Unlocker" is correct, including the vmwarebase error you get during the install.
I have ESXi 5.1.0 U1 running fine with the "Unlocker" v1.1.0 installed and OS X 10.8.3, this was however a from scratch install.
So I guess either you have some remains of your vCenter Server environment, or your upgrade has left some underlying issues, I have seen some comments on the VMware Community about using update manager causing spurious problems, these were resolved by doing the upgrade from the install ISO burned to USB or CD, which method did you use?