Error while Loading Vbox

Asked by UbuntuAma

When i load Vbox on my Ubuntu 9.10 (upgraded from 8.10-9.04 to 9.10) i get this error "
Virtual machine 'WinXPpro' has terminated unexpectedly during startup.

Result Code:
NS_ERROR_FAILURE (0x80004005)
Component:
Machine
Interface:
IMachine {1e509de4-d96c-4f44-8b94-860194f710ac}
 then followed by this "The VirtualBox Linux kernel driver (vboxdrv) is either not loaded or there is a permission problem with /dev/vboxdrv. Re-setup the kernel module by executing

'/etc/init.d/vboxdrv setup'

When i go on terminal and Run Sudo etc/init.d/vboxdrv setup i get this message back

~$ sudo /etc/init.d/vboxdrv setup
 * Stopping VirtualBox kernel module * done.
 * Recompiling VirtualBox kernel module
 * Look at /var/log/vbox-install.log to find out what went wrong
so if you look at the last line it shows there could be an error somewhere
i did as it says on that last line and i get ACCESS DENIED how can i get into that file not sure how to get access as it didnt ask for password etc etc

Question information

Language:
English Edit question
Status:
Solved
For:
Ubuntu virtualbox-ose Edit question
Assignee:
No assignee Edit question
Solved by:
actionparsnip
Solved:
Last query:
Last reply:
Revision history for this message
Vikram Dhillon (dhillon-v10) said :
#1

On Sat, Jan 2, 2010 at 5:22 PM, UbuntuAma
<email address hidden> wrote:
> New question #95972 on Ubuntu:
> https://answers.launchpad.net/ubuntu/+question/95972
>
> When i load Vbox on my Ubuntu 9.10 (upgraded from 8.10-9.04 to 9.10) i get this error "
> Virtual machine 'WinXPpro' has terminated unexpectedly during startup.
>
> Result Code:
> NS_ERROR_FAILURE (0x80004005)
> Component:
> Machine
> Interface:
> IMachine {1e509de4-d96c-4f44-8b94-860194f710ac}
>  then followed by this "The VirtualBox Linux kernel driver (vboxdrv) is either not loaded or there is a permission problem with /dev/vboxdrv. Re-setup the kernel module by executing
>
> '/etc/init.d/vboxdrv setup'
>
> When i go on terminal and Run Sudo etc/init.d/vboxdrv setup i get this message back
>
> ~$ sudo /etc/init.d/vboxdrv setup
>  * Stopping VirtualBox kernel module * done.
>  * Recompiling VirtualBox kernel module
>  * Look at /var/log/vbox-install.log to find out what went wrong
> so if you look at the last line it shows there could be an error somewhere
> i did as it says on that last line and i get ACCESS DENIED how can i get into that file not sure how to get access as it didnt ask for password etc etc
>
> --
> You received this question notification because you are an answer
> contact for Ubuntu.
>

First off go to the terminal and do sudo nautilus, That should open up
the root file-browser. Then browse to the location
/var/log/vbox-install. That should do that. Where did you get the VBox
from? Did you get it from the repositories, if so you may want to get
one from the original website, which is pretty good, I got it working
with no problem :D

--
Regards,
Vikram Dhillon

~~~
There are lots of Linux users who don't care how the kernel works, but
only want to use it. That is a tribute to how good Linux is.
-- Linus Torvalds

Revision history for this message
UbuntuAma (ama-bone) said :
#2

****So i went into the file and the screen i got below is this****

Attempting to install using DKMS
  removing old DKMS module vboxdrv version

Error! Invalid number of parameters passed.
Usage: remove -m <module> -v <module-version> --all
   or: remove -m <module> -v <module-version> -k <kernel-version>

------------------------------
Deleting module version: 2.0.6
completely from the DKMS tree.
------------------------------
Done.

Creating symlink /var/lib/dkms/vboxdrv/2.0.6/source ->
                 /usr/src/vboxdrv-2.0.6

DKMS: add Completed.

Kernel preparation unnecessary for this kernel. Skipping...

Building module:
cleaning build area....
su nobody -c "make KERNELRELEASE=2.6.31-17-generic -C /lib/modules/2.6.31-17-generic/build M=/var/lib/dkms/vboxdrv/2.0.6/build"....(bad exit status: 2)

Error! Bad return status for module build on kernel: 2.6.31-17-generic (i686)
Consult the make.log in the build directory
/var/lib/dkms/vboxdrv/2.0.6/build/ for more information.
0
0
Failed to install using DKMS, attempting to install without
make KBUILD_VERBOSE=1 -C /lib/modules/2.6.31-17-generic/build SUBDIRS=/tmp/vbox.2 SRCROOT=/tmp/vbox.2 modules
make[1]: Entering directory `/usr/src/linux-headers-2.6.31-17-generic'
test -e include/linux/autoconf.h -a -e include/config/auto.conf || ( \
 echo; \
 echo " ERROR: Kernel configuration is invalid."; \
 echo " include/linux/autoconf.h or include/config/auto.conf are missing."; \
 echo " Run 'make oldconfig && make prepare' on kernel src to fix it."; \
 echo; \
 /bin/false)
mkdir -p /tmp/vbox.2/.tmp_versions ; rm -f /tmp/vbox.2/.tmp_versions/*
make -f scripts/Makefile.build obj=/tmp/vbox.2
  gcc -Wp,-MD,/tmp/vbox.2/linux/.SUPDrv-linux.o.d -nostdinc -isystem /usr/lib/gcc/i486-linux-gnu/4.4.1/include -Iinclude -I/usr/src/linux-headers-2.6.31-17-generic/arch/x86/include -include include/linux/autoconf.h -Iubuntu/include -D__KERNEL__ -Wall -Wundef -Wstrict-prototypes -Wno-trigraphs -fno-strict-aliasing -fno-common -Werror-implicit-function-declaration -Wno-format-security -fno-delete-null-pointer-checks -O2 -m32 -msoft-float -mregparm=3 -freg-struct-return -mpreferred-stack-boundary=2 -march=i586 -mtune=generic -Wa,-mtune=generic32 -ffreestanding -fstack-protector -fstack-protector-all -pipe -Wno-sign-compare -fno-asynchronous-unwind-tables -mno-sse -mno-mmx -mno-sse2 -mno-3dnow -Wframe-larger-than=1024 -fno-omit-frame-pointer -fno-optimize-sibling-calls -Wdeclaration-after-statement -Wno-pointer-sign -fno-strict-overflow -fno-dwarf2-cfi-asm -I/lib/modules/2.6.31-17-generic/build/include -I/tmp/vbox.2/ -I/tmp/vbox.2/include -I/tmp/vbox.2/r0drv/linux -D__KERNEL__ -DMODULE -DRT_OS_LINUX -DIN_RING0 -DIN_RT_R0 -DIN_SUP_R0 -DVBOX -DRT_WITH_VBOX -DVBOX_WITH_HARDENING -DCONFIG_VBOXDRV_AS_MISC -DRT_ARCH_X86 -DMODULE -D"KBUILD_STR(s)=#s" -D"KBUILD_BASENAME=KBUILD_STR(SUPDrv_linux)" -D"KBUILD_MODNAME=KBUILD_STR(vboxdrv)" -c -o /tmp/vbox.2/linux/.tmp_SUPDrv-linux.o /tmp/vbox.2/linux/SUPDrv-linux.c
/tmp/vbox.2/linux/SUPDrv-linux.c: In function ‘VBoxDrvLinuxCreate’:
/tmp/vbox.2/linux/SUPDrv-linux.c:650: error: ‘struct task_struct’ has no member named ‘euid’
/tmp/vbox.2/linux/SUPDrv-linux.c:663: error: ‘struct task_struct’ has no member named ‘uid’
/tmp/vbox.2/linux/SUPDrv-linux.c:664: error: ‘struct task_struct’ has no member named ‘gid’
make[2]: *** [/tmp/vbox.2/linux/SUPDrv-linux.o] Error 1
make[1]: *** [_module_/tmp/vbox.2] Error 2
make[1]: Leaving directory `/usr/src/linux-headers-2.6.31-17-generic'
make: *** [vboxdrv] Error 2

****NOT SO SURE WHAT TO LOOK ON THAT CHUNKY****

Any further help

Revision history for this message
actionparsnip (andrew-woodhead666) said :
#3

Have you rebooted since installing virtualbox?

Revision history for this message
UbuntuAma (ama-bone) said :
#4

Yes i have reboot several times and still getting the same Error
***I have thinking if it is possible just to install the new Vbox and getting my Windows to hook up into it the same OS i was using in this troubled Vbox?****

Revision history for this message
Best actionparsnip (andrew-woodhead666) said :
#5

You can install the newest virtualbox:
https://launchpad.net/~debfx/+archive/virtualbox

Before installing, run:

sudo apt-get --purge remove virtualbox*; sudo apt-get --purge autoremove

Then install the virtualbox from the PPA

Revision history for this message
UbuntuAma (ama-bone) said :
#6

Thanks actionparsnip, that solved my question.

Revision history for this message
UbuntuAma (ama-bone) said :
#7

had to install new vbox and got my windows back in thanks all