Home

[Mac OSx86] VMware Troubleshooting Guide Print E-mail

Description:

Troubleshooting Guide for OSx86 installations in VMware

********* 

Find the error you are getting below and follow the steps to correct it.

ACPI driver not found

  • Repartition the drive
  • Reinstall Mac OS X
  • Select the "Intel kexts" option at the Custom install screen

ACPI related errors in Verbose mode

  • Switch the guest OS to Windows NT
  • Make sure the virtual disks are set to IDE and not SCSI
  • Boot OS X
  • If the error still persists, boot OS X with the -legacy flag

Alternate Configuration VMX file

If you have problems related to configuration, try this alternate VMX file (you will have to change the file names to match yours). Note that this file won't work with VMware Server though, VMware Player and VMware Workstation only for this VMX file:

config.version = "8"
virtualHW.version = "4"
scsi0.present = "TRUE"
memsize = "1024"
ide0:0.present = "TRUE"
ide0:0.fileName = "Mac OS X Tiger.vmdk"
ide0:0.mode = "persistent"
ide1:0.present = "TRUE"
ide1:0.fileName = "auto detect"
ide1:0.deviceType = "cdrom-raw"
floppy0.present = "FALSE"
ethernet0.present = "TRUE"
ethernet0.connectionType = "nat"
sound.present = "TRUE"
sound.virtualDev = "es1371"
sound.fileName = "-1"
sound.autodetect = "TRUE"
displayName = "Mac OS X Tiger"
guestOS = "other"
nvram = "Mac OS X Tiger.nvram"

ide0:0.redo = ""
ethernet0.addressType = "generated"
uuid.location = "56 4d 24 5d 4c 16 e3 df-a0 17 e2 5e 56 3e 82 94"
uuid.bios = "56 4d 2d 7e c6 a9 7d a7-57 72 d2 43 16 83 d8 7c"
ide1:0.autodetect = "TRUE"
ethernet0.generatedAddress = "00:0c:29:83:d8:7c"
ethernet0.generatedAddressOffset = "0"

ide0:0.deviceType = "rawDisk"
workingDir = "."

b0 error

  • Reboot the system and boot to the DVD.
  • Tap F8 to access additional boot options and start the DVD with "-v -s" flags.
  • At the prompt, enter "fdisk -e /dev/rdisk0" (depends on your HD partition).
  • Type in "print" to get a list of partitions.
  • Find the Mac OS X partition and type in "flag <partition number>".
  • Type "quit" to save changes and reboot.

Cannot mount ISO on Linux host

  • Convert the ISO to a VMware VMDK file using qemu-img
  • Command: qemu-img convert -f raw <name>.iso -O vmdk <name>.vmdk
  • Attach the converted ISO as an IDE disk in VMware
  • Attach the ISO as a CD device
  • Boot from the IDE disk

com.apple.boot.plist not found error when booting
  • This usually happens because of a defective DVD
  • Try increasing the VM RAM in VMware
  • Press Enter when the screen comes up saying press any key to start Mac OS X installation. Press enter again on the next screen
  • If you are mounting the ISO instead of burning it to DVD, try burning it instead
  • If nothing works, get the Mac OS X 10.4.8 [JaS AMD-Intel-SSE2-SSE3 with PPF1 & PPF2] ISO

Cross symbol appears on the Apple logo 

  • This usually happens on the first boot after OS X installation. It is followed by a DVD/CD DMA message (see below). Click OK to the message and the symbol probably won't come up again. If it does, ignore it. It doesn't mean anything

DMA message

  • Just click OK and click the Don't show me this tip or whatever checkbox

Hard drive doesn't show up in Disk Utility

  • You have to partition and format the drive as shown in Step 6
  • Make sure the virtual drive is IDE, not SCSI

Input (keboard, mouse) doesn't work

  • Click inside the VMware screen to use input on the VM
  • If that doesn't work, get the JaS 10.4.8 ISO listed in the Software Requirements

Installation hangs

  • Please start the installer using the -v switch (verbose mode) and note the error
  • Report the error to PCWiz through our web form (below)

ISO image doesn't work

  • See if mounting the image in Daemon Tools makes a difference
  • Try burning the ISO to DVD (best option)
  • If that doesn't work, the image probably isn't compatible with VMware
  • Get a new ISO image

Kernel stack fault in 64-bit mode

  • Set the guest OS to Windows NT
  • Make sure that the virtual disks are set to IDE and not SCSI
  • Boot OS X with the
  • -legacy flag

"launchd" failure

  • This can happen if you mount the ISO on VMware's own virtual emulation
  • Use Daemon Tools to mount the ISO instead

MaxxussAMDPCNET.kext is not installed properly

  • Open Terminal and type the following lines, 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 {} \;

NAT Networking doesn't work

  • Remove the ethernet0.virtualDev="e1000" line
  • At installation, install AMD patch even if the computer is Intel

OS X hangs at the grey apple screen

  • This could be faulty virtual hardware or bad drivers.
  • Disable the Ethernet on VMware and also try installing OS x86 without anything except the Essential software and the patch for your CPU.
  • Updating VMware Workstation from version 5.5 to version 6 sometimes solves the problem
  • If that doesn't work, try booting Mac OS X in single user mode by holding the Windows key + S at startup
  • Another solution is to change scsi0.present="TRUE" in the VMX file to "FALSE"
  • Also try this: remove the scsi0.virtualDev = "lsilogic" line from the VMX file

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

  • This can be caused by a number of things:
  • It could be because your processor is too old and does support SSE2 but not SSE3 and you applied the SSE3 patch
  • Your processor may not support SSE2 at all
  • This happens on some lower end Core 2 Duo systems (E6600, 6230). No solution has been found

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

  • Set the guest OS to Windows NT to fix this
  • After setting the OS to Windows NT, make sure your virtual HD type is IDE, not SCSI

VMware continually reboots when booting the DVD

  • This happens 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)

  • Use a different emulation program such as Virtual Clone Drive or Alcohol 120%

VMware says that you are trying to run a 64-bit OS when its 32-bit

  • This could happen if you updated your unofficial x86 machine with Apple Software Update
  • If you didn't update and you are using a 10.4.8 image, make sure you are using one that's patched with PPF1
  • Disable Intel Virtualization in the BIOS of the VM if your processor is using it
  • Try changing the guest OS to FreeBSD 64 bit

"You have to restart your computer" error

  • If this error appears after following the instructions for the b0 error, then restart the installation and select the patch for your CPU/patched kernel (You will have to completely restart installation)



Enjoy this article? Bookmark onto:
Digg!Reddit!Del.icio.us!Google!Live!Facebook!Slashdot!Netscape!Technorati!StumbleUpon!Spurl!Wists!Simpy!Newsvine!Blinklist!Furl!Fark!Blogmarks!Yahoo!Smarking!Netvouz!Shadows!RawSugar!Ma.gnolia!PlugIM!Squidoo!BlogMemes!FeedMeLinks!BlinkBits!Tailrank!linkaGoGo!Free social bookmarking plugins and extensions for Joomla! websites!
 
< Prev   Next >
[ Back ]

Copyright © 2008 PCWiz Computer [Powered by Joomla] | Site Map | Donate | Mac OSx86 Search Engine
OSx86 Hardware Database

spacer.png, 0 kB
 spacer.png, 0 kB