Bug 3613

Thanks , I'm address this issue to kwizart . 
Yesterday I already had a complain on ask [1]
meanwhile please enable  repo rpmfusion-free-updates-testing temporarily with :

yum --enablerepo=rpmfusion-free-updates-testing update kernel\*


[1] https://ask.fedoraproject.org/en/question/67915/how-to-install-virtualbox-guest-for-not-latest-kernel/

this should work for you: 

yum --enablerepo=rpmfusion-free-updates-testing update kmod-VirtualBox kernel\*

(In reply to comment #0)
> It seems everytime a kernel update occurs in Fedora 21 I have a problem with
> VirtualBox. It seems kmod-VirtualBox does not get updated correctly to match
> the new kernel version.
> 

No one is forcing you to update the kernel, most people wait till the matching kmod-VirtualBox is available.
 
> Any idea what is wrong here?

Yes, It's user impatience! and your reluctance to use akmod.

> 
> And yes, I know about the akmod workaround that is advertised on many places,
> but I think this should just be fixed.

There isn't a real issue here!, it's always going to take a day or two for rpmfusion to sync with the official repos

Not all the time, but this reports are useful to alert the push is late ( because is manual )  ... 
This report expose other problem of akmods2 structure, shortly the user doesn't installed kernel-3.19.5 that was on stable repos and now on stable repos we got kernel-3.19.6, kmod-VirtualBox-4.3.26-1.fc21.5 (version 5) ask for kernel-3.19.5 and new kmod-VirtualBox-4.3.26-1.fc21.6 (version 6) ask for kernel kernel-3.19.6 . 
User got kernel version 4 , kernel version 5 was deleted from update-stable repo because was pushed version 6, so from rpmfusion updates-stable, version 5 ask for a kernel that already not exist in repos and that why we got this error, but if user got kernel updated on version 5, on update of kernel version 6 will miss updates of kmod version 6 until they aren't pushed to stable. User will be frustrated when boot in new kernel version (without kmods) . So at end this error is not so bad, I'm trying sum up all this flaws in :
https://bugzilla.rpmfusion.org/show_bug.cgi?id=3386

Thanks,

*** This bug has been marked as a duplicate of bug 3386 ***

(In reply to comment #3)
> (In reply to comment #0)
> > It seems everytime a kernel update occurs in Fedora 21 I have a problem with
> > VirtualBox. It seems kmod-VirtualBox does not get updated correctly to match
> > the new kernel version.
> > 
> 
> No one is forcing you to update the kernel, most people wait till the matching
> kmod-VirtualBox is available.

true. This is not my complaint. The point I wanted to make is that even if an update exists in rpmfusion-free-updates it does not get installed.

Another example occurred today. Kernel was updated to 3.19.7-200.fc21.x86_64 but  kmod-VirtualBox did not follow.
I then removed VirtualBox and installed it again and  kmod-VirtualBox-3.19.7-200.fc21.x86_64 is available and gets installed ...

From this it seems to me that even if an update of kmod for the new kernel version is available it does not get installed.
So either something is wrong in the organisation of the repository or its meta data, or something is wrong in my local cache of this data.
Since I am no guru on the internal workings of yum or repositories I would expect some help on how to verify what actually is the matter on my system.

> > Any idea what is wrong here?
> 
> Yes, It's user impatience! and your reluctance to use akmod.

no, it has nothing to do with impatience as described above. I have no problem waiting a few days for an update to appear, and will happily reboot into an older kernel if I need VirtualBox in this case. However, if you decide to package kmod-VirtualBox it should work correctly and people should be allowed to complain if it does not.

(In reply to comment #6)
> (In reply to comment #3)
> > (In reply to comment #0)
> > > It seems everytime a kernel update occurs in Fedora 21 I have a problem with
> > > VirtualBox. It seems kmod-VirtualBox does not get updated correctly to match
> > > the new kernel version.
> > > 
> > 
> > No one is forcing you to update the kernel, most people wait till the matching
> > kmod-VirtualBox is available.
> 
> true. This is not my complaint. The point I wanted to make is that even if an
> update exists in rpmfusion-free-updates it does not get installed.

did you ? : 

yum install kmod-VirtualBox-4.3.26-2.fc21.1

> Another example occurred today. Kernel was updated to 3.19.7-200.fc21.x86_64
> but  kmod-VirtualBox did not follow.
> I then removed VirtualBox and installed it again and 
> kmod-VirtualBox-3.19.7-200.fc21.x86_64 is available and gets installed ...
> 
> From this it seems to me that even if an update of kmod for the new kernel
> version is available it does not get installed.
> So either something is wrong in the organisation of the repository or its meta
> data, or something is wrong in my local cache of this data.
> Since I am no guru on the internal workings of yum or repositories I would
> expect some help on how to verify what actually is the matter on my system.
> 
> > > Any idea what is wrong here?
> > 
> > Yes, It's user impatience! and your reluctance to use akmod.
> 
> no, it has nothing to do with impatience as described above. I have no problem
> waiting a few days for an update to appear, and will happily reboot into an
> older kernel if I need VirtualBox in this case. However, if you decide to
> package kmod-VirtualBox it should work correctly and people should be allowed
> to complain if it does not.

yeah, you could complain ! and it is welcome , I think you need kmod-VirtualBox-4.3.26-2.fc21.1 meta package :

This is a meta-package which sole purpose is to require the
VirtualBox kernel module(s) for the newest kernel.
to make sure you get it together with a new kernel.

This time, I think, it's all sync correctly, kmods for 3.19.7-200.fc21.x86_64 in updates stable . 
kmods for 3.19.8-200.fc21.x86_64 in updates testing and soon should also came with new upstream release 
VirtualBox-4.3.28 ;) 

Thanks for helping on testing VirtualBox of RPMFusion !

Well, for some reason I didn't get email notifications, even though I am in the cc list. It turns out gmail classified them as spam.

Anyway, another kernel update is here (4.0.4-202), and I deinstalled and reinstalled VirtualBox and kmod-VirtualBox before I read your answer.

Just for reference, my current versions areL

VirtualBox.x86_64       4.3.28-1.fc21    @rpmfusion-free-updates
kmod-VirtualBox.x86_64  4.3.28-1.fc21.3  @rpmfusion-free-updates-testing

To answer your question, no, as I wrote earlier, deinstalling and reinstalling from the "*testing" repository allowed me to get it running again, so then there is no point of doing a command like yum install kmod-VirtualBox-4.3.26-2.fc21.1

I'll keep on using and testing and let you know in case I think things don't work out for a next kernel update.

(In reply to comment #8)
> Well, for some reason I didn't get email notifications, even though I am in the
> cc list. It turns out gmail classified them as spam.

Hi, 
IIRC rpmfusion can be classified as SPAM, I had to add rpmfusion.net in white list , so the best is tell to  antispam that emails sent by rpmfusion servers, are good, It is what I do. Also IIRC  in gmail.com I put rpmfusion in withlist . 

> Anyway, another kernel update is here (4.0.4-202), and I deinstalled and
> reinstalled VirtualBox and kmod-VirtualBox before I read your answer.
> 
> Just for reference, my current versions areL
> 
> VirtualBox.x86_64       4.3.28-1.fc21    @rpmfusion-free-updates
> kmod-VirtualBox.x86_64  4.3.28-1.fc21.3  @rpmfusion-free-updates-testing
> 
> To answer your question, no, as I wrote earlier, deinstalling and reinstalling
> from the "*testing" repository allowed me to get it running again, so then
> there is no point of doing a command like yum install
> kmod-VirtualBox-4.3.26-2.fc21.1
> 
> I'll keep on using and testing and let you know in case I think things don't
> work out for a next kernel update.

1/2 hour later, package VirtualBox-kmod-4.3.28-1.fc21.3 on rpmfusion-free-updates-testing have been pushed to stable. 
Thanks for the alert ;)  

Explanation: 

dnf repoquery kmod-VirtualBox-4.3.26-2.fc21.1 --requires

kmod-VirtualBox-3.19.7-200.fc21.x86_64 >= 4.3.26-2.fc21.1

Now that you have a version 4.3.28  you will need a 
dnf repoquery kmod-VirtualBox-4.3.28 

kmod-VirtualBox-0:4.3.28-1.fc21.1.x86_64
kmod-VirtualBox-0:4.3.28-1.fc21.x86_64
kmod-VirtualBox-0:4.3.28-1.fc21.3.x86_64
kmod-VirtualBox-0:4.3.28-1.fc21.2.x86_64

dnf repoquery kmod-VirtualBox-4.3.28 --requires

kmod-VirtualBox-4.0.4-200.fc21.x86_64 >= 4.3.28-1.fc21.1
kmod-VirtualBox-3.19.8-200.fc21.x86_64 >= 4.3.28-1.fc21
kmod-VirtualBox-4.0.4-202.fc21.x86_64 >= 4.3.28-1.fc21.3
kmod-VirtualBox-4.0.4-201.fc21.x86_64 >= 4.3.28-1.fc21.2

So what need for kernel 4.0.4-202 is kmod-VirtualBox-4.0.4-202.fc21.x86_64 
dnf install kmod-VirtualBox-0:4.3.28-1.fc21.3.x86_64

and if you not reboot the system, you need removed the old kmods loaded and load the new ones, freshly installed, with: 

rmmod vboxnetadp vboxnetflt vboxdrv

and

systemctl restart systemd-modules-load