Fedora 12 & vboxvfs issue

[BC2009]

I am having some strange behavior with the guest additions on Fedora 12 with x86_64 architecture.
My host machine is Mac OSX 10.6.2 with 64-bit Kernel enabled.

Guest output from uname -a is as follows:

Linux [hostname] 2.6.32.10-90.fc12.x86_64 #1 SMP Tue Mar 23 09:47:08 UTC 2010 x86_64 x86_64 x86_64 GNU/Linux

Host output from uname -a is:
Darwin [hostname] 10.2.0 Darwin Kernel Version 10.2.0: Tue Nov 3 23:07:25 PST 2009; root:xnu-1486.2.11~3/RELEASE_X86_64 x86_64

When I run the installer for the guest additions it reports no errors whatsoever. However, during boot of the guest I get the following:

Starting the VirtualBox Guest Additions ^[[60G[^[[0;31mFAILED^[[0;39m]^M
(modprobe vboxvfs failed)

I believe the funky characters around the word "FAILED" are for making it appear in red on the startup screen.

After boot, if I run "modproble vboxvfs" I would get the following:

FATAL: Error inserting vboxdrv (/lib/modules/2.6.32.10-90.fc12.x86_64/misc/vboxdrv.ko): Invalid module format

And if I tried to mount a share, I would get:
/sbin/mount.vboxsf: mounting failed with the error: No such device

Sooooo.... I hunted around the internet and found somebody saying they had problems similar with other modules.
And they tried using "insmod" instead.... So I gave this a try:

> insmod /lib/modules/2.6.32.10-90.fc12.x86_64/extra/vboxvfs.ko

It did not return any errors, and now I can mount the shares without a hitch.

However, if I do a "modprobe vboxdrv" that still fails with the "Invalid module format". -- not sure what "vboxdrv" does, I read somewhere that the other guest modules depend on it.

Anyway, my big question is.... why do I need to do this to get the vboxvfs module to load? I can throw in a startup script to do this, but I'd like to fix my guest OS. Any help would be appreciated. Thanks!

I also read somewhere that you need DKMS to load dynamic kernel modules -- so I installed that along the way to fix it, and these are the packages I found:

>rpm -qa | grep -i dkms
dkms-openafs-1.4.11-1.1.2.fc12.x86_64
dkms-2.1.0.1-1.fc12.noarch
dkms-ap-kernelmodule-1.0.8b-17.fc11.x86_64

[mathis]

I have the same problem with OSX 10.6.3 with an X86 architecture and a 64-bit Kernel enabled.

I also get on mounting a share:
/media$ sudo mount -t vboxsf ubuntufolder /media/ubuntufolder
/sbin/mount.vboxsf: mounting failed with the error: No such device

However, I haven't tried the insmod fix yet.

[Sasquatch]

Are you sure you installed the proper GA version (i.e. the amd64 version instead of the x86 one)?
You should not have a module called vboxdrv, that's for Host systems only (in case Linux is the host). The following modules should exist on a Linux Guest:

• vboxvideo
• vboxvfs
• vboxguest

[edd]

Are you still having these issue with vboxvfs. I've just found out that from the virtualbox documentation (changelog to be specific) that from version 3.1.8 onwards they have changed vboxvfs to vboxsf.

So try replacing vboxvfs to vboxsf

Hope this helps.

Shared folders: renamed the guest kernel module from vboxvfs to vboxsf to make it load on demand by the Linux kernel. Fixes mounting from /etc/fstab in Ubuntu 10.04