virtualbox crash during startup

Bug #494150 reported by azesm
14
This bug affects 2 people
Affects Status Importance Assigned to Milestone
virtualbox-ose (Ubuntu)
Invalid
Undecided
Unassigned

Bug Description

Binary package hint: virtualbox-ose

Код ошибки:
NS_ERROR_FAILURE (0x80004005)
Компонент: Machine
Интерфейс: IMachine {540dcfda-3df2-49c6-88fa-033a28c2ff85}

 Kernel driver not installed (rc=-1908)
Please install the virtualbox-ose-source package.

ProblemType: Bug
Architecture: amd64
Date: Tue Dec 8 16:40:11 2009
DistroRelease: Ubuntu 9.10
InstallationMedia: Ubuntu 9.10 "Karmic Koala" - Release amd64 (20091027.1)
LiveMediaBuild: Ubuntu 9.10 "Karmic Koala" - Release amd64 (20091027.1)
Package: virtualbox-ose-qt 3.0.8-dfsg-1ubuntu1
ProcEnviron:
 PATH=(custom, no user)
 LANG=ru_UA.UTF-8
 SHELL=/bin/bash
ProcVersionSignature: Ubuntu 2.6.31-16.52-server
SourcePackage: virtualbox-ose
Uname: Linux 2.6.31-16-server x86_64
VirtualBoxOse.DpkgList:
 ii virtualbox-ose 3.0.8-dfsg-1ubuntu1 x86 virtualization solution - base binaries
 ii virtualbox-ose-qt 3.0.8-dfsg-1ubuntu1 x86 virtualization solution - Qt based user interface
 ii virtualbox-ose-source 3.0.8-dfsg-1ubuntu1 x86 virtualization solution - kernel module source
VirtualBoxOse.ModInfo:

Revision history for this message
azesm (aazesm) wrote :
Revision history for this message
Martin Erik Werner (arand) wrote :

Is the virtualbox-ose-source package installed?
And is the kernel driver module in operation?

Changed in virtualbox-ose (Ubuntu):
status: New → Incomplete
Revision history for this message
Philip Muškovac (yofel) wrote :

We'd like to figure out what's causing this bug for you, but we haven't heard back from you in a while. Could you please provide the requested information? Thanks!

Changed in virtualbox-ose (Ubuntu):
status: Incomplete → Invalid
Revision history for this message
Jan Grobecker (jan-grobecker) wrote :

Some time ago I was also effected by this problem sporadically. It turned out that /etc/init.d/virtualbox-ose (as well as /etc/init.d/cups) hadn't been run by upstart in that cases and thus the kernel module vboxdrv hadn't been loaded. After running "invoke-rc.d vboxdrv start" manually virtualbox worked normally. Due to the obvious correlation to the cups script not having been run by upstart I have marked this bug as a duplicate of bug 497299.

To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.