On 02/06/2014 05:37 PM, Rodney Baker pecked at the keyboard and wrote:
On Thu, 6 Feb 2014 08:27:47 Bernhard Voelker wrote:
On 02/06/2014 07:54 AM, Roger Oberholtzer wrote:
I have the same problem with the shares not being mounted automatically. In the VB manager. I have checked Auto-mount. This did work the first time I booted the guest, at which access was perfect (except for making symlinks - which I found how to correct). But it is no longer mounted in subsequent boots.
You don't want that, really ... as long as systemd continues to fail to continue booing on mount failures from /etc/fstab:
In the case the kernel got updated, the vboxsf module will fail to load and needs to be recompiled. Just mount it later, via boot.local, sudo or whatever.
Unless you have dkms installed and working and the vbox modules registered with dkms. No more manually recompiling kernel modules, it happens automatically when booting with the new kernel. :-)
Works for vbox and Nvidia drivers here. Google "virtualbox dkms setup" and you'll find a tutorial on how to do it. I can't remember the exact steps now.
Rodney.
We don't think that is the issue here with auto-mounting VB shares. The version of VirtualBox from openSuSE doesn't support it. -- Ken Schneider SuSe since Version 5.2, June 1998 -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org