"shared folder" does not work

[Plagrö]

Thank you both again:

VBox.log.zip

(30.12 KiB) Downloaded 267 times

[scottgus1]

So we have Guest Additions installed, and matching the host Virtualbox version:

00:00:00.876869 VirtualBox VM 6.1.30_Debian r148432 linux.amd64 (Dec 6 2021 19:17:27) release log
00:00:11.641581 VMMDev: Guest Additions information report: Version 6.1.30 r148432 '6.1.30'
00:00:11.643360 VMMDev: Guest Log: vboxguest: Successfully loaded version 6.1.30 r148432

Here's the shared folder:

00:00:01.148242 Host path '/home/Plagroe/1_Daten_Toshiba', map name '1_Daten_Toshiba', read-only, automount=true, automntpnt=/, create_symlinks=false, missing=false

I'd suggest looking at this part:

automount=true, automntpnt=/

It appears that you may not have specified an automount point?

[Plagrö]

The mount point was ...

Code: Select all

/home/Plagroe/1_Daten_Toshiba

However I have already tried /mnt above some days ago without success.

[scottgus1]

Was that to be the mount point in the VM? so it would read the same as the host path?

[Plagrö]

Not sure, if I understand your question right.

It's the path I have in the 3rd field here in Virtualbox which is installed on the host:

k20240117-195118.png (25.58 KiB) Viewed 4555 times

But I have also once tried /mnt .

Yes, I have this path also in MX-19 Host. It's the path to my separate HDD.
And I also want to have this path in my MX-19 guest.

[fth0]

FWIW, the name of your host's folder sounds as if it could be a symlink. There's a known issue that was fixed one and a half year ago in VirtualBox 6.1.36 (6.1.50 is current). Additionally, you should have a look at Re: shared folder guest side cannot follow symlinks in shared folder host side.

[Plagrö]

FWIW, the name of your host's folder sounds as if it could be a symlink.

Not sure, but I do not think, that it is a simlink. It's a mount point of my other HDD:

This is what I have in /etc/fstab on the host:

Code: Select all

# /etc/fstab: static file system information.
#
# <file system> <mount point>   <type>  <options>       <dump>  <pass>

#Entry for /dev/sda1 :
UUID=2e888888-61a1-44be-8f43-44a0ce5d79c7	/	ext4	noatime	1	1
#Entry for /dev/sdc2 :
UUID=53f44444-1fbe-4472-93a1-0df87c4d7925	/home/Plagroe/1_Daten_Toshiba	ext4	defaults,nosuid,nodev,relatime	0	0
#Entry for /dev/sdc1 :
UUID=79c17d9a-6a1d-49af-9636-55555879deac	swap	swap	defaults	0	0

How ever, I will have a look at the link.

[Plagrö]

Additionally, you should have a look at Re: shared folder guest side cannot follow symlinks in shared folder host side.

I have executed now the following command in my guest:

Code: Select all

echo "options vboxsf follow_symlinks=1" | sudo tee /etc/modprobe.d/vboxsf.conf > /dev/null

Unfortunately it has not solved the problem after a restart.

[fth0]

Thanks for reporting back!

FWIW, I also successfully tried myself that host-side mounted volumes' mount points can be used as Shared Folders (in VirtualBox 6.1.48 on macOS and VirtualBox 7.0.14 on Linux).

Out of curiosity: Why are you still using VirtualBox 6.1.30?

VirtualBox 6.1.30 is more than two years old and consequently a lot of bugs and security issues are well-known. I don't claim that your issue will vanish with an up-to-date VirtualBox version, though. And I also know and understand the "Never change a running system" paradigm, although it often competes with today's higher security needs.

[Byroniac]

I cannot answer for him, but Linux MX 19.4 is old (around the time of VirtualBox 6.1.20 or so, according what I could find in its packages online), so it might be that 6.1.30 is the newest version that it is even possible to install on that version of Linux. I was going to say I suggest completely uninstalling all of the virtualbox guest additions and reinstalling (still not sure if he has both native repo and retail versions partially installed in the system). But really, he should move to a newer version of Linux if his hardware supports it. In my testing, such as with Ubuntu and Debian and Kali, the native repo versions of the guest additions have generally worked fine (with some exceptions, and for some reason, currently on Kali Linux the VirtualBox 7.0.14 file manager session will not allow opening a session with the repo 7.0.12 guest addition installed, not that I need it, but if I did I'd have to remove the native repo versions and install from the 7.0.14 virtual cdrom).

[Plagrö]

... Linux MX 19.4 is old (around the time of VirtualBox 6.1.20 or so, according what I could find in its packages online), so it might be that 6.1.30 is the newest version that it is even possible to install on that version of Linux.

Yes, MX-19 only has 6.1.30 and 7.0.6 in its repository. And I doubt, if it would be a good idea to install 7.0.6. I have heard, that there are problems with early virtualbox 7 versions.

the native repo versions of the guest additions have generally worked fine (with some exceptions, and for some reason, currently on Kali Linux the VirtualBox 7.0.14 file manager session will not allow opening a session with the repo 7.0.12 guest addition installed, not that I need it, but if I did I'd have to remove the native repo versions and install from the 7.0.14 virtual cdrom).

Not sure what you mean with native guest additions. In Version 6.1.30 I have added a virtual CD rom:

k20240119-221435.png (28.93 KiB) Viewed 4297 times

And from there I have installed the guest additions in the guest-system with the command ...

Code: Select all

sudo ./VBoxLinuxAdditions.run

I was going to say I suggest completely uninstalling all of the virtualbox guest additions and reinstalling

But weren't the guest additions already uninstalled and reinstalled anyway, when I made this (viewtopic.php?p=545025#p545025)?:

Code: Select all

Plagroe@mx:/media/Plagroe/VBox_GAs_6.1.30
$ sudo ./VBoxLinuxAdditions.run
[sudo] Passwort für Plagroe: 
Verifying archive integrity... All good.
Uncompressing VirtualBox 6.1.30 Guest Additions for Linux........
VirtualBox Guest Additions installer
Removing installed version 6.1.30 of VirtualBox Guest Additions...
You may need to restart your guest system to finish removing guest drivers.
update-initramfs: Generating /boot/initrd.img-4.19.0-25-amd64
I: The initramfs will attempt to resume from /dev/sda2
I: (UUID=e33a7ed9-3b40-4025-9d56-b092d15887d2)
I: Set the RESUME variable to override this.
Copying additional installer modules ...
Installing additional modules ...
VirtualBox Guest Additions: Starting.
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: or
VirtualBox Guest Additions:   /sbin/rcvboxadd quicksetup all
VirtualBox Guest Additions: Building the modules for kernel 4.19.0-25-amd64.
update-initramfs: Generating /boot/initrd.img-4.19.0-25-amd64
cryptsetup: ERROR: Couldn't resolve device 
    /dev/disk/by-uuid/79c17d9a-6a1d-49af-9636-50003879deac
cryptsetup: WARNING: The initramfs image may not contain cryptsetup binaries 
    nor crypto modules. If that's on purpose, you may want to uninstall the 
    'cryptsetup-initramfs' package in order to disable the cryptsetup initramfs 
    integration and avoid this warning.
I: The initramfs will attempt to resume from /dev/sda2
I: (UUID=e33a7ed9-3b40-4025-9d56-b092d15887d2)
I: Set the RESUME variable to override this.
VirtualBox Guest Additions: Running kernel modules will not be replaced until 
the system is restarted
Building the VirtualBox Guest Additions kernel modules.  This may take a while.
To build modules for other installed kernels, run
  /sbin/rcvboxadd quicksetup <version>
or
  /sbin/rcvboxadd quicksetup all
Running kernel modules will not be replaced until the system is restarted
vboxadd-service.sh: Starting VirtualBox Guest Addition service.
Plagroe@mx:/media/Plagroe/VBox_GAs_6.1.30
$ 

Line 7:

Code: Select all

Removing installed version 6.1.30 of VirtualBox Guest Additions...

[Byroniac]

I am guessing here, but I mean I think you have the virtualbox-guest-utils and maybe also the virtualbox-guest-x11 installed from your MX-Linux repository. It might be worth trying to do a "sudo apt-get remove --purge virtualbox-guest-utils virtualbox-guest-x11" (going from memory so may not be accurate) and uninstall/reinstall the VirtualBox guest additions from the cdrom and do that "usermod -aG vboxsf yourlogin" where yourlogin is whatever you use (byron for me).

[Plagrö]

Thank you.

I am guessing here, but I mean I think you have the virtualbox-guest-utils and maybe also the virtualbox-guest-x11 installed from your MX-Linux repository.

Yes. virtualbox-guest-utils, virtualbox-guest-x11 was automatically installed from repository. And also virtualbox-guest-utils-modified-init.

It might be worth trying to do a "sudo apt-get remove --purge virtualbox-guest-utils virtualbox-guest-x11" (going from memory so may not be accurate)

A) Should I also remove virtualbox-guest-utils-modified-init?

and uninstall/reinstall the VirtualBox guest additions from the cdrom and do that "usermod -aG vboxsf yourlogin" where yourlogin is whatever you use (byron for me).

Confused: Do I not need virtualbox-guest-utils, virtualbox-guest-x11 and virtualbox-guest-utils-modified-init?

[Byroniac]

I've never heard of virtualbox-guest-utils-modified-init but I think you should remove all of these, including the x11, as they conflict with (and intend to replace) the guest additions from the VirtualBox cdrom version (or get rid of the VirtualBox cdrom version). Just don't have both, as that looks like the root of your problem.

[Plagrö]

Thank you again.

OK. I have deleted the packages virtualbox-guest-utils, virtualbox-guest-x11 and virtualbox-guest-utils-modified-init in the host:

Code: Select all

The following packages are REMOVED:
  virtualbox-guest-utils virtualbox-guest-utils-modified-init
  virtualbox-guest-x11
0 updated, 0 reinstalled, 3 to be removed and 0 not updated.
After this operation 8'182 kB disk space is released.
(Read database ... 551542 files and directories are currently installed).
Removing virtualbox-guest-x11 (6.1.30-dfsg-1~mx19+1) ...
Removing virtualbox-guest-utils (6.1.30-dfsg-1~mx19+1) ...
Removing virtualbox-guest-utils-modified-init (20.07.01) ...
dpkg-divert: Error: Renaming involves overwriting "/etc/init.d/virtualbox-guest-utils" with
  other file "/etc/init.d/virtualbox-guest-utils.dpkg-distrib", not allowed
Triggers for man-db (2.8.5-2) are processed ...

After I have called in the guest terminal the command

Code: Select all

$ sudo ./VBoxLinuxAdditions.run

After I have rebooted the guest.

Then I have checked if I am still part of "vboxsf". Yes, I am.

Unfortunately: Same behaviour.