|
12-15-2008, 07:26 AM
|
 |
|
|
Join Date: Jan 2008
Location: WA, USA
Posts: 933
|
|
Quote:
Originally Posted by axhi
interesting, i am not certain. i believe i am using a backup now because its the only thing that doesnt make my stuff crash. How do i make sure that my mach_kernel.voodoo is gonna be mach_kernel?
|
well for starters you could simply rename it... or read the documentation.
directly from the documentation:
Quote:
Note: If you want to use VMware Fusion, you kernel must be named /mach_kernel.
This is a bug in VMware, which requires the running kernel to use the default
name. The recommended workaround is to rename the existing kernel, and create a
symlink as follows (in Terminal) :
sudo mv /mach_kernel /mach_kernel.original
sudo ln -s /mach_kernel.voodoo /mach_kernel
|
now the two kernels (mach_kernel and mach_kernel.voodoo are actually the same one so VMWare and Parallels don't have issues...
I hope this helps because if its not a kernel panic then I don't know what else it could be... both work on my system and I'm doing exactly what I told you to do. |