Jump to content


  • Content Count

  • Joined

  • Last visited

About VMErik

  • Rank
    InsanelyMac Protégé
  1. Update to add to the documentation here. It would appear that VMware is considerably more stringent about applying compatibility rules when you're using vCenter to manage multiple ESX Servers. If I register the virtual machine to a server via the vCenter server and try to boot it, I get the error message noted above. However, if I use the VI Client to connect directly to the server, I can start the VM. Same server, same VM. Bottom line, running OS X VMs on ESX requires that you are connected directly to the ESX Server and not via vCenter. This (unfortunately) means that you can't take advantage of the vCenter features like High Availability and Load Balancing (DRS). The datastore issue I was chasing was a red herring.
  2. A couple of secondary points to look into. I had originally installed my VM on the internal storage of the ESX Server and since this machine will be getting reinstalled, I copied the VM using the regular VMware tools over to an iSCSI volume. I tried to boot and ended up with the regular PXE boot so I checked the vmx file and found that it had been modified by ESX and replaced darwin-64 with other. I replaced the original darwin-64 value and tried to start the machine and am now getting: Power On virtual machine OSXS The guest operating system 'darwin64Guest' is not supported. Administrateur VC-VSPHERE 01/07/2009 10:25:28 01/07/2009 10:25:28 01/07/2009 10:25:28 I'm going to try and rebuild a new VM on the iSCSI datastore and re-use the existing disk to see if that works, but this is an annoying problem since it means that you have to be extra careful and using the standard VMware tools to manage an OSX VM.
  3. Excellent job ! A few little points to add into the documentation concerning the ESX(i) configurations: If you want to verify whether or not your CPU is compatible, the best method is to use the VMware cpuid utility, available at: http://www.vmware.com/download/shared_utilities.html. It's an ISO image. Burn it to a CD, boot your machine and look for the line "Supports 64 bit VMware". If it's yes, you're good to go, if it's no, stop beating your head against the desk and find another machine. Side note: Xeon based HP DL380 G4's are a no go, but DELL PE2950 gen III with Xeon 5450's work peachy. When you copy up the vmware-darwin-200 package to the ESX server, make sure that you put it on local storage and don't run the commands over and over again from a shared volume since your backups will be overwritten each time you run it on another server. Note that you will have to run this script on all the servers in a cluster in order for an OSX VM to be able to move freely and reboot from any of the ESX servers. Do NOT run the "setup.sh --install" twice or you will start getting messages that darwinGuest is not a supported GuestOS. On ESX Server I used the LSI Parallel card and that didn't work. The disks show up, but as read only. Switching to IDE seems to be the only currrent choice on ESX for the moment. You're limited to 2 disks with that configuration, but you can always add the GlobalSAN iSCSI driver for direct iSCSI attachments later if required (or NFS or whatever turns your crank). Congratulations guys - awesome work!