VirtualBox

Custom Query (16363 matches)

Filters
 
Or
 
  
 
Columns

Show under each result:


Results (1288 - 1290 of 16363)

Ticket Resolution Summary Owner Reporter
#16670 fixed mount.vboxsf symlink broken chr.moench-tegeder
Description

This looks like a regression in 5.1.20.

Guest system is Linux - reproduced with both Debian 8 and openSUSE 42.2. After upgrading Guest Additions from 5.1.18, the /sbin/mount.vboxsf symlink points to the wrong location:

root@host1:~# ls -l /sbin/mount.vboxsf lrwxrwxrwx 1 root root 49 Apr 19 10:33 /sbin/mount.vboxsf -> /opt/VBoxGuestAdditions-5.1.20/other/mount.vboxsf root@host1:~# find /opt/VBoxGuestAdditions-5.1.20/ -name mount\* /opt/VBoxGuestAdditions-5.1.20/lib/VBoxGuestAdditions/mount.vboxsf

With previous versions of the Guest Additions (checked 5.1.18 and 5.1.14, that's what I have around currently), /sbin/mount.vboxsf points to /usr/lib{64,/x86_64-linux-gnu}/VBoxGuestAdditions/mount.vboxsf (exact location of the lib64 directory varies per linux distribution, examples taken from CentOS 7 and Debian 8).

A quick test for stale symlinks (find -L / -xdev -type l) shows that mount.vboxsf is the only file affected. This allows for the simple workaround of fixing the symlink: root@host1:~# ln -sf /usr/lib/x86_64-linux-gnu/VBoxGuestAdditions/mount.vboxsf /sbin/mount.vboxsf

(remember to check the lib64 path for your distribution, e.g. lib64 on Redhat/Centos-based distributions)

#1603 fixed mount vboxsf filesystems automatically => Fixed in 1.6.2 Matthijs Melchior
Description

Please add code like the following to /etc/init.d/vboxvfs inside a Linux guest. This will mount and umount the 'vboxsf' filesystems mentioned in /etc/fstab whenever the vboxvfs kernel module is inserted or removed.

Thanks.

--- vboxvfs-ORG	2008-05-22 17:24:00.000000000 +0200
+++ vboxvfs	2008-05-23 16:14:16.000000000 +0200
@@ -140,16 +140,21 @@
             fail "modprobe $modname failed"
         }
     }
+    # Now we can mount vboxsf filesystems mentioned in /etc/fstab
+    mount -a -t vboxsf
+
     succ_msg
     return 0
 }
 
 stop() {
     begin "Stopping VirtualBox Additions shared folder support ";
-    if running; then
-        rmmod $modname || fail "Cannot unload module $modname"
-    fi
-    succ_msg
+    # must umount vboxsf filesystems first
+    umount -a -t vboxsf &&
+        if running; then
+            rmmod $modname || fail "Cannot unload module $modname"
+        fi &&
+        succ_msg
     return 0
 }
 
#3046 obsolete mount media in Windows doesn't work for non-default drive letter David Smiley
Description

The default drive letter for the CD-ROM drive in my Windows VM is "D". This can be changed in Windows to a different letter (search Windows help for instructions), which I did since I want to use D for a mapped drive. When I do this, I lose the ability to virtually mount .iso files (like the guest additions iso).

Batch Modify
Note: See TracBatchModify for help on using batch modify.
Note: See TracQuery for help on using queries.

© 2024 Oracle Support Privacy / Do Not Sell My Info Terms of Use Trademark Policy