NS_ERROR_FAILURE (0x00004005) on natty ubuntu

[lime4by4]

I get the following error when going under system of a vm. I'm running 64 bit natty ubuntu. Downloaded the latest version of virtualbox. installed the expansion pak and guest tools.


Result Code:
NS_ERROR_FAILURE (0x00004005)
Component:
Host
Interface:
IHost {35b004f4-7806-4009-bfa8-d1308adba7e5}
Callee:
IMachine {662c175e-a69d-40b8-a77a-1d719d0ab062}

[Perryg]

Did you put your user name in the vboxusers group?

[lime4by4]

yes

[Perryg]

Is natty the host or the guest

[lime4by4]

natty is the host w7 is the guest. Also the other odd thing was during the install of the deb package natty gave an error about it being a poorly prepared package. The deb package i downloaded from virtualbox.org

[Perryg]

Did you install the needed packages to build external modules first? Keep in mind, while I am able to install VirtualBox in natty it may not be so for everyone. Support was just added a few days ago and there may be issues. Try installing the packages below and then run /etc/init.d/vboxdrv setup or install VirtualBox again.

Code: Select all

sudo apt-get install dkms build-essential linux-headers-generic

[lime4by4]

yes those packages were installed but 'm unable to run setup

john@john-linux:~$ sudo apt-get install dkms build-essential linux-headers-generic
[sudo] password for john:
Reading package lists... Done
Building dependency tree
Reading state information... Done
build-essential is already the newest version.
dkms is already the newest version.
linux-headers-generic is already the newest version.
0 upgraded, 0 newly installed, 0 to remove and 0 not upgraded.
john@john-linux:~$ /etc/init.d/vboxdrv setup
* Stopping VirtualBox kernel modules
* Cannot unload module vboxnetadp

[Perryg]

Reboot or at the very least log off and back in and try again.

[lime4by4]

i had to use sudo /etc/init.d/vboxdrv setup. i no longer get that error. Thanks

[kahun]

Hi

I have the same problem in arch 64 bits with virtualbox 4.0.6 and kernel 2.6.38

• The user is on the vboxusers group
• Clicking on settings shows the error:

  Code: Select all

  Código Resultado: 
  NS_ERROR_FAILURE (0x00004005)
  Componente: 
  Host
  Interfaz: 
  IHost {35b004f4-7806-4009-bfa8-d1308adba7e5}
  Receptor: 
  IMachine {662c175e-a69d-40b8-a77a-1d719d0ab062}

• The devices are created:

  Code: Select all

  $ ls -lhd /dev/vboxdrv 
  crw-rw---- 1 root vboxusers 10, 58 abr 24 17:10 /dev/vboxdrv
  $ ls -lhd /dev/bus/usb/001/002
  crw-rw-r-- 1 root vboxusers 189, 1 abr 24 17:22 /dev/bus/usb/001/002
  

• The modules are loaded:

  Code: Select all

  $ lsmod | grep vbox
  vboxnetflt             19018  0 
  vboxnetadp              5555  0 
  vboxdrv              1765266  2 vboxnetflt,vboxnetadp
  

• The extension pack is installed:

  Code: Select all

  $ VBoxManage list extpacks
  Extension Packs: 1
  Pack no. 0:   Oracle VM VirtualBox Extension Pack
  Version:      4.0.6
  Revision:     71344
  Description:  USB 2.0 Host Controller, VirtualBox RDP, PXE ROM with E1000 support.
  VRDE Module:  VBoxVRDP
  Usable:       true 
  Why unusable: 

• But Virtualbox doesn't see any usb host:

  Code: Select all

  $ VBoxManage list usbhost
  Host USB Devices:
  
  <none>
  

Any help will be appreciated

Thanks

[Perryg]

@kahun,

did you reboot the host?

[kahun]

@kahun,

did you reboot the host?

Yes, also I rerun:

Code: Select all

sudo /etc/rc.d/vboxdrv setup

The modules compile ok but usb doesn't work

[Perryg]

User name in the vboxusers group on the host?
type id in a terminal and see if you are in the group.

[kahun]

User name in the vboxusers group on the host?
type id in a terminal and see if you are in the group.

Yes, it is:

Code: Select all

$ id
uid=1000(kahun) gid=1000(kahun) grupos=1000(kahun),7(lp),10(wheel),90(network),91(video),92(audio),93(optical),95(storage),96(scanner),98(power),100(users),108(vboxusers),120(gdm),140(usbmux)

Maybe is related to this bug: http://www.virtualbox.org/ticket/6986

[Perryg]

I doubt it is related to that ticket. They are using Windows as host and that is a different issue.
It may be an issue with natty as I said support is enabled but there may be issues. You can post a ticket in bugtracker (you need to create an account there). I don't see this issue and can not reproduce it but I am working on a different level of VirtualBox. I don't have a natty (dedicated box) available to me at the moment with the release version of VirtualBox on it.