id,summary,reporter,owner,description,type,status,component,version,resolution,keywords,cc,guest,host 4924,Change mount behaviour in suse guests (vboxadd),Michael Kromer,,"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.",enhancement,new,guest additions,VirtualBox 3.0.4,,,,Linux,Linux