Opened 5 years ago
Closed 5 years ago
#18961 closed defect (worksforme)
5.2.X new guest additions don't work with Linux 5.3 kernels
| Reported by: | Frank Batschulat (Oracle) | Owned by: | Frank Batschulat (Oracle) |
|---|---|---|---|
| Component: | guest additions | Version: | VirtualBox 5.2.32 |
| Keywords: | Cc: | ||
| Guest type: | Linux | Host type: | Linux |
Description
The current 5.2.X testbuild guest additions to not quite work with a guest running a Linux 5.3 kernel. testbuilds that contain the fixes for: #18911 (closed defect: fixed) Fixes for Linux kernel 5.3 wanted - part 1 https://www.virtualbox.org/ticket/18911
HOST:
Linux lserver 4.18.0-80.11.1.el8_0.x86_64 #1 SMP Thu Sep 12 03:35:29 GMT 2019 x86_64 x86_64 x86_64 GNU/Linux $ cat /etc/os-release NAME="Oracle Linux Server" VERSION="8.0" ID="ol" ID_LIKE="fedora" VARIANT="Server" VARIANT_ID="server" VERSION_ID="8.0" PLATFORM_ID="platform:el8" PRETTY_NAME="Oracle Linux Server 8.0"
GUEST:
Fedora-Workstation-Live-x86_64-31_Beta-1.1.iso
root@localhost ~]# uname -a Linux localhost.localdomain 5.3.0-1.fc31.x86_64 #1 SMP Mon Sep 16 12:34:42 UTC 2019 x86_64 x86_64 x86_64 GNU/Linux [root@localhost ~]# cat /etc/os-release NAME=Fedora VERSION="31 (Workstation Edition)" ID=fedora VERSION_ID=31 VERSION_CODENAME="" PLATFORM_ID="platform:f31" PRETTY_NAME="Fedora 31 (Workstation Edition)" ANSI_COLOR="0;34" LOGO=fedora-logo-icon CPE_NAME="cpe:/o:fedoraproject:fedora:31"
Virtualboxversion:
Linux EL8 64-bit 5.2.x revision 133577
Extension Pack 5.2.x revision 133571
https://www.virtualbox.org/download/testcase/VirtualBox-5.2-5.2.33_133577_el8-1.x86_64.rpm
https://www.virtualbox.org/download/testcase/Oracle_VM_VirtualBox_Extension_Pack-5.2.33-133571.vbox-extpack
whe installing and compiling the guest additions inside the guest we see:
touch: cannot touch '/var/lib/VBoxGuestAdditions/skip-5.3.0-1.fc31.x86_64': No such file or directory Copying additional installer modules ... Installing additional modules ... VirtualBox Guest Additions: Building the VirtualBox Guest Additions kernel modules. This may take a while. VirtualBox Guest Additions: To build modules for other installed kernels, run VirtualBox Guest Additions: /sbin/rcvboxadd quicksetup <version> VirtualBox Guest Additions: Building the modules for kernel 5.3.0-1.fc31.x86_64. VirtualBox Guest Additions: Running kernel modules will not be replaced until the system is restarted VirtualBox Guest Additions: Starting. VirtualBox Guest Additions: modprobe vboxsf failed
=> then reboot the guest.
We get the guest to a certain stage at graphcial boot but apparently it does not reach the state where it presents the login screen finally.
=> removed shared folder from settings and reboot = same problem => removing shared clipboard settings and reboot = same problem
NB: This does not happen with the 6.0.X test builds from: https://www.virtualbox.org/wiki/Testbuilds
VirtualBox-6.0-6.0.13_133347_el8-1.x86_64.rpm Oracle_VM_VirtualBox_Extension_Pack-6.0.13-133347.vbox-extpack
these are also test builds that contain the fixes for: #18911 (closed defect: fixed) Fixes for Linux kernel 5.3 wanted - part 1 https://www.virtualbox.org/ticket/18911
running those on the host and inside the a Fedora 31 kernel 5.3 guest,the shared folders, shared cliboard and everything else just works.
So this must be something specific to the 5.2.X virtualbox guest additions.
Needs more investigation.
Change History (12)
follow-up: 2 comment:1 by , 5 years ago
comment:2 by , 5 years ago
Replying to socratis:
Duplicate of #18911.
You shouldn't be opening a new ticket for something that has already a ticket assigned, just comment on the existing ticket, even if it's marked as [Fixed]...
Nope, this is not a duplicate. We have quite a different set of problems even after that fix. I'll update tomorrow with more details.
comment:3 by , 5 years ago
| Owner: | set to |
|---|---|
| Status: | new → accepted |
follow-up: 5 comment:4 by , 5 years ago
In my eyes, you simply comment on, and reopen ticket #18911, but I'm not a VirtualBox developer... ;)
comment:5 by , 5 years ago
comment:6 by , 5 years ago
I can confirm the problem on Archlinux when the Linux Host and Guest are running the 5.2 and 5.3 kernel. I maintain the 5.2.x branch package on AUR (Arch User Repository). However, when using the same Host running the 5.3 kernel, but Linux guest running the 4.x kernel (like openSUSE leap 15), the vboxsf module is present and working fine. I must stay with the 5.2 branch for now due to running guests --headless and windows guests with the 6.x release are unusably slow. They continue working great with the 5.2 branch. The only current issue being the missing vboxsf module for Guests running the 5.3 kernel.
I did further testing with the latest testbuild package for 5.2.33 and still on the 5.3 kernel there is no vboxsf module for Linux guests. The modules available in the Linux guests are:
$ lsmod | grep vbox vboxvideo 40960 1 drm_vram_helper 20480 1 vboxvideo drm_kms_helper 212992 1 vboxvideo drm 516096 5 drm_kms_helper,drm_vram_helper,vboxvideo,ttm vboxguest 45056 0
The testbuild build packages used were:
VirtualBox-5.2.33-133577-Linux_amd64.run
VirtualBoxSDK-5.2.33-133577.zip
VBoxGuestAdditions_5.2.33-133577.iso
While on the 4.x kernel all modules are available:
$ lsmod | grep vbox vboxsf 49152 1 vboxvideo 49152 2 vboxguest 303104 5 vboxsf drm_kms_helper 196608 1 vboxvideo ttm 114688 1 vboxvideo drm 438272 5 vboxvideo,ttm,drm_kms_helper syscopyarea 16384 2 vboxvideo,drm_kms_helper sysfillrect 16384 2 vboxvideo,drm_kms_helper sysimgblt 16384 2 vboxvideo,drm_kms_helper
That was surprising given both Guests above are running on the same Archlinux Host. Is there another patch I can test to see if I can get the vboxsf to appear on Guests with the 5.3 kernel? Let me know if there are additional patches to try. Also, let me know if I can provide further information that will help.
comment:7 by , 5 years ago
OK so here is the log how the guest additions compliation fails:
I have attempted to remove the ones installed by default with the guest OS and then we install and build the ones from us matching the hosts VBOX installation:
[root@localhost /]# dnf remove virtualbox-guest-additions Running transaction Preparing : 1/1 Running scriptlet: virtualbox-guest-additions-6.0.12-1.fc31.x86_64 1/1 Removed /etc/systemd/system/multi-user.target.wants/vboxservice.service. Erasing : virtualbox-guest-additions-6.0.12-1.fc31.x86_64 1/1 Running scriptlet: virtualbox-guest-additions-6.0.12-1.fc31.x86_64 1/1 Verifying : virtualbox-guest-additions-6.0.12-1.fc31.x86_64 1/1 Removed: virtualbox-guest-additions-6.0.12-1.fc31.x86_64
=> reboot guest VM, interestingly we still get VBOX modules loaded:
[fbatschu@localhost ~]$ lsmod|grep vbox vboxguest 45056 0 vboxvideo 40960 2 drm_vram_helper 20480 1 vboxvideo drm_kms_helper 212992 1 vboxvideo drm 512000 6 drm_kms_helper,drm_vram_helper,vboxvideo,ttm
=> now insert and install/build the real guest additions matching the hosts VBPX version:
[root@localhost VBox_GAs_5.2.33]# ./VBoxLinuxAdditions.run Verifying archive integrity... All good. Uncompressing VirtualBox 5.2.33 Guest Additions for Linux........ VirtualBox Guest Additions installer Copying additional installer modules ... Installing additional modules ... VirtualBox Guest Additions: Building the VirtualBox Guest Additions kernel modules. This may take a while. VirtualBox Guest Additions: To build modules for other installed kernels, run VirtualBox Guest Additions: /sbin/rcvboxadd quicksetup <version> VirtualBox Guest Additions: Building the modules for kernel 5.3.0-1.fc31.x86_64. VirtualBox Guest Additions: Running kernel modules will not be replaced until the system is restarted VirtualBox Guest Additions: Starting. VirtualBox Guest Additions: modprobe vboxsf failed [root@localhost VBox_GAs_5.2.33]# echo $? 2
=> we see we fail to build the shared folder module vboxsf due below errors:
modprobe: ERROR: could not insert 'vboxsf': Unknown symbol in module, or unknown parameter (see dmesg) [root@localhost VBox_GAs_5.2.33]# echo $? 1 [root@localhost /]# cat /var/log/vboxadd-setup.log Building the main Guest Additions module for kernel 5.3.0-1.fc31.x86_64. Building the shared folder support module. Building the graphics driver module. [ 335.568161] vboxsf: loading out-of-tree module taints kernel. [ 335.568192] vboxsf: module verification failed: signature and/or required key missing - tainting kernel [ 335.568222] vboxsf: Unknown symbol VBoxGuest_RTMemTmpFree (err -2) [ 335.568229] vboxsf: Unknown symbol VBoxGuestIDC (err -2) [ 335.568239] vboxsf: Unknown symbol VBoxGuest_RTSemFastMutexRequest (err -2) [ 335.568248] vboxsf: Unknown symbol VBoxGuest_RTSemFastMutexRelease (err -2) [ 335.568256] vboxsf: Unknown symbol VBoxGuest_RTLogRelGetDefaultInstanceEx (err -2) [ 335.568263] vboxsf: Unknown symbol VBoxGuest_RTStrCopy (err -2) [ 335.568272] vboxsf: Unknown symbol VBoxGuest_RTErrConvertToErrno (err -2) [ 335.568282] vboxsf: Unknown symbol VBoxGuest_RTSemFastMutexCreate (err -2) [ 335.568289] vboxsf: Unknown symbol VBoxGuest_RTSemFastMutexDestroy (err -2) [ 335.568302] vboxsf: Unknown symbol VBoxGuest_RTAssertShouldPanic (err -2) [ 335.568311] vboxsf: Unknown symbol VBoxGuest_RTLogLoggerEx (err -2) [ 335.568340] vboxsf: Unknown symbol VBoxGuest_RTMemTmpAllocTag (err -2) [ 335.568350] vboxsf: Unknown symbol VBoxGuest_RTAssertMsg1Weak (err -2) [ 335.568372] vboxsf: Unknown symbol VBoxGuest_RTAssertMsg2Weak (err -2) [ 343.044448] vboxsf: Unknown symbol VBoxGuest_RTMemTmpFree (err -2) [ 343.044456] vboxsf: Unknown symbol VBoxGuestIDC (err -2) [ 343.044466] vboxsf: Unknown symbol VBoxGuest_RTSemFastMutexRequest (err -2) [ 343.044475] vboxsf: Unknown symbol VBoxGuest_RTSemFastMutexRelease (err -2) [ 343.044484] vboxsf: Unknown symbol VBoxGuest_RTLogRelGetDefaultInstanceEx (err -2) [ 343.044491] vboxsf: Unknown symbol VBoxGuest_RTStrCopy (err -2) [ 343.044499] vboxsf: Unknown symbol VBoxGuest_RTErrConvertToErrno (err -2) [ 343.044510] vboxsf: Unknown symbol VBoxGuest_RTSemFastMutexCreate (err -2) [ 343.044518] vboxsf: Unknown symbol VBoxGuest_RTSemFastMutexDestroy (err -2) [ 343.044531] vboxsf: Unknown symbol VBoxGuest_RTAssertShouldPanic (err -2) [ 343.044539] vboxsf: Unknown symbol VBoxGuest_RTLogLoggerEx (err -2) [ 343.044548] vboxsf: Unknown symbol VBoxGuest_RTMemTmpAllocTag (err -2) [ 343.044599] vboxsf: Unknown symbol VBoxGuest_RTAssertMsg1Weak (err -2) [ 343.044889] vboxsf: Unknown symbol VBoxGuest_RTAssertMsg2Weak (err -2) [ 343.796150] vboxsf: Unknown symbol VBoxGuest_RTMemTmpFree (err -2) [ 343.796158] vboxsf: Unknown symbol VBoxGuestIDC (err -2) [ 343.796167] vboxsf: Unknown symbol VBoxGuest_RTSemFastMutexRequest (err -2) [ 343.796176] vboxsf: Unknown symbol VBoxGuest_RTSemFastMutexRelease (err -2) [ 343.796184] vboxsf: Unknown symbol VBoxGuest_RTLogRelGetDefaultInstanceEx (err -2) [ 343.796191] vboxsf: Unknown symbol VBoxGuest_RTStrCopy (err -2) [ 343.796199] vboxsf: Unknown symbol VBoxGuest_RTErrConvertToErrno (err -2) [ 343.796211] vboxsf: Unknown symbol VBoxGuest_RTSemFastMutexCreate (err -2) [ 343.796218] vboxsf: Unknown symbol VBoxGuest_RTSemFastMutexDestroy (err -2) [ 343.796231] vboxsf: Unknown symbol VBoxGuest_RTAssertShouldPanic (err -2) [ 343.796240] vboxsf: Unknown symbol VBoxGuest_RTLogLoggerEx (err -2) [ 343.796248] vboxsf: Unknown symbol VBoxGuest_RTMemTmpAllocTag (err -2) [ 343.796257] vboxsf: Unknown symbol VBoxGuest_RTAssertMsg1Weak (err -2) [ 343.796268] vboxsf: Unknown symbol VBoxGuest_RTAssertMsg2Weak (err -2) [ 410.882254] vboxsf: Unknown symbol VBoxGuest_RTMemTmpFree (err -2) [ 410.882263] vboxsf: Unknown symbol VBoxGuestIDC (err -2) [ 410.882273] vboxsf: Unknown symbol VBoxGuest_RTSemFastMutexRequest (err -2) [ 410.882283] vboxsf: Unknown symbol VBoxGuest_RTSemFastMutexRelease (err -2) [ 410.882291] vboxsf: Unknown symbol VBoxGuest_RTLogRelGetDefaultInstanceEx (err -2) [ 410.882299] vboxsf: Unknown symbol VBoxGuest_RTStrCopy (err -2) [ 410.882307] vboxsf: Unknown symbol VBoxGuest_RTErrConvertToErrno (err -2) [ 410.882319] vboxsf: Unknown symbol VBoxGuest_RTSemFastMutexCreate (err -2) [ 410.882326] vboxsf: Unknown symbol VBoxGuest_RTSemFastMutexDestroy (err -2) [ 410.882339] vboxsf: Unknown symbol VBoxGuest_RTAssertShouldPanic (err -2) [ 410.882348] vboxsf: Unknown symbol VBoxGuest_RTLogLoggerEx (err -2) [ 410.882357] vboxsf: Unknown symbol VBoxGuest_RTMemTmpAllocTag (err -2) [ 410.882366] vboxsf: Unknown symbol VBoxGuest_RTAssertMsg1Weak (err -2) [ 410.882376] vboxsf: Unknown symbol VBoxGuest_RTAssertMsg2Weak (err -2) 1581674 4 drwxr-xr-x 4 root root 4096 Sep 23 14:22 /opt/VBoxGuestAdditions-5.2.33/src/vboxguest-5.2.33/vboxsf [root@localhost vboxsf]# ls dirops.c Makefile.include.footer quad.h udivmoddi4.c VBoxGuestR0LibIdc-unix.c vfsmod.c divdi3.c Makefile.include.header r0drv umoddi3.c VBoxGuestR0LibInternal.h vfsmod.h include moddi3.c regops.c utils.c VBoxGuestR0LibSharedFolders.c lnkops.c product-generated.h revision-generated.h VBoxGuestR0LibHGCM.c vbsfmount.h Makefile qdivrem.c udivdi3.c VBoxGuestR0LibIdc.c version-generated.h
=> now reboot the guest VM again, again it booted into graphical mode, but black screen not reaching the login dialog => system is remotely accessiblea, dmesg shows:
[ 28.107491] vboxsf: Successfully loaded version 5.2.33 (interface 0x00010004)
[ 34.305664] VBoxService 5.2.33 r133533 (verbosity: 0) linux.amd64 (Sep 23 2019 14:22:37) release log
00:00:00.000177 main Log opened 2019-09-25T16:30:52.884520000Z
[ 34.305716] 00:00:00.000252 main OS Product: Linux
[ 34.305743] 00:00:00.000291 main OS Release: 5.3.0-1.fc31.x86_64
[ 34.305756] 00:00:00.000317 main OS Version: #1 SMP Mon Sep 16 12:34:42 UTC 2019
[ 34.305773] 00:00:00.000330 main Executable: /opt/VBoxGuestAdditions-5.2.33/sbin/VBoxService
00:00:00.000330 main Process ID: 1086
00:00:00.000331 main Package type: LINUX_64BITS_GENERIC
[ 34.307010] 00:00:00.001542 main 5.2.33 r133533 started. Verbose level = 0
[ 34.320046] 00:00:00.014581 automount vbsvcAutoMountWorker: Shared folder 'Downloads' was mounted to '/media/sf_Downloads'
[fbatschu@localhost ~]$
=> the shared folder however is available and mounted!
[fbatschu@localhost ~]$ mount |grep vbox /home/fbatschu/Downloads on /media/sf_Downloads type vboxsf (rw,nodev,relatime) [root@localhost fbatschu]# ls /media/sf_Downloads teamviewer-host_14.5.5819_amd64.deb Fedora-Workstation-Live-x86_64-31_Beta-1.1.iso teamviewer-host_14.5.5819.x86_64.rpm Oracle_VM_VirtualBox_Extension_Pack-5.2.33-133571.vbox-extpack teamviewer-host-suse_14.5.5819.x86_64.rpm Oracle_VM_VirtualBox_Extension_Pack-6.0.13-133347.vbox-extpack teamviewer-suse_14.5.5819.x86_64.rpm teamviewer_14.5.5819_amd64.deb VirtualBox-5.2-5.2.33_133577_el8-1.x86_64.rpm teamviewer_14.5.5819.x86_64.rpm VirtualBox-6.0-6.0.13_133347_el8-1.x86_64.rpm
=> and the vboxsf module is loaded:
[root@localhost log]# lsmod |grep vbox vboxsf 49152 1 vboxvideo 36864 2 drm_kms_helper 212992 1 vboxvideo ttm 122880 1 vboxvideo drm 512000 5 drm_kms_helper,vboxvideo,ttm vboxguest 266240 2 vboxsf
=> order of vbox related events in dmesg during boot:
[ 1.598183] ACPI: Video Device [GFX0] (multi-head: yes rom: no post: no)
[ 1.598224] input: Video Bus as /devices/LNXSYSTM:00/LNXSYBUS:00/PNP0A03:00/LNXVIDEO:00/input/input6
[ 1.611518] vboxguest: loading out-of-tree module taints kernel.
[ 1.611577] vboxguest: module verification failed: signature and/or required key missing - tainting kernel
[ 1.615063] vgdrvHeartbeatInit: Setting up heartbeat to trigger every 2000 milliseconds
[ 1.615115] input: Unspecified device as /devices/pci0000:00/0000:00:04.0/input/input7
[ 1.615206] vboxguest: misc device minor 57, IRQ 20, I/O port d020, MMIO at 00000000f0400000 (size 0x400000)
[ 1.615207] vboxguest: Successfully loaded version 5.2.33 (interface 0x00010004)
[ 1.662932] fbcon: vboxvideodrmfb (fb0) is primary device
[ 1.665280] Console: switching to colour frame buffer device 100x37
[ 1.665918] vboxvideo 0000:00:02.0: fb0: vboxvideodrmfb frame buffer device
[ 1.669080] [drm] Initialized vboxvideo 1.0.0 20130823 for 0000:00:02.0 on minor 0
[ 28.107491] vboxsf: Successfully loaded version 5.2.33 (interface 0x00010004)
[ 34.305664] VBoxService 5.2.33 r133533 (verbosity: 0) linux.amd64 (Sep 23 2019 14:22:37) release log
00:00:00.000177 main Log opened 2019-09-25T16:30:52.884520000Z
[ 34.305716] 00:00:00.000252 main OS Product: Linux
[ 34.305743] 00:00:00.000291 main OS Release: 5.3.0-1.fc31.x86_64
[ 34.305756] 00:00:00.000317 main OS Version: #1 SMP Mon Sep 16 12:34:42 UTC 2019
[ 34.305773] 00:00:00.000330 main Executable: /opt/VBoxGuestAdditions-5.2.33/sbin/VBoxService
00:00:00.000330 main Process ID: 1086
00:00:00.000331 main Package type: LINUX_64BITS_GENERIC
[ 34.307010] 00:00:00.001542 main 5.2.33 r133533 started. Verbose level = 0
[ 34.320046] 00:00:00.014581 automount vbsvcAutoMountWorker: Shared folder 'Downloads' was mounted to '/media/sf_Downloads'
Sep 25 18:31:19 localhost.localdomain gnome-shell[1143]: Failed to CRTC gamma: drmModeCrtcSetGamma on CRTC 32 failed: Functio>
[root@localhost /]# ps -eafd|grep X
gdm 1159 1143 0 18:31 ? 00:00:00 /usr/bin/Xwayland :1024 -rootless -noreset -accessx -core -auth /run/user/42/.mutter-Xwaylandauth.MAGN8Z -listen 4 -listen 5 -displayfd 6
root 1693 1492 0 19:26 pts/0 00:00:00 grep --color=auto X
[root@localhost /]# kill -SIGHUP 1159
=> this brings back a working GDM instance. Interestingly without a login dialog, I am immediately logged in as myself. => screen resizing works too now so does the shared clipboard bi-directional work.
=> reboot now
=> the guest extension remember the enlarged screen size, but again, display manager does not come up with a login screen.
follow-up: 9 comment:8 by , 5 years ago
All the VBoxGuest_RT* symbols complained about during load of vboxsf module are not in our code base, not in 5.2 not in 6.0 and not in Trunk either.
comment:9 by , 5 years ago
Replying to fbatschu:
All the VBoxGuest_RT* symbols complained about during load of vboxsf module are not in our code base, not in 5.2 not in 6.0 and not in Trunk either.
That is because they are not defined that way in the source code, instead except for VBoxGuestIDC, all other symbol names complained about need to remove the VBoxGuest_ prefix when searching for it in the source code, eg: VBoxGuest_RTMemTmpFree really is RTMemTmpFree() and so forth.
comment:10 by , 5 years ago
so the error messages about unresolvable symbols during installation of our offical guest additions related to the previously installed default distribution vbox modules (which where of newer revision) and not to the ones currently installed.
We seen instances of that in the past a lot with disctribution default modules, eg:
https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=712108
https://forums.gentoo.org/viewtopic-t-1085266-start-0.html
https://superuser.com/questions/1268741/virtualbox-ubuntu-guest-additions-not-installing-modprobe-vboxsf-failed
https://www.virtualbox.org/ticket/17189
https://www.virtualbox.org/ticket/17189#comment:3
comment:11 by , 5 years ago
So I can confirm that the latest guest addtions do work depsite the initial impression when filing this bug.
Here's the detailed log of the working installatiom with thoe host/guest combination and Virtualbox packages as described to begin with:
[root@localhost log]# VBoxClient --version
5.2.33r133533
-rw-r--r--. 1 root root 1 Sep 25 18:19 vboxadd-install.log
-rw-r--r--. 1 root root 153 Sep 25 18:20 vboxadd-setup.log
[root@localhost log]# cat vboxadd-setup.log
Building the main Guest Additions module for kernel 5.3.0-1.fc31.x86_64.
Building the shared folder support module.
Building the graphics driver module.
[root@localhost log]# cat vboxadd-install.log
[root@localhost log]# lsmod|grep vbox
vboxsf 49152 1
vboxvideo 36864 3
drm_kms_helper 212992 1 vboxvideo
ttm 122880 1 vboxvideo
drm 512000 6 drm_kms_helper,vboxvideo,ttm
vboxguest 266240 5 vboxsf
dmesg:
[ 31.345497] vboxsf: Successfully loaded version 5.2.33 (interface 0x00010004)
[ 34.134497] VBoxService 5.2.33 r133533 (verbosity: 0) linux.amd64 (Sep 23 2019 14:22:37) release log
00:00:00.000135 main Log opened 2019-09-30T13:48:59.680169000Z
[ 34.134525] 00:00:00.000193 main OS Product: Linux
[ 34.134539] 00:00:00.000209 main OS Release: 5.3.0-1.fc31.x86_64
[ 34.134551] 00:00:00.000222 main OS Version: #1 SMP Mon Sep 16 12:34:42 UTC 2019
[ 34.134568] 00:00:00.000235 main Executable: /opt/VBoxGuestAdditions-5.2.33/sbin/VBoxService
00:00:00.000235 main Process ID: 938
00:00:00.000235 main Package type: LINUX_64BITS_GENERIC
[ 34.135639] 00:00:00.001298 main 5.2.33 r133533 started. Verbose level = 0
[ 34.152748] 00:00:00.018385 automount vbsvcAutoMountWorker: Shared folder 'Downloads' was mounted to '/media/sf_Downloads'
[ 569.960455] ISO 9660 Extensions: Microsoft Joliet Level 3
[ 570.011617] ISO 9660 Extensions: RRIP_1991A
[root@localhost log]# mount|grep vboxsf
Downloads on /media/sf_Downloads type vboxsf (rw,nodev,relatime)
[root@localhost /]# find / -name vboxsf* -ls
find: ‘/run/user/1000/gvfs’: Permission denied
17091 0 drwxr-xr-x 5 root root 0 Sep 30 15:48 /sys/module/vboxsf
17101 0 lrwxrwxrwx 1 root root 0 Sep 30 16:06 /sys/module/vboxguest/holders/vboxsf -> ../../vboxsf
1581674 4 drwxr-xr-x 4 root root 4096 Sep 23 14:22 /opt/VBoxGuestAdditions-5.2.33/src/vboxguest-5.2.33/vboxsf
1450586 2416 -rw-r--r-- 1 root root 2471768 Sep 25 18:20 /usr/lib/modules/5.3.0-1.fc31.x86_64/misc/vboxsf.ko
[root@localhost /]# cd /sys/module/vboxsf
[root@localhost vboxsf]# cat version
5.2.33 r133533
[root@localhost ~]# ls -la /usr/lib/modules/5.3.0-1.fc31.x86_64/misc/vbox*
-rw-r--r--. 1 root root 11928512 Sep 25 18:20 /usr/lib/modules/5.3.0-1.fc31.x86_64/misc/vboxguest.ko
-rw-r--r--. 1 root root 2471768 Sep 25 18:20 /usr/lib/modules/5.3.0-1.fc31.x86_64/misc/vboxsf.ko
-rw-r--r--. 1 root root 4013472 Sep 25 18:20 /usr/lib/modules/5.3.0-1.fc31.x86_64/misc/vboxvideo.ko
[root@localhost ~]# nm /usr/lib/modules/5.3.0-1.fc31.x86_64/misc/vboxsf.ko|grep VBoxGuest_RT
U VBoxGuest_RTAssertMsg1Weak
U VBoxGuest_RTAssertMsg2Weak
U VBoxGuest_RTAssertShouldPanic
U VBoxGuest_RTErrConvertToErrno
U VBoxGuest_RTLogLoggerEx
U VBoxGuest_RTLogRelGetDefaultInstanceEx
U VBoxGuest_RTMemTmpAllocTag
U VBoxGuest_RTMemTmpFree
U VBoxGuest_RTSemFastMutexCreate
U VBoxGuest_RTSemFastMutexDestroy
U VBoxGuest_RTSemFastMutexRelease
U VBoxGuest_RTSemFastMutexRequest
U VBoxGuest_RTStrCopy
[root@localhost ~]# nm /usr/lib/modules/5.3.0-1.fc31.x86_64/misc/vboxguest.ko|grep VBoxGuest_RTAssertMsg1Weak
00000000000014b0 r __kstrtab_VBoxGuest_RTAssertMsg1Weak
0000000000000020 r __ksymtab_VBoxGuest_RTAssertMsg1Weak
0000000000013840 T VBoxGuest_RTAssertMsg1Weak
[root@localhost ~]# nm /usr/lib/modules/5.3.0-1.fc31.x86_64/misc/vboxguest.ko|grep VBoxGuest_RTMemTmpFree
0000000000000107 r __kstrtab_VBoxGuest_RTMemTmpFree
00000000000002d8 r __ksymtab_VBoxGuest_RTMemTmpFree
0000000000007350 T VBoxGuest_RTMemTmpFree
comment:12 by , 5 years ago
| Resolution: | → worksforme |
|---|---|
| Status: | accepted → closed |
Duplicate of #18911.
You shouldn't be opening a new ticket for something that has already a ticket assigned, just comment on the existing ticket, even if it's marked as [Fixed]...