Gentoo Forums
Gentoo Forums
Gentoo Forums
Quick Search: in
[SOLVED]guest additions fail against kernel 4.18
View unanswered posts
View posts from last 24 hours

 
Reply to topic    Gentoo Forums Forum Index Portage & Programming
View previous topic :: View next topic  
Author Message
pourpier
Tux's lil' helper
Tux's lil' helper


Joined: 27 Sep 2017
Posts: 105

PostPosted: Tue Aug 14, 2018 5:17 pm    Post subject: [SOLVED]guest additions fail against kernel 4.18 Reply with quote

Hello!
I've just compiled the kernel 4.18 without any issue. I did emerge @module-rebuild and I got the following error messages:
https://paste.pound-python.org/show/tyFyJYWhM1pBf03msfLa/
Presumably the version of the kernel is not supported by the 5.2.16 version of VirtualBox.
Best regards,
pourpier


Last edited by pourpier on Tue Aug 14, 2018 8:18 pm; edited 1 time in total
Back to top
View user's profile Send private message
fedeliallalinea
Bodhisattva
Bodhisattva


Joined: 08 Mar 2003
Posts: 20122
Location: here

PostPosted: Tue Aug 14, 2018 5:36 pm    Post subject: Reply with quote

Sorry for the question, bu why you continue to update kernel to latest available when you know that you're in trouble with virtualbox?
Anyway in virtualbox bug tracker there isn't patch for solve problem
_________________
Questions are guaranteed in life; Answers aren't.
Back to top
View user's profile Send private message
pourpier
Tux's lil' helper
Tux's lil' helper


Joined: 27 Sep 2017
Posts: 105

PostPosted: Tue Aug 14, 2018 5:45 pm    Post subject: Reply with quote

fedeliallalinea wrote:
Sorry for the question, bu why you continue to update kernel to latest available when you know that you're in trouble with virtualbox?
Anyway in virtualbox bug tracker there isn't patch for solve problem


I like to test the latest kernel and perhaps thanks to the fact that I do it really quickly I can relate the bug more rapidly to other users would might be in the same situation.
I have to mention that I always keep the previous kernel so I can always boot in a kernel where the guest additions are fully operational.
I know also that you are quick on the trigger to help me and I do really appreciate this.
Maybe the 5.2.18 version will solve the issue or someone from Arch, Siduction or Tumbleweed will find a patch as they are always the first to propose the latest kernel and the latest guest additions.
Best regards,
pourpier
Back to top
View user's profile Send private message
fedeliallalinea
Bodhisattva
Bodhisattva


Joined: 08 Mar 2003
Posts: 20122
Location: here

PostPosted: Tue Aug 14, 2018 6:00 pm    Post subject: Reply with quote

pourpier wrote:
I like to test the latest kernel and perhaps thanks to the fact that I do it really quickly I can relate the bug more rapidly to other users would might be in the same situation.
I have to mention that I always keep the previous kernel so I can always boot in a kernel where the guest additions are fully operational.

Ok now for me is clear. However was a question without any criticism :D
_________________
Questions are guaranteed in life; Answers aren't.
Back to top
View user's profile Send private message
pourpier
Tux's lil' helper
Tux's lil' helper


Joined: 27 Sep 2017
Posts: 105

PostPosted: Tue Aug 14, 2018 6:06 pm    Post subject: Reply with quote

fedeliallalinea wrote:
pourpier wrote:
I like to test the latest kernel and perhaps thanks to the fact that I do it really quickly I can relate the bug more rapidly to other users would might be in the same situation.
I have to mention that I always keep the previous kernel so I can always boot in a kernel where the guest additions are fully operational.

Ok now for me is clear. However was a question without any criticism :D


I didn't feel any criticism in your question. You've helped me so many times! :D
Cheers
Back to top
View user's profile Send private message
Cuong Nguyen
Tux's lil' helper
Tux's lil' helper


Joined: 18 Jan 2018
Posts: 106

PostPosted: Tue Aug 14, 2018 7:47 pm    Post subject: Reply with quote

I've applied manual patch as follows and virtualbox-guest-additions successfully compiled. Nevertheless, I haven't tested it in run time.

How to patch:
Code:
ebuild /usr/portage/app-emulation/virtualbox-guest-additions/virtualbox-guest-additions-5.2.16.ebuild clean configure

change to /var/tmp/portage/app-emulation/virtualbox-guest-additions-5.2.16/work
Code:
patch -p1 < fix-timespec.patch

Code:
ebuild /usr/portage/app-emulation/virtualbox-guest-additions/virtualbox-guest-additions-5.2.16.ebuild compile


fix-timespec.patch file:
Code:

diff -Naru 1/vboxsf/utils.c 2/vboxsf/utils.c
--- 1/vboxsf/utils.c    2018-08-13 21:58:52.000000000 +0700
+++ 2/vboxsf/utils.c    2018-08-13 22:06:59.623300208 +0700
@@ -50,7 +50,11 @@
     RTTimeSpecSetNano(ts, t);
 }
 #else /* >= 2.6.0 */
+#if (LINUX_VERSION_CODE < KERNEL_VERSION(4, 18, 0))
 static void sf_ftime_from_timespec(struct timespec *tv, RTTIMESPEC *ts)
+#else
+static void sf_ftime_from_timespec(struct timespec64 *tv, RTTIMESPEC *ts)
+#endif //(LINUX_VERSION_CODE < KERNEL_VERSION(4, 18, 0))
 {
     int64_t t = RTTimeSpecGetNano(ts);
     int64_t nsec;
@@ -60,7 +64,11 @@
     tv->tv_nsec = nsec;
 }

+#if (LINUX_VERSION_CODE < KERNEL_VERSION(4, 18, 0))
 static void sf_timespec_from_ftime(RTTIMESPEC *ts, struct timespec *tv)
+#else
+static void sf_timespec_from_ftime(RTTIMESPEC *ts, struct timespec64 *tv)
+#endif //(LINUX_VERSION_CODE < KERNEL_VERSION(4, 18, 0))
 {
     int64_t t = (int64_t)tv->tv_nsec + (int64_t)tv->tv_sec * 1000000000;
     RTTimeSpecSetNano(ts, t);
Back to top
View user's profile Send private message
pourpier
Tux's lil' helper
Tux's lil' helper


Joined: 27 Sep 2017
Posts: 105

PostPosted: Tue Aug 14, 2018 8:18 pm    Post subject: Reply with quote

Cuong Nguyen wrote:
I've applied manual patch as follows and virtualbox-guest-additions successfully compiled. Nevertheless, I haven't tested it in run time.

How to patch:
Code:
ebuild /usr/portage/app-emulation/virtualbox-guest-additions/virtualbox-guest-additions-5.2.16.ebuild clean configure

change to /var/tmp/portage/app-emulation/virtualbox-guest-additions-5.2.16/work
Code:
patch -p1 < fix-timespec.patch

Code:
ebuild /usr/portage/app-emulation/virtualbox-guest-additions/virtualbox-guest-additions-5.2.16.ebuild compile


fix-timespec.patch file:
Code:

diff -Naru 1/vboxsf/utils.c 2/vboxsf/utils.c
--- 1/vboxsf/utils.c    2018-08-13 21:58:52.000000000 +0700
+++ 2/vboxsf/utils.c    2018-08-13 22:06:59.623300208 +0700
@@ -50,7 +50,11 @@
     RTTimeSpecSetNano(ts, t);
 }
 #else /* >= 2.6.0 */
+#if (LINUX_VERSION_CODE < KERNEL_VERSION(4, 18, 0))
 static void sf_ftime_from_timespec(struct timespec *tv, RTTIMESPEC *ts)
+#else
+static void sf_ftime_from_timespec(struct timespec64 *tv, RTTIMESPEC *ts)
+#endif //(LINUX_VERSION_CODE < KERNEL_VERSION(4, 18, 0))
 {
     int64_t t = RTTimeSpecGetNano(ts);
     int64_t nsec;
@@ -60,7 +64,11 @@
     tv->tv_nsec = nsec;
 }

+#if (LINUX_VERSION_CODE < KERNEL_VERSION(4, 18, 0))
 static void sf_timespec_from_ftime(RTTIMESPEC *ts, struct timespec *tv)
+#else
+static void sf_timespec_from_ftime(RTTIMESPEC *ts, struct timespec64 *tv)
+#endif //(LINUX_VERSION_CODE < KERNEL_VERSION(4, 18, 0))
 {
     int64_t t = (int64_t)tv->tv_nsec + (int64_t)tv->tv_sec * 1000000000;
     RTTimeSpecSetNano(ts, t);


Hello Cuong Nguyen!
I tried your patch and it works fine!
Thanks a lot.
Cheers,
pourpier
Back to top
View user's profile Send private message
cdstealer
Guru
Guru


Joined: 30 Oct 2005
Posts: 422
Location: Leeds

PostPosted: Sat Aug 25, 2018 9:21 am    Post subject: Reply with quote

Hi, This has now been fixed in kernel 4.18.5 :)
_________________
# touch it
touch: cannot touch `it': Permission denied
Back to top
View user's profile Send private message
pourpier
Tux's lil' helper
Tux's lil' helper


Joined: 27 Sep 2017
Posts: 105

PostPosted: Sat Aug 25, 2018 9:30 am    Post subject: Reply with quote

cdstealer wrote:
Hi, This has now been fixed in kernel 4.18.5 :)


Indeed!
Cheers
Back to top
View user's profile Send private message
if
n00b
n00b


Joined: 15 Jun 2010
Posts: 21

PostPosted: Sat Aug 25, 2018 12:55 pm    Post subject: Reply with quote

Do you guys now have fully operational Virtualbox on Gentoo-guest & Windows-host box?

I have had this problem since my last working kernel 4.15.8.
After that, I have trouble with 4.16.x, 4.17.x, 4.18.x to date including 4.18.5.
With the patch for 4.18.x (fix-timespec.patch), virtualbox-guest-additions builds fine, but when booting the kernel,
Code:
Aug 25 20:21:05 localhost kernel: [   17.157327] vboxsf: Unknown symbol VBoxGuest_RTMemTmpFree (err 0)
Aug 25 20:21:05 localhost kernel: [   17.157341] vboxsf: Unknown symbol VBoxGuestIDC (err 0)
Aug 25 20:21:05 localhost kernel: [   17.157356] vboxsf: Unknown symbol VBoxGuest_RTSemFastMutexRequest (err 0)
Aug 25 20:21:05 localhost kernel: [   17.157372] vboxsf: Unknown symbol VBoxGuest_RTSemFastMutexRelease (err 0)
Aug 25 20:21:05 localhost kernel: [   17.157384] vboxsf: Unknown symbol VBoxGuest_RTLogRelGetDefaultInstanceEx (err 0)
Aug 25 20:21:05 localhost kernel: [   17.157397] vboxsf: Unknown symbol VBoxGuest_RTStrCopy (err 0)
Aug 25 20:21:05 localhost kernel: [   17.157408] vboxsf: Unknown symbol VBoxGuest_RTErrConvertToErrno (err 0)
Aug 25 20:21:05 localhost kernel: [   17.157422] vboxsf: Unknown symbol VBoxGuest_RTSemFastMutexCreate (err 0)
Aug 25 20:21:05 localhost kernel: [   17.157434] vboxsf: Unknown symbol VBoxGuest_RTSemFastMutexDestroy (err 0)
Aug 25 20:21:05 localhost kernel: [   17.157453] vboxsf: Unknown symbol VBoxGuest_RTAssertShouldPanic (err 0)
Aug 25 20:21:05 localhost kernel: [   17.157466] vboxsf: Unknown symbol VBoxGuest_RTLogLoggerEx (err 0)
Aug 25 20:21:05 localhost kernel: [   17.157479] vboxsf: Unknown symbol VBoxGuest_RTMemTmpAllocTag (err 0)
Aug 25 20:21:05 localhost kernel: [   17.157494] vboxsf: Unknown symbol VBoxGuest_RTAssertMsg1Weak (err 0)
Aug 25 20:21:05 localhost kernel: [   17.157510] vboxsf: Unknown symbol VBoxGuest_RTAssertMsg2Weak (err 0)

vboxsf won't be loaded in my case.

Searching for "vboxsf: Unknown symbol VBoxGuest_RTMemTmpFree," I found this bug report from Redhat guys, and this fixed driver.
The fix seems to be similar to the one in fix-timespec.patch.

Any tip to make vboxsf loaded would be appreciated! :)
Back to top
View user's profile Send private message
cdstealer
Guru
Guru


Joined: 30 Oct 2005
Posts: 422
Location: Leeds

PostPosted: Sat Aug 25, 2018 1:23 pm    Post subject: Reply with quote

Hi,
I have again now ;) This always happens every few major releases or so.

What version of VB are you running?

Code:
Host
sys-kernel/gentoo-sources-4.18.5
app-emulation/virtualbox-5.2.18

Client
sys-kernel/gentoo-sources-4.18.5
app-emulation/virtualbox-guest-additions-5.2.18


My client is built on my Linux rig and then exported to my Windows laptop.
_________________
# touch it
touch: cannot touch `it': Permission denied
Back to top
View user's profile Send private message
pourpier
Tux's lil' helper
Tux's lil' helper


Joined: 27 Sep 2017
Posts: 105

PostPosted: Sat Aug 25, 2018 1:26 pm    Post subject: Reply with quote

if wrote:
Do you guys now have fully operational Virtualbox on Gentoo-guest & Windows-host box?

I have had this problem since my last working kernel 4.15.8.
After that, I have trouble with 4.16.x, 4.17.x, 4.18.x to date including 4.18.5.
With the patch for 4.18.x (fix-timespec.patch), virtualbox-guest-additions builds fine, but when booting the kernel,
Code:
Aug 25 20:21:05 localhost kernel: [   17.157327] vboxsf: Unknown symbol VBoxGuest_RTMemTmpFree (err 0)
Aug 25 20:21:05 localhost kernel: [   17.157341] vboxsf: Unknown symbol VBoxGuestIDC (err 0)
Aug 25 20:21:05 localhost kernel: [   17.157356] vboxsf: Unknown symbol VBoxGuest_RTSemFastMutexRequest (err 0)
Aug 25 20:21:05 localhost kernel: [   17.157372] vboxsf: Unknown symbol VBoxGuest_RTSemFastMutexRelease (err 0)
Aug 25 20:21:05 localhost kernel: [   17.157384] vboxsf: Unknown symbol VBoxGuest_RTLogRelGetDefaultInstanceEx (err 0)
Aug 25 20:21:05 localhost kernel: [   17.157397] vboxsf: Unknown symbol VBoxGuest_RTStrCopy (err 0)
Aug 25 20:21:05 localhost kernel: [   17.157408] vboxsf: Unknown symbol VBoxGuest_RTErrConvertToErrno (err 0)
Aug 25 20:21:05 localhost kernel: [   17.157422] vboxsf: Unknown symbol VBoxGuest_RTSemFastMutexCreate (err 0)
Aug 25 20:21:05 localhost kernel: [   17.157434] vboxsf: Unknown symbol VBoxGuest_RTSemFastMutexDestroy (err 0)
Aug 25 20:21:05 localhost kernel: [   17.157453] vboxsf: Unknown symbol VBoxGuest_RTAssertShouldPanic (err 0)
Aug 25 20:21:05 localhost kernel: [   17.157466] vboxsf: Unknown symbol VBoxGuest_RTLogLoggerEx (err 0)
Aug 25 20:21:05 localhost kernel: [   17.157479] vboxsf: Unknown symbol VBoxGuest_RTMemTmpAllocTag (err 0)
Aug 25 20:21:05 localhost kernel: [   17.157494] vboxsf: Unknown symbol VBoxGuest_RTAssertMsg1Weak (err 0)
Aug 25 20:21:05 localhost kernel: [   17.157510] vboxsf: Unknown symbol VBoxGuest_RTAssertMsg2Weak (err 0)

vboxsf won't be loaded in my case.

Searching for "vboxsf: Unknown symbol VBoxGuest_RTMemTmpFree," I found this bug report from Redhat guys, and this fixed driver.
The fix seems to be similar to the one in fix-timespec.patch.

Any tip to make vboxsf loaded would be appreciated! :)


Which version of VirtualBox and of the guest additions do you have?
Did you emerge the xf86-video-vboxvideo as this driver is needed since a while now?
Cheers,
pourpier
Back to top
View user's profile Send private message
if
n00b
n00b


Joined: 15 Jun 2010
Posts: 21

PostPosted: Sun Aug 26, 2018 2:46 am    Post subject: Reply with quote

Hi all!

My Virtualbox is running on Windows 10, hosting Gentoo box as guest.
I try to run Gentoo (kernel 4.18.5 with virtualbox-guest-additions 5.2.18 ).
Latest working version is kernel 4.15.18 and virtualbox-guest-additions 5.2.10.
After that, updating kernel and virtualbox-guest-additions (even if emerge works fine) stops booting normally.

I checked the other thread and make kernel options regarding to virtualbox modules turned on.

Testing 5.2.14 (latest stable version) again. Here's a warning from virtualbox-guest-additions.
Code:
>>> Installing (1 of 1) app-emulation/virtualbox-guest-additions-5.2.14::gentoo
 * >>> SetUID: [chmod go-r] /sbin/mount.vboxsf ...                       [ ok ]
 * Removing app-emulation/virtualbox-guest-additions-5.2.18 from moduledb.
 * Updating module dependencies for 4.18.5-gentoo ...
depmod: WARNING: //lib/modules/4.18.5-gentoo/misc/vboxsf.ko needs unknown symbol VBoxGuest_RTMemTmpFree
depmod: WARNING: //lib/modules/4.18.5-gentoo/misc/vboxsf.ko needs unknown symbol VBoxGuestIDC
depmod: WARNING: //lib/modules/4.18.5-gentoo/misc/vboxsf.ko needs unknown symbol VBoxGuest_RTSemFastMutexRequest
depmod: WARNING: //lib/modules/4.18.5-gentoo/misc/vboxsf.ko needs unknown symbol VBoxGuest_RTSemFastMutexRelease
depmod: WARNING: //lib/modules/4.18.5-gentoo/misc/vboxsf.ko needs unknown symbol VBoxGuest_RTLogRelGetDefaultInstanceEx
depmod: WARNING: //lib/modules/4.18.5-gentoo/misc/vboxsf.ko needs unknown symbol VBoxGuest_RTStrCopy
depmod: WARNING: //lib/modules/4.18.5-gentoo/misc/vboxsf.ko needs unknown symbol VBoxGuest_RTErrConvertToErrno
depmod: WARNING: //lib/modules/4.18.5-gentoo/misc/vboxsf.ko needs unknown symbol VBoxGuest_RTSemFastMutexCreate
depmod: WARNING: //lib/modules/4.18.5-gentoo/misc/vboxsf.ko needs unknown symbol VBoxGuest_RTSemFastMutexDestroy
depmod: WARNING: //lib/modules/4.18.5-gentoo/misc/vboxsf.ko needs unknown symbol VBoxGuest_RTAssertShouldPanic
depmod: WARNING: //lib/modules/4.18.5-gentoo/misc/vboxsf.ko needs unknown symbol VBoxGuest_RTLogLoggerEx
depmod: WARNING: //lib/modules/4.18.5-gentoo/misc/vboxsf.ko needs unknown symbol VBoxGuest_RTMemTmpAllocTag
depmod: WARNING: //lib/modules/4.18.5-gentoo/misc/vboxsf.ko needs unknown symbol VBoxGuest_RTAssertMsg1Weak
depmod: WARNING: //lib/modules/4.18.5-gentoo/misc/vboxsf.ko needs unknown symbol VBoxGuest_RTAssertMsg2Weak                                              [ ok ]
 * Adding module to moduledb.
 *


Removing /lib/modules/4.18.5-gentoo and emerged 5.2.14 again, then got
Code:
/usr/lib/gcc/x86_64-pc-linux-gnu/8.2.0/../../../../x86_64-pc-linux-gnu/bin/ld: warning: creating a DT_TEXTREL in a shared object.
 * Preparing vboxguest module
make -j4 HOSTCC=x86_64-pc-linux-gnu-gcc CROSS_COMPILE=x86_64-pc-linux-gnu- 'LDFLAGS=-m elf_x86_64' KERN_DIR=/usr/src/linux KERNOUT=/usr/src/linux all
/tmp/portage/app-emulation/virtualbox-guest-additions-5.2.14/work/vboxguest/Makefile.include.header:99: *** The variable KERN_DIR must be a kernel build folder and end with /build without a trailing slash, or KERN_VER must be set.  Stop.
 * ERROR: app-emulation/virtualbox-guest-additions-5.2.14::gentoo failed (compile phase):
 *   emake failed
 *
 * If you need support, post the output of `emerge --info '=app-emulation/virtualbox-guest-additions-5.2.14::gentoo'`,
 * the complete build log and the output of `emerge -pqv '=app-emulation/virtualbox-guest-additions-5.2.14::gentoo'`.
 * The complete build log is located at '/tmp/portage/app-emulation/virtualbox-guest-additions-5.2.14/temp/build.log'.
 * The ebuild environment file is located at '/tmp/portage/app-emulation/virtualbox-guest-additions-5.2.14/temp/environment'.
 * Working directory: '/tmp/portage/app-emulation/virtualbox-guest-additions-5.2.14/work/vboxguest'
 * S: '/tmp/portage/app-emulation/virtualbox-guest-additions-5.2.14/work/VirtualBox-5.2.14'


Above error seems to be caused by removing whole module directory.
After building kernel and modules again and emerging virtualbox-guest-additions-5.2.16 got no error but again the same warning
Code:
>>> Installing (1 of 1) app-emulation/virtualbox-guest-additions-5.2.16::gentoo
 * >>> SetUID: [chmod go-r] /sbin/mount.vboxsf ...                       [ ok ]
 * Removing app-emulation/virtualbox-guest-additions-5.2.14 from moduledb.
 * Updating module dependencies for 4.18.5-gentoo ...
depmod: WARNING: //lib/modules/4.18.5-gentoo/misc/vboxsf.ko needs unknown symbol VBoxGuest_RTMemTmpFree
depmod: WARNING: //lib/modules/4.18.5-gentoo/misc/vboxsf.ko needs unknown symbol VBoxGuestIDC
depmod: WARNING: //lib/modules/4.18.5-gentoo/misc/vboxsf.ko needs unknown symbol VBoxGuest_RTSemFastMutexRequest
depmod: WARNING: //lib/modules/4.18.5-gentoo/misc/vboxsf.ko needs unknown symbol VBoxGuest_RTSemFastMutexRelease
depmod: WARNING: //lib/modules/4.18.5-gentoo/misc/vboxsf.ko needs unknown symbol VBoxGuest_RTLogRelGetDefaultInstanceEx
depmod: WARNING: //lib/modules/4.18.5-gentoo/misc/vboxsf.ko needs unknown symbol VBoxGuest_RTStrCopy
depmod: WARNING: //lib/modules/4.18.5-gentoo/misc/vboxsf.ko needs unknown symbol VBoxGuest_RTErrConvertToErrno
depmod: WARNING: //lib/modules/4.18.5-gentoo/misc/vboxsf.ko needs unknown symbol VBoxGuest_RTSemFastMutexCreate
depmod: WARNING: //lib/modules/4.18.5-gentoo/misc/vboxsf.ko needs unknown symbol VBoxGuest_RTSemFastMutexDestroy
depmod: WARNING: //lib/modules/4.18.5-gentoo/misc/vboxsf.ko needs unknown symbol VBoxGuest_RTAssertShouldPanic
depmod: WARNING: //lib/modules/4.18.5-gentoo/misc/vboxsf.ko needs unknown symbol VBoxGuest_RTLogLoggerEx
depmod: WARNING: //lib/modules/4.18.5-gentoo/misc/vboxsf.ko needs unknown symbol VBoxGuest_RTMemTmpAllocTag
depmod: WARNING: //lib/modules/4.18.5-gentoo/misc/vboxsf.ko needs unknown symbol VBoxGuest_RTAssertMsg1Weak
depmod: WARNING: //lib/modules/4.18.5-gentoo/misc/vboxsf.ko needs unknown symbol VBoxGuest_RTAssertMsg2Weak                                              [ ok ]
 * Adding module to moduledb.


Last edited by if on Sun Aug 26, 2018 5:35 am; edited 1 time in total
Back to top
View user's profile Send private message
cdstealer
Guru
Guru


Joined: 30 Oct 2005
Posts: 422
Location: Leeds

PostPosted: Sun Aug 26, 2018 5:09 am    Post subject: Reply with quote

Hi, I just realised I had the same issue with xtable-addons. Could you check the following kernel option?
Code:
[*] Enable loadable module support  --->
    [ ]   Trim unused exported kernel symbols


If Trim is enabled, disable it and recompile.

Hope it helps.
CD
_________________
# touch it
touch: cannot touch `it': Permission denied
Back to top
View user's profile Send private message
if
n00b
n00b


Joined: 15 Jun 2010
Posts: 21

PostPosted: Sun Aug 26, 2018 6:22 am    Post subject: Reply with quote

I check my kernel setting of 4.18.5. It is not set (desabled) like in 4.15.8.
In case I am mistaken, I tested by making the option set (enabled) and the result is

Code:
>>> Emerging (1 of 1) app-emulation/virtualbox-modules-5.2.16::gentoo
 * vbox-kernel-module-src-5.2.16.tar.xz BLAKE2B SHA512 size ;-) ...      [ ok ]
 * Determining the location of the kernel source code
 * Found kernel source directory:
 *     /usr/src/linux
 * Found kernel object directory:
 *     /lib/modules/4.18.5-gentoo/build
 * Found sources for kernel version:
 *     4.18.5-gentoo
 * Checking for suitable kernel configuration options...
 *   CONFIG_TRIM_UNUSED_KSYMS:    should not be set. But it is.
 * Please check to make sure these options are set correctly.
 * Failure to do so may cause unexpected problems.
 * Once you have satisfied these options, please try merging
 * this package again.
 * ERROR: app-emulation/virtualbox-modules-5.2.16::gentoo failed (setup phase):
 *   Incorrect kernel configuration options
 *
 * Call stack:
 *                          ebuild.sh, line 124:  Called pkg_setup
 *   virtualbox-modules-5.2.16.ebuild, line  31:  Called linux-mod_pkg_setup
 *                   linux-mod.eclass, line 586:  Called linux-info_pkg_setup
 *                  linux-info.eclass, line 965:  Called check_extra_config
 *                  linux-info.eclass, line 857:  Called die
 * The specific snippet of code:
 *         die "Incorrect kernel configuration options"
 *
 * If you need support, post the output of `emerge --info '=app-emulation/virtualbox-modules-5.2.16::gentoo'`,
 * the complete build log and the output of `emerge -pqv '=app-emulation/virtualbox-modules-5.2.16::gentoo'`.
 * The complete build log is located at '/tmp/portage/app-emulation/virtualbox-modules-5.2.16/temp/build.log'.
 * The ebuild environment file is located at '/tmp/portage/app-emulation/virtualbox-modules-5.2.16/temp/die.env'.
 * Working directory: '/tmp/portage/app-emulation/virtualbox-modules-5.2.16/homedir'
 * S: '/tmp/portage/app-emulation/virtualbox-modules-5.2.16/work'

>>> Failed to emerge app-emulation/virtualbox-modules-5.2.16, Log file:


so, it must be turned off, I see.

After turned off and building kernel-4.18.5, virtualbox-modules-5.2.16, and virtualbox-guest-addtions-5.2.16 makes no error but the same warning in virtualbox-guest-addtions
Code:
>>> Installing (1 of 1) app-emulation/virtualbox-guest-additions-5.2.16::gentoo
 * >>> SetUID: [chmod go-r] /sbin/mount.vboxsf ...                       [ ok ]
 * Removing app-emulation/virtualbox-guest-additions-5.2.16 from moduledb.
 * Updating module dependencies for 4.18.5-gentoo ...
depmod: WARNING: //lib/modules/4.18.5-gentoo/misc/vboxsf.ko needs unknown symbol VBoxGuest_RTMemTmpFree
depmod: WARNING: //lib/modules/4.18.5-gentoo/misc/vboxsf.ko needs unknown symbol VBoxGuestIDC
depmod: WARNING: //lib/modules/4.18.5-gentoo/misc/vboxsf.ko needs unknown symbol VBoxGuest_RTSemFastMutexRequest
depmod: WARNING: //lib/modules/4.18.5-gentoo/misc/vboxsf.ko needs unknown symbol VBoxGuest_RTSemFastMutexRelease
depmod: WARNING: //lib/modules/4.18.5-gentoo/misc/vboxsf.ko needs unknown symbol VBoxGuest_RTLogRelGetDefaultInstanceEx
depmod: WARNING: //lib/modules/4.18.5-gentoo/misc/vboxsf.ko needs unknown symbol VBoxGuest_RTStrCopy
depmod: WARNING: //lib/modules/4.18.5-gentoo/misc/vboxsf.ko needs unknown symbol VBoxGuest_RTErrConvertToErrno
depmod: WARNING: //lib/modules/4.18.5-gentoo/misc/vboxsf.ko needs unknown symbol VBoxGuest_RTSemFastMutexCreate
depmod: WARNING: //lib/modules/4.18.5-gentoo/misc/vboxsf.ko needs unknown symbol VBoxGuest_RTSemFastMutexDestroy
depmod: WARNING: //lib/modules/4.18.5-gentoo/misc/vboxsf.ko needs unknown symbol VBoxGuest_RTAssertShouldPanic
depmod: WARNING: //lib/modules/4.18.5-gentoo/misc/vboxsf.ko needs unknown symbol VBoxGuest_RTLogLoggerEx
depmod: WARNING: //lib/modules/4.18.5-gentoo/misc/vboxsf.ko needs unknown symbol VBoxGuest_RTMemTmpAllocTag
depmod: WARNING: //lib/modules/4.18.5-gentoo/misc/vboxsf.ko needs unknown symbol VBoxGuest_RTAssertMsg1Weak
depmod: WARNING: //lib/modules/4.18.5-gentoo/misc/vboxsf.ko needs unknown symbol VBoxGuest_RTAssertMsg2Weak                                              [ ok ]
 * Adding module to moduledb.


cdstealer wrote:
Hi, I just realised I had the same issue with xtable-addons. Could you check the following kernel option?
Code:
[*] Enable loadable module support  --->
    [ ]   Trim unused exported kernel symbols


If Trim is enabled, disable it and recompile.

Hope it helps.
CD


Last edited by if on Sun Aug 26, 2018 7:05 am; edited 1 time in total
Back to top
View user's profile Send private message
cdstealer
Guru
Guru


Joined: 30 Oct 2005
Posts: 422
Location: Leeds

PostPosted: Sun Aug 26, 2018 6:40 am    Post subject: Reply with quote

Hmmm.. Could you try upgrading to version 5.2.18 of guest additions?
_________________
# touch it
touch: cannot touch `it': Permission denied
Back to top
View user's profile Send private message
if
n00b
n00b


Joined: 15 Jun 2010
Posts: 21

PostPosted: Sun Aug 26, 2018 7:43 am    Post subject: Reply with quote

After emerging virtualbox-modules-5.2.18 and virtualbox-guest-additions-5.2.18, there still is the same warning.

Code:
>>> Installing (1 of 1) app-emulation/virtualbox-guest-additions-5.2.18::gentoo
 * >>> SetUID: [chmod go-r] /sbin/mount.vboxsf ...                       [ ok ]
 * Removing app-emulation/virtualbox-guest-additions-5.2.18 from moduledb.
 * Updating module dependencies for 4.18.5-gentoo ...
depmod: WARNING: //lib/modules/4.18.5-gentoo/misc/vboxsf.ko needs unknown symbol VBoxGuest_RTMemTmpFree
depmod: WARNING: //lib/modules/4.18.5-gentoo/misc/vboxsf.ko needs unknown symbol VBoxGuestIDC
depmod: WARNING: //lib/modules/4.18.5-gentoo/misc/vboxsf.ko needs unknown symbol VBoxGuest_RTSemFastMutexRequest
depmod: WARNING: //lib/modules/4.18.5-gentoo/misc/vboxsf.ko needs unknown symbol VBoxGuest_RTSemFastMutexRelease
depmod: WARNING: //lib/modules/4.18.5-gentoo/misc/vboxsf.ko needs unknown symbol VBoxGuest_RTLogRelGetDefaultInstanceEx
depmod: WARNING: //lib/modules/4.18.5-gentoo/misc/vboxsf.ko needs unknown symbol VBoxGuest_RTStrCopy
depmod: WARNING: //lib/modules/4.18.5-gentoo/misc/vboxsf.ko needs unknown symbol VBoxGuest_RTErrConvertToErrno
depmod: WARNING: //lib/modules/4.18.5-gentoo/misc/vboxsf.ko needs unknown symbol VBoxGuest_RTSemFastMutexCreate
depmod: WARNING: //lib/modules/4.18.5-gentoo/misc/vboxsf.ko needs unknown symbol VBoxGuest_RTSemFastMutexDestroy
depmod: WARNING: //lib/modules/4.18.5-gentoo/misc/vboxsf.ko needs unknown symbol VBoxGuest_RTAssertShouldPanic
depmod: WARNING: //lib/modules/4.18.5-gentoo/misc/vboxsf.ko needs unknown symbol VBoxGuest_RTLogLoggerEx
depmod: WARNING: //lib/modules/4.18.5-gentoo/misc/vboxsf.ko needs unknown symbol VBoxGuest_RTMemTmpAllocTag
depmod: WARNING: //lib/modules/4.18.5-gentoo/misc/vboxsf.ko needs unknown symbol VBoxGuest_RTAssertMsg1Weak
depmod: WARNING: //lib/modules/4.18.5-gentoo/misc/vboxsf.ko needs unknown symbol VBoxGuest_RTAssertMsg2Weak                                              [ ok ]
 * Adding module to moduledb.


cdstealer wrote:
Hmmm.. Could you try upgrading to version 5.2.18 of guest additions?
Back to top
View user's profile Send private message
if
n00b
n00b


Joined: 15 Jun 2010
Posts: 21

PostPosted: Sun Aug 26, 2018 9:12 am    Post subject: Reply with quote

So, I found this page and it says
Quote:
* You cannot have built another kernel in your kernel source than the one you are running on, or you're very likely to get version magic errors. Cure is a 'make distclean' in the kernel source. That wipes the .config, so be sure to have it backed up. Then remake your running kernel config to get a correct Module.symvers.
in business_kid's post on page 2.

So far, I have updated all of these under kernel-4.15.18, which is latest working kernel inside Virtualbox to me.
After reading that the kernel version is the problem, I tried to boot into kernel-4.18.5.
Then I emerged once again kernel-4.18.5, virtualbox-guest-addtions-5.2.18, and virtualbox-modules-5.2.18 in this order after clearing /lib/modules/4.18.5/misc.

The result is the same. The next boot stopped as explained before.

To make sure, I did make clean in the kernel source and did the same three emerges above. The same result.

Quote:
* Lastly, if you're left wondering what kernel config option gives your particular missing symbol, a good way to find out is to search the kernel source with grep -r for your missing symbol. You want the file that EXPORTS it, which should be a .c file. Then, grep that .c file for the term CONFIG. That will list the kernel config options it references. You can usually run it down that way.


grep -r RTMemTmpFree or grep -r RTAssertMsg1Weak do not find a thing in the kernel source.

So, what causes the symbol errors and how do I get rid of them? :?
Back to top
View user's profile Send private message
if
n00b
n00b


Joined: 15 Jun 2010
Posts: 21

PostPosted: Sun Aug 26, 2018 4:46 pm    Post subject: Reply with quote

Regarding to the missing symbols, I looked for them in the vbox source codes.
Here is what I found out.

Besides VBoxGuestIDC, which is exactly defined in the codes, all other symbols miss VBoxGuest_ prefix in the codes.
So, if you look for VBoxGuest_RTMemTmpFree, then only RTMemTmpFree can be found, not VBoxGuest_RTMemTmpFree as a whole.

Code:

VBoxGuest_RTMemTmpFree: include/iprt/mangling.h include/iprt/mem.h VBoxGuestR0LibSharedFolders.c
VBoxGuestIDC: include/VBox/VBoxGuest.h VBoxGuestR0LibIdc-unix.c
VBoxGuest_RTSemFastMutexRequest: include/iprt/semaphore.h include/iprt/mangling.h VBoxGuestR0LibHGCM.c
VBoxGuest_RTSemFastMutexRelease: include/iprt/semaphore.h include/iprt/mangling.h VBoxGuestR0LibHGCM.c
VBoxGuest_RTLogRelGetDefaultInstanceEx: include/iprt/log.h include/iprt/mangling.h
VBoxGuest_RTStrCopy: include/iprt/string.h include/iprt/mangling.h VBoxGuestR0LibHGCM.c
VBoxGuest_RTErrConvertToErrno: dirops.c include/iprt/err.h include/iprt/mangling.h regops.c utils.c
VBoxGuest_RTSemFastMutexCreate: include/iprt/semaphore.h include/iprt/mangling.h VBoxGuestR0LibHGCM.c
VBoxGuest_RTSemFastMutexDestroy: include/iprt/semaphore.h include/iprt/mangling.h VBoxGuestR0LibHGCM.c
VBoxGuest_RTAssertShouldPanic: include/iprt/assert.h include/iprt/mangling.h
VBoxGuest_RTLogLoggerEx: include/iprt/log.h include/iprt/mangling.h
VBoxGuest_RTMemTmpAllocTag: include/iprt/mangling.h include/iprt/mem.h
VBoxGuest_RTAssertMsg1Weak: include/iprt/assert.h include/iprt/mangling.h
VBoxGuest_RTAssertMsg2Weak:  include/iprt/assert.h include/iprt/mangling.h


As you see, all the symbols except VBoxGuestIDC are defined in include/iprt/mangling.h, in which all the symbols are defined as one of RT_MANGLER functions.

Here is the comment in include/iprt/mangling.h to understand what this header file is about.
Code:
 * IPRT - Symbol Mangling.
 *
 * This header is used to mangle public IPRT symbol to make it possible to have
 * several IPRT version loaded into one symbol space at the same time.  To
 * enable symbol mangling you create a header which the compiler includes for
 * every compilation unit (check out the -include option of gcc).  Your header
 * will define RT_MANGLER(name) and then include this header to set up the
 * actual mappings.


So, why is VBoxGuest_ prefix attached and why is VBoxGuest_RT_MANGLER not called?
Back to top
View user's profile Send private message
wfdawson
n00b
n00b


Joined: 05 Aug 2010
Posts: 13

PostPosted: Sun Nov 11, 2018 7:44 pm    Post subject: Reply with quote

I am also seeing this error. In my case, with (currently) kernel at 4.19.1 and virtualbox-guest-additions at 5.2.22.
Anyone make it work, yet?

Code:
[   15.039919] vboxsf: loading out-of-tree module taints kernel.
[   15.039978] vboxsf: Unknown symbol VBoxGuest_RTMemTmpFree (err -2)
[   15.039983] vboxsf: Unknown symbol VBoxGuestIDC (err -2)
[   15.039992] vboxsf: Unknown symbol VBoxGuest_RTSemFastMutexRequest (err -2)
[   15.040001] vboxsf: Unknown symbol VBoxGuest_RTSemFastMutexRelease (err -2)
[   15.040006] vboxsf: Unknown symbol VBoxGuest_RTLogRelGetDefaultInstanceEx (err -2)
[   15.040011] vboxsf: Unknown symbol VBoxGuest_RTStrCopy (err -2)
[   15.040017] vboxsf: Unknown symbol VBoxGuest_RTErrConvertToErrno (err -2)
[   15.040030] vboxsf: Unknown symbol VBoxGuest_RTSemFastMutexCreate (err -2)
[   15.040034] vboxsf: Unknown symbol VBoxGuest_RTSemFastMutexDestroy (err -2)
[   15.040133] vboxsf: Unknown symbol VBoxGuest_RTAssertShouldPanic (err -2)
[   15.040157] vboxsf: Unknown symbol VBoxGuest_RTLogLoggerEx (err -2)
[   15.040165] vboxsf: Unknown symbol VBoxGuest_RTMemTmpAllocTag (err -2)
[   15.040174] vboxsf: Unknown symbol VBoxGuest_RTAssertMsg1Weak (err -2)
[   15.040184] vboxsf: Unknown symbol VBoxGuest_RTAssertMsg2Weak (err -2)
[   89.150075] vboxsf: Unknown symbol VBoxGuest_RTMemTmpFree (err -2)
[   89.150082] vboxsf: Unknown symbol VBoxGuestIDC (err -2)
[   89.150091] vboxsf: Unknown symbol VBoxGuest_RTSemFastMutexRequest (err -2)
[   89.150101] vboxsf: Unknown symbol VBoxGuest_RTSemFastMutexRelease (err -2)
[   89.150108] vboxsf: Unknown symbol VBoxGuest_RTLogRelGetDefaultInstanceEx (err -2)
[   89.150113] vboxsf: Unknown symbol VBoxGuest_RTStrCopy (err -2)
[   89.150120] vboxsf: Unknown symbol VBoxGuest_RTErrConvertToErrno (err -2)
[   89.150132] vboxsf: Unknown symbol VBoxGuest_RTSemFastMutexCreate (err -2)
[   89.150138] vboxsf: Unknown symbol VBoxGuest_RTSemFastMutexDestroy (err -2)
[   89.150155] vboxsf: Unknown symbol VBoxGuest_RTAssertShouldPanic (err -2)
[   89.150164] vboxsf: Unknown symbol VBoxGuest_RTLogLoggerEx (err -2)
[   89.150172] vboxsf: Unknown symbol VBoxGuest_RTMemTmpAllocTag (err -2)
[   89.150181] vboxsf: Unknown symbol VBoxGuest_RTAssertMsg1Weak (err -2)
[   89.150192] vboxsf: Unknown symbol VBoxGuest_RTAssertMsg2Weak (err -2)
[44799.123671] vboxsf: Unknown symbol VBoxGuest_RTMemTmpFree (err -2)
[44799.123676] vboxsf: Unknown symbol VBoxGuestIDC (err -2)
[44799.123685] vboxsf: Unknown symbol VBoxGuest_RTSemFastMutexRequest (err -2)
[44799.123695] vboxsf: Unknown symbol VBoxGuest_RTSemFastMutexRelease (err -2)
[44799.123701] vboxsf: Unknown symbol VBoxGuest_RTLogRelGetDefaultInstanceEx (err -2)
[44799.123706] vboxsf: Unknown symbol VBoxGuest_RTStrCopy (err -2)
[44799.123712] vboxsf: Unknown symbol VBoxGuest_RTErrConvertToErrno (err -2)
[44799.123725] vboxsf: Unknown symbol VBoxGuest_RTSemFastMutexCreate (err -2)
[44799.123730] vboxsf: Unknown symbol VBoxGuest_RTSemFastMutexDestroy (err -2)
[44799.123746] vboxsf: Unknown symbol VBoxGuest_RTAssertShouldPanic (err -2)
[44799.123754] vboxsf: Unknown symbol VBoxGuest_RTLogLoggerEx (err -2)
[44799.123762] vboxsf: Unknown symbol VBoxGuest_RTMemTmpAllocTag (err -2)
[44799.123771] vboxsf: Unknown symbol VBoxGuest_RTAssertMsg1Weak (err -2)
[44799.123781] vboxsf: Unknown symbol VBoxGuest_RTAssertMsg2Weak (err -2)


[Moderator edit: added [code] tags to preserve output layout. -Hu]
Back to top
View user's profile Send private message
pourpier
Tux's lil' helper
Tux's lil' helper


Joined: 27 Sep 2017
Posts: 105

PostPosted: Sun Nov 11, 2018 8:07 pm    Post subject: Reply with quote

wfdawson wrote:
I am also seeing this error. In my case, with (currently) kernel at 4.19.1 and virtualbox-guest-additions at 5.2.22.
Anyone make it work, yet?

[ 15.039919] vboxsf: loading out-of-tree module taints kernel.
[ 15.039978] vboxsf: Unknown symbol VBoxGuest_RTMemTmpFree (err -2)
[ 15.039983] vboxsf: Unknown symbol VBoxGuestIDC (err -2)
[ 15.039992] vboxsf: Unknown symbol VBoxGuest_RTSemFastMutexRequest (err -2)
[ 15.040001] vboxsf: Unknown symbol VBoxGuest_RTSemFastMutexRelease (err -2)
[ 15.040006] vboxsf: Unknown symbol VBoxGuest_RTLogRelGetDefaultInstanceEx (err -2)
[ 15.040011] vboxsf: Unknown symbol VBoxGuest_RTStrCopy (err -2)
[ 15.040017] vboxsf: Unknown symbol VBoxGuest_RTErrConvertToErrno (err -2)
[ 15.040030] vboxsf: Unknown symbol VBoxGuest_RTSemFastMutexCreate (err -2)
[ 15.040034] vboxsf: Unknown symbol VBoxGuest_RTSemFastMutexDestroy (err -2)
[ 15.040133] vboxsf: Unknown symbol VBoxGuest_RTAssertShouldPanic (err -2)
[ 15.040157] vboxsf: Unknown symbol VBoxGuest_RTLogLoggerEx (err -2)
[ 15.040165] vboxsf: Unknown symbol VBoxGuest_RTMemTmpAllocTag (err -2)
[ 15.040174] vboxsf: Unknown symbol VBoxGuest_RTAssertMsg1Weak (err -2)
[ 15.040184] vboxsf: Unknown symbol VBoxGuest_RTAssertMsg2Weak (err -2)
[ 89.150075] vboxsf: Unknown symbol VBoxGuest_RTMemTmpFree (err -2)
[ 89.150082] vboxsf: Unknown symbol VBoxGuestIDC (err -2)
[ 89.150091] vboxsf: Unknown symbol VBoxGuest_RTSemFastMutexRequest (err -2)
[ 89.150101] vboxsf: Unknown symbol VBoxGuest_RTSemFastMutexRelease (err -2)
[ 89.150108] vboxsf: Unknown symbol VBoxGuest_RTLogRelGetDefaultInstanceEx (err -2)
[ 89.150113] vboxsf: Unknown symbol VBoxGuest_RTStrCopy (err -2)
[ 89.150120] vboxsf: Unknown symbol VBoxGuest_RTErrConvertToErrno (err -2)
[ 89.150132] vboxsf: Unknown symbol VBoxGuest_RTSemFastMutexCreate (err -2)
[ 89.150138] vboxsf: Unknown symbol VBoxGuest_RTSemFastMutexDestroy (err -2)
[ 89.150155] vboxsf: Unknown symbol VBoxGuest_RTAssertShouldPanic (err -2)
[ 89.150164] vboxsf: Unknown symbol VBoxGuest_RTLogLoggerEx (err -2)
[ 89.150172] vboxsf: Unknown symbol VBoxGuest_RTMemTmpAllocTag (err -2)
[ 89.150181] vboxsf: Unknown symbol VBoxGuest_RTAssertMsg1Weak (err -2)
[ 89.150192] vboxsf: Unknown symbol VBoxGuest_RTAssertMsg2Weak (err -2)
[44799.123671] vboxsf: Unknown symbol VBoxGuest_RTMemTmpFree (err -2)
[44799.123676] vboxsf: Unknown symbol VBoxGuestIDC (err -2)
[44799.123685] vboxsf: Unknown symbol VBoxGuest_RTSemFastMutexRequest (err -2)
[44799.123695] vboxsf: Unknown symbol VBoxGuest_RTSemFastMutexRelease (err -2)
[44799.123701] vboxsf: Unknown symbol VBoxGuest_RTLogRelGetDefaultInstanceEx (err -2)
[44799.123706] vboxsf: Unknown symbol VBoxGuest_RTStrCopy (err -2)
[44799.123712] vboxsf: Unknown symbol VBoxGuest_RTErrConvertToErrno (err -2)
[44799.123725] vboxsf: Unknown symbol VBoxGuest_RTSemFastMutexCreate (err -2)
[44799.123730] vboxsf: Unknown symbol VBoxGuest_RTSemFastMutexDestroy (err -2)
[44799.123746] vboxsf: Unknown symbol VBoxGuest_RTAssertShouldPanic (err -2)
[44799.123754] vboxsf: Unknown symbol VBoxGuest_RTLogLoggerEx (err -2)
[44799.123762] vboxsf: Unknown symbol VBoxGuest_RTMemTmpAllocTag (err -2)
[44799.123771] vboxsf: Unknown symbol VBoxGuest_RTAssertMsg1Weak (err -2)
[44799.123781] vboxsf: Unknown symbol VBoxGuest_RTAssertMsg2Weak (err -2)


Hello,
I did compile the latest guest additions 5.2.22 against the kernel 4.19.1 without any issue and without having to patch it like I had to do it with the version 5.2.20.
What version of VirtualBox itself do you have? Mine is 5.2.22 too
Also the first line tells you seem to have a tainted kernel. Reading this article might give you a clue:
https://unix.stackexchange.com/questions/118116/what-is-a-tainted-kernel-in-linux
Cheers
Back to top
View user's profile Send private message
Cuong Nguyen
Tux's lil' helper
Tux's lil' helper


Joined: 18 Jan 2018
Posts: 106

PostPosted: Mon Nov 12, 2018 4:37 am    Post subject: Reply with quote

Hello,

The same error happened here with either 4.19.1-gentoo or 4.18.16-ck-gnu VirtualBox-Guest-Additions 5.2.22. Downgrading to latest stable version of 5.2.14 could not cure the problem.

I will make some investigations this afternoon. I usually compile in chroot environment of different kernel version.

So, the temporary fix to this problem is to remove vboxsf module loading from openrc-init or systemd services files. As I remember, my latest use of vboxsf services is running VirtualBox under Windows to get files from linux vbox. If you are running Linux host, you might us sshd of vbox and avoid using vboxsf in guest OS.
Back to top
View user's profile Send private message
wfdawson
n00b
n00b


Joined: 05 Aug 2010
Posts: 13

PostPosted: Tue Nov 13, 2018 4:17 am    Post subject: Reply with quote

I appreciate the kind hints. As for ssh, I'm attempting to mount my shared system drive from within the guest, something I have done many times with lower kernels and guest addition versions. That fails, and causes the messages seen in dmesg output.

# mount /mnt/C_DRIVE/
/sbin/mount.vboxsf: mounting failed with the error: No such device
Back to top
View user's profile Send private message
Display posts from previous:   
Reply to topic    Gentoo Forums Forum Index Portage & Programming All times are GMT
Page 1 of 1

 
Jump to:  
You cannot post new topics in this forum
You cannot reply to topics in this forum
You cannot edit your posts in this forum
You cannot delete your posts in this forum
You cannot vote in polls in this forum