В Wed, 05 Feb 2014 19:08:42 +0000 Dylan пишет:

Hi

I have an oS 13.1 guest running in virtualbox on a 13.1 host. I am trying to set up a shared directory, but cannot get it to mount when the VM boots.

Manually mounting the configured share with:

mount -t vboxsf data /home/dylan/host-data

works as expected. And when it is added to /etc/fstab as:

data /home/dylan/host-data vboxsf defaults 0 0

then mount -at vboxsf mounts it as expected. However, when the VM is rebooted, the share fails to mount, leaving me with an endless loop of the emergency messages (no ability to log in to recover the system.) At

This is a known bug https://bugzilla.novell.com/show_bug.cgi?id=852021

this stage the only option is to revert to the previous snapshot.

Have I missed something or am I doing something wrong?

I suspect that to mount it VBox services must be started, modules loaded etc. And filesystems from /etc/fstab are mounted way too early, before it (just guessing, I do not have vbox available).

On HOST: dylan@zeus:~> rpm -qa | grep virtual virtualbox-4.3.6-108.8.x86_64 virtualbox-host-kmp-desktop-4.3.6_k3.11.6_4-108.8.x86_64 virtualbox-qt-4.3.6-108.8.x86_64 virtualbox-guest-kmp-desktop-4.3.6_k3.11.6_4-108.8.x86_64 dylan@zeus:~>

on GUEST: dylan@virt:~> rpm -qa | grep virtual virtualbox-guest-kmp-desktop-4.3.6_k3.11.6_4-108.8.x86_64 virtualbox-guest-x11-4.3.6-108.8.x86_64 virtualbox-guest-tools-4.3.6-108.8.x86_64 dylan@virt:~>

Any assistance will be gratefully accepted...

Dylan

-- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org

On Wednesday, February 05, 2014 10:41:08 PM Ken Schneider - openSUSE wrote:

On 02/05/2014 06:31 PM, Bernhard Voelker pecked at the keyboard and wrote:

...

On 02/05/2014 08:08 PM, Dylan wrote:

...

Hi

I have an oS 13.1 guest running in virtualbox on a 13.1 host. I am trying to set up a shared directory, but cannot get it to mount when the VM boots.

Manually mounting the configured share with:

mount -t vboxsf data /home/dylan/host-data

works as expected. And when it is added to /etc/fstab as:

data /home/dylan/host-data vboxsf defaults 0 0

then mount -at vboxsf mounts it as expected. However, when the VM is rebooted, the share fails to mount, leaving me with an endless loop of the emergency messages (no ability to log in to recover the system.) At this stage the only option is to revert to the previous snapshot.

Have I missed something or am I doing something wrong?

That's because /etc/fstab is used for localfs target by systemd. That prevents further booting.

I'm using the 'noauto' flag instead and mount it via sudo. Not much of help, I know ...

Have a nice day, Berny

Go into the "Settings" for your VM guest and set up your shared directories (for the host) under "Shared Folders". You can access them under /media on the guest. Make sure you are a member of vboxsf group on the guest.

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. I am a member of the vboxfs group. Of course, that is only important for accessing the mounts, not for the mount itself, as the mount happens before a user logs in. -- Yours sincerely, Roger Oberholtzer Ramböll RST / Systems Office: Int +46 10-615 60 20 Mobile: Int +46 70-815 1696 roger.oberholtzer@ramboll.se ________________________________________ Ramböll Sverige AB Krukmakargatan 21 P.O. Box 17009 SE-104 62 Stockholm, Sweden www.rambollrst.se -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org

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. Have a nice day, Berny -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org

On 02/06/2014 01:10 PM, Roger Oberholtzer wrote:

I would be ok with mounting by hand if I could get the group permissions (for vboxfs) to work for members of that group. Which was ok when it got mounted automatically. I just can't seem to figure out the masks to get what worked for a bit.

I've just the following in /etc/fstab (okay, the host in this particular case is Win7, so I don't really care about strange fmode/dmode/umask mappings, but you get'll the point) shared_dir /share vboxsf noauto,uid=$USER,gid=users,fmode=0700,dmode=0700,umask=0077 0 0 ... and mount the share via sudo. You can even put the sudo command into $HOME/.xinitrc One annoying thing about vboxsf is that 'mount -v' doesn't work, and even leads to an error. Have a nice day, Berny -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org

On 02/06/2014 03:08 PM, Dylan wrote:

How do I get sudo to allow me to run the command without entering the password? I have:

dylan ALL = (ALL) NOPASSWD: ALL

in my sudoers file but I still get asked for my password...

*your* password? IMHO that's not a good sudo config anyway because it should ask the target user's password ("targetpw"). I'd use something like Defaults targetpw root ALL=(ALL) ALL berny ALL=(root) NOPASSWD: /usr/bin/mount /share and have a little script ... or an alias like alias mountshare='sudo /usr/bin/mount /share' Have a nice day, Berny -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org

On 06/02/14 15:08, Bernhard Voelker wrote:

On 02/06/2014 03:08 PM, Dylan wrote:

...

How do I get sudo to allow me to run the command without entering the password? I have:

dylan ALL = (ALL) NOPASSWD: ALL

in my sudoers file but I still get asked for my password...

*your* password? IMHO that's not a good sudo config anyway because it should ask the target user's password ("targetpw").

Yes, *my* password - that's one of the reasons to use sudo rather than su... But no matter... I've solved it now Dx

I'd use something like

Defaults targetpw

root ALL=(ALL) ALL berny ALL=(root) NOPASSWD: /usr/bin/mount /share

and have a little script ... or an alias like

alias mountshare='sudo /usr/bin/mount /share'

Have a nice day, Berny

-- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org

On 06/02/14 19:22, Patrick Shanahan wrote:

* Dylan [02-06-14 13:51]:

...

On 06/02/14 15:08, Bernhard Voelker wrote:

...

On 02/06/2014 03:08 PM, Dylan wrote:

...

How do I get sudo to allow me to run the command without entering the password? I have:

dylan ALL = (ALL) NOPASSWD: ALL

in my sudoers file but I still get asked for my password...

*your* password? IMHO that's not a good sudo config anyway because it should ask the target user's password ("targetpw").

Yes, *my* password - that's one of the reasons to use sudo rather than su...

But no matter... I've solved it now

Dx

...

I'd use something like

Defaults targetpw

root ALL=(ALL) ALL berny ALL=(root) NOPASSWD: /usr/bin/mount /share

and have a little script ... or an alias like

alias mountshare='sudo /usr/bin/mount /share'

Have a nice day, Berny

IF you have *solved* it, consider providing the solution and also marking the thread as solved.

Not doing so provides no assistance to anyone following with similar problems and is very inconsiderate! Remember the prime reason for the existance of these lists is solve problems.

Because the original problem of the tread is NOT solved - Virtualbox VMs don't automatically mount shares, and putting them in fstab makes the VM unbootable. The workaround/hack/cludge of mounting the shares through a script executed on login is not a solution, and the resolution of my temporary minor error in sudo configuration does not warrant a [SOLVED] annotation. Nevertheless, I'll consider myself suitably patronised

-- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org

On 06/02/14 20:29, Patrick Shanahan wrote:

* Dylan [02-06-14 14:59]: [...]

...

Because the original problem of the tread is NOT solved - Virtualbox VMs don't automatically mount shares, and putting them in fstab makes the VM unbootable. The workaround/hack/cludge of mounting the shares through a script executed on login is not a solution, and the resolution of my temporary minor error in sudo configuration does not warrant a [SOLVED] annotation.

But... You still have not provided the solution to the problem you posed in spite it not being the "Subject:"

I trusted yast to put the new entry in sudoers - it went in the wrong place (before the root entry) so I moved it to after and now it (sudo) works as I want (doesn't ask me for any password)...

...

Nevertheless, I'll consider myself suitably patronised

no need, but why the mysteries?

-- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org

On 06/02/14 20:58, Ken Schneider - openSUSE wrote:

On 02/06/2014 02:57 PM, Dylan pecked at the keyboard and wrote:

...

On 06/02/14 19:22, Patrick Shanahan wrote:

...

* Dylan [02-06-14 13:51]:

...

On 06/02/14 15:08, Bernhard Voelker wrote:

...

On 02/06/2014 03:08 PM, Dylan wrote:

...

Because the original problem of the tread is NOT solved - Virtualbox VMs don't automatically mount shares, and putting them in fstab makes the VM unbootable. The workaround/hack/cludge of mounting the shares through a script executed on login is not a solution, and the resolution of my temporary minor error in sudo configuration does not warrant a [SOLVED] annotation.

Nevertheless, I'll consider myself suitably patronised

...

As I stated in a previous post I have two shared folders configured and both show as follows in a running system:

ken@os12-2:~> ll /media/ total 12 drwxrwx--- 1 root vboxsf 8192 Feb 6 15:35 sf_Documents drwxrwx--- 1 root vboxsf 111 Jan 21 19:43 sf_storage ken@os12-2:~>

Both are automounted at boot.

That's all very well for 12.2 but it doesn't work here in 13.1 Dx -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org

On 06/02/14 21:58, Ken Schneider - openSUSE wrote:

On 02/06/2014 04:01 PM, Dylan pecked at the keyboard and wrote:

...

On 06/02/14 20:58, Ken Schneider - openSUSE wrote:

...

As I stated in a previous post I have two shared folders configured and both show as follows in a running system:

ken@os12-2:~> ll /media/ total 12 drwxrwx--- 1 root vboxsf 8192 Feb 6 15:35 sf_Documents drwxrwx--- 1 root vboxsf 111 Jan 21 19:43 sf_storage ken@os12-2:~>

Both are automounted at boot.

That's all very well for 12.2 but it doesn't work here in 13.1

Dx

This is on my 13.1 test VM.

Ah, I was misled by the "os12-2" in the prompt...

Do you get any errors when running:

openSUSE-test:~ # /etc/init.d/vboxadd setup

On the host or guest? Dx -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org

On 02/06/2014 05:02 PM, Dylan pecked at the keyboard and wrote:

On 06/02/14 21:58, Ken Schneider - openSUSE wrote:

...

On 02/06/2014 04:01 PM, Dylan pecked at the keyboard and wrote:

...

On 06/02/14 20:58, Ken Schneider - openSUSE wrote:

...

As I stated in a previous post I have two shared folders configured and both show as follows in a running system:

ken@os12-2:~> ll /media/ total 12 drwxrwx--- 1 root vboxsf 8192 Feb 6 15:35 sf_Documents drwxrwx--- 1 root vboxsf 111 Jan 21 19:43 sf_storage ken@os12-2:~>

Both are automounted at boot.

That's all very well for 12.2 but it doesn't work here in 13.1

Dx

This is on my 13.1 test VM.

Ah, I was misled by the "os12-2" in the prompt...

No you were not, I have both versions in a VM.

...

Do you get any errors when running:

openSUSE-test:~ # /etc/init.d/vboxadd setup

On the host or guest?

Dx

On the guest. -- 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

On 06/02/14 22:10, Ken Schneider - openSUSE wrote:

On 02/06/2014 05:05 PM, Dylan pecked at the keyboard and wrote:

...

On 06/02/14 21:58, Ken Schneider - openSUSE wrote:

...

Do you get any errors when running:

openSUSE-test:~ # /etc/init.d/vboxadd setup

No

dylan@virt:~> sudo /etc/init.d/vboxadd setup Recompiling VirtualBox kernel module, NOT. It has been packaged. done dylan@virt:~>

I run the VirtualBox version downloaded from the repo:

https://www.virtualbox.org/wiki/Downloads

Which version do you run?

HOST: dylan@zeus:~> rpm -qa | grep virtual virtualbox-4.3.6-108.8.x86_64 virtualbox-host-kmp-desktop-4.3.6_k3.11.6_4-108.8.x86_64 virtualbox-qt-4.3.6-108.8.x86_64 virtualbox-guest-kmp-desktop-4.3.6_k3.11.6_4-108.8.x86_64 dylan@zeus:~> GUEST: dylan@virt:~> rpm -qa | grep virtual virtualbox-guest-kmp-desktop-4.3.6_k3.11.6_4-108.8.x86_64 virtualbox-guest-x11-4.3.6-108.8.x86_64 virtualbox-guest-tools-4.3.6-108.8.x86_64 dylan@virt:~> From: dylan@zeus:~> zypper lr -u [SNIP] 7 | download.opensuse.org-Virtualization | openSUSE BuildService - Virtualization (VirtualBox) | Yes | Yes | http://download.opensuse.org/repositories/Virtualization/openSUSE_13.1/ -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org

On 02/06/2014 05:16 PM, Dylan pecked at the keyboard and wrote:

On 06/02/14 22:10, Ken Schneider - openSUSE wrote:

...

On 02/06/2014 05:05 PM, Dylan pecked at the keyboard and wrote:

...

On 06/02/14 21:58, Ken Schneider - openSUSE wrote:

...

Do you get any errors when running:

openSUSE-test:~ # /etc/init.d/vboxadd setup

No

dylan@virt:~> sudo /etc/init.d/vboxadd setup Recompiling VirtualBox kernel module, NOT. It has been packaged. done dylan@virt:~>

I run the VirtualBox version downloaded from the repo:

https://www.virtualbox.org/wiki/Downloads

Which version do you run?

HOST: dylan@zeus:~> rpm -qa | grep virtual virtualbox-4.3.6-108.8.x86_64 virtualbox-host-kmp-desktop-4.3.6_k3.11.6_4-108.8.x86_64 virtualbox-qt-4.3.6-108.8.x86_64 virtualbox-guest-kmp-desktop-4.3.6_k3.11.6_4-108.8.x86_64 dylan@zeus:~>

GUEST: dylan@virt:~> rpm -qa | grep virtual virtualbox-guest-kmp-desktop-4.3.6_k3.11.6_4-108.8.x86_64 virtualbox-guest-x11-4.3.6-108.8.x86_64 virtualbox-guest-tools-4.3.6-108.8.x86_64 dylan@virt:~>

From: dylan@zeus:~> zypper lr -u [SNIP] 7 | download.opensuse.org-Virtualization | openSUSE BuildService - Virtualization (VirtualBox) | Yes | Yes | http://download.opensuse.org/repositories/Virtualization/openSUSE_13.1/

That may make all the difference, you have the openSuSE version and I have the latest one direct from Oracle. It's possible that the version you have from openSuSE didn't enable automounting shares in the guest additions. Only the builder of the package can say for sure. -- 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

On 02/06/2014 05:26 PM, Patrick Shanahan pecked at the keyboard and wrote:

* Dylan [02-06-14 17:16]:

...

On 06/02/14 22:10, Ken Schneider - openSUSE wrote:

...

I run the VirtualBox version downloaded from the repo:

https://www.virtualbox.org/wiki/Downloads

Which version do you run?

HOST: dylan@zeus:~> rpm -qa | grep virtual virtualbox-4.3.6-108.8.x86_64 virtualbox-host-kmp-desktop-4.3.6_k3.11.6_4-108.8.x86_64 virtualbox-qt-4.3.6-108.8.x86_64 virtualbox-guest-kmp-desktop-4.3.6_k3.11.6_4-108.8.x86_64 dylan@zeus:~>

GUEST: dylan@virt:~> rpm -qa | grep virtual virtualbox-guest-kmp-desktop-4.3.6_k3.11.6_4-108.8.x86_64 virtualbox-guest-x11-4.3.6-108.8.x86_64 virtualbox-guest-tools-4.3.6-108.8.x86_64 dylan@virt:~>

From: dylan@zeus:~> zypper lr -u [SNIP] 7 | download.opensuse.org-Virtualization | openSUSE BuildService - Virtualization (VirtualBox) | Yes | Yes | http://download.opensuse.org/repositories/Virtualization/openSUSE_13.1/

Ah, he's running the openSUSE packages which, iirc, do not provide usb or automagic shared directories....

The *only* reason I use the rpms from Oracle.

Same here, I don't like using crippled software. -- 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

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

On 02/07/2014 01:30 AM, Roger Oberholtzer pecked at the keyboard and wrote:

On Thursday, February 06, 2014 09:01:00 PM Dylan wrote:

...

On 06/02/14 20:58, Ken Schneider - openSUSE wrote:

...

On 02/06/2014 02:57 PM, Dylan pecked at the keyboard and wrote:

...

...

* Dylan [02-06-14 13:51]:

...

On 06/02/14 15:08, Bernhard Voelker wrote: > On 02/06/2014 03:08 PM, Dylan wrote: Because the original problem of the tread is NOT solved - Virtualbox VMs don't automatically mount shares, and putting them in fstab makes the VM unbootable. The workaround/hack/cludge of mounting the shares through a

On 06/02/14 19:22, Patrick Shanahan wrote: script executed on login is not a solution, and the resolution of my temporary minor error in sudo configuration does not warrant a [SOLVED] annotation.

Nevertheless, I'll consider myself suitably patronised

As I stated in a previous post I have two shared folders configured and both show as follows in a running system:

ken@os12-2:~> ll /media/ total 12 drwxrwx--- 1 root vboxsf 8192 Feb 6 15:35 sf_Documents drwxrwx--- 1 root vboxsf 111 Jan 21 19:43 sf_storage ken@os12-2:~>

Both are automounted at boot.

That's all very well for 12.2 but it doesn't work here in 13.1

This past week I have installed in VirtualBox (host is oS12.3 with whatever is the current VB version) the following oS versions:

11.2, 12.1, 12.3 and 13.1

None of these automount the shared drive. My money is on the host being the cause of the problem and not the guest.

If you are using the version supplied from openSUSE, USB and auto-mounting of shared folders is crippled. I use the rpm from Oracle via their repo and do not have such problems. -- 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

On 02/05/2014 01:08 PM, Dylan wrote:

then mount -at vboxsf mounts it as expected. However, when the VM is rebooted, the share fails to mount, leaving me with an endless loop of the emergency messages (no ability to log in to recover the system.) At this stage the only option is to revert to the previous snapshot.

the vboxsf kernel module (ON THE GUEST) was not loaded automatically on reboot so the fstab mount failed. I'm not sure what a 13.1 guest does for automatically loading the vitrualbox modules, but it will be something similar to creating an /etc/modules-load.d/vbox.conf file with the 'vboxsf' module name (along with any of the other vbox modules you want loaded on boot. Eg: [[ -d /etc/modules-load.d ]] && \ sudo echo -e "vboxguest\nvboxsf\nvboxvideo" > /etc/modules-load.d/vbox.conf -- David C. Rankin, J.D.,P.E. -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org