PCWiz Blog - Mac OSx86 VMware Troubleshooting Guide
(Fixes)

This troubleshooting guide is a modified part of the Mac OS X 10.4.8 Installation Guide. It is presented here stand-alone for your convenience:

ACPI Driver Not Found

This is easy enough to fix. The first thing to try is booting with the Guest OS set to Windows NT. If that doesn't work, try booting with the -legacy parameter and the boot prompt. As a last resort, repartition the drive, reinstall Mac OS X and this time, choose to install the Intel kexts option.

b0 error

Reboot the VM and boot into the DVD. Tap F8 to get to the boot prompt. Enter '-v -s' (without quotations) and press enter. At the prompt, enter 'fdisk -e /dev/rdisk0' (without quotations) and press enter. Now type in 'print' (without quotations) to get a list of partitions. Find the partition you installed Mac OS X on and type in 'flag <partition#>' (without quotations, replacing partition# with your partition number) and press enter. Type in 'quit' (without quotations) to save changes and reboot.

com.apple.Boot.plist not found

This usually happens because of a defective DVD or ISO. The last thing to try is increasing the RAM. If that doesn't work, try burning the ISO to a DVD if you are mounting. As a last resort, get a good healthy ISO file and burn it to DVD and then try installing.

Cross symbol appears on Apple logo

This is usually a one-time thing that happens right after installing Mac OS X. This symbol is usually followed with a DMA message. Click OK to the message and reboot the VM and the symbol shouldn't appear again.

DMA Message

Just click the checkbox so that the message doesn't appear again and click OK. This is not a serious error in most cases.

Hard drive doesn't show up in Disk Utility

Make sure your virtual hard drive is IDE, not SCSI. This is what causes the problem.

Hard drive doesn't show up in OS X installer

Make sure you have partition and formated the virtual drive as "Mac OS Extended (Journaled)". If the hard drive is not partitioned and formatted, it will not appear in the installer screen.

Input (Keyboard, Mouse) doesn't work

Make sure you have clicked inside the VMware screen to let you control OS X. If you have clicked inside and it still doesn't work, try using a PS/2 mouse and keyboard. As a last resort, you will have to obtain a different ISO or DVD because the one you are using is not compatible with VMware or your hardware.

Installation hangs

Start up the Mac OS X DVD in verbose mode (enter '-v' without quotations and the F8 boot prompt and hit enter). Note the line where the installation hangs. Report the line to PCWiz by sending a message and we may be able to help you. You can also post a topic in the InsanelyMac Forums and see if someone on the forums can help you.

ISO Image doesn't work

If you have mounted the image, make sure it is mounted on a 3rd party program such as Daemon Tools or Alcohol 120%. Next, try burning the ISO to a DVD and see if that makes a difference. If nothing works, the image is probably not compatible with VMware. Obtain a new image and try again.

'launchd' failure

This error comes up if you are mounting the OS X ISO directly on VMware. You have to mount the ISO on a 3rd party program such as Daemon Tools or Alcohol 120%. You can also burn the ISO to DVD, which will work better.

MaxxusAMDPCNET is not installed properly error

Open Terminal in Mac OS X (/Applications/Utilities) and type the following commands pressing enter after each one:

cd /System/Library/Extensions
sudo find MaxxussAMDPCNET.kext -type d -exec /bin/chmod 0755 {} \;
sudo find MaxxussAMDPCNET.kext -type f -exec /bin/chmod 0644 {} \;

Now reboot the virtual machine and the error should be gone.

NAT Networking Doesn't Work

Try removing the ethernetVirtualDev="e1000" line from the VMX configuration file if its there, and try adding the line to the VMX configuration file if it isn't already there. If that doesn't fix it, install the MaxxussAMDPCNET driver. You can find instructions in this post.

OS X hangs at gray Apple screen

This happens usually because of faulty virtual hardware or bad drivers, language packs, patches, etc. There are many things you can try to fix this problem. Here are the possible solutions (from obvious to least obvious):

1) Disable the Ethernet, Sound, USB, Floppy, and any other unneccessary hardware in VMware
2) Reinstall OS X with just the base operating system and the patch for your CPU
3) If you are running VMware Server, switch to Workstation 6 and try
4) If you are running VMware Workstation 5.5 or lower, try updating to version 6
5) In the VMX configuration file, change scsi0="TRUE" to scsi0="FALSE"
6) Boot OS X in single user mode by entering the -s switch at the F8 boot prompt

"The CPU has been disabled by the guest operating system. You will need to power off or reset the virtual machine and this point." error

If you get this error, you're pretty much doomed. This can happen because your processor doesn't support SSE2/SSE3 or if you installed the wrong CPU patch durning OS X installation. This error also seems to come up on lower end Core 2 Duo CPUs. No exact solution to this problem has been found.

**Virtual machine kernel stack fault (hardware reset)*** error

If this happens before you install OS X, try setting the guest OS to Windows NT and your hard drive type to IDE. If this happens after an OS kernel update, then that is the problem. Revert back to a previous configuration using a virtual machine snapshot (if you can). If you didn't make a snapshot and you did back up the old kernel, boot into single user mode using the -s F8 boot prompt switch and copy the old kernel back using the sudo cp -R command:

sudo cp -R <path of old kernel> /mach_kernel

Replace <path of old kernel> with the path of your kernel backup. If you didn't back up the kernel and you didn't make a snapshot, you will have to reinstall OS X.

VMware continually reboots when booting DVD

This can happen on some Conroe boards and Intel Core Duo/Solo processors when the guest OS is set to FreeBSD. To fix this, set the guest OS to Windows NT and set the number of virtual processors to 1.

VMware runs extremely slow (when using Daemon Tools 4.06 or newer to mount ISO)

Mount the ISO using a different program like Virtual Clone Drive or Alcohol 120%.

VMware says that you are running a 64-bit OS when you are running 32-bit

This can happen if you update your hacked OS X using Apple Software Update. If you didn't update and you are using a 10.4.8 image, make sure it is patched with PPF1. The last thing to try is to disable Intel Virtualization in VM BIOS if your processor is using it.

"You have to restart your computer" panic screen error

If this appeared after the b0 error, reinstall OS X and select the correct patch for your CPU. If this jappened after a kernel update, follow the instructions in the "Virtual machine kernel stack fault" error to restore the old kernel if you have it backed up. You can also restore a snapshot if you made one. If this just appears for no reason, post a message on the forums or send a message to pcwiz.

If you have an error that is not on this guide, please send a message to pcwiz


Read The Full Article:
http://forum.insanelymac.com/index.php?automodule=blog&blogid=146&showentry=283

Add to del.icio.us

Digg this

Post to Furl

Add to reddit

Add to myYahoo!