Your message dated Tue, 8 Jun 2010 11:43:22 +0200
with message-id <20100608094322.ga15...@feivel.credativ.lan>
and subject line Re: [Pkg-virtualbox-devel] Bug#584680: Bug#584680: 
[virtualbox-ose-dkms] After installing kernel source and headers and 
reinstalling VirtualBox, Virtualbox says to disable KVM extension
has caused the Debian Bug report #584680,
regarding [virtualbox-ose-dkms] doesn't compile modules at installation
to be marked as done.

This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.

(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact ow...@bugs.debian.org
immediately.)


-- 
584680: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=584680
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: virtualbox-ose-dkms
Version: 3.2.0-dfsg-1
Severity: grave

--- Please enter the report below this line. ---

Vistualbox fails to compile some modules.


I reinstalled virtualbox-ose and virtualbox-ose-dkms.

After installation of Virtualbox and lauch of a device, the application states:

::Kernel driver not installed (rc=-1908)

::Please install the virtualbox-ose-dkms package and execute 'modprobe vboxdrv' as root.

The suggestion doesn't resolve the problem.



LISTING from Synaptics

(Reading database ... 768200 files and directories currently installed.)
Preparing to replace virtualbox-ose 3.2.0-dfsg-1 (using .../virtualbox-ose_3.2.0-dfsg-1_amd64.deb) ...
Unpacking replacement virtualbox-ose ...
Preparing to replace virtualbox-ose-dkms 3.2.0-dfsg-1 (using .../virtualbox-ose-dkms_3.2.0-dfsg-1_all.deb) ...

-------- Uninstall Beginning --------
Module:  virtualbox-ose
Version: 3.2.0
Kernel:  2.6.32-3-amd64 (x86_64)
-------------------------------------

Status: Before uninstall, this module version was ACTIVE on this kernel.

vboxdrv.ko:
 - Uninstallation
   - Deleting from: /lib/modules/2.6.32-3-amd64/updates/dkms/
 - Original module
   - No original module was found for this module on this kernel.
   - Use the dkms install command to reinstall any previous module version.


vboxnetadp.ko:
 - Uninstallation
   - Deleting from: /lib/modules/2.6.32-3-amd64/updates/dkms/
 - Original module
   - No original module was found for this module on this kernel.
   - Use the dkms install command to reinstall any previous module version.


vboxnetflt.ko:
 - Uninstallation
   - Deleting from: /lib/modules/2.6.32-3-amd64/updates/dkms/
 - Original module
   - No original module was found for this module on this kernel.
   - Use the dkms install command to reinstall any previous module version.

depmod.....

DKMS: uninstall Completed.

------------------------------
Deleting module version: 3.2.0
completely from the DKMS tree.
------------------------------
Done.
Unpacking replacement virtualbox-ose-dkms ...
Setting up virtualbox-ose (3.2.0-dfsg-1) ...
Stopping VirtualBox kernel modules.
Starting VirtualBox kernel modulesNo suitable module for running kernel found ... failed!
 failed!
invoke-rc.d: initscript virtualbox-ose, action "restart" failed.
Setting up virtualbox-ose-dkms (3.2.0-dfsg-1) ...
Loading new virtualbox-ose-3.2.0 DKMS files...
Building only for 2.6.32-trunk-amd64
Module build for the currently running kernel was skipped since the
kernel source for this kernel does not seem to be installed.
Stopping VirtualBox kernel modules.
Starting VirtualBox kernel modulesNo suitable module for running kernel found ... failed!
 failed!
invoke-rc.d: initscript virtualbox-ose, action "restart" failed.



--- System information. ---
Architecture: amd64
Kernel: Linux 2.6.32-trunk-amd64

Debian Release: squeeze/sid
500 testing ftp.es.debian.org

--- Package information. ---
Depends (Version) | Installed
========================-+-=============
dkms (>= 2.1.0.0) | 2.1.1.2-2


Package's Recommends field is empty.

Package's Suggests field is empty.




--- End Message ---
--- Begin Message ---
On Sun, Jun 06, 2010 at 01:30:15PM -0400, Michael Gilbert wrote:
> > I compiled VirtualBox running Linux 2.6.32-trunk-amd64.
> > I rebooted and compiled VirtualBox running Linux 2.6..32-3-amd64

The problem is not which kernel was running, but for which kernel do you have
the headers installed and you apparently don't have headers for -trunk 
installed.

> apt log).  kvm and vbox should be able to coexist just fine, but running

Well not really, only one of those can use the VT extension but not both.
Please make sure that the kvm module is not installed when starting virtualbox.

As I cannot see a bug in virtualbox-ose here, I close this report.

Michael
-- 
Michael Meskes
Michael at Fam-Meskes dot De, Michael at Meskes dot (De|Com|Net|Org)
Michael at BorussiaFan dot De, Meskes at (Debian|Postgresql) dot Org
ICQ 179140304, AIM/Yahoo/Skype michaelmeskes, Jabber mes...@jabber.org
VfL Borussia! Força Barça! Go SF 49ers! Use Debian GNU/Linux, PostgreSQL


--- End Message ---

Reply via email to