On 09/05/2014 11:06 AM, Bob Goodwin - Zuni, Virginia, USA wrote:
>
> On 09/05/14 11:52, Kevin Martin wrote:
>> How did you install VirtualBox (via kmod/akmod or from virtualbox.org)? Have
you recently updated your kernel? If you've done the
>> latter then you'll need to either reboot and let akmod rebuild a VirtualBox
kmod or you'll need to reinstall the VirtualBox app that
>> you downloaded from
virtualbox.org to get the vboxdrv rebuilt and loaded.
>>
>> Kevin
> Dunno how but I am certain it was via yum, but from where? I guess what I need to do
is find the kmod/akmod version and install
> that. I'm sure the kernel has been updated several times since VBox was
installed. And I know from experience that without the auto
> update feature I will have problems.
>
> I wasted my money on a copy of VMware that became useless after most kernel updates,
finally gave up trying to deal with that.
>
> Tnx,
>
> Bob
>
I gave up on the version from rpmfusion since they are unable to keep up with kernel
updates from what I can tell and the akmod
would fail to rebuild. I downloaded the version from
VirtualBox.org, checked to see what
patches I might need for the kernel I'm
on, patched and built it and it's working flawlessly at this time. It's
important to note that Oracle/VirtualBox *also don't tend
to keep up with the kernel versions very well but there are a number of people who do
figure out where the patches need to be and
submit patches on the forums to get things working. It's much easier to patch, at
least I think it is, the
virtualbox.org version
than it is to try to de-rpm the rpmfusion version, patch it, and re-rpm it back to a
state where it can be reinstalled with yum/dnf
and work (temporarily).
Kevin
Just to be clear: if you keep to the standard Fedora kernels there's no
need to patch anything. VBox Just Works(tm) and updates via yum as it
should. The DKMS stuff takes care of everything else automatically.
poc