Virtualbox on Maverick - Failed to load VMMR0.r0

[Mapache23]

After some problems with VirtualBox 4.2.18 on Maverick I installed 4.3.0.
This worked well until reboot.

Now I got this error message:

Code: Select all

Failed to load VMMR0.r0

I had to reinstall VirtualBox from the DMG to get it working again. So every reboot requires a reinstallation of VirtualBox.
This can not be the final solution as it is pretty annoying.
I just wanted to report this issue in case that it is not already known.
Please let me know if there is some way to avoid it.

Regards

[zhangpeng_otn]

I got the same problem with 4.3.0 hosts on Maverick.

[dangjavageek]

Same problem, using Mac OS X 10.9 Build 13A603 and Virtual Box 4.3.0 r89960

Failed to open a session for the virtual machine Windows7.

Failed to load VMMR0.r0 (VERR_SYMBOL_NOT_FOUND).

Result Code: NS_ERROR_FAILURE (0x80004005)
Component: Console
Interface: IConsole {8ab7c520-2442-4b66-8d74-4ff1e195d2b6}

UPDATE: following the uninstall-re-install cycle suggested elsewhere, I can get the Windows 7 virtual box guest to load, but it is waaaaay slow and unusable, spinning beach ball of death is more or less permanent. Console indicates things are not well...

kernel[0]: VirtualBoxVM (map: 0xffffff80505ff000) triggered DYLD shared region unnest for map: 0xffffff80505ff000, region 0x7fff89a00000->0x7fff89c00000. While not abnormal for debuggers, this increases system memory footprint until the target exits.
VirtualBoxVM[2858]: IOHIDDeviceRegisterInputValueCallback called with a null context
VirtualBoxVM[2858]: IOHIDDeviceRegisterInputValueCallback called with a null context
[... tons of repeats of last message...]

[tgfbeta]

Just got the same problem.

It seems that running /Library/Application Support/VirtualBox/LaunchDaemons/VirtualBoxStartup.sh again would rescue:

Code: Select all

sudo /Library/Application\ Support/VirtualBox/LaunchDaemons/VirtualBoxStartup.sh restart

This script would unload kernel extensions and reload them.

[tgfbeta]

BTW, I found another copy of kexts in /Library/Extensions/, which might be left-over from a previous version of VirtualBox( 4.2.18 in my case) installed to OS X 10.8.x.

[dettix]

I run 4.3.0 on Maverick and get the same error message. Any details when this will be fixed?

Thanks Detlef

[ChipMcK]

Any details when this will be fixed?

A workaround is available in the forum

[Ramji]

Any Solutions to this issue will greatly appreciated. I have same issue. I thought there is issue in my working rac configuration and deleted the complete test area i created.

Thanks
Ramji

[Quaestor]

Any details when this will be fixed?

A workaround is available in the forum

Where in the forum? What is the thread title?

[ChipMcK]

Events continue to happen (life goes on, and so forth, and so forth, and so forth, . . . )

Discuss the 4.3.2 release

[Jatai]

Thanks tgfbeta.

The solution you posted has solved my problem. My Virtual Box now run smoothly again with all my virtual machines.