David's work was commissioned by VMware and is well documented at his website Darwin/X86 http://www.tgwbd.org/darwin/. After all the testing I did it was great timing that I finished it the night before VMware released Fusion 2 beta, which actually proved my minimal set of extensions would work.
Some things to remember:
1. You will need a processor supported natively by Mac OSX as VMware virtualizes the CPU not emulating a specific version . So this won't work for anything other than supported Intel processors - no AMD or other processor.
2. The VMX settings here are crucial unlike for Hackintoshes where frequently you could alter things such as guest os being set to Solaris or FreeBSD.
3. The CD will have to remain mounted during boot, as none of the ways of copying the boot-132 code to the hard disk works. Trust me I have spent 2 weeks trying!!!
4. You must copy the vmware-vmx.exe to vmware-vmx-debug.exe (back up the original) or you will get a triple boot fault. this is because debug code is always enabled in beta version from VMware. This shouldn't be a problem after release of 6.5. This should probably work on Server 2 and Fusion 2 betas.
To install download the template for the guest and a cd image from http://www.mediafire.com/?1zyfhhmlckc. Extract to a folder. To install:
1. Boot the system with the vmdonk.iso attached. You will see a VMware error pop-up which you can ignore safely whenever you are booting the system. You should see the first screen below.
2. Change the loaded cd image to the retail Leopard image by using the VM-->Removable Devices menu item.
3. Enter 9f at the next screen and you should now be taken to the leopard boot line. Enter any parameters you want here, but for me it loaded with no additional boot parameters. See the second screen.
4. Install leopard using the usual installation method of partition the virtual disk using Disk Utility. Stick with GUID Partition and all should be OK.
5. When the system restarts you must reset the cd image to vmdonk.iso for it to boot. When prompted for the device to use specify 80 as in screenshot 3.
One thing I have found is to ensure the guest does not go to sleep. Use the Energy settings to switch off any sleep settings, and switch the Screensaver off as well. I have found that Leopard locks up if it enters any sleep or screen saver states.
If you download Fusion 2 beta 2 you can install the tools from the extracted darwin.iso, but in my experience there are errors showing up in the console logs that lead me to believe they are not functioning. Also I can't get sound to function, but other than that the performance is great. One last tip if you update then the first reboot is best done with -v -f -x boot flags.
Enjoy!
Donk
Update 1 2008-08-01 - Boot physical Leopard image
I have successfully run a Carbon Copy Cloner image from an external USB drive. To do this take the basic template I uploaded and remove the virtual hard drive. I also deleted the VMDK files from the folder. Then add a new virtual disk and select physical drive. You must select the whole drive. This is advanced usage of VMware so you really need to know what you are doing. For example if on Windows ensure that the USB drive does not have a drive letter associated with it, which happens if you are running MacDrive.
Update 2 2008-08-05 - Guest memory settings
If you have slow performance and/or in installation (mine took about 30 minutes) you may need to change your guest's memory settings. I have 4GB in my Dell D620 and set the virtual machine to 2GB. Your system may be paging as the virtual machine memory is equal to the physical RAM on the host. Try reducing it to say 1GB in virtual machine options.
Update 3 2008-08-11 - VMware Fusion 2 beta 2
If you are running Fusion you can use this procedure for all versions of Leopard. Rename the /Library/Application Support/VMware Fusion/isoimages/darwin.iso to something else. Then when you start it up there is an error message about the tools CD but just ignore it and off you go!
Update 4 2008-08-11 - Stop the popup error message
Search for darwin.iso and darwin.iso.sig. Copy or rename them, then create 2 zero byte files with the same name. You will find the popup error message disappears. There is an error message in the vmware.log file but that can be safely ignored. Note that Fusion 2 beta 2 and Workstation 6.5 beta 2 for Linux actually ship with these files, whereas currently Workstation 6.5 beta for Windows does not.



Sign In
Create Account







