Solved [SOLVED]Can't Start Virtualbox

M

miracle20003

Today,When I update the emulators/virtualbox-ose after I can't start Virtualbox
I got the error message:
Code: 
Failed to open a session for the virtual machine winxp.

Failed to load VMMR0.r0 (VERR_SYMBOL_NOT_FOUND).

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

Here is the Virtualbox log:
Code: 
00:00:00.949983 232: RTTimeMilliTS
00:00:00.949983 233: RTTimeNanoTS
00:00:00.949983 234: RTTimeNow
00:00:00.949983 235: RTTimerCanDoHighResolution
00:00:00.949983 236: RTTimerChangeInterval
00:00:00.949983 237: RTTimerCreate
00:00:00.949983 238: RTTimerCreateEx
00:00:00.949983 239: RTTimerDestroy
00:00:00.949983 240: RTTimerGetSystemGranularity
00:00:00.949983 241: RTTimerReleaseSystemGranularity
00:00:00.949983 242: RTTimerRequestSystemGranularity
00:00:00.949983 243: RTTimerStart
00:00:00.949983 244: RTTimerStop
00:00:00.949983 245: RTTimeSystemMilliTS
00:00:00.949983 246: RTTimeSystemNanoTS
00:00:00.949983 247: RTUuidCompare
00:00:00.949983 248: RTUuidCompareStr
00:00:00.949983 249: RTUuidFromStr
00:00:00.949983 AssertLogRel /usr/ports/emulators/virtualbox-ose/work/VirtualBox-4.3.6/src/VBox/HostDrivers/Support/SUPLib.cpp(1753) int supLoadModuleResolveImport(RTLDRMODINTERNAL*, const char*, const char*, unsigned int, RTUINTPTR*, void*): <NULL>
00:00:00.949983 VMMR0.r0 is importing RTLogGetDefaultInstance which we couldn't find
00:00:00.949983 SUP: RTLdrGetBits failed for VMMR0.r0 (/usr/local/lib/virtualbox/VMMR0.r0). rc=VERR_SYMBOL_NOT_FOUND
00:00:00.949983 pdmR3LoadR0U: pszName="VMMR0.r0" rc=VERR_SYMBOL_NOT_FOUND szErr="SUPR3LoadModule: supLoadModule returned VERR_SYMBOL_NOT_FOUND"
00:00:00.949983 VMSetError: /usr/ports/emulators/virtualbox-ose/work/VirtualBox-4.3.6/src/VBox/VMM/VMMR3/VM.cpp(594) int vmR3CreateU(UVM*, uint32_t, int (*)(UVM*, VM*, void*), void*); rc=VERR_SYMBOL_NOT_FOUND
00:00:00.949983 VMSetError: Failed to load VMMR0.r0
00:00:00.949983 ERROR [COM]: aRC=NS_ERROR_FAILURE (0x80004005) aIID={8ab7c520-2442-4b66-8d74-4ff1e195d2b6} aComponent={Console} aText={Failed to load VMMR0.r0 (VERR_SYMBOL_NOT_FOUND)}, preserve=false
00:00:00.960856 Power up failed (vrc=VERR_SYMBOL_NOT_FOUND, rc=NS_ERROR_FAILURE (0X80004005))
00:00:00.971110 UIMediumEnumerator: Medium-enumeration finished!
00:00:00.972298 Using XKB for keycode to scan code conversion

FreeBSD Version:
uname -an
Code: 
FreeBSD Kkill 9.2-RELEASE FreeBSD 9.2-RELEASE #0 r255898: Fri Sep 27 03:52:52 UTC 2013     root@bake.isc.freebsd.org:/usr/obj/usr/src/sys/GENERIC  i386


Virtualbox Version:
VBoxManage --version
Code: 
4.3.6_OSEr91406



How can I fix it.
Thanks
 
Re: Can't Start Virtualbox

After the upgrade, did you reboot or do an kldunload and kldload of the vboxdrv kernel module?
Code: 
kldunload vboxdrv
kldload vboxdrv
If you have vboxnet_enable=yes in your /etc/rc.conf, you should also unload/load the vboxnetflt and vboxnetadp kernel modules as well.
 
Re: Can't Start Virtualbox

miracle20003 said:
FreeBSD Version:
uname -an
Code: 
FreeBSD Kkill 9.2-RELEASE FreeBSD 9.2-RELEASE #0 r255898: Fri Sep 27 03:52:52 UTC 2013     root@bake.isc.freebsd.org:/usr/obj/usr/src/sys/GENERIC  i386
Click to expand...
Not related to your issue but I see you're missing a couple security patches. For your own safety and peace of mind, install security updates when they're available.
 
Re: Can't Start Virtualbox

Could be a few snags causing this.

Check your user is in the vboxusers group and reboot (some instances of this have cleared after a simple reboot! - This allows the old kernel modules to be cleared and the updated ones to be loaded).

It might be worth creating a new machine with chopped down to essential "hardware" and pointing it to your existing HDD. If that starts; remove the old one and rename new once you have restored all appropriate hardware.

VirtualBox.xml may also have been corrupted and it may pay to remove this (with VirtualBox closed). Pain of that is to re-register VMs.
 
Re: Can't Start Virtualbox

It may be related, but I've had some real problems on FreeBSD RELEASE 10 with a recent (new) build. I had to create ~/.VirtualBox/VirtualBox.xml by hand, and initially run as sudo -[myusername] to get it to even start. Only then would it actually work without using sudo. This was with all prerequisites met, as per the documentation.

If you do a little googling, you can see others have had similar problems. I suspect it's something the emulation team are working on - Here is the thread I found about it.
 
Re: Can't Start Virtualbox

Had the same problem and the "fix" is easy. I agree it had something to do with the ports update after FreeBSD 10 was released.

1) Re-install virtualbox-ose by itself.
2) Then reinstall virtualbox-ose-kmod by itself
3) Restart FreeBSD.

This fixed it for me.
 
Re: Can't Start Virtualbox

Thanks everybody!
I remove ~/.VirtualBox/ and De-install Re-install
Now,It was working.
 
You must log in or register to reply here.
Back
Top