Why... Why... Why?
This blog is dedicated to documenting error resolution and other tidbits that I discover while working as a Consultant in the Oracle EPM (Hyperion) field. As much of my job revolves around issue resolution, I see an opportunity to supplement the typical troubleshooting avenues such as the Oracle Knowledgebase and Oracle Forums with more pinpointed information about specific errors as they are encountered. Beware, the information found in this blog is for informational purposes only and comes without any warranty or guarantee of accuracy.

EPMVirt: Create your own Oracle Hyperion Virtual Environment:

Monday, December 12, 2016

Getting Virtual Box Working on Ubuntu


I recently purchased a new laptop, and this time around I finally decided to ditch Windows and install Ubuntu (Linux). While trying to get Virtual Box running I ran into a small issue.

When I tried to configure the EPMVirt VM, it ran into this error:

The VirtualBox Linux kernel driver (vboxdrv) is either not loaded or there is a permission problem with /dev/vboxdrv. Please reinstall the kernel module by executing
/sbin/vboxconfig




However, when running the vboxconfig command, it fails
root@kingn-ThinkPad-X260:~# /sbin/vboxconfig
vboxdrv.sh: Building VirtualBox kernel modules.
vboxdrv.sh: Starting VirtualBox services.
vboxdrv.sh: Building VirtualBox kernel modules.
vboxdrv.sh: failed: modprobe vboxdrv failed. Please use 'dmesg' to find out why.
There were problems setting up VirtualBox.  To re-start the set-up process, run
  /sbin/vboxconfig
as root.

Looking through the system logs, it appears the kernel module simply cannot be loaded:
tail -1000 /var/log/syslog
Dec 12 22:21:19 kingn-ThinkPad-X260 vboxdrv.sh: failed: modprobe vboxdrv failed. Please use 'dmesg' to find out why.
Dec 12 22:21:19 kingn-ThinkPad-X260 systemd[1]: Starting VirtualBox Linux kernel module...
Dec 12 22:21:19 kingn-ThinkPad-X260 vboxdrv.sh[11598]: vboxdrv.sh: Starting VirtualBox services.
Dec 12 22:21:19 kingn-ThinkPad-X260 vboxdrv.sh: Starting VirtualBox services.
Dec 12 22:21:19 kingn-ThinkPad-X260 vboxdrv.sh[11598]: vboxdrv.sh: Building VirtualBox kernel modules.
Dec 12 22:21:19 kingn-ThinkPad-X260 vboxdrv.sh: Building VirtualBox kernel modules.
Dec 12 22:21:35 kingn-ThinkPad-X260 vboxdrv.sh: VirtualBox kernel modules built.
Dec 12 22:21:35 kingn-ThinkPad-X260 vboxdrv.sh[11598]: vboxdrv.sh: failed: modprobe vboxdrv failed. Please use 'dmesg' to find out why.
Dec 12 22:21:35 kingn-ThinkPad-X260 vboxdrv.sh: failed: modprobe vboxdrv failed. Please use 'dmesg' to find out why.
Dec 12 22:21:35 kingn-ThinkPad-X260 systemd[1]: vboxdrv.service: Control process exited, code=exited status=1
Dec 12 22:21:35 kingn-ThinkPad-X260 systemd[1]: Failed to start VirtualBox Linux kernel module.
Dec 12 22:21:35 kingn-ThinkPad-X260 systemd[1]: vboxdrv.service: Unit entered failed state.
Dec 12 22:21:35 kingn-ThinkPad-X260 systemd[1]: vboxdrv.service: Failed with result 'exit-code'.
Dec 12 22:21:35 kingn-ThinkPad-X260 systemd[1]: Started vboxballoonctrl-service.service.
Dec 12 22:21:35 kingn-ThinkPad-X260 systemd[1]: Started vboxautostart-service.service.
Dec 12 22:21:35 kingn-ThinkPad-X260 systemd[1]: Started vboxweb-service.service.
Dec 12 22:21:41 kingn-ThinkPad-X260 dbus[891]: [system] 
To solve this I was able to read some online articles and find that we can disable the Secure Boot option in the BIOS settings to help fix the issue. Rebooting into the system BIOS:



Simply turning off secure boot seems to fix the problem,
root@kingn-ThinkPad-X260:~# /sbin/vboxconfig
vboxdrv.sh: Building VirtualBox kernel modules.
vboxdrv.sh: Starting VirtualBox services.
root@kingn-ThinkPad-X260:~#
kPad-X260 dbus[891]: [system] Successfully activated service 'org.freedesktop.hostname1'
Dec 12 22:21:41 kingn-ThinkPad-X260 systemd[1]: Started Hostname Service.
Now, on to installing EPMVirt...

No comments:

Post a Comment