Ticket #4924 (new enhancement)

Opened 9 years ago

Last modified 8 years ago

Change mount behaviour in suse guests (vboxadd)

Reported by: mkromer Owned by:
Priority: minor Component: guest additions
Version: VirtualBox 3.0.4 Keywords:
Cc: Guest type: Linux
Host type: Linux


Having vboxsf in the fstab with opensuse is not that good, as suse cannot umount volumes correctly (did not track down this one), however I think the way devices get unmounted is not the best way to do so.

As vboxadd simply unmounts mounted devices defined by fstab, it will never unmount manual mounts (umount -a -t vboxsf), so I suggest to read in /proc/mounts to unmount all *currently* mounted devices, so removing kernel modules wont fail.

Also there is a problem with vboxsf in conjunction with suse: a correctly configured fstab shows mount usage at boot time, as mount.vboxsf does not recognize vboxsf correctly at boot time (at least with suse), so i think its a good idea to use "auto" as per default. I changed my configuration to use noauto, and changed mount -a -t vboxsf to a simple mount for loop with all vboxsf definitions.

For all described the attached patch is working.


vboxadd-mount.patch Download (885 bytes) - added by mkromer 9 years ago.

Change History

Changed 9 years ago by mkromer

comment:1 Changed 8 years ago by willyo

I second the motion...

The patch seems to me to be a reasonable way to handle VirtualBox shared file-system mounts at boot-time based upon the contents of /etc/fstab.

With the current way (3.1.4) if there's a vboxsf entry in /etc/fstab without noauto there'll be an error when the initial mounts are done since (at least on Fedora) the vboxadd stuuf hasn't yet been loaded.

Note: See TracTickets for help on using tickets.
ContactPrivacy policyTerms of Use