[Pkg-virtualbox-devel] Bug#576255: Bug#576255: FATAL: Error inserting vboxvfs (/lib/modules/2.6.30-bpo.1-amd64/updates/dkms/vboxvfs.ko): Unknown symbol in module, or unknown parameter (see dmesg)

Mathieu Malaterre mathieu.malaterre at gmail.com
Fri Apr 2 13:37:22 UTC 2010


On Fri, Apr 2, 2010 at 10:29 AM, Michael Meskes <meskes at debian.org> wrote:
> First of all why should this be a bug in guest-utils? This looks to me as if

sorry. VBox was working fine and only when I decided to use
SharedFolders did I got this issue.

> you don't have the right modules for your kernel. Unfortunately your bug report
> lacks information about the virtualbox-ose-guest-dkms version installed. Also
> we need to make sure that you indeed have compiled modules for your kernel. So
> please remove the modules you have and re-build them

$ sudo apt-get remove --purge virtualbox-ose virtualbox-ose-guest-dkms
virtualbox-ose-guest-x11 virtualbox-ose-guest-utils dkms
...

$ sudo apt-get install virtualbox-ose-guest-utils
Reading package lists... Done
Building dependency tree
Reading state information... Done
The following packages were automatically installed and are no longer required:
  libdb4.5-java libswt3.4-gtk-java libdb4.5-java-gcj liblucene-java
libswt3.4-gtk-jni
Use 'apt-get autoremove' to remove them.
The following extra packages will be installed:
  dkms virtualbox-ose-guest-dkms virtualbox-ose-guest-x11
The following NEW packages will be installed:
  dkms virtualbox-ose-guest-dkms virtualbox-ose-guest-utils
virtualbox-ose-guest-x11
0 upgraded, 4 newly installed, 0 to remove and 220 not upgraded.
Need to get 70.1kB/2121kB of archives.
After this operation, 8552kB of additional disk space will be used.
Do you want to continue [Y/n]?
Get:1 http://www.backports.org lenny-backports/main dkms
2.1.1.2-2~bpo50+1 [70.1kB]
Fetched 70.1kB in 0s (287kB/s)
Selecting previously deselected package dkms.
(Reading database ... 411596 files and directories currently installed.)
Unpacking dkms (from .../dkms_2.1.1.2-2~bpo50+1_all.deb) ...
Selecting previously deselected package virtualbox-ose-guest-dkms.
Unpacking virtualbox-ose-guest-dkms (from
.../virtualbox-ose-guest-dkms_3.1.4-dfsg-1~bpo50+1_all.deb) ...
Selecting previously deselected package virtualbox-ose-guest-utils.
Unpacking virtualbox-ose-guest-utils (from
.../virtualbox-ose-guest-utils_3.1.4-dfsg-1~bpo50+1_amd64.deb) ...
Selecting previously deselected package virtualbox-ose-guest-x11.
Unpacking virtualbox-ose-guest-x11 (from
.../virtualbox-ose-guest-x11_3.1.4-dfsg-1~bpo50+1_amd64.deb) ...
Processing triggers for man-db ...
Processing triggers for hal ...
Regenerating hal fdi cache ...
Restarting Hardware abstraction layer: hald.
Setting up dkms (2.1.1.2-2~bpo50+1) ...
Setting up virtualbox-ose-guest-dkms (3.1.4-dfsg-1~bpo50+1) ...
Loading new virtualbox-ose-guest-3.1.4 DKMS files...
First Installation: checking all kernels...
Building only for 2.6.30-bpo.1-amd64
Building for architecture amd64
Building initial module for 2.6.30-bpo.1-amd64
Done.

vboxguest.ko:
Running module version sanity check.
 - Original module
   - No original module exists within this kernel
 - Installation
   - Installing to /lib/modules/2.6.30-bpo.1-amd64/updates/dkms/

vboxvfs.ko:
Running module version sanity check.
 - Original module
   - No original module exists within this kernel
 - Installation
   - Installing to /lib/modules/2.6.30-bpo.1-amd64/updates/dkms/

vboxvideo.ko:
Running module version sanity check.
 - Original module
   - No original module exists within this kernel
 - Installation
   - Installing to /lib/modules/2.6.30-bpo.1-amd64/updates/dkms/

depmod....

DKMS: install Completed.
Setting up virtualbox-ose-guest-utils (3.1.4-dfsg-1~bpo50+1) ...
Setting up virtualbox-ose-guest-x11 (3.1.4-dfsg-1~bpo50+1) ...

$ sudo modprobe vboxvfs
WARNING: Error inserting vboxguest
(/lib/modules/2.6.30-bpo.1-amd64/updates/dkms/vboxguest.ko): No such
device
FATAL: Error inserting vboxvfs
(/lib/modules/2.6.30-bpo.1-amd64/updates/dkms/vboxvfs.ko): Unknown
symbol in module, or unknown parameter (see dmesg)

Where dmesg is:

...
[193140.862592] vboxguest: VirtualBox Guest PCI device not found.
[193140.895542] vboxvfs: Unknown symbol RTSemFastMutexCreate
[193140.895644] vboxvfs: Unknown symbol VBoxGuestIDCCall
[193140.895725] vboxvfs: Unknown symbol RTMemTmpFree
[193140.895773] vboxvfs: Unknown symbol RTErrConvertToErrno
[193140.895822] vboxvfs: Unknown symbol RTSemFastMutexRequest
[193140.895887] vboxvfs: Unknown symbol RTMemTmpAlloc
[193140.895935] vboxvfs: Unknown symbol RTLogRelDefaultInstance
[193140.895992] vboxvfs: Unknown symbol RTMemContAlloc
[193140.896040] vboxvfs: Unknown symbol RTSemFastMutexRelease
[193140.896140] vboxvfs: Unknown symbol VBoxGuestIDCOpen
[193140.896197] vboxvfs: Unknown symbol AssertMsg2
[193140.896264] vboxvfs: Unknown symbol RTMemContFree
[193140.896332] vboxvfs: Unknown symbol RTAssertShouldPanic
[193140.896389] vboxvfs: Unknown symbol RTLogLoggerEx
[193140.896540] vboxvfs: Unknown symbol VBoxGuestIDCClose
[193140.896631] vboxvfs: Unknown symbol AssertMsg1
[193140.896685] vboxvfs: Unknown symbol RTSemFastMutexDestroy


If I try to modprobe vboxguest I get:

[193438.326626] vboxguest: VirtualBox Guest PCI device not found.
[193484.525488] vboxdrv: Trying to deactivate the NMI watchdog permanently...
[193484.525490] vboxdrv: Successfully done.
[193484.525492] vboxdrv: Found 8 processor cores.
[193484.525543] VBoxDrv: dbg - g_abExecMemory=ffffffffa1004080
[193484.528842] vboxdrv: fAsync=0 offMin=0x70a offMax=0x3afda
[193484.528874] vboxdrv: TSC mode is 'synchronous', kernel timer mode
is 'normal'.
[193484.528876] vboxdrv: Successfully loaded version 3.1.4_OSE
(interface 0x00100001).
[193484.535074] vboxguest: exports duplicate symbol RTMemExecFree
(owned by vboxdrv)
[193484.540567] vboxguest: exports duplicate symbol RTMemExecFree
(owned by vboxdrv)
[193529.782516] vboxguest: exports duplicate symbol RTMemExecFree
(owned by vboxdrv)
[193529.783003] vboxvfs: Unknown symbol VBoxGuestIDCCall
[193529.783410] vboxvfs: Unknown symbol VBoxGuestIDCOpen
[193529.783867] vboxvfs: Unknown symbol VBoxGuestIDCClose


Using :


$ apt-cache policy virtualbox-ose dkms
virtualbox-ose:
  Installed: 3.1.4-dfsg-1~bpo50+1
  Candidate: 3.1.4-dfsg-1~bpo50+1
  Version table:
     3.1.4-dfsg-3 0
        100 http://ftp.fr.debian.org unstable/main Packages
     3.1.4-dfsg-2 0
        200 http://ftp.fr.debian.org testing/main Packages
 *** 3.1.4-dfsg-1~bpo50+1 0
        600 http://www.backports.org lenny-backports/main Packages
        100 /var/lib/dpkg/status
     1.6.6-dfsg-3 0
        500 http://ftp.fr.debian.org lenny/main Packages
dkms:
  Installed: 2.1.1.2-2~bpo50+1
  Candidate: 2.1.1.2-2~bpo50+1
  Version table:
     2.1.1.2-2 0
        200 http://ftp.fr.debian.org testing/main Packages
        100 http://ftp.fr.debian.org unstable/main Packages
 *** 2.1.1.2-2~bpo50+1 0
        600 http://www.backports.org lenny-backports/main Packages
        100 /var/lib/dpkg/status

All I want to do is `mount.vboxsf Share /mnt/Share`. Maybe I do not
need to modprobe vboxvfs first... but I could not find anything. There
is no man page for mount.vboxsf. So I simply tried:

$ mkdir /tmp/vboxshared
$ sudo mount -t vboxsf shared /tmp/vboxshared
/sbin/mount.vboxsf: mounting failed with the error: No such device

Some search on the net suggest to actually do the (manual) `modprobe
vboxvfs` first. Should I modprobe vboxvfs first or not to get
mount.vboxsf working ?


Thanks !
-- 
Mathieu





More information about the Pkg-virtualbox-devel mailing list