Virtualbox shared folders on Current
by aikempshall from LinuxQuestions.org on (#5C695)
My host machine is 14.2 using virtualbox-5.0.40-x86_64-1_SBo and virtualbox-kernel-5.0.40_4.4.240-x86_64-2_SBo
I can't get Shared Folders to work in a Guest machine running Current with the 5.10.3 Kernel.
In this same Guest Machine, before I upgraded to 5.10.3, I was previously using Guest Additions 6.0.15 against the 5.4 series kernel. This was working successfully.
Since upgrading to 5.10.3, I skipped 5.10.1, when I start current as a Guest machine I get this message shortly before the plasma logon screen presents -
Quote:
vboxadd-setup.log contains this which may be relevant
Quote:
Both the quoted "missing files" appear to exist
Quote:
It then attempts to compile, but eventually fails with
Quote:
I get the same result with
VBoxGuestAdditions_6.0.24.iso
VBoxGuestAdditions_6.1.16.iso
the system would start but shared folders weren't good. The best I could get was for them to be mounted, but owned by root. Before with 5.4.68 they would be mounted and owned by the user stipulated in the mount command.
I tthen tried VBoxGuestAdditions_6.1.17.iso the modules were successfully built against Kernel 5.10.3, but the system failed to start because of repeating segmentation faults. It was completely unstable. On one occasion it interrupted the boot process with an invitation to drop into root to fix a problem. I did this, but could do very little because of the recurring segmentation faults other then look.
I then managed to start the system at Level 1 this got me in. So I could uninstall VBoxGuestAdditions_6.1.17.iso. I could then boot the system consistently into Level 4.
I then cloned this now working Guest Machine and tried again with a freshly downloaded VBoxGuestAdditions_6.1.17.iso. Similar result to before, segmentation errors, except I couldn't even get to root even when I booted to level 1. Removed this clone.
I again cloned the working Guest Machine and tried again with a freshly downloads VBoxGuestAdditions_6.1.16.iso same result as the previous attempt, with 6.1.15, the system would successfully start but permissions on the shared folder were wrong.
I shall continue to investigate.
I can't get Shared Folders to work in a Guest machine running Current with the 5.10.3 Kernel.
In this same Guest Machine, before I upgraded to 5.10.3, I was previously using Guest Additions 6.0.15 against the 5.4 series kernel. This was working successfully.
Since upgrading to 5.10.3, I skipped 5.10.1, when I start current as a Guest machine I get this message shortly before the plasma logon screen presents -
Quote:
| VirtualBox Guest Additions: Building the modules for kernel 5.10.3 VirtualBox Guest Additions: Look at /var/log/vboxadd-setup.log to find out what went wrong |
Quote:
| Error building the module. Build output follows. make V=1 CONFIG_MODULE_SIG= CONFIG_MODULE_SIG_ALL= -C /lib/modules/5.10.3/build M=/tmp/vbox.0 SRCROOT=/tmp/vbox.0 -j4 modules make[1]: warning: -jN forced in submake: disabling jobserver mode. test -e include/generated/autoconf.h -a -e include/config/auto.conf || ( \ echo >&2; \ echo >&2 " ERROR: Kernel configuration is invalid."; \ echo >&2 " include/generated/autoconf.h or include/config/auto.conf are missing.";\ echo >&2 " Run 'make oldconfig && make prepare' on kernel src to fix it."; \ echo >&2 ; \ /bin/false) make -f ./scripts/Makefile.build obj=/tmp/vbox.0 \ |
Quote:
| -rw-r--r-- 1 root root 163412 Dec 26 21:18 /usr/src/linux-5.10.3/include/config/auto.conf -rw-r--r-- 1 root root 248185 Dec 26 21:18 /usr/src/linux-5.10.3/include/generated/autoconf.h |
It then attempts to compile, but eventually fails with
Quote:
| In file included from /tmp/vbox.0/combined-os-specific.c:33: /tmp/vbox.0/r0drv/linux/memobj-r0drv-linux.c: In function 'rtR0MemObjLinuxVMap': /tmp/vbox.0/r0drv/linux/memobj-r0drv-linux.c:560:34: error: implicit declaration of function 'alloc_vm_area' [-Werror=implicit-function-declaration] 560 | pMemLnx->pArea = alloc_vm_area(pMemLnx->Core.cb, papPtes); /* Note! pArea->nr_pages is not set. */ | ^~~~~~~~~~~~~ /tmp/vbox.0/r0drv/linux/memobj-r0drv-linux.c:560:32: warning: assignment to 'struct vm_struct *' from 'int' makes pointer from integer without a cast [-Wint-conversion] 560 | pMemLnx->pArea = alloc_vm_area(pMemLnx->Core.cb, papPtes); /* Note! pArea->nr_pages is not set. */ | ^ cc1: some warnings being treated as errors make[2]: *** [scripts/Makefile.build:279: /tmp/vbox.0/combined-os-specific.o] Error 1 make[2]: *** Waiting for unfinished jobs.... ./tools/objtool/objtool orc generate --module --no-fp --retpoline --uaccess /tmp/vbox.0/combined-agnostic.o make[1]: *** [Makefile:1805: /tmp/vbox.0] Error 2 make: *** [/tmp/vbox.0/Makefile-footer.gmk:117: vboxguest] Error 2 |
I get the same result with
VBoxGuestAdditions_6.0.24.iso
VBoxGuestAdditions_6.1.16.iso
the system would start but shared folders weren't good. The best I could get was for them to be mounted, but owned by root. Before with 5.4.68 they would be mounted and owned by the user stipulated in the mount command.
I tthen tried VBoxGuestAdditions_6.1.17.iso the modules were successfully built against Kernel 5.10.3, but the system failed to start because of repeating segmentation faults. It was completely unstable. On one occasion it interrupted the boot process with an invitation to drop into root to fix a problem. I did this, but could do very little because of the recurring segmentation faults other then look.
I then managed to start the system at Level 1 this got me in. So I could uninstall VBoxGuestAdditions_6.1.17.iso. I could then boot the system consistently into Level 4.
I then cloned this now working Guest Machine and tried again with a freshly downloaded VBoxGuestAdditions_6.1.17.iso. Similar result to before, segmentation errors, except I couldn't even get to root even when I booted to level 1. Removed this clone.
I again cloned the working Guest Machine and tried again with a freshly downloads VBoxGuestAdditions_6.1.16.iso same result as the previous attempt, with 6.1.15, the system would successfully start but permissions on the shared folder were wrong.
I shall continue to investigate.