Run mac os on vmware workstation 11 mac os x#
Run mac os on vmware workstation 11 drivers#
Run mac os on vmware workstation 11 update#
Run mac os on vmware workstation 11 pro#
Run mac os on vmware workstation 11 license#

Despite that concern, it seems to work fine in my experience. The efi32-srvr.rom file is pretty old, and VMware’s own EFI firmware has probably been updated quite a bit in the meantime, so you’ll be missing out on some fixes. Note that there is a potential danger in doing this. vmx file, and add the following line to the vmx file: efi32.filename = 'efi32-srvr.rom' Once you have the file, put it in the same directory as your. This custom firmware is called efi32-srvr.rom and is included with older versions of the unlocker I mentioned earlier. I’ve found other workarounds online that involve adding files to the CD and hard drive to fool VMware into thinking it’s booting to a server install, but there’s an easier approach: use a custom EFI firmware that doesn’t perform this check.

Run mac os on vmware workstation 11 mac os x#

If you try to boot the install disc at this point, VMware will complain because you’re not running Mac OS X Server. There’s nothing really special about the setup at this point. The hard drive and CD drive can both be SATA. Set the guest OS to “Mac OS X Server 10.5 32-bit.” Yes, that’s 10.5 - like I said earlier, 10.4 was never supported, so 10.5 is the closest choice we’ve got. I’m going to walk you step-by-step through the process of fixing each little glitch as we run into it. VMware technically doesn’t support OS X 10.4 through 10.6 (except for the server versions of 10.5 and 10.6), but if you follow these directions, it will work. Finally, you need access to a newer install disc that has a compatible kernel you can borrow, so it makes more sense to just use the newer disc to install it in the first place.

Run mac os on vmware workstation 11 update#

You also have to install the 10.4.11 combo update onto the hard drive before it will be bootable, because the kernel installed by the older disc ends up having the same problem. The process is complicated and easy to screw up. I’d recommend not doing this for several reasons. It is actually possible to take an older 10.4 install disc and replace its kernel, kexts, and supporting files with newer versions that are capable of booting into VMware.

Run mac os on vmware workstation 11 pro#

An install disc for a Core 2 Duo MacBook Pro (MacBookPro3,1) with 10.4.10 works fine with no modifications.

Run mac os on vmware workstation 11 drivers#

I think it is missing the proper drivers for the storage controllers emulated by VMware, because it gets stuck waiting for the root device when I try to boot the CD, regardless of whether I make the CD drive SATA or IDE. My MacBook Pro 17″ Core Duo (MacBookPro1,2) came with 10.4.6, and its installer disc will not boot a VMware VM. I’d recommend shooting for version 10.4.7 or higher. You’ll need a 10.4 install DVD that originally came with an Intel Mac from that era. As I’ve already mentioned, the Intel build of 10.4 was never released as a retail copy. The first challenge is you need to find an OS X 10.4 install disc that contains the Intel version. If you really don’t care about following the rules on this, there is an unlocker that you can run to modify VMware Player or VMware Workstation to support OS X guests on Windows and Linux.

Run mac os on vmware workstation 11 license#

Once again, this is because Mac OS X’s license agreement only allows you to run Mac OS X on Macs. You have to be using VMware Fusion to do this, because the Windows and Linux versions of VMware don’t support virtualizing OS X. I would like to give credit to the following sites/forums for helping to explain various pieces of the puzzle: This is mostly just a compilation of information available on different parts of the internet. I’m going to do my best to explain what to do. In order to create a VMware virtual machine of Mac OS X 10.4, there are several challenges that you have to overcome. Who knows - maybe it’s still useful for certain developers who still need to test how things work on 10.4 without keeping an old power-hungry machine around that is capable of running it. With that said, I really doubt Apple cares about such an old version of OS X these days, and I think creating a VM of it is a really cool thing to do for educational purposes. And technically, it’s against OS X’s license agreement to virtualize it (same with the non-server versions of 10.5 and 10.6). Nobody’s really using it anymore because it’s so old. It was only bundled with the first Intel Macs before 10.5 “Leopard” came out in 2007.īecause of the way it was weirdly released, it’s not super common to virtualize OS X 10.4 for Intel. There wasn’t a retail copy of the Intel version of Tiger.

Because the Intel version came out in 2006 after the PowerPC version had already been in stores, it’s kind of a weird release. It was also the version that Apple first used on its Intel Macs in 2006. If you can believe it, Mac OS X 10.4 “Tiger” is over 12 years old as of this writing.