Jump to content
817 posts in this topic

Recommended Posts

Hi guys,

 

I was postponing the SL/L installation on my ESXi 5 then today i found this topic.

 

My host is running ESXi 5.0.0 build 623860, i think that´s only one fix missing at VMWare´s site.

 

Is the fix version 1.1.0 compatible with my installation ?

 

I read the scripts and got confused about at which folder specific should i run them ...

create a folder at datastore1, chmod +x and run install.sh ?

Hi,

 

is there any documentation out there how to modify a vanilla Snow Leopard installation so that it runs on ESXi 5.0 in "hackintosh" mode without the need for an Unlocker?

Or is there any method to overcome the need to restart my Management Services every 4-5 vMotions already known?

Any help would be greatly appreciated... :-)

 

 

Best regards,

oegie

Hi Donk,

 

Got a "Patching vmwarebase is not supported on this platform"

Does build 702118 (http://kb.vmware.com/kb/2019857) supported with Unlocker v1.1.0?

 

Thanks

 

That is an information message. Nothing to worry about.

Hi thasmots,

 

Could you please describe what you mean with "working perfect with vCenter"?

Is it now possible to start OSX VMs through vCenter and also to move them around in the cluster? This would be indeed perfect!

 

cheers,

oegie

 

You only need to start the VM directly connected to the standalone ESXi. I don't try to migrate allready.

Ah, ok.

Using vCenter together with the patched ESXi hosts does not allow you to migrate the VMs from one host to another. You also cannot move non-OSX VMs around after a few vMotion operations. As a workaround you can restart the Management Processes on the hosts or restart them. Then you can use vMotion again for a couple of times.

So the patch works flawlessly in a single host environment, but not in a vCenter context. :(

But that is definitely better than not being able to run OSX...

Hi All,

Running ESXi 5.0.0 build 623860

I've done the chmod +x command on the files

but get this error when running ./install.sh

 

 

VMware ESXi 5.0 Unlocker 1.1.0

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

Copyright: Dave Parsons 2011-12

Patching files...

cp: write error: No space left on device

cp: cannot close 'bin/vmx-debug': No space left on device

 

As you can see linux commands and not my strong point

what do i need to change or unlock to get it to install

 

Cheers

Hi PCF_Ronin,

 

please try this: (in the directory where you issued "./install.sh"!)

cp * /tmp

cd /tmp

chmod +x ./install.sh

./install.sh

 

 

cheers,

oegie

 

You need to put it on the datastore not the rootfs (VisorFS) as that is not persisted. /vmfs/volumes/datastore1

  • Like 1
  • 4 weeks later...

hi all! 1st of all sorry for my ugly english.

 

I`ve prcessed patch on my esxi v5, and i can install and start OSx snowleopard well BUT, after sime time i use it for some ordinary tasks(using apple email(imap), ical, address book(ldap) or even browsing the Internet) vm just hangs and stops answering on any mouse\keyboard keys, to get it back i need to reset VM, it helps till next hang, others vms started on this ESX works perfectly as always. Does anyone met such issue and maybe knows how to fix it?

 

UPD. i've applied patch 1.1.0

Edited by tihon_one
  • 2 weeks later...
  • 3 weeks later...

Hello

 

I installed Lion Server on VMware esxi 5.0 721882. It works normally about 8 Weeks. Yesterday the Lion Server Crashed.

The Problem is that after I Restart the VM it shows the Error Message "Darwin11_64Guest not Supported" When I restart the complete esxi host Lion run only once (Without Darwin11 Guest Error). The next startup stops with Darwin11_64Guest Error Message.

 

What can I do?

 

Regards

Florian

 

I have an work around. The Problem is shows only when I start the VM with VMWare vCenter. When I Connect directly with the client, the startup works without any Problems. Is there a workaround to startup the Lion Client with VM vCenter?

 

Regards

Florian

Hi!

I have a problem with esxi-5 CLI & guest vm [10.5/10.6/10.7/10.8].

I think, that is problem in patch.

 

When I restore VM from snapshot:

vim-cmd vmsvc/snapshot.revert %vmid% %snapshotID% suppressPowerOff

 

and then I'll trying to start vm:

vim-cmd vmsvc/power.on %vmid%

 

i get error like:

Powering on VM:
Power on failed

 

On the vSphere Client Console:

A general system error occurred/l The virtual machine could not start

 

Any ideas?

Thanks

 

P.S. only esxi-host reboot fix errors

×
×
  • Create New...