Monday, August 04, 2008

Virtualizing Mac OS X Leopard Client

VMWare Fusion 2.0 beta2 supports virtualizing Mac OS X Server as a guest OS. If you try to install a Leopard Client guest, you get an error
The guest operating system is not Mac OS X Server.
However, if you create an ISO/CDR image from your Leopard install DVD, mount it then do
touch "/Volumes/Mac OS X Install DVD/System/Library/CoreServices/ServerVersion.plist"
then unmount it, you can now use that image to install Leopard Client into VMWare with no complaints. After you install, reboot VMWare from the install DVD ISO again, run Terminal and
touch "/Volumes/Macintosh HD/System/Library/CoreServices/ServerVersion.plist"
then reboot from the HD. This probably violates your license agreement so don't do it, I certainly wouldn't.
Update: You can automate the deletion and creation of the ServerVersion.plist file using a LaunchDaemon. Put the following xml in a new file /Library/LaunchDaemons/com.rectalogic.vmware.plist
<?xml version="1.0" encoding="UTF-8"?>
<!DOCTYPE plist PUBLIC "-//Apple Computer//DTD PLIST 1.0//EN"
    "http://www.apple.com/DTDs/PropertyList-1.0.dtd">
<plist version="1.0">
<dict>
    <key>Label</key>
    <string>com.rectalogic.vmware</string>
    <key>ProgramArguments</key>
    <array>
            <string>/bin/bash</string>
            <string>-c</string>
            <string>/bin/rm -f /System/Library/CoreServices/ServerVersion.plist; trap "/usr/bin/touch /System/Library/CoreServices/ServerVersion.plist; exit" SIGINT SIGTERM SIGHUP; sleep 999999 &amp; wait $!</string>
    </array>
    <key>KeepAlive</key>
    <true/>
    <key>RunAtLoad</key>
    <true/>
</dict>
</plist>
Then run
sudo launchctl load /Library/LaunchDaemons/com.rectalogic.vmware.plist
Now when you login ServerVersion.plist will be deleted, when you shutdown it will be recreated ready for the next reboot.
Alternative approach: An alternative approach discussed in the comments is to hack VMWare to disable the check for server.
sudo bash
cd "/Library/Application Support/VMware Fusion/isoimages"
mkdir original
mv darwin.iso tools-key.pub *.sig original
perl -n -p -e 's/ServerVersion.plist/SystemVersion.plist/g' > darwin.iso
openssl genrsa -out tools-priv.pem 2048
openssl rsa -in tools-priv.pem -pubout -out tools-key.pub
openssl dgst -sha1 -sign tools-priv.pem > darwin.iso.sig
for A in *.iso ; do openssl dgst -sha1 -sign tools-priv.pem < $A > $A.sig ; done
exit
VMWare Fusion 3.0: Fusion 3.0 uses EFI instead of BIOS by default. After creating a new VM and before booting it from the install DVD/ISO, edit the *.vmx file and remove/comment out the firmware="efi" line. VMWare will then use the hacked boot image from darwin.iso.

VMWare Fusion 4.0: Fusion 4.0 is similar to 3.0, but the path in the script above must be changed from /Library/Application Support/VMware Fusion/isoimages to /Applications/VMware Fusion.app/Contents/Library/isoimages. Each time you boot the guest you will get an error dialog No operating system was found. Click OK. You may then get an error dialog Your Mac OS guest is using this CD-ROM device. Click Cancel. Now you should have a black screen with No operating system found displayed, click on the window and hit Return to boot.

136 comments:

rectalogic said...

Software Updates are a bit tedious with this hack. You have to remove ServerVersion.plist before checking for updates, or it won't find any. Then after you install them when you reboot, you need to leave it removed or the updates won't install. So then when you reboot the VM will fail to start since it is now Client again. So you have to mount the disk or boot off the hacked DVD ISO and use Terminal to restore ServerVersion.plist and then you can reboot off the HD again.

Anonymous said...

ServerVersion.plist is identical to SystemServer.plist with the exception of the product name, which is Mac OS X Server instead of Mac OS X

Jon said...

Couldn't you just symbolically link ServerVersion.plist SystemVersion.plist ? On my 10.5.4 client I don't see a SystemServer.plist in /System/Library/CoreServices

insideo said...

Does this work for Tiger? I would *love* to virtualize that for application / web browser testing...

Anonymous said...

One solution for the SystemServer.plist issue would be a script or LaunchDaemon that deletes it on boot, and creates it when killed. Unfortunately, I don't see any way to capture the quit signal in a bash script without resorting to subscripts, which just wouldn't work well with launchd. I'll keep examining this, and whip up a little C program if necessary.

rectalogic said...

I updated the post with a LaunchDaemon that automatically removes the ServerVersion.plist on bootup and recreates it on shutdown.

Anonymous said...

I'm using disk utility to create a dmg, then running the 'touch' command, then converting to iso - still won't boot the installer image.... what am I doing wrong?

Using beta2 and a retail disc to create the image....

rectalogic said...

I had problems converting a DMG to an ISO with Disk Utility. Try creating an ISO directly from the DVD instead of a DMG.

If it's not booting with the "The guest operating system is not Mac OS X Server" error, then you probably didn't create the ServerVersion.plist in the correct place in the ISO.

Anonymous said...

For those that care, this hack lets you install in Parallels Server also.

Phillip Moore said...

>> I'm using disk utility to create a dmg, then running the 'touch' command, then converting to iso - still won't boot the installer image.... what am I doing wrong?

Be sure you select the disk itself when creating the image, not the Mac OSX installer volume. If you don't select the disk you don't get the boot sectors off the DVD

Anonymous said...

Actually, all this is far too complicated. The check for Server vs. Client is in darwin.iso, which can be modified.

Unfortunately, the ISO images are signed. Well, kind of. The public key for verifying the signatures is located in the very same directory. Nice.

cd "/Library/Application Support/VMware Fusion/isoimages"
mkdir original
mv *.sig original
mv darwin.iso original
sed "s/Server.plist/System.plist/g" < original/darwin.iso > darwin.iso
openssl genrsa -out tools-priv.pem 2048
openssl rsa -in tools-priv.pem -pubout -pubout -out tools-key.pub
openssl dgst -sha1 -sign tools-priv.pem < darwin.iso > darwin.iso.sig
sh -c "for A in *.iso ; do openssl dgst -sha1 -sign tools-priv.pem < $A > $A.sig ; done"

(Posting this to give the fine VMWare guys a chance to close this particular hole in Fusion 2 final.)

Anonymous said...

Forgot one step:

mv tools-key.pub original/

where appropriate.

rectalogic said...

Nice! Works for me, but it should be:

sed "s/ServerVersion.plist/SystemVersion.plist/g" < original/darwin.iso > darwin.iso

Nic said...

The last shell script is giving me an error about A being and undefined variable. What shell should I be using?

Anonymous said...

The correct and reliably sequence is probably

sudo bash

followed by

cd "/Library/Application Support/VMware Fusion/isoimages"
mkdir original
mv darwin.iso tools-key.pub *.sig original
sed "s/ServerVersion.plist/SystemVersion.plist/g" < original/darwin.iso > darwin.iso
openssl genrsa -out tools-priv.pem 2048
openssl rsa -in tools-priv.pem -pubout -out tools-key.pub
openssl dgst -sha1 -sign tools-priv.pem < darwin.iso > darwin.iso.sig
for A in *.iso ; do openssl dgst -sha1 -sign tools-priv.pem < $A > $A.sig ; done
exit

Works for me :-)

Nic said...

That was the ticket! Thanks!

Wappie said...

Another (easier?) way of creating a working ISO is y converting a dmg into a toast image or creating a toast image from the installer DVD. .toast images are 100% ISO. Just rename the .toast extension into .iso.

Wappie said...

Also intersting: I managed to clone my everyday Leopard install and run it as a VM by mounting my VMware Leopard-Server virtual disk on my desktop and overwriting its contents by cloning my startup-disk onto it using Carbon Copy Cloner. After that the Leopard-client VM booted just fine using the "SystemServer.plist " method posted here (THANKS!). Just remember to use the right name for your volume, if it isn't "Macintosh HD".

Wappie said...

For those of you who don't know how to mount your VM's virtual-disk: just right-klick your virtual-machine file (i has the extension .vmwarevm) and select "Show Package Contents" Now look for the file "Virtual Disk.vmdk" Doubleklick it and it will just mount on your desktop.
You won't be able to mount suspended disk-images or VM's with snapshots. So make sure your leopard-VM is shut down, and all snapshots are gone.

Anonymous said...

For me the script at first seemed to work (VMWare detected my Leopard DVD as OS X Leopard Server 64-bit), however once VMWare booted into the installer it says: Mac OS X cannot be installed on this computer. Any ideas?

rectalogic said...

"Mac OS X cannot be installed on this computer." means you are using a non-retail install DVD on a different platform. The client DVDs you get with a new Mac are specific to a set of hardware (e.g. a certain generation of MacBook Pro, or iMac or whatever). You will have best luck with a retail DVD. I'm not sure if you could use the DVD for the physical Mac you are running VMWare on - not sure if VMWare virtualizes the right pieces to fool the DVD.

Anonymous said...

When I run the "touch..."-command I get the message "Read-only file system".
How to make a image, which is not Read-Only but can be used as bootimge for VM?

Anonymous said...

Instead of "sudo bash" it's better to use "sudo -i"

rectalogic said...

"sudo -i" will run the current users preferred shell, which may not be bash - could be zsh, tcsh whatever. The script is a bash script, so better to be explicit.

Dave said...

Hey this is great. But I'm having a problem.

I run my virtual machine, it boots off the .iso ok, launches into the installer and I step through to where it asks where do I want to install OSX. But there's nothing in that window to select to install OSX on to.

I'm having the same problem if I try to install OSX Server too.

I'm sure I've set up the virtual machine settings to use a 64GB IDE virtual disk...

Any ideas?

Dave said...

Umm... sorry... never mind. I figured it out. I'm a dufus :p

urkle said...

I did the "darwin.iso" hack, and I OS X causes a stack fault in kernel mode just after the gray "apple" logo screen appears.

I have a 10.5.0 Retail DVD. Tried both "32bit" and "64bit" options for the VM type, and this is on my Mac Pro (dual 2Ghz xeons)

Alan@polyphase.ca said...
This comment has been removed by the author.
Anonymous said...

Virtualizing Mac OS X Leopard Desktop is much easier now. Just use the DiscCloud Virtual Appliance that runs on VMware. Load the Appliance on Vmware server or ESX, connect a Leopard client, and run the DiscCloud tools to virtualized the desktop.

See: http://www.disccloud.com

and

http://disccloud.ning.com

Its real easy .. I set up my 4 year old dual opteron box with 4 SATA drives and now my user desktop on my eMac is 1TB! My desktop lives entirely in a virtual machine running on VMware server on the opteron machine!

Anonymous said...

Just tried the iso image hack with the latest vmware fusion "Version 2.0 (116369)" and it works nicely. Albeit for me the install never gets past the spining grey circle :( perhaps its a coreduo vs core2duo thing?

great blog btw!

Imre said...

My problem is, that after having tried this process, my system request server serial after that action and i can type anything during the boot and the system doesn't boot at all. Any idea? Any suggestion is welcome! Thanks in advance!

Martin said...

Installation went great. I used the plist-method. But now, when it comes to the welcome screen, it can't use mouse and keyboard no more. The virtual machine doesn't seem to have any input devices and I haven't found a way to activate it in a virtaul machine. Did i miss something, or is there a special trick about it?

Thanx!

Anonymous said...

I used the patch method on a final (= non beta) VMware Fusion 2.0 (Build 116369) - with the perl command instead of sed. I'm using a 24" Aluminum iMac with 4 GiB and 2.8 GHz.

After the patch the freshly created VM accepted the regular retail OS X 10.5(.0) Client DVD without any complaints straight from the SuperDrive and booted right into the installer.

As I'm typing this, the VM has already rebooted: Afterwards I was able to create my usual user/administrator accounts (of course I canceled the registration process, duh!) - as I type this it has just rebooted again after the installation of the VMtools.

Thanks a lot for this very valuable blog post!

rdbrown said...

I got OS X Leopard Client installed and updated to 10.5.5. Now the only thing I can't get to work is Sound. I installed VMware Tools, and still no sound. Does the VMware Tools not work on the Client?

Rhea said...

Thanks for writing this.

zyvangelist said...

Is it possible to just somehow run Mac OS X Server in VMware on a leopard client desktop/laptop? Everytime I try with my dvd it doesn't work right.
in 64-bit it says EBIOS error, and 32-bit it says that andjust loading dvd contents

Anonymous said...

It appears that VMware Fusion version 2.0.1 (released Nov 14, 2008) has added some checks that disable the work-arounds listed above.

I previously had Mac OS X 10.5.5 running flawlessly using the "alternative approach" with the perl command (listed near the end of the instructions above). With VMware Fusion 2.0, I was able to restart the VM at will, but when I attempt to boot this same VM under 2.0.1, it gives me the "Not Mac OS X Server" error.

Luckily I still have a snapshot taken with my Mac OS X client 10.5.5 VM running, so I can always revert to that. I just can't reboot the VM any more.

If anyone finds a way around this problem, please share!

Anonymous said...

Installing 2.0.1 overwrote your patched darwin.iso. Given that the stock Leopard Client DVD boots just fine in 2.0.1 with a freshly patched darwin.iso: Did you re-apply the patch commands after updating?

Anonymous said...

rdbrown: Fusion doesn't support sound for MacOS guests, regardless whether Server or Client :-( That's a known limitation (and documented in the release notes.)

Anonymous said...

I'm the Anonymous guy who posted above: "I used the patch method on a final (= non beta) VMware Fusion 2.0 (Build 116369)"

After updating to Fusion 2.01 (Build 128865), the Leopard VM did not boot - as others have reported, "Not Mac OS X Server" ... sure the 2.01 installer overwrote the patched files.

I then re-applied the patch (again with perl instead of sed), and it went right through without any trouble.
As I'm typing this, Fusion 2.01 has booted the Leopard VM as if nothing happened.

Anonymous said...

The "signature hack" worked flawlessly on my MacBook, with VMWare 2.01 and Leopard retail - thanks!

Anonymous said...

Has anyone tried or has gotten Mac OSX Leopard Client to work on Parallels 4?

Anonymous said...

I'm having trouble following the last part. What do you mean by, " After you install, reboot VMWare from the install DVD ISO again, run Terminal and touch "/Volumes/Macintosh HD/System/Library/CoreServices/ServerVersion.plist"
then reboot from the HD."

I'm getting an error from VMWare Fusion that reads "The Guest Operating System is not OS X Server."

Is the touch command creating the plist file on the Host OS X or the Virtual OS X Machine? I ran the touch "/Volumes/Macintosh HD/System/Library/CoreServices/ServerVersion.plist" command and found it created the ServerVersion.plist on my Host OS X system.

hayward room said...

Great posts here. I also tried the alternative approach and did the perl. It did finally recognize the Mac OS X DVD installation but when booting during the setup it could never get past to the "circle colored ball." Just spins and unable to install completely. Any ideas on how to resolve this?

Anonymous said...

Hi all !! i did the touch thing and the Hack for darwin iso. but i'm still block after choosing language :( it saied that OS X can not be installed on this computer... is it bcause i'm using a retail DVD i had with my MBP ?

Anonymous said...

Still working with the 2.0.2 update :)

barakthecat said...

I had to reapply the Anonymous' "correct and reliable" hack after the 2.0.2 update, but it worked.

David Martorana said...

Using the launch daemon may require one more step. When you log in to your OS for the first time, launch terminal. You'll need to change permissions on the script.

sudo chown root:wheel /Library/LaunchDaemons/com.rectalogic.vmware.plist

After that, run the launch daemon loader:

sudo launchctl load /Library/LaunchDaemons/com.rectalogic.vmware.plist

Then you should be all good. I noticed that the console was giving me "dubious permissions (skipped)" for the .plist file. Once chown is run, the system will launch it automatically.

Anonymous said...

Same here - I again used the hack with the "perl" line instead of the "sed" line. Worked flawlessly on 2.0.2 (147997), my Leopard Client test VM boots again.

Anonymous said...

Though the alternative patch works great with a Leopard host, if you run Fusion on a Tiger host then the very same Leopard client machine won't work. Of course that's when you implement the .plist flipper, and then you're back in business.
The reason for a Tiger host, btw, is that there isn't as much fighting over graphics resources that way, and dragging VMLeopard windows is less choppy - for those of us cursed with GMA 950 displays.

Anonymous said...

Nevermind about using a Tiger host to get rid of choppiness: If you have a GMA 950 machine, then only use *one* CPU in your VMs (of course, I modified the VM to use *two*). The best I could come up with for an explanation for this was Google results for the MacBook Air, which is basically a really flat incarnation of a regular MacBook (for VMware hosting purposes anyway) -- that article simply said that it can't handle it.

I hardly ever go with the defaults when I install any software, but the algorithm VMware uses to determine machine defaults is pretty much right on.

Anonymous said...

For those who have a DMG and need to convert it to ISO, just use this command.

hdiutil convert image.dmg -format UDTO -o image.iso

Anonymous said...

As usual: I again used the hack with the "perl" line instead of the "sed" line. Worked flawlessly on 2.0.3 (156731), my Leopard Client test VM boots again - on a Leopard host.

Pepijn said...

Just to chime in, this still works with the 2.0.4 update. Had to redo the hackery after updating, hence returning to this page...

William J Sisti said...

Used the alternative method w/ PERL and it worked with my dev build of Snow Leopard.

Pepijn said...

Still works for the 2.0.5 update from 6/23/09.

Anonymous said...

I know this is a little off topic, but how would one boot OS X Server 10.4.11 as a guest to VMware or Parallels Server? Would just changing the ServerVersion.plist do it?

Anonymous said...

Did anyone manage to either run Tiger in a VM on a Leopard host or vice versa?

Anonymous said...

Hi,

here my experience:

I could successfully install Snow Leopard on VMWare 2.0.5. (but installation on VMWare 2.0.1 did not work).

I used the normal 30EUR/$ installation DVD.

Using the original Leopard DVD's that came with my MacMini and MacBook Pro did not work (as already mentioned).

Anonymous said...

Ran the darwin patch for the 2.0.6 beta and it still works, was able to start the 10.5 image I installed earlier.

AppleMacGenius said...

Has anybody had any luck with 3.0? I need this asap.

rectalogic said...

This still works fine with the new Fusion 3.0 released today.

Patrick said...

@rectalogic

I just installed Fusion 3 and followed the alternate approach but it does not work for me.

It always tells me that it's not a server version of OS X.

Can you please elaborate on how you fixed this?


Thanks in advance

rectalogic said...

I have a shell script named fix-vmware and just run "sudo fix-vmware". Contents of the script are:


cd "/Library/Application Support/VMware Fusion/isoimages"
mkdir -p original
mv darwin.iso tools-key.pub *.sig original
perl -n -p -e 's/ServerVersion.plist/SystemVersion.plist/g' < original/darwin.iso > darwin.iso
openssl genrsa -out tools-priv.pem 2048
openssl rsa -in tools-priv.pem -pubout -out tools-key.pub
openssl dgst -sha1 -sign tools-priv.pem < darwin.iso > darwin.iso.sig
for A in *.iso ; do openssl dgst -sha1 -sign tools-priv.pem < $A > $A.sig ; done

Paul said...

Having issues with the dreaded "spinning ball" during boot up. Performed all the required patches/etc, and it does boot, just gets stuck at the spinning ball and never progresses. Anyone able to offer a solution or a potential course of action? Thanks

Anonymous said...

I'm using Fusion 3.0, and a shiny retail Leopard disk. I ran the just-reposted script, and I still get the "This isn't Server" message.

In case it helps:

bash-3.2# pwd
/Library/Application Support/VMware Fusion/isoimages

bash-3.2# md5 darwin.iso original/darwin.iso
MD5 (darwin.iso) = 61f5ed0859f1113d2f3539a716b6a7fd
MD5 (original/darwin.iso) = ac0c962beb3cd595ce765f824da3f29b

VMware Fusion reports its version as Version 3.0.0 (204229).

Paul said...
This comment has been removed by the author.
Paul said...

DOH!!! Wrong button... anyway, the md5 checksums are fine, same as what I have but that's not the issue. This is:

To Anon above:

Did you do the touch command on the ISO on the drive? You have to make an ISO of the Snow Leopard DVD on the drive and then touch it so it creates the Server.plist file (empty but it's there).

Without that, you're dead in the water - you can't do this by trying to install directly from the physical DVD in the optical drive; it can only be done properly with an ISO (made with Disk Utility as a CD/DVD Master and done properly).

I made the mistake others make and chose the actual "Mac OS X Install DVD" entry in Disk Utility several times and wasted it because it was never properly bootable. You have to choose the actual optical drive (the physical drive) where the disc is inserted - that's how you end up with an image that's bootable.

Tough lesson but I got it now... ;)

Still stuck with the spinning ball, however, just can't seem to resolve that. Hopefully rectalogic can offer some info or someone else can, pretty please, if you can help.

Anonymous said...

I didn't do the create disk image and touch the file step ... my understanding is that if I patched darwin.iso, I didn't have to edit the installer image...

Anonymous said...

Vmware changed how they are implementing the Checks.

If you have a preexisting VMware of Leopard client, the Alternate fix still works, provided they still use VMware's Darwin bootloader method.

However, if your trying to create a new VM in Fusion 3.0, the new VM will now use a EFI firmware, vs the Darwin boot loader. With the new EFI firmware, the only option I found that works is the ServerVersion.plist hack.

rectalogic said...

Adding:

isolation.tools.osNotMacOSXServer.disable = "TRUE"

to your *.vmx changes the behavior somewhat. Instead of getting the dialog you get a message from the BIOS. This doesn't help, but might be a clue for someone.

rectalogic said...

OK, if you edit your *.vmx config file for your VM and comment out:

#firmware = "efi"

Then vmware will boot using the old BIOS instead of EFI and everything will work again.

I just successfully installed Snow Leopard client in Fusion 3.0 from an ISO of a retail DVD (have to use an ISO so you can touch the ServerVersion.plist)

Anonymous said...

I've just done an install of Snow Leopard Client in Fusion 3.0 -- from the DVD, not from an ISO of the DVD. No requirement to make an empty ServerVersion.plist file in the image or alter the install disc.

Procedure:

In Terminal, execute:
sudo bash

Enter your password if prompted. When you get the # prompt, cut and paste the following into the Terminal window:

cd "/Library/Application Support/VMware Fusion/isoimages"
mkdir -p original
mv darwin.iso tools-key.pub *.sig original
perl -n -p -e 's/ServerVersion.plist/SystemVersion.plist/g' < original/darwin.iso > darwin.iso
openssl genrsa -out tools-priv.pem 2048
openssl rsa -in tools-priv.pem -pubout -out tools-key.pub
openssl dgst -sha1 -sign tools-priv.pem < darwin.iso > darwin.iso.sig
for A in *.iso ; do openssl dgst -sha1 -sign tools-priv.pem < $A > $A.sig ; done

Launch VMware Fusion, create a new VM for Snow Leopard. Save the VM, and then exit Fusion. Using either the terminal or Finder, navigate inside the VM and edit the *.vmx file.

Find the line that reads:

firmware = "efi"

Change it to read:

firmware = "bios"

Do not add a line that says isolation.tools.osNotMacOSXServer.disable = "TRUE" as was suggested above. It seems to screw this up -- my DVD didn't boot with it, but consistently boots without it.

You should now be able to rerun Fusion, and boot the VM from your Snow Leopard DVD, or an unmodified ISO. I've just completed an install using this method, and it booted up from the virtual hard drive and so far is working fine.

Paul said...

Been attempting this stuff for two days nearly, still no progress past the spinning ball so, I'm givin' up on it, will come back to this in the future at some point. Not that big of a deal I suppose.

Borrowed an actual OSX Snow Leopard Server install DVD (the real thing) from a friend/I.T. cohort and same thing, just stops after the boot/pre-language selection, black cursor on grey background for about 30 seconds, then the cursor turns into the spinning beachball and that's it. Left it sitting for an hour in the background, doesn't do anything from that point on.

Oh well... thanks for the post regardless.

Anonymous said...

Paul: Could you try booting your installer in verbose mode, and telling me what the last output you get before it hangs is?

To do this, hit F8 when prompted to do so for boot options, and use "-v" as the options.

Alvaro said...

I am folloing the guide to change ISO configuration and vmx file. But every time the error is the same: "Guest machine has disabled the CPU, you must shutdown the vm"

What is the problem? I try the four option 10.5, 10.6, with 32 and 64 bits for Snow Leopard, but any works fine.

Thanks by your help.

Alvaro said...

I solved the problem.
I uninstalled VMware Fusion, that was an upgrade version from 2.0 to 3.0
Reinstall the application, I do again the modification in Fusion and now Is working.

Anonymous said...

I'm using the ServerVersion.plist hack with Parallels Desktop 5 and it works like a charm, Leopard is running just fine. There is a small problem with Parallel Tools though, it installs fine, right after install you can access shared folders, but after reboot, shared folders is gone and the message on the bottom says Parallels Tools are not installed.
Does anyone have a workaround for this?

Leni said...

I was trying to do the darwin patch on Fusion 3.0 and still getting the same "System is not Server" error. I just successfully ran SnowLeopard so i decided to share with all you guys what worked for me, may help someone still in the dark. Here is the procedure that works 100%:
- make sure you CLOSE vmware
- apply the darwin patch as follow:
sudo bash
cd "/Library/Application Support/VMware Fusion/isoimages"
mkdir original
mv darwin.iso tools-key.pub *.sig original
perl -n -p -e 's/ServerVersion.plist/SystemVersion.plist/g' < original/darwin.iso > darwin.iso
openssl genrsa -out tools-priv.pem 2048
openssl rsa -in tools-priv.pem -pubout -out tools-key.pub
openssl dgst -sha1 -sign tools-priv.pem < darwin.iso > darwin.iso.sig
for A in *.iso ; do openssl dgst -sha1 -sign tools-priv.pem < $A > $A.sig ; done

-now edit the vmx config file and find the line firmware = "efi" and CHANGE TO firmware = "bios"
Commenting this line out will NOT work. Set firmware to bios and you're good to go
-Run VMware Fusion and start your machine. Happy mac virtualizing ;-)

Thanks everybody for all the help and all the valuable pieces of information put together on this article. Happy new year!

Anonymous said...

I'm using Fusion 3.0.1 with 10.6.2 and the plist hack. Is anyone else having trouble with input devices (mouse and keyboard) after a period of time, i.e. having to force shutdown the virtual machine to enable input again?

Thanks

Anonymous said...

I'm trying the last solution for the vmware fusion 3.0.1 and It doesn't work. It says there is no bootable device!!
What can I do? I'm lost, please some help.

Anonymous said...

The darwin.iso hack still works with Fusion Version 3.0.2 (232708).

Odinian said...
This comment has been removed by the author.
Odinian said...

so, if I create a VM with 10.6 client on a mac, can I move the VMClient to a Linux box and run it with VMWare player?

Anonymous said...

I tried but VMWare v3.0.2 said that no bootable device was detected.

Anonymous said...

hm, unfortunately the plist as listed above seems not to work.
When I treid to save it, I got several errors concerning the structure of the plist

Anonymous said...

solved the plist problem

its just a weired doubling of the code

Anonymous said...

Just to say I used touch and the plist flipper daemon as is described in the original article, on Parallels Desktop 5 and a normal retail edition of Snow Leopard (not Server), and it works great.

Anonymous said...

I'm using Parallels Server 3 with OS X Leopard Client. All installs find with the above noted ServerVersion.plist hack and Daemon.

Question: Might anyone know how to hack Parallels Server so it doesn't check for this file? You know, like the VMware hack.

Thanks.

below said...

I have followed all the steps (patching the darwin.iso with my own key), but either one of two things happen:

1) The Virtual Machine does boot into the OS X Kernel (Grey Background, Apple: Bootloader, Spinning Wheel: Kernel), but then Fusion gives me the message:
"The guest operating system is not Mac OS X Server." or

2) VMWare Fusion stays in text-boot mode, and waits forever at "please wait for the dvd to load"

Host is OS X 10.6.3, VMWare Fusion 3.1 Beta

Guest is 10.6 client (image from Apple Developer Connection, converted with hdituil convert -format UDTO)

Thanks

Anonymous said...

I just installed Snow Leopard off a physical retail disc with VMWare Fusion 3.0.2.

You need to make sure and follow the post Leni gave above and not just comment out the firmware but change firmware to "bios" in the .vmx file. That fixed my "No operating system found error" I was getting after I installed it and tried to reboot.

I haven't gotten into the system updates yet or anything but so far it works like well.

Pepijn said...

Just a quick "me too" regarding the updated method posted by Leni for patching Fusion 3.0.2. Did the steps again with a freshly updated 3.0.2 version, tweaked my VMX files and everything is happy again. On a side note, I created a few shell scripts to manually start up VMs in headless mode since the previous method from V2.x no longer works (FluxCapacitor etc) - using general instructions found here: http://drchriswilson.blogspot.com/2009/12/vmware-fusion-3-headless.html. All is well again.

Bhagtu said...

Has anyone manage to get the VMWare tools installed in your VM? I have the Leopard running in the VM (had to try 6 different images before it worked). VMWare Fusion version is 3.1.0 (261058) - just upgraded and I can attest that the methods listed here do work to get MacOS running in a VM.

Anonymous said...

Try the latest version of VirtualBox. Works out of the box natively without any need to do any of these steps. My biggest issue with vbox is that one cannot easily move the vms but other than that it gives a good test bed for stuff before doing them on the iMac itself.

Ryos said...

I've just installed 10.6 Client on Fusion 3.1 using the plist method. I did, however, run into a snag—I couldn't figure out how to boot the VM from the hacked install .dmg after installation was complete. The usual startup keys didn't work, and Fusion said that this particular VM does not support selecting the boot device directly in the VM settings.

What I did instead was to mount the virtual hard disk and use Terminal in my host OS to touch the plist file. (Unfortunately, I also fell prey to the VMDK Mounter issue documented here, necessitating a reinstall of VMware Fusion. Whew!)

Anonymous said...

Saying it works "on the latest VirtualBox" is meaningless. We have no idea what the latest version is when you did this. In the future please post the actual version number you used. This is especially important because VirtualBox has posted a notice not to talk about this on their forums and there is no way to know if this has been disabled "in the latest version." Which right now is 3.2.6 (see how useful that version number is?)

Anonymous said...

Hey, tried all the tips here with my VMware fusion 3.1 and it still says it's not a server OS wen I start it. :-(

VirtualBox works but runs like a dog.

Tim said...

Using the initial tips above, I have both 10.4.11 and 10.5.8 running successfully under VMWare 3.1.0 (261058). The launchd entries do the update on shutdown, so I have all three OSes running on my Mac Pro under 10.6.4.

Thanks for keeping this link updated after all of this time.

Randall said...

There is a typo, likely due to the blog format: the code contains "&amp" when it should have just an "&". (The "&" after a command in a shell script runs the command in a sub-process, used here to then wait for completion.)

Thomas said...

Have a VMware Fusion 3.1.1 and Mac OS X 10.6.3 Server DVD, but cannot install it. The error is: Mac OS X can't be installed on this computer. Hardware is a Mac Mini... Any thoughts?

Anonymous said...

I tried all ways:
(1) modify SL CLIENT cd image, boot with EFI option, which is fail

(2) modify darwin.iso (follow Leni's post), boot from "BIOS" option. fail too

(3) follow someone's post somewhere telling install a SL SERVER first and create another vurtural HD, and install SL CLIENT into that HD, remove the SERVER HD, boot up from the SL CLIENT HD. fail also!!!

i'm running SL 10.6.4 10F2061 with an iMac 27" iCore7.
I tried those ways on VMware Fusion 3.1.1 and 3.0.2.

Any idea how to make it work? really appreciate for any help.

sahid said...

Hi, I want to install OS X Tiger on my VMware Fusion 3 on my 10.6.4. 10.4 installed successfully on the virtual disk however, having a slight issue running the virtual disk. I have followed the instruction where I have remove the firmware="efi" line which has been done but when I start VMware Fusion to run the VM disk i get an error failed to load.

Is there something I am doing wrong? please help - thanks

KR said...

Here's how I created a virtual Mac OS X 10.6 ("client") machine using VMware Fusion 3.1.1 (282344) and my copy of the Mac OS X Snow Leopard install disk (retail version). These instructions were cobbled together from previous posts with a lot of trial-and-error:

1. Quit VMware Fusion3 if running.

2. Apply the darwin patch as follows:

sudo bash
cd "/Library/Application Support/VMware Fusion/isoimages"
mkdir original
mv darwin.iso tools-key.pub *.sig original
perl -n -p -e 's/ServerVersion.plist/SystemVersion.plist/g' < original/darwin.iso > darwin.iso
openssl genrsa -out tools-priv.pem 2048
openssl rsa -in tools-priv.pem -pubout -out tools-key.pub
openssl dgst -sha1 -sign tools-priv.pem < darwin.iso > darwin.iso.sig
for A in *.iso ; do openssl dgst -sha1 -sign tools-priv.pem < $A > $A.sig ; done

3. Create a fake Mac OS X Server install disk from a Mac OS X Snow Leopard install disk (retail version) as follows:

- Insert Mac OS X Snow Leopard install disk into your optical drive.
- Launch Disk Utility, select the device for your optical drive (note that this is NOT the Mac OS X install disk, but rather the device that has mounted it; the device should be named something like "HL-DT-ST DVD-RW GH41N").
- From Disk Utility's File menu, choose "New > Disk Image from [device]" from the File menu, set the image format to "DVD/CD master" and create the disk image.
- Mount the new disk image and turn it into a fake Mac OS X Server install disk with the following command in Terminal:

touch "/Volumes/Mac OS X Install DVD/System/Library/CoreServices/ServerVersion.plist"

4. Create a new virtual machine in VMware Fusion. I chose Mac OS X Server 10.6 64-bit as the type, but I suspect any type will work. Select the disk image from step 3 as the OS disk image.

5. Allow VMware Fusion to create your virtual machine and install Mac OS X Server 10.6 (really just your regular version of Mac OS X). After installation completes, the new virtual machine will boot and give you the "guest operating system is not Mac OS X Server" error. Let it shut down and proceed to the next step.

6. Choose "Show Package Contents" on virtual machine file for the machine created in step 4, then edit the vmx config file and change the firmware = "efi" line to firmware = "bios" (commenting this line out will NOT work).

7. Launch VMware Fusion once again and start your virtual machine. You'll now be prompted by Mac OS X to create your administrator's account. Have fun with your new Mac OS X virtual machine!

Anonymous said...

Hi there,

I have a question for the webmaster/admin here at blog.rectalogic.com.

Can I use part of the information from this blog post above if I give a link back to this website?

Thanks,
Thomas

Anonymous said...

@KR: You are THE MAN!!! Thank you!! Your instructions above worked perfectly.

The only only extra step I had to perform was during Step 5 ... I had to launch Disk Utility within the VM during the install process and create a partition for the install (this is common during "real" installs of OS X too, so not a big deal).

Anonymous said...

I just got this running on VirtualBox 4 with no hacking at all. Create an OS X Server (I chose 64-bit) and run through the defaults on the rest. Insert OS X Install DVD and start VM. Before starting the OS X Installation, run Disk Utility from the Utilities menu in the menubar and create a single partition. Then quit Disk Utility and continue with the install. I guess VirtualBox doesn't have any checks to see if it's actually the Server version of OS X or the client.

Mario said...

@KR: It did work great for me as well. This was actually the only place where I found detailed instructions and it did work as a charm! :)
Thanks!!!!

Anonymous said...

Not sure if anybody is still checking this, but cannot get KR's instructions to work. I have re-installed VMware Fusion 3.1 (282344) and followed his instructions using a retail SL DVD. When the VM boots, the Apple logo eventually changes to a 'NO' sign, and there is no progress. Any thoughts? Much appreciated.

Anonymous said...

Hi there,

Thanks for sharing the link - but unfortunately it seems to be down? Does anybody here at blog.rectalogic.com have a mirror or another source?


Thanks,
Charlie

julie said...

RE: ServerVersion.plist is identical to SystemServer.plist with the exception of the product name, which is Mac OS X Server instead of Mac OS X

I created the ServerVersion from the SystemVersion, making the one change and now it both boots correctly and I was able to update to 10.6.7 w/o any problem.

veropcnet said...

FYI...
Using KR's Post above, I have OS X 10.5.6 client running on OS X 10.7 Lion DP3 host with VMware Fusion 3.1.3. It does work, and that means I can run PPC Rosetta apps under the upcoming 10.7 Lion (Appleworks 6 still works!) Thanks for all the posts.

Anonymous said...

KR's method did not work with Fusion 3.1.3. I too got the dreaded "NOT" symbol (circle/bar) and no installation. I tried installing the original unmodified disc image with the same results. No error message at all. Just NOT and nothing. Really annoying. An error message would be appreciated VMWare . . .

I also backed up the 'isoimages' directory first and simply replaced the modified one to get back to where I was. I don't really understand fully what the script does. Is there anything else that needs to be changed back to get to the point before the script was run?

Anonymous said...

same problem: I got also the dreaded "NOT" symbol (circle/bar) !!

I was running beta, and thinking problem came form. I deleted beta and resinstalled v3.

then I redid all steps in terminal by copy/paste.

apparently all is ok.

I tried to create a new machine, but problem remains

Frederico said...

For those having trouble with the 'No Disk' (circle with cross line) or other bad disk image messages in VB, VMWare, Parallels, I was going through the same thing; could not install from my ISO image in any VM program.

I finally took the time to *CAREFULLY* read KR's instructions above; turns out his instruction for choosing your DVD *DEVICE* in Disk Utility, and *NOT* the CD Image (icon) of the 'Mac OS X Install DVD' in the column browser is *CRUCIAL* to making this work.

After making a new ISO (CD/DVD Master) disk image as he describes, I was able to successfully install 10.6 client retail in VB, VMWF and Parallels.

Please Note: I have a legal license for all these OS versions in Server, as well as in client running on Apple branded hardware; I am running this operation as an exercise in moral licensing options for use with legacy applications and development.

Anonymous said...

Thanks to the tips here and at hints.macworld.com/article.php?story=20081031054054546 it was no problem getting a 10.5 client running in Parallels 6 under OS 10.6. But I'd really like to get a 10.4 client going so I can use my old Photoshop, etc. I'd rather not have to buy Fusion in addition to Parallels. Has anybody managed to get Tiger running in Parallels, and if so, how?

Chadbag said...

Ok, I was able to install 10.6 with VMWare 3.1.3 running on 10.6.8 . The goal is to be able to upgrade the base Mac Pro to run Lion and still be able to run some stuff under Rosetta that I need to run under 10.6.x

I made the .cdr of my Family Pack retail Snow Leopard install disk. I mounted it and did the touch thing.

I created a VM. I had to edit the .vmx file to show ide0 instead of scsi1 for the CD image. It would not boot from a SCSI cd it said. I had to leave the firmware as "efi" .

After that it was pretty much straight forward. I got the VMWare tools installed. They seem to work just fine.

I just put the launchctl plist stuff in and am testing that.

SirB said...

Chadbag mentioned the issue with SCSI1 vs IDE0. I am running VMWARE FUSION 3.1.3 on OSX LION 10.7.0.

I was following the the summaries and could run an installation of OSX 10.6.0 until the 1st reboot.

Then the ERROR regarding: Cannot boot from SCSI
occurred

Chadbag, at how many places inside of the .vmx file have you replaced SCSI1 with IDE0 ? And did you use "EFI" or "BIOS" as firmware?

SirB said...

Errata: The solution to my boot issue was:

Permanently assign "darwin_snow.iso" as boot device.

Now it basically works and all upgrades to 10.6.8 worked very well out of the box

My current issue is:

I can't resize the screen resolution. I am stuck at 1024x768 pixels. Even if I press the full screen button.

Is there any way to add VMware drivers to OSC 10.6 client? The VMware tools didn't install for me out of the menu.

SirB said...

KR' and some findings of my own ... Working for an iMac running Lion 10.7.0 and VMware Fusion 3.1.3 as host system.

How to create a virtual Mac OS X 10.6 ("client") machine using VMware Fusion 3.1.3. These instructions were cobbled together from previous posts with a lot of trial-and-error:

1. Quit VMware Fusion3 if running.

2. Apply the darwin patch as follows in terminal:

sudo bash;

cd "/Library/Application Support/VMware Fusion";
tar cvf IsoImages.tar ./isoimages;

cd "/Library/Application Support/VMware Fusion/isoimages";
mkdir original;
mv darwin.iso tools-key.pub *.sig ./original;
perl -n -p -e 's/ServerVersion.plist/SystemVersion.plist/g' < ./original/darwin.iso > ./darwin.iso;
openssl genrsa -out tools-priv.pem 2048;
openssl rsa -in tools-priv.pem -pubout -out tools-key.pub;
openssl dgst -sha1 -sign tools-priv.pem < darwin.iso > darwin.iso.sig;
for A in *.iso ; do openssl dgst -sha1 -sign tools-priv.pem < $A > $A.sig ; done;


3. Create a fake Mac OS X Server install disk from a Mac OS X Snow Leopard install disk (retail version) as follows:

------------- HINT to read carefully:
--------------------------------------
------------- choosing your DVD *DEVICE* in Disk Utility,
------------- and *NOT* the CD Image (icon) of the
------------- 'Mac OS X Install DVD' in the column browser
------------- is *CRUCIAL* to making this work

- Insert Mac OS X Snow Leopard install disk into your optical drive.
- Launch Disk Utility, select the device for your optical drive (note that this is NOT the Mac OS X install disk, but rather the device that has mounted it; the device should be named something like "HL-DT-ST DVD-RW GH41N").
- From Disk Utility's File menu, choose "New > Disk Image from [device]" from the File menu, set the image format to "DVD/CD master" and create the disk image.
- Mount the new disk image and turn it into a fake Mac OS X Server install disk with the following command in Terminal:

touch "/Volumes/Mac OS X Install DVD/System/Library/CoreServices/ServerVersion.plist"


4. Create a new virtual machine in VMware Fusion. I chose Mac OS X Server 10.6 64-bit as the type, but I suspect any type will work. Select the disk image from step 3 as the OS disk image.


5. Allow VMware Fusion to create your virtual machine and install Mac OS X Server 10.6 (really just your regular version of Mac OS X). After installation completes, the new virtual machine will boot and give you the "guest operating system is not Mac OS X Server" error. Let it shut down and proceed to the next step.


6. Choose "Show Package Contents" on virtual machine file for the machine created in step 4, then edit the vmx config file and change the firmware = "efi" line to firmware = "bios" (commenting this line out will NOT work).


7. Launch VMware Fusion once again and start your virtual machine. You'll now be prompted by Mac OS X to create your administrator's account. Have fun with your new Mac OS X virtual machine!


8. I created a VM. I had to edit the .vmx file to show ide0 instead of scsi1 for the CD image. It would not boot from a SCSI cd it said. I had to leave the firmware as "efi" .


9. On Intel iMac enter the "darwin_snow.iso" as boot image file for this virtual Snow Leopard Machine in VMware's 1st CDROM/DVD config.


10. To Install VMware tools, use VMware menu "Virtual machine", alternatively mount darwin.iso to the second DVD/CD drive and run the installation. Restart the VM.


11. Finally increase screen resolution.

---------- Now all is OK for me ---------

Anonymous said...

Followed the directions here. Thank you SirB and the others who he built on. I installed Snow Leopard in VMWare 3.1.3 with Leopard still on the Mac (getting ready for Lion). But Quicken 2007 acts like a folder and won't Launch. Quicken requires Rosetta which was installed. I copied Quicken over. Any ideas?

Anonymous said...

I'm amazed that these two lines have survived all versions of this "script":

openssl dgst -sha1 -sign tools-priv.pem < darwin.iso > darwin.iso.sig;
for A in *.iso ; do openssl dgst -sha1 -sign tools-priv.pem < $A > $A.sig ; done;

Since the second line does *all* files that end in .iso, darwin.iso gets signed twice.

Anyway, here's a "real" shell script. Put it in a file and run it as root (i.e., in terminal type this:

cat > /tmp/foo


sudo sh /tmp/foo

Make sure you don't have line breaks in the wrong place.).


-------
#!/bin/sh

# Change to the fusion app support directory
cd "/Library/Application Support/VMware Fusion"
# Create a backup of the isoimages directory
tar cvf IsoImages.tar isoimages
# Go into the isoimages directory
cd isoimages
# Make the change -- string lengths must be equal
perl -p -i -e 's/ServerVersion.plist/SystemVersion.plist/g' darwin.iso
# Generate a new key
openssl genrsa -out tools-priv.pem 2048
# Create the public key
openssl rsa -in tools-priv.pem -pubout -out tools-key.pub
#
for ISO in *.iso
do
openssl dgst -sha1 -sign tools-priv.pem < $ISO > $ISO.sig
done
# We don't really need the private key, since what they app
# will do is check the signature of the iso (generated by the private
# key) against the public key. But no harm in leaving it.
-----

After changing the firmware line from "efi" to "boot", I was *almost* able to boot -- the problem was, it wasn't properly chaining to the DVD drive -- I had to eject the disk in the VM, tell Fusion to mount the physical disk instead of darwin.iso, and then tell the VM to boot.

That worked for the install, but I had problems after the install on reboot. Still working on that, but seems that made the optical drive a SCSI drive, and it says it couldn't boot off that. I'm sure it's just a matter of setting the optical drive correctly or telling it not to boot the darwin.iso image.

DeesPhotography said...

I'm by far a "geek" with all this stuff.. I can't get it to run at all...

Efit!

Anonymous said...

Any news about Fusion 4?

massiverobot said...

Ack, using Fusion 4, trying to get Snow Leopard going, I've gone over all these postings and still can't get past the "The Guest OS is Not Mac OSX Server. THis virtual machine will shutoff."

You have to use EFI or madness ensues.

Can someone explain what Fusion uses that darwin.iso for, and _Does it need it_ after you've installed Snow Leopard on the vm?

massiverobot said...

Ok, got it working on Fusion4. I don't think it's any different.

Here is what worked - follow the directions so far posted, till you get to the point where you can install OSX and it completes the install, boots back and tells you this isn't OSX Server, and so the VM will shut down.

Now, do this:

1. Click on the Options for the VM.
2. Select CDROM
3. Choose disk image, pick any ISO image.
3b. Click on Add Device and create a 2ND CDROM (this is what you will use for things in your VM). Assign it to your read DVD for now.
4. Click ok. Quit Fusion to be safe.
5. Edit your .vmx file
6. find the line that has the name of the ISO image you picked in #3. Replace it with this:


scsi0:1.fileName = "/Applications/VMware Fusion.app/Contents/Library/isoimages/darwin.iso"

7. Now, go back and change that EFI string to BIOS.
8. Save the .vmx file

Start your VM. It will say "The CDROM is in use ... blah blah..." Just click OK. It will say that the CDROM is in use again, just Click OK.

Now you should see some text that darwin is loading... then after a bit you'll get the grey screeen with the Apple logo and then OSX will boot!.

I have no idea what will happen when I try and update this. :)

Take snapshots.

Anonymous said...

I was able get the it working on Fusion 4 using the SeverVersion.plist option.

Used Mac OS X Server 10.6 64-bit to create the image.

After installing I added the line "bios.forceSetupOnce = "TRUE" to vmx file. This allowed me to select booting from CDROM image so I could add ServerVersion.plist and boot the vm and finish the install. Which I'm doing right now. Plan in adding the LaunchDeamon. Left firmware="efi", forgot about changing to bios. Haven't found any problems so far.

Karthikeyan M said...

Upgraded to VMWare Fusion 4.0.1, both 10.5 & 10.6 Virtual Machines stopped booting. Its shows "Operating system not found".

Follow the below steps to to meake your existing Virtual Machines to work with VMware fusion4


1. Click on the Options for the VM.
2. Select CDROM
3. Choose disk image, pick any ISO image.
3b. Click on Add Device and create a 2ND CDROM (this is what you will use for things in your VM). Assign it to your read DVD for now.
4. Click ok. Quit Fusion to be safe.
5. Edit your .vmx file
6. find the line that has the name of the ISO image you picked in #3. Replace it with this:

scsi0:1.fileName = "/Applications/VMware Fusion.app/Contents/Library/isoimages/darwin.iso"

(Because VMware Fusion 4 stores the isoimages settings in "Applications/VMware Fusion.app/Contents/Library/isoimages" instead of "/Library/Application Support/VMware Fusion/isoimages" like in previous versions.)

7. Now, go back and change that EFI string to BIOS.
8. Save the .vmx file

Start your VM. It will say "The CDROM is in use ... blah blah..." Just click OK. It will say that the CDROM is in use again, just Click OK.

Now you should see some text that darwin is loading... then after a bit you'll get the grey screeen with the Apple logo and then OSX will boot!.

I have no idea what will happen when I try and update this. :)

Anonymous: Thanks for the tips

rectalogic said...

I finally upgraded to Fusion 4. I didn't have to do any of the above steps. When I got the black "No operating system found" screen, I hit enter and Snow Leopard booted.

You do have to change the path to the ISOs when you rewrite their signatures after upgrading - they are now in /Applications/VMware Fusion.app/Contents/Library/isoimages instead of /Library/Application Support/VMware Fusion/isoimages

Keybounce said...

With the new late-2011 "Lion only" hardware, does anyone have this working in either the newest Parallels or VMWare Fusion?

As I understand all that has been mentioned in this topic, the two choices are either (A) Constantly toggle the client/server plist file (which makes patches that need reboots fail), or (B) modify a file in the VMWare software that checks for this file, _BUT NOT BOTH_. Is that correct? Not both, just one?

Is a 10.7 host, and a 10.6 guest the best way to go? And as another old photoshop user, can a 10.4 client guest be set up in the same manner?

I'm upgrading from a PPC machine. Yes, I'm behind the times.

Chadbag said...

@SirB

Sorry, I've left the country the day after I posted and did not see this until today. It looks like you got this working but I replaced all the SCSI types with IDE for the darwin.iso file entry. That is what it starts the boot with. Also, I have "efi" set.

EL PRODUCTO said...

I am attempting to run SL in VMware Fusion 4. I followed some directions above. I changed paths to reflect new locations. I added "cpuid.1.eax = "0000:0000:0000:0001:0000:0110:1010:0101" to my vmx file to allow booting of SL version before 10.6.3. My only issue is when booting from my CDR image I get the prohibitory sign on boot. What should I do to get passed the prohibitory sign

This is what I have done so far based on KRs post above with changes for Fusion 4 except I used DMG instead of a physical cd:

1. Quit VMware Fusion 4 if running.

2. Apply the darwin patch as follows in terminal:

sudo bash;

cd "/Applications/VMware Fusion.app/Contents/Library/";
tar cvf IsoImages.tar ./isoimages;

cd "/Applications/VMware Fusion.app/Contents/Library/isoimages";
mkdir original;
mv darwin.iso tools-key.pub *.sig ./original;
perl -n -p -e 's/ServerVersion.plist/SystemVersion.plist/g' < ./original/darwin.iso > ./darwin.iso;
openssl genrsa -out tools-priv.pem 2048;
openssl rsa -in tools-priv.pem -pubout -out tools-key.pub;
openssl dgst -sha1 -sign tools-priv.pem < darwin.iso > darwin.iso.sig;
for A in *.iso ; do openssl dgst -sha1 -sign tools-priv.pem < $A > $A.sig ; done;


- Mounted Mac OS X Snow Leopard install dmg.
- Launch Disk Utility, select Mac OS X install DVD
- From Disk Utility's File menu, choose "New > Disk Image from Mac OS X install DVD" from the File menu, set the image format to "DVD/CD master" and create the disk image.
- Mount the new disk image and turn it into a fake Mac OS X Server install disk with the following command in Terminal:

touch "/Volumes/Mac OS X Install DVD/System/Library/CoreServices/ServerVersion.plist"


4. Create a new virtual machine in VMware Fusion. I chose Mac OS X Server 10.6 64-bit as the type, but I suspect any type will work. Select the disk image just created.

Dave Miller said...

Anonymous wrote: I installed Snow Leopard in VMWare 3.1.3 with Leopard still on the Mac (getting ready for Lion). But Quicken 2007 acts like a folder and won't Launch. Quicken requires Rosetta which was installed. I copied Quicken over. Any ideas?

Yep...I got SL up and running as a VM in Fusion 4, thanks to some excellent work by many coders. The whole reason I did it was to run Quicken, so I could upgrade to Lion (which doesn't do Quicken). I was dismayed that Quicken is evidently a "package," and shows up that way in the VM.

Would any of you kewl geeks (who helped me do this to start with!) have any ideas about how to get Quicken to run in this environment? (I have a feeling this might apply to other Rosetta-dependent apps too, because M$ Office 2004 shows up as a bunch of Unix executables in my SL VM.)

Many, many thanks for any time and attention someone with expertise cares to devote to this!

Anonymous said...

aunchd only executes files in /Library/LaunchDaemons if they belong to the system, so following commands should be issued:

sudo chown root:wheel /Library/LaunchDaemons/com.rectalogic.vmware.plist
sudo chmod 444 /Library/LaunchDaemons/com.rectalogic.vmware.plist

for the patch to work under Fusion 4.1.1 and Lion.

veropcnet said...

vmware fusion 4.1 allows for 10.5 & 10.6 installation without ANY of these hacks. Fusion 4.1.1 disables os x client installs , so stick with 4.1 and avoid all these heacks listed on this page.

MichaelLAX said...

Thank you to David Martorana, who earlier showed us how to update the LaunchDaemon plist's permissions with this Terminal command:

sudo chown root:wheel /Library/LaunchDaemons/com.rectalogic.vmware.plist

and THEN run the launch daemon loader:

sudo launchctl load /Library/LaunchDaemons/com.rectalogic.vmware.plist

This now also works for Lion with Snow Leopard installed in Parallels 7

MichaelLAX said...

http://forums.macrumors.com/showthread.php?t=1365439