Snow Leopard Server doesn’t seem to install in a virtual machine on VMWare Fusion 3.0

osx-snow-leopardvmware-fusion

I have purchased a new Mac Mini with Snow Leopard Server pre installed.

I plan to use many of its services: Web serving, calendar sharing, mail, file sharing, VPN, etc, for up to 10 users. Problem is, being new to networking, I anticipate this to be a trial and error process.

So I have decided to virtualize Snow Leopard Server under VMWare Fusion 3.0 on my (fairly powerful) iMac, first, do all the trial and error, and once I have gotten it right, setting up the Mac Mini properly.

Problem is, despite Fusion 3.0 working very well with Ubuntu, Windows 7, XP, etc…. the VM gives me an error when trying to install from the Snow Leopard Server disk that came with the Mac Mini: "Mac OS/X cannot be installed on this machine", in this case "this machine" of course being the Fusion 3.0 virtual machine (2 gig RAM, 40 gig HD).

Anybody suggest what I am doing wrong? Isn't Leopard Server supposed to be virtualizable on Apple hardware?

Best Answer

Are you running the install disc that came with a server, or the full version. If you are trying to install it by the machine specific version, you will find that it will not work as it's looking for a specific machine ID and will not continue.

I've installed SL Server from the full version DVD without a hitch but was not impressed with the speed.

Related Solutions

VMWare Fusion: Bridged Network Using a Bonded NIC

Try the Tokamak Networking Scripts for VMware Fusion, they provide advanced networking setup and might possibly do what you're looking for...

WARNING: If you have a Home Directory protected by FileVault, DO NOT INSTALL FROM WITHIN THAT DIRECTORY! It will mess up FileVault (happeend to me once)

EDIT: You might also try this thread on the VMware community forums. An exerpt for you:

After seeing this post by powervm: http://communities.vmware.com/thread/151384?tstart=0

I was able to get bonded nics/link aggregates to work.

edit /Library/Application Support/VMware Fusion/boot.sh and look for the vmnet-bridge section and edit accordingly.

vmnet-bridge puts itself in background (daemon mode)
Bridge to host network interface 'en0'.
"$LIBDIR/vmnet-bridge" -d /var/run/vmnet-bridge-vmnet0.pid vmnet0 en0
Bridge to host network interface 'en1'
"$LIBDIR/vmnet-bridge" -d /var/run/vmnet-bridge-vmnet2.pid vmnet2 en1
#"$LIBDIR/vmnet-bridge" -d /var/run/vmnet-bridge-vmnet3.pid vmnet3 bond0
Bridge to the primary host network interface (which can change over time).
#"$LIBDIR/vmnet-bridge" -d /var/run/vmnet-bridge-vmnet0.pid vmnet0 ''

Edit the vmx file for your virtual machine and change 

ethernet0.connectionType = "bridged"
ethernet0.vnet = "/dev/vmnet0"

to

ethernet0.connectionType = "custom"
ethernet0.vnet = "/dev/vmnet0"

make sure fusion isnt running and restart it with

sudo /Library/Application\ Support/VMware\ Fusion/boot.sh --restart 

Im not certain what speed im getting on the link in the VM, as task manager states it running at 10mb/s as does the driver. But I have network connectivity, which is all I wanted.

Mysql – Snow Leopard: MySQL doesn’t start

After adding the /usr/local/mysql/bin path to PATH I get the following error when executing ./mysqld

100105 14:14:11 [Warning] Setting lower_case_table_names=2 because file system for /usr/local/mysql-5.0.51b-osx10.5-x86/ is case insensitive
100105 14:14:11 [ERROR] Fatal error: Please read "Security" section of the manual to find out how to run mysqld as root!

100105 14:14:11 [ERROR] Aborting

100105 14:14:11 [Note] ./mysqld: Shutdown complete

Best Answer

Related Solutions

VMWare Fusion: Bridged Network Using a Bonded NIC

Mysql – Snow Leopard: MySQL doesn’t start

Related Topic