Submit Hint Search The Forums LinksStatsPollsHeadlinesRSS
14,000 hints and counting!

10.5: Virtualize machine-specific 10.4 in Fusion 2 Apps
First of all, this hint (which is based on some very good previous hints appearing here) is only of academic interest, almost as a proof of concept, for now (at least until Apple will change their licensing terms). So, let's take it only as an -- I hope interesting -- exercise to understand things a little better.

So, why would one hypothetically want to do all this? Well, it could be very good for running legacy, up-to-Tiger-only programs (see, for example, Photoshop 7, which won't run on Leopard; etc.) and/or for testing software in a Tiger/Intel environment, without being forced to have a partition dedicated to Tiger. So, Apple, it would really be a great thing to permit virtualization of *all* your Intel-compatible OSes, both server and client, starting from Tiger and upwards.

Now, assuming you have a machine-specific Mac OS X 10.4.x Tiger DVD for Intel, and want to try to run this operating system as a virtual machine through VMware Fusion 2.x, on the same computer upgraded to Leopard? Well, let's try to do this in an as simple way as possibile, from within Mac OS X 10.5.x Leopard...

Read on for my how-to...

  1. Create a new Mac OS X 10.5 Server 64-bit (the default setting) virtual Machine (VM) in VMware Fusion; don't start it, then quit Fusion.
  2. Navigate to the VM package's position (by default located in ~/Documents » Virtual Machines, unless you have changed it). Control-click on the package, then choose More » Mount Virtual Disk from the pop-up menu, thus mounting the pre-formatted (with HFS+ Journaled) VM disk on the Desktop.
  3. Insert your Tiger/Intel DVD and navigate to /System » Installation » Packages » OSInstall.mpkg, then double-click it to open the Mac OS X installer.
  4. In the Mac OS X installer, select the mounted VM disk as the target, and then install Tiger as usual: now, as you install from within your specific machine, the installer won't complain, even if you select a virtual disk image as the target disk (and not, for example, your internal HD).
  5. Once the install is complete (no reboot needed), exit the installer.
  6. Open the Terminal and issue the command:
    sudo touch "/Volumes/Macintosh HD/System/Library/CoreServices/ServerVersion.plist"
    This makes it possibile to run the client version in a server-based VM; if you renamed the VM disk, of course, use the actual name instead of the default Macintosh HD.
  7. Also in Terminal, do this:
    sudo nano "/Volumes/Macintosh HD/Library/LaunchDaemons/com.automate.vmware.plist"
    You can use whatever name you want to insted of automate, but leave the rest alone. Then paste this text into the new file:
    <?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.automate.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 & wait $!</string>
    </array>
    <key>KeepAlive</key>
    <true/>
    <key>RunAtLoad</key>
    <true/>
    </dict>
    </plist>
    This will automate the creation and deletion of the ServerVersion.plist file, so Fusion thinks that the OS is server before booting it, while OS X thinks that it correctly is the client once booted. Then use the usual Control-O, Enter, and Control-X to save the file. Finally, unmount the VM disk from the Finder.
  8. Open VMware Fusion and then start the Mac OS X VM in the Virtual Machine Library: everything should be OK, as in an ordinary VM, and you will boot into a virtualized Mac OS X Tiger, where you can do the usual things.
  9. This is probably optional, but while booted into Tiger for the first time, open the Terminal and issue this command:
    sudo launchctl load /Library/LaunchDaemons/com.automate.vmware.plist
    It should say that it's already loaded, if things are working right.
Voilà: Tiger running in a VMware Fusion VM, where everything works as usual -- except, sadly, for the VMware Tools, which don't (yet?) work in Tiger (so there's no point in installing them).

If you want a better screen resolution than the default 1024x768 one, edit the /Library » Preferences » SystemConfiguration » com.apple.Boot.plist file with nano (see above) or TextEdit from within the Tiger VM, adding this:
<key>Graphics Mode</key>
<string>1680x1050x32</string>
Replace with whatever resolution and color depth you want. Add this immediately after the <string>Yes</string> line. Save the file, and you will reboot with that resolution as the default one the next time you boot.

Full screen view works at the specified resolution, while windowed mode view is scaled down, due to the lack of Tiger-compatible VMware Tools.

BTW, personally I found that NAT networking worked better than the default bridged mode (but that might also depend on your router, etc.); Sadly, there is still no sound support in Fusion for Mac OS X-based VMs.

[robg adds: I haven't tested this one. It's similar to this previous hint, but specific to virtualizing 10.4 machine-specific DVD discs. Given how I make my living, I share the author's opinion that Apple should allow virtualization of all the Intel-capable OSes. I know it'd make my life much simpler!]
    •    
  • Currently 3.91 / 5
  You rated: 2 / 5 (11 votes cast)
 
[37,351 views]  

10.5: Virtualize machine-specific 10.4 in Fusion 2 | 38 comments | Create New Account
Click here to return to the '10.5: Virtualize machine-specific 10.4 in Fusion 2' hint
The following comments are owned by whoever posted them. This site is not responsible for what they say.
10.5: Virtualize machine-specific 10.4 in Fusion 2
Authored by: atverd on Nov 03, '08 12:05:50PM

Tried generic 10.4.6 and 10.4.6 from my MacBook Pro and they don't boot after installation. First doesn't boot at all, second starts and crashes. What version of 10.4 you tried in your installation?



[ Reply to This | # ]
10.5: Virtualize machine-specific 10.4 in Fusion 2
Authored by: Sven G on Nov 03, '08 01:01:42PM

I tried it with a Mac OS X 10.4.10 Mac Mini install DVD, and everything worked well. Could it maybe be that some older versions are incompatible with Fusion? I don't know...



[ Reply to This | # ]
10.5: Virtualize machine-specific 10.4 in Fusion 2
Authored by: dirtysauce on Nov 03, '08 06:00:54PM

I've also had the same issue with this and 10.4.6. I tried this same method for 10.5 and both have a kernel panic [crash] and only get as far as the grey apple logo.

Does anyone have any of the same issues?



[ Reply to This | # ]
10.5: Virtualize machine-specific 10.4 in Fusion 2
Authored by: Sven G on Nov 03, '08 11:17:52PM

I tried the hint also with a Mac OS X 10.5 retail DVD, and that too worked without problems. Maybe it could be that there's something wrong with your Fusion installation...? Personally, I have sometimes fixed problems simply by reinstalling Fusion.



[ Reply to This | # ]
10.5: Virtualize machine-specific 10.4 in Fusion 2
Authored by: jiclark on Nov 05, '08 10:59:33AM

From my experience, most recent machines require something newer than 10.4.6; my MBP 10.4.8 disks worked fine...



[ Reply to This | # ]
10.5: Virtualize machine-specific 10.4 in Fusion 2
Authored by: apeish on Nov 05, '08 06:52:56AM

Similar issues here. Tried a generic 10.4 disk and the specific for the Mac i've tested on.

* The hardware-specific disc failed while installation (tried twice) an a macbookpro and once on a Mac Pro.
* the generic install works but fails while booting in VMware (can't locate com.apple.Boot.plist)

So for me it looks like its not finding where to boot from at all.



[ Reply to This | # ]
10.5: Virtualize machine-specific 10.4 in Fusion 2
Authored by: mkuron on Nov 11, '08 05:42:12AM

There are no generic Intel-Tiger discs (they never got sold through retail). So you probably used a PPC disk, which obviously won't work.



[ Reply to This | # ]
10.5: Virtualize machine-specific 10.4 in Fusion 2
Authored by: pediger on Nov 03, '08 01:32:48PM

Well, I can't get past step 2. Obviously it's a VMWare/VMDKMounter issue, but I thought I'd ask in case anyone has experienced this.

When I try to mount the new, as well as any old, image, I just get a popup window that says "test.vmdk" and "The specified disk is not mounted." This has been reported on the VMware forums but with no clear resolution.

I uninstalled the newer MacFuse 1.7.1 and reinstalled VMWare in order to get version 1.5.1 (verified), rebooted, and successfully tested MacFuse with sshfs. When I do try to mount a suspended image, rather than the new one that is shut down, the error message is different and indicates I indeed cannot mount a suspended image.

Anyway, I thought I'd ask here first.
(10.5.5; VMWare 2.0 116369)



[ Reply to This | # ]
10.5: Virtualize machine-specific 10.4 in Fusion 2
Authored by: Sven G on Nov 03, '08 11:27:37PM

I, too, had problems mounting VMs some time ago; now, anyway, I have the latest versions of Leopard, Fusion, and MacFuse (installed separately): so it shouldn't be a version problem. Maybe you could try to reinstall the latest MacFuse from their website, and then reinstall Fusion...?

(BTW, regarding the last part of the hint, one can of course set the preferred screen resolution also before booting the VM for the first time, by editing the related file directly on the mounted disk image. Anyway, be sure to unmount the image before starting Fusion; if it repeatedly gives a disk in use error, one can always try to logout or reboot to unmount it.)



[ Reply to This | # ]
10.5: Virtualize machine-specific 10.4 in Fusion 2
Authored by: pediger on Nov 04, '08 10:15:27AM

Thanks for that Sven. Since I tried both, I agree the version of Fuse was probably not the issue and will upgrade again when I get a chance. I haven't really gotten much use out of Fuse lately; I need to check for any new "filesystems" out there that may be of more use.

In order to follow through with this VMWare/OS X experiment, I was able to get Leopard working as a client by using the alternative ISO-image installation method. Works mostly (no crashing or panics; VMWare Tools support is pretty good) but networking is more or less dead. NAT gives me nothing but a 169.254... address; Bridged does get a valid address from my router, so some network traffic is flowing, but after that neither LAN nor WAN traffic gets in or out. Bonjour shares are showing, interestingly, but don't connect. Must be that certain protocols are not being routed properly.



[ Reply to This | # ]
10.5: Virtualize machine-specific 10.4 in Fusion 2
Authored by: Sven G on Nov 04, '08 11:25:49AM

On my experimental Tiger VM (the one described in the hint), NAT networking works flawlessly, while bridged mode doesn't connect (at least the first time I booted): it looks similar to a problem I had in Ubuntu with bridged networking, where I had to edit /etc/sysctl.conf, adding these lines:

net.ipv4.tcp_syncookies = 1
net.ipv4.tcp_window_scaling = 0
net.ipv4.tcp_ecn = 0

(effective after rebooting). This because my router didn't work well with the default settings: but how would one do this in Mac OS X? Is there an easy way? That's the problem...



[ Reply to This | # ]
10.5: Virtualize machine-specific 10.4 in Fusion 2
Authored by: pediger on Nov 04, '08 01:29:17PM

Both NAT and Bridged appear to work fine after a reboot of the host. Pshaw! I rebooted after reinstalling VMWare so I didn't think to do it again.



[ Reply to This | # ]
10.5: Virtualize machine-specific 10.4 in Fusion 2
Authored by: Sven G on Nov 04, '08 10:56:00PM

Same here: both NAT and bridged mode now work in my experimental Tiger VM, too - at least, this problem is solved! ;-) :-)

BTW, returning to the hint, even if the are no Tiger-compatible VMware Tools, there is a minimal mouse integration (à la Screen Sharing); but, sadly, there's no time synchronization between host and guest.

To the previous posters: are you sure you made a 64-bit VM? Personally, I had hangs at boot when I tried to make ordinary, non-64-bit Mac OS X VMs. But probably this is not the problem...

Another question: do there exist retail or other generic Tiger/Intel DVDs? I thought that they were all machine-specific (even if this can be modified with a simple hack by modifying an invisible file, if I'm not mistaken: maybe there was even a hint on this, here, some time ago), and thus can install only on the computer they came with.



[ Reply to This | # ]
10.5: Virtualize machine-specific 10.4 in Fusion 2
Authored by: mkuron on Nov 09, '08 10:26:42AM
Just tried it with a 10.4.8 DVD that came with my MacBookPro2,2 (October 2006). Installing to the vmdk worked seamlessly (after I manually formatted it with HFS+ by mounting it into a Leopard VM). But it won't boot - it just gets stuck at the grey Apple logo, even before the spinner shows up. If I boot it up with the option -v or -s, it gets stuck at a black screen after scrolling through a list of messages (ending with something about TSC clock). I even upgraded the vmdk to 10.4.11 (just point the 10.4.11 combo updater to the mounted vmdk), but no difference. I don't think the problem is Fusion-related since I'm running a Leopard VM without any problems.

[ Reply to This | # ]
10.5: Virtualize machine-specific 10.4 in Fusion 2
Authored by: Sven G on Nov 09, '08 11:48:19PM

An update: somtimes it indeed happens that the VM hangs at boot, also in my case, where everything worked from the beginning; but rebooting it from the VMware Fusion menu usually solves the problem. As for the Tiger/Intel DVD version compatibility, I cannot really say, as I only have a 10.4.10 DVD. Updating the system on the VM with the 10.4.11 Combo updater before booting, as said above, could be worth a try, anyway, if the VM hangs or crashes.

Things could probably improve if also Tiger became an officially supported system on VMs...



[ Reply to This | # ]
10.5: Virtualize machine-specific 10.4 in Fusion 2
Authored by: Timpraetor on Dec 16, '09 07:52:54AM

I was witnessing this hang overnight. It hung for 20 minutes or so if I didn't access the VM for around 30 minutes. I changed the VM settings to use an ISO image of a Linux distribution as the default attached CD. So far (3 hours now), I've not seen the hang since mounting the disk ISO image rather than using the real drive.



[ Reply to This | # ]
No Luck!
Authored by: Timpraetor on Dec 16, '09 08:16:43AM

Ugh! It finally hung again. My trick postponed the hang, but it still happened.

Has anyone had any luck determining the true cause?



[ Reply to This | # ]
VM Still Hangs after all updates
Authored by: Timpraetor on Dec 16, '09 03:58:24PM

I've now updated to the 10.4.11 level in the VM and I'm still witnessing hangs. However, this time I got a message from VMWare telling me the the virtual CPU had gone into standby mode.

I'm using the default settings of 1 CPU and 1024MB. Any thoughts?



[ Reply to This | # ]
VM Still Hangs after all updates
Authored by: Sven G on Dec 16, '09 10:23:53PM

Have you tried simply disconnecting the virtual CD/DVD drive (from the VM's status bar, on the bottom right of its window)? But maybe there are also other reasons for those hangs, who knows (does the VM go into sleep mode, maybe? if so, you could set it to never sleep in the Tiger VM's Energy Saving preferences)...



[ Reply to This | # ]
VM Still Hangs after all updates
Authored by: Timpraetor on Dec 17, '09 07:14:53AM

I've just changed to not sleep, not put the hard drives to sleep, and no screen saver. I'll report back in a few hours.



[ Reply to This | # ]
VM Running Successfully
Authored by: Timpraetor on Dec 17, '09 09:32:12AM

I'm pleased to report that the power management stuff seems to have been the problem. I've now run my 10.4.11 VM for far longer than I've ever run it up to now and it's still going strong. While it was running, I used a similar process to test the feasibility of Leopard in the same light and it is also successfully running.

And NOW I can retire my 10.4 and 10.5 boot partitions.

Looks like a session with BRU PE and my LTO-4 SAS drive will let me reconstruct my system in a Snow Leopard only form (250GB boot drive and 3 750GB drives striped for performance) and give me back a good bit of wasted disk space!



[ Reply to This | # ]
10.5: Virtualize machine-specific 10.4 in Fusion 2
Authored by: Sven G on Nov 14, '08 11:46:09AM
IMPORTANT! There is an error (after "999999"...) in the com.automate.vmware.plist file above, which thus should correctly say:

<?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.automate.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>

(as from this website: http://blog.rectalogic.com/2008/08/virtualizing-mac-os-x-leopard-client.html, which was cited in a previous hint).

I'm sorry for the mistake.

P.S.: A bug I recently discovered is that sometimes the Tiger VM becomes unresponsive for a certain amount of time, and it looks like it is accessing the DVD drive during that period: so, another strange issue with this of course completely unsupported configuration...

[ Reply to This | # ]
10.5: Virtualize machine-specific 10.4 in Fusion 2
Authored by: Sven G on Nov 15, '08 02:07:15AM
Hmmm... of course with no semicolon (";") after:

<!DOCTYPE plist PUBLIC "-//Apple Computer//DTD PLIST 1.0//EN"
"http://www.apple.com/DTDs/PropertyList-1.0.dtd">;

(must have been added automatically by the forum software, which also underlined the URL).

[ Reply to This | # ]
10.5: Virtualize machine-specific 10.4 in Fusion 2
Authored by: builtinbc on Nov 25, '08 10:39:51AM

I've managed to install Tiger 10.4.10 on a MacBook Pro 2.6 Ghz - well, sort of - using this hint. I used Tiger installer disks I talked Apple into selling me for the previous MBP model that came bundled with it - it took some doing to get these, because mine came with Leopard and wasn't designed to run Tiger. In any event, Tiger runs perfectfully when installed on and booted from a separate partition on my MBP. I used Carbon Copy Cloner to clone my Tiger partition to a new disk created in VMware Fusion 2.0.1. However, I can't boot from a shut down state, only resume from a snapshot. Over time I imagine this will lead to severe memory fragmentation. Does anyone have a fix for this?

My reason for trying to run Tiger is that I use ViaVoice OS X for Mac (I've trained it on thousands of specialized words and phrases, so MacSpeech Dictate doesn't do it for me). Unfortunately it breaks under Leopard. Audio doesn't work in the VMWare installation, but I can run ViaVoice anyway because I can connect my Plantronics USB dictation headset directly. However, performance varies unpredictably from acceptable to awful, depending on what "kernel task" is doing in the background. At best it isn't as accurate as when I boot directly into my Tiger partition, partly because the MBP's audio system seems to improve gain control, so it's less sensitive to headset microphone positioning.

Some folks say Parallels Desktop may be faster, so I upgraded my Parallels to v.4 which also permits OS X 10.5 Server to be installed. However I haven't been successful in getting it to run, although by creating the
/Volumes/Macintosh HD/System/Library/CoreServices/ServerVersion.plist
file in a clone of the client Mac OS X Install Disc 1, Parallels stops complaining that I can only install OS X 10.5 Server. Has anyone successfully figured out how to install a Tiger client iunder Parallels Desktop 4? This is nontrivial , as Parallels equivalent of VMDK Mounter won't allow the virtual disk to be mounted unless a valid Mac OS has already been installed.




[ Reply to This | # ]
10.5: Virtualize machine-specific 10.4 in Fusion 2
Authored by: mkuron on Nov 30, '08 12:27:35PM

How about connecting the image to a Leopard VM in Parallels? That should allow you to partition/format the virtual disk.



[ Reply to This | # ]
10.5: Virtualize machine-specific 10.4 in Fusion 2
Authored by: Sven G on Dec 01, '08 01:33:25AM

Another way could be to connect the unformatted Tiger (or Leopard) client image to an Ubuntu Desktop or GParted live CD, thus starting it up from the CD and formatting the image with the included GParted partitioning tool: IIRC, it can create HFS+ Journaled volumes (but I'm not completely sure...).

(Of course, with this method it isn't necessary to hack the Leopard or Tiger install DVD with the ServerVersion.plist trick, in order to start up from it and format the drive image from there with Disk Utility.)

BTW, strange that Parallels 4, with all its features, still doesn't preformat Mac OS X server VMs (à la VMware Fusion)...



[ Reply to This | # ]
10.5: Virtualize machine-specific 10.4 in Fusion 2
Authored by: Sven G on Dec 02, '08 11:39:46AM

(^^^ My post above of course should have been a nested reply to the previous ones...)

Anyway, I tried to create a Mac OS X Server VM in Parallels 4, changed the OS type to Ubuntu Linux and finally started it up with the Intrepid Desktop CD: well, from the partitioning tool it is clear that the image is indeed preformatted with HFS+ (Journaled); and, at least in the Ubuntu version, it also seems that GParted cannot create HFS partitions (they are greyed out in the formatting options).

So, theoretically there should be no problems mounting the image: but it isn't possibile for some reason, as Parallels Mounter fails to activate it on the desktop.

Strange...



[ Reply to This | # ]
10.5: Virtualize machine-specific 10.4 in Fusion 2
Authored by: marcdeb on Feb 09, '09 12:29:21PM

I just wanted to add that this procedure works exceptionally well with Leopard as a guest as well. Not one single problem.



[ Reply to This | # ]
10.5: Virtualize machine-specific 10.4 in Fusion 2
Authored by: PapaJ on Mar 10, '09 11:27:33AM

Absolutely yes, installing [Leopard or Tiger] this way means being able to surf the web while the installation is chugging away.

Note on that though: The Leopard DVD doesn't show its System directory in Finder. Getting there through Terminal is easy enough though...
i.e. here is my command line, after navigating to the Packages directory
" open ./OSInstall.mpkg "

Another note: I tried taking such an image created on a Mac Mini over to a MacBook and it would only ever Kernel-Panic, right after starting up.
-- In case you are wondering what would happen under such a scenario.



[ Reply to This | # ]
10.5: Virtualize machine-specific 10.4 in Fusion 2
Authored by: Timpraetor on Dec 15, '09 03:36:43PM

I've just stumbled across this and have successfully installed my Mac Pro 10.4.7 version onto VMWare 3. Thanks to Sven and MOH! Everything looks great - except the fact that I am unable to install any applications as they all think that there's no OS X 10.4 installed on the disk. I specifically need Xcode for debugging under 10.4...

I've even gone so far as to exit VMWare, mount the vmdk as in the installation steps and try there. Still no luck.

Has anyone gotten beyond simply installing and getting this to run?



[ Reply to This | # ]
10.5: Virtualize machine-specific 10.4 in Fusion 2
Authored by: Timpraetor on Dec 15, '09 03:49:05PM
Oooh! I feel like a "Mr. Kotter" moment just smacked me up side the head.
  • Delete the /System/Library/CoreServices/ServerVersion.plist file
  • Perform the installs
  • Recreate the ServerVersion.plist file


[ Reply to This | # ]
10.5: Virtualize machine-specific 10.4 in Fusion 2
Authored by: Sven G on Dec 16, '09 05:59:21AM

The creation and deletion of the ServerVersion.plist file should be automatic, with the script supplied in the hint: but be sure to use the original one, provided in one of my latest comments.

BTW, one can use a machine-specific 10.4 Intel DVD to install Tiger as a virtual machine in VMware Fusion also on another Mac, by editing the "/Mac OS X Install DVD/System/Installation/Packages/OSInstall.mpkg/Contents/OSInstall.dist" file: see Google for more details...

Still waiting for Apple to officially support - at least ideally - virtualization of Mac OS X client; anyway, as they have said nothing on this matter, probably for them it is basically OK anyway: which might be good enough, also considering that no harm is really done to Apple by virtualizing Tiger, etc. etc.; indeed, an even better and more rational use of their excellent OSes can be done by also virtualizing them!



[ Reply to This | # ]
Switched to the new plist - works much better
Authored by: Timpraetor on Dec 16, '09 07:56:09AM

Too bad that you can't edit the original entry to change that. I didn't read all of the comments, so missed the changed code.

So far, so good. I'm now about to switch to Snow Leopard permanently on my Mac Pro (versus tri-booting) and run Tiger and Leopard as VMs for testing and debugging.

Thanks again!



[ Reply to This | # ]
Switched to the new plist - works much better
Authored by: Sven G on Dec 16, '09 09:32:14AM

Good to know it finally worked... :-)

The only really big issue remaining is the lack of sound support - no drivers included - for OS X VMs, and, in the case of Tiger, also the lack of compatible VMware Tools (which anyway are still rather limited also with Leopard+ VMs: no Unity view, for example, AFAIK). There are, indeed, some AppleAC97Audio.kext and similar extensions floating around in the Hackintosh sites and forums on the web, but I haven't yet found one which really works in Fusion (well, I also only tried one time, and the downloaded extension probably was outdated: the audio hardware - after adding it in the Fusion VM preferences - was indeed recognized, but no sound came out of the Tiger VM anyway): maybe other MacOSXHints readers know better how to solve this problem...?



[ Reply to This | # ]
10.5: Virtualize machine-specific 10.4 in Fusion 2
Authored by: Sven G on Jan 15, '10 05:33:33AM

The blog above - http://blog.rectalogic.com/2008/08/virtualizing-mac-os-x-leopard-client.html - now recommends this for VMware Fusion 3:

"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 [Fusion] will then use the hacked boot image from darwin.iso."

Some of the latest comments in that blog (the Fusion 3-related ones) are also interesting.

So, essentially, in order to virtualize Mac OS X Client in Fusion 3, be sure to change the virtual firmware to BIOS instead of the default EFI (if you create a new VM in Fusion 3; existing VMs created from Fusion 2 should continue to work without problems)...



[ Reply to This | # ]
10.5: Virtualize machine-specific 10.4 in Fusion 2
Authored by: mdc1952 on Mar 02, '10 01:18:21PM

I hypothetically tried this on an early intel iMac that I would like to update to Snow Leopard. After installing SL on a small partition, I academically successfully got Tiger to run. However, the Graphics Mode change seems to have no effect on the resolution. Anything else I can try or what may have gone wrong?



[ Reply to This | # ]
10.5: Virtualize machine-specific 10.4 in Fusion 2
Authored by: Sven G on Mar 06, '10 04:04:35AM

Well, hypothetically and academically above all in the name of free knowledge: it's quite logical and fascinating to experimentally virtualize also Mac OS X Client, Spock would have said (maybe?)... :-)

As for your problem, it's difficult to help without more details; BTW, sure that you correctly changed the graphics mode key in the guest virtual machine, and not by mistake on the host...?



[ Reply to This | # ]
10.5: Virtualize machine-specific 10.4 in Fusion 2
Authored by: mdc1952 on Mar 09, '10 12:07:22PM

After some additional fiddling with the plist file, I finally got it to boot in 1440x900 so I can work in full screen. Thanks for the tip. Now if only Apple would make it ok for VMWare to do a more fully functional method.



[ Reply to This | # ]