Bug 4663 - virtualbox-4.1.8-3.mga2.src.rpm need dkms-virtualbox
Summary: virtualbox-4.1.8-3.mga2.src.rpm need dkms-virtualbox
Status: RESOLVED FIXED
Alias: None
Product: Mageia
Classification: Unclassified
Component: RPM Packages (show other bugs)
Version: Cauldron
Hardware: x86_64 Linux
Priority: Normal normal
Target Milestone: ---
Assignee: Thomas Backlund
QA Contact:
URL:
Whiteboard:
Keywords: NEEDINFO
: 4668 (view as bug list)
Depends on:
Blocks:
 
Reported: 2012-02-23 20:41 CET by Bernard SIAUD
Modified: 2012-04-05 09:14 CEST (History)
2 users (show)

See Also:
Source RPM: virtualbox-4.1.8-3.mga2.src.rpm
CVE:
Status comment:

Attachments
Add an attachment (proposed patch, testcase, etc.)

Description Bernard SIAUD 2012-02-23 20:41:51 CET 
Description of problem:
I have installed the new mageia 2. bêta 1 today.
I can't use Virtualbox because dkms-virtualbox isn't installed

I have intall dkms-virtualbox ans virtualbox run now.
Comment 1 Manuel Hiebel 2012-02-23 22:13:06 CET 
Hello, 

what is the output of rpm -qa | grep kernel ?
with mageia 2 there is no need anymore of the dkms.
We provide something called kmod. It's the same that in the past in mandriva

http://svnweb.mageia.org/packages/cauldron/virtualbox/current/SPECS/virtualbox.spec?revision=196091&view=markup

75 	Requires: kmod(vboxdrv) = %{version}

So virtualbox should install also virtualbox-kernel-`uname -r `

Keywords: (none) => NEEDINFO

Comment 2 Bernard SIAUD 2012-02-24 08:30:53 CET 
# rpm -qa | grep kernel
kernel-desktop-3.2.6-3.mga2-1-1.mga2
kernel-desktop-devel-latest-3.2.6-3.mga2
kernel-desktop-latest-3.2.6-3.mga2
kernel-firmware-20111229-1.mga2
kernel-userspace-headers-3.2.6-2.mga2
virtualbox-kernel-desktop-latest-4.1.8-12.mga2
virtualbox-kernel-3.2.6-desktop-3.mga2-4.1.8-12.mga2
kernel-desktop-devel-3.2.6-3.mga2-1-1.mga2

My first OS is Mageia 2. And in mageia 2 I run Virtual to try Windows XP for compiling programs. When I have intalled dkms-virtualbox, I think that some rpm with kernel have been installed.
Comment 3 Manuel Hiebel 2012-02-24 12:07:14 CET 
*** Bug 4668 has been marked as a duplicate of this bug. ***

CC: (none) => uli.effer

Comment 4 Bernard SIAUD 2012-02-24 14:05:40 CET 
Yes, 4668 and 4663 are the same bug.
Comment 5 Manuel Hiebel 2012-02-24 23:08:22 CET 
Seems indeed to it's only in the dkms, and modprobe can't found the module

Keywords: NEEDINFO => (none)
Assignee: bugsquad => tmb

Comment 6 Thomas Backlund 2012-03-02 19:19:46 CET 
Hmmm, the provides are there:

[tmb@tmb release]$ rpm -qp --provides virtualbox-kernel-3.2.9-desktop-1.mga2-4.1.8-15.mga2.x86_64.rpm
kmod(vboxdrv) = 4.1.8-3.mga2
kmod(vboxnetadp) = 4.1.8-3.mga2
kmod(vboxnetflt) = 4.1.8-3.mga2
virtualbox-kernel-3.2.9-desktop-1.mga2 = 4.1.8-15.mga2
virtualbox-kernel-3.2.9-desktop-1.mga2(x86-64) = 4.1.8-15.mga2
Comment 7 Manuel Hiebel 2012-03-13 00:07:44 CET 
bug still valid with the recent updates ? (one more is coming)

Keywords: (none) => NEEDINFO

Comment 8 Marja Van Waes 2012-03-29 07:24:13 CEST 
(In reply to comment #7)
> bug still valid with the recent updates ? (one more is coming)

@ Bernard
@ Uli

Is this  bug stil there in updated cauldron? If you won't reply within two weeks from now, I will have to close this bug as OLD. Thank you.

CC: (none) => marja11

Comment 9 Uli Selle 2012-04-03 05:46:17 CEST 
(In reply to comment #8)
> (In reply to comment #7)
> > bug still valid with the recent updates ? (one more is coming)
> 
> @ Bernard
> @ Uli
> 
> Is this  bug stil there in updated cauldron? If you won't reply within two
> weeks from now, I will have to close this bug as OLD. Thank you.

No, uninstalled all components and installed new, choosing only "virtualbox" in the graphic installer. The new virtualbox installation could start its guests without failures...
Comment 10 Marja Van Waes 2012-04-05 09:14:58 CEST 
(In reply to comment #9)
> (In reply to comment #8)
> > (In reply to comment #7)
> > > bug still valid with the recent updates ? (one more is coming)
> > 
> > @ Bernard
> > @ Uli
> > 
> > Is this  bug stil there in updated cauldron? If you won't reply within two
> > weeks from now, I will have to close this bug as OLD. Thank you.
> 
> No, uninstalled all components and installed new, choosing only "virtualbox" in
> the graphic installer. The new virtualbox installation could start its guests
> without failures...

Thanks for the feedback, Uli :)

Closing as fixed

@ Bernard
If it wasn't fixed for you in updated cauldron, please reopen

Status: NEW => RESOLVED
Resolution: (none) => FIXED
Note You need to log in before you can comment on or make changes to this bug.