-c

Yep, that’s certainly another way to do it – I mentioned at the beginning that the method in my post was not using the pre-packaged Fedora versions (from RPMFusion) because they are old (currently 4.0.2, vs 4.1).

I don’t think that kmod is actually easier to maintain at all – sometimes when you get a new kernel update there is no new kmod package for VirtualBox yet – that means when you reboot, you can’t use VirtualBox unless you boot back to your old kernel, or build it you yourself anyway. The akmod method would be better as it gets around this problem (akmod-VirtualBox-OSE) but this means that you need devel tools anyway.

By comparison, using the method in my post, you never ever have to manually build the kernel modules on the host. It’s all done for you automatically, no-matter what kernel you have, or what kernel you boot! To me, that’s much less annoying than the kmod method

-c

http://www.rpmfusion.org/

They have the virtualbox kmod, meaning you do not need to compile the kernel module.

I prefer this method as I do not like installing gcc and the releated development tools and it is easier to maintain, yum will update the kmod with the kernel, so no need to build a kernel module manually with each new kernel.

http://download1.rpmfusion.org/free/fedora/development/source/SRPMS/repoview/VirtualBox-OSE-kmod.html

http://download1.rpmfusion.org/free/fedora/development/source/SRPMS/repoview/VirtualBox-OSE.html

Install the guest additions, however, is another matter. Some distros include the guest additions in the repos, so you might want to check on that before you compile.

Glad it could help!

-c

Your article resolved issues i was facing.