VMware Communities
th0m4s42
Contributor
Contributor

Fusion 6 vm won't start "Unable to retrieve kernel symbols"

Hi,

I've just upgraded Fusion to 6.0.1 and all my vm won't start, these screens popped when I try to start any one of them.


Unable to retrieve kernel symbols

Failed to initialize monitor device

Cannot find a valid peer procces to connect to

Version 6.0.1 (1331545)

OS : 10.8.5 Build 12F45

Any suggestion to fix this problem?

Cheers

26 Replies
abhilashhb
VMware Employee
VMware Employee

Please refer this below Thread. it should fix your issue.

Re: Unable to retrieve kernel symbols

If you found my answer correct/helpful, mark the answer appropriately

Abhilash B
LinkedIn : https://www.linkedin.com/in/abhilashhb/

0 Kudos
th0m4s42
Contributor
Contributor

Thanks for your quick response but I already tried to uninstall Fusion 6 (entirely), reinstalled it and even tried with fusion 5.0.3.

Moreover my os is up to date and I use the latest version of Fusion.

0 Kudos
dariusd
VMware Employee
VMware Employee

Hi th0m4s42, and welcome to the VMware Communities!

Interesting... we've had another two users report the same problem recently with the 10.8.5 update in this other thread: My Virtual Machine doesn't start anymore in Fusion

Could you provide the output of running the following three commands in Terminal on the affected system?

   uname -a


   system_profiler SPSoftwareDataType


   ls -l /mach_kernel

Thanks,

--

Darius

0 Kudos
dariusd
VMware Employee
VMware Employee

Also, have you recently installed the OS X 10.8.5 "Supplemental Update", which was released only a few days ago?

Thanks,

--

Darius

0 Kudos
th0m4s42
Contributor
Contributor

uname -a

Darwin toto.local 12.5.0 Darwin Kernel Version 12.5.0: Sun Sep 29 13:33:47 PDT 2013; root:xnu-2050.48.12~1/RELEASE_X86_64 x86_64

system_profiler SPSoftwareDataType

    System Software Overview:

      System Version: OS X 10.8.5 (12F45)

      Kernel Version: Darwin 12.5.0

      Boot Volume: OSXML

      Boot Mode: Normal

      Computer Name: tata

      User Name: toto (toto)

      Secure Virtual Memory: Enabled

      Time since boot: 18:50

Yes I installed this supplemental update.

foooo I've just realized that I don't find my mach_kernel Smiley Sad but It's weird I can use my mac :smileyconfused:

I will try to retrieve this file with my TM.

I'll let you know.

0 Kudos
dariusd
VMware Employee
VMware Employee

Interesting...  Thanks for the info!

We're still trying to understand how /mach_kernel is going missing.  Do you recall moving/deleting it recently?

As to why your Mac is still usable, OS X creates a kernelcache which rolls up /mach_kernel along with all the drivers needed to start the OS.  If you're interested, the kernelcache is in /System/Library/Caches/com.apple.kext.caches/Startup/kernelcache on your boot volume.  That's the file which is used to boot and run the OS.  If /mach_kernel goes missing, your OS will be unable to generate a new kernelcache – which may be required if certain software, drivers or hardware are installed or removed, and may be crucial if the changes are relevant to OS boot – and you will also be unable to run Fusion, but otherwise the OS will generally continue to operate normally.

Cheers,

--

Darius

0 Kudos
th0m4s42
Contributor
Contributor

I didn't touch ever /mach_kernel but in my TM It miss after the installation of Fusion 6 (I uninstalled 5.0.3 and I installed the 6.0.1).

So I retrieve my mach_kernel file but I still have the problem.

I think the problem come from my mach_kernel which disappeared.

Btw thanks for the informations.

Cheers,

Tom

0 Kudos
karthikg2013
Enthusiast
Enthusiast

Solution to the issue is:

1. Download the update package from http://support.apple.com/kb/DL1686

2. Create an empty mach_kernel file (otherwise the update installer won't work) using Terminal command:


sudo touch /mach_kernel


3. Install the OSXUpd10.8.5Supp.pkg from the downloaded file. It should restore the proper mach_kernel file.


After installing the update (and before restarting) it's possible to verify that the file was installed correctly:


ls -l /mach_kernel


It should show the permissions -rw-r--r--, owner root, group wheel, and file size 8244640 bytes.

To prevent the mach_kernel file from showing up in Finder, run the command:


sudo chflags hidden /mach_kernel

th0m4s42
Contributor
Contributor

It's working, thank you very much karthikg2013 and Darius for your help.

All my vm are working Smiley Wink

Cheers,

Tom

0 Kudos
MoRRiS1
Contributor
Contributor

i have the same issue. Last night i installed the supplemental updates, but in my case there still was a mach_kernel file.

just to be sure, i moved it, and reinstalled it by means of the mentioned update dmg

But Vmware Fusion 6.0.1 still can't boot any of the VM's or create any new ones.

So i can't start my VM's at the moment.

0 Kudos
dariusd
VMware Employee
VMware Employee

Hi MoRRis1,

Could you provide the output of running the following three commands in Terminal on the affected system?

   uname -a


   system_profiler SPSoftwareDataType


   ls -l /mach_kernel

Thanks,

--

Darius

0 Kudos
MoRRiS1
Contributor
Contributor

Darwin dhcp-031.local 12.5.0 Darwin Kernel Version 12.5.0: Mon Jul 29 16:33:49 PDT 2013; root:xnu-2050.48.11~1/RELEASE_X86_64 x86_64

Software:

    System Software Overview:

      System Version: OS X 10.8.5 (12F45)

      Kernel Version: Darwin 12.5.0

      Boot Volume: Macintosh HD

      Boot Mode: Normal

      Computer Name: MacBook Pro

      User Name: Xxxxxx Xxxxxx (Xxxxxxx)

      Secure Virtual Memory: Enabled

      Time since boot: 2:37

-rw-r--r--  1 root  wheel  8244640 Sep 29 22:34 /mach_kernel

0 Kudos
dariusd
VMware Employee
VMware Employee

Hi MoRRiS1,

Thanks for that information.  The OS X update didn't complete quite correctly, leaving your system in an inconsistent state.

   Darwin Kernel Version 12.5.0: Mon Jul 29 16:33:49 PDT 2013; root:xnu-2050.48.11~1/RELEASE_X86_64 x86_64

That's the kernel for the original release of OS X 10.8.5 (12F37).  But...

   System Version: OS X 10.8.5 (12F45)

you've got the supplemental update installed, yet your system is still running the pre-update kernel.

Here are a few things to try in order:

1. Launch Disk Utility and use the First Aid tab to verify all of your disks.

2. If your Mac has multiple hard disk drives using software RAID, use Disk Utility again to verify that your RAID set is not degraded.  If it is degraded, rebuild it.

3. Restart your Mac and try using Fusion again.

If that does not resolve the problem, you may need to reinstall the 10.8.5 Supplemental Update one more time – after all the above steps – to correct the situation.

Cheers,

--

Darius

0 Kudos
MoRRiS1
Contributor
Contributor

i tried all the steps, and reinstalled the supplemental update, but nothing changes.

It doesn't seem to update the kernel to the later version.

any suggestions ?

Is there another update i should try ?

0 Kudos
dariusd
VMware Employee
VMware Employee

I don't have any immediate suggestions.  Perhaps we might find some clues in the Support Information bundle...  Launch Fusion, choose Help > Collect Support Information, enter your password if prompted, and it'll create a file on your Desktop.  Attach that file to a reply in this thread (Choose Use advanced editor in the top-right corner of the reply window, then choose Browse... below and select the file to attach) and I'll take a look.

Thanks,

--

Darius

0 Kudos
MoRRiS1
Contributor
Contributor

full filenames and usernames are in that logfile, so i can't post it to a public forum.

can i send, and/or protect it ?

0 Kudos
dariusd
VMware Employee
VMware Employee

I've provided my contact information via a forum Private Message.

Cheers,

--

Darius

0 Kudos
BillPennock
Contributor
Contributor

Dariusd: Sorry this didn't work for the original poster but your post to MoRRiS1 worked great for me.  Thank you

0 Kudos
dariusd
VMware Employee
VMware Employee

Cool!

There are many ways to end up in this situation, any given post is unlikely to address every case.  I'm glad it helped you out there!

Just for the record, I worked offline with MoRRiS1 and discovered a truly bizarre configuration problem on their system.  The scenario is so absurdly unlikely that I won't post the details of its resolution here – it will be of no value to the greater community – but we did get the problem resolved.  :smileycool:

Cheers,

--

Darius

0 Kudos