Jump to content
Welcome to InsanelyMac Forum

Register now to gain access to all of our features. Once registered and logged in, you will be able to contribute to this site by submitting your own content or replying to existing content. You'll be able to customize your profile, receive reputation points as a reward for submitting content, while also communicating with other members via your own private inbox, plus much more! This message will be removed once you have signed in.


  • Content count

  • Joined

  • Last visited

About hippoth

  • Rank
    InsanelyMac Protégé
  1. Thank you for the explanation. Good to know!
  2. Hi, one question: why do we need to patch the ESXi host with the unlocker if the host supports Mac OS X native? The compatibility says Mac OS 10.8 desktop and server is supported --> http://www.vmware.com/resources/compatibility/detail.php?deviceCategory=software&testConfig=16&productid=34335&releaseid=201&supRel=243,201,171,&deviceCategory=software&operatingSystems=188&productNames=115&testConfigurations=16&page=1&display_interval=10&sortColumn=Partner&sortOrder=Asc&testConfig=16 So why to patch the ESXi (5.1/5.1U1/5.5) with the unlocker? I don´t have a install medium here, so I can´t test and that´s why I ask you.
  3. How can I start it via ESXi directly? Edit: Ok, now I know what you mean. Connecting to the ESXi directly, not via vCenter Server. Great, it works! Thank you very much for that hint!!
  4. Is there anybody who as an idea to solve that problem?
  5. It is actually "guestOS = "darwin-64"" and this worked fine for a long time. I don´t know why the client calls it "darwin64guest". It doesn´t change anything I set it to "guestOS = "darwin64""(without -).
  6. Hello, I´am currently running an ESXi 4.1.0 381591 but my Mac OS X 10.6.3 doesn´t start anymore. The vSphere client tells me that my guest OS "darwin64guest" is not supported. It seems like the darwin.iso is not installed, but it is. In the past, after an ESXi update I have run the "./setup.sh --install" again and I could start Mac OS X fine. But now it seems to be broken. Was there a significant change in one of the last updates so that can not run Mac OS X again?
  7. Press F8 during the first boot to come to the prompt, than F10 or F5 and you will see your attached install dvd and then enter "rd(0,1)/legacy_kernel -v" to boot up from the ISO. Your vmx looks good, with ESXi you can also use SCSI harddrives.
  8. Can you explain in a few words how to do this? Please, can you provide some more informations?
  9. Yes it does. The problem of a clean install is, you need to reconfigure your server. This you don´t need, if you can make an update.
  10. I think there was something with the ESXi ... I can´t explain what. It started with the update process from 4.0 U2 to 4.1. I had to run this update process three times, because after the first reboots of the updates my server was still running 4.0 U2 instead of 4.1. After the third try of update the server was on 4.1. Now I have made a clean install of 4.1 and the problems seems to be gone. It sounds strange but the update process was at no time the strengh of VMware.
  11. After reinstalling the ESXi the new Mac OS X works fine. I could install 10.6.0 without any problems and easily update to 10.6.4. Now I have two running Mac OS X, one with IDE drives and the new one with SCSI. I will try a performance test!
  12. Yes, this is what I always do. The SCSI adapter was my fault, by trying different options. I think I will reinstall the ESXi because he shows some strange behavior I can not explain. The most strange is that sometimes changings in the setting will not be reflected in the vmx - I don´t know why!? I will be back after reinstalling the ESXi. It´s a testing machine so it´s aim is to be handled rough.
  13. Here we go ... vmware.log.txt Mac_OS_X.vmx.txt
  14. I don´t know why but it does not work for me. Days before I could boot up to the start of the install process but my mouse did not work for me (I just forgot the USB controller). After adding the USB controller the mouse worked but I did not have an harddrive (I didn´t forget) but I could Mac OS X did not see any harddrive. So I made a complete new Mac OS virtual machine with a new IDE drive and later with a SCSI drive and now the problem with the "still waiting for root device"-problem started. I use the following addition setting in the vmx: monitor.virtual_exec="hardware" monitor.virtual_mmu="software" ich7m.present = "TRUE" keyboard.vusb.enable = "TRUE" mouse.vusb.enable = "TRUE" smc.present = "FALSE" guestOS = "darwin10-64" numvcpus = "1" I have tried it with IDE and SCSI harddrives. Anybody else an idea what could cause this problem?
  15. Thank you for this fast reply but the problem still exists. I don´t have an Nehalem based CPU so I should use monitor.virtual_mmu = "hardware"- software is just for troubleshooting Nehalem CPUs, isn´t it?