(Solved)How to Automount shared folder openSUSE 11.4?

[loukingjr]

I just installed the last beta of openSUSE 11.4 before the release in a few days. I have the 4.0.4 guest additions already installed and everything seems to work but, normally when I choose automount a shared folder in other distros a vboxsf group is created and I just have to add myself to it. But the shared folder is not showing up in /media as normal and no group seems to be created. Any thoughts on what I'm missing?

thanks.

[Perryg]

I can't speak as to why it was not created but I have seen this before in pre-release OSes. Just create the group and then add yourself to it and see if that solves your problem.

[loukingjr]

I can't speak as to why it was not created but I have seen this before in pre-release OSes. Just create the group and then add yourself to it and see if that solves your problem.

well, openSUSE wants a PID number in order to create a group and I'm not sure how to get it.

as far as it being pre-release it's going to be released in 9 days so it's not all that pre.

[Perryg]

I know but with hundreds or distros wanting to do things their way and releasing them at random (no one wants to commit to a universal release policy) making it is really tuff to keep all of these all in tune and get any other work done. I will try to install the latest Novel build here today and see what needs to be done and get back with you. Oh and the issue may already be resolved as I am able to use the shared folder in openSUSE-11.4 but on my alpha builds. I will try it on my release build instead.

[loukingjr]

I know but with hundreds or distros wanting to do things their way and releasing them at random (no one wants to commit to a universal release policy) making it is really tuff to keep all of these all in tune and get any other work done. I will try to install the latest Novel build here today and see what needs to be done and get back with you. Oh and the issue may already be resolved as I am able to use the shared folder in openSUSE-11.4 but on my alpha builds. I will try it on my release build instead.

thanks Perry. Just for your info, I tried the "normal" way of adding mount -t vboxsf Media /home/louis/Multimedia/ to /etc/fstab and mount -t vboxsf Media /mnt/Media to fstab and neither worked. However, mount -t vboxsf Media /home/louis/Multimedia/ worked fine in a terminal.

[Perryg]

IIRC you don't add them to fstab in openSUSE. I need to see exactly where but with automount it will not matter. Here is a screen shot showing that it does in fact work although this copy I believe I had to create my own vboxsf group. Anyway I am going to install to my release version later today and see.

openSUSE-SF.png (79.34 KiB) Viewed 5986 times

[loukingjr]

IIRC you don't add them to fstab in openSUSE. I need to see exactly where but with automount it will not matter. Here is a screen shot showing that it does in fact work although this copy I believe I had to create my own vboxsf group. Anyway I am going to install to my release version later today and see.

openSUSE-SF.png

hmmm, well someone from the openSUSE forum told me to add it there. Not that it worked.
and I did create a vboxsf group although that didn't seem to help either. I'll wait and see.

edit: btw, mount -t vboxsf Media /home/louis/Multimedia/ works just fine in a terminal.

[Perryg]

The problem with using fstab is it runs before the VirtualBox modules get loaded so it sees the statement and can't do anything with it. Now if it happens to catch this later then it recoups. Using rc.local solves this but openSUSE has decided not to use it anymore (that is what I was thinking about above). Solution is below
http://forums.opensuse.org/archives/sf- ... local.html

[loukingjr]

The problem with using fstab is it runs before the VirtualBox modules get loaded so it sees the statement and can't do anything with it. Now if it happens to catch this later then it recoups. Using rc.local solves this but openSUSE has decided not to use it anymore (that is what I was thinking about above). Solution is below
http://forums.opensuse.org/archives/sf- ... local.html

thanks Perry. after you posted this I realized I had the same issue with 11.3 and had completely forgotten. The solution worked fine.

thanks again.

[loukingjr]

I found a different problem using shared folders in openSUSE 11.4 RC2. It seems if I try and use VLC 1.1.7 to played videos from the shared folder, VLC quickly uses up all memory and pegs the CPU to 100%. None of my other guests have the same issue.

[Perryg]

Have you also noticed how slow and sluggish 11.4 is lately (since milestone 4)? I don't know for sure but this seems to be a problem with the OS and not so much VirtualBox.

[loukingjr]

Have you also noticed how slow and sluggish 11.4 is lately (since milestone 4)? I don't know for sure but this seems to be a problem with the OS and not so much VirtualBox.

well it does seem slow. I only tried milestone 2 I think. then deleted the guest till RC2. I noticed it also uses a fair amount of memory doing nothing. I'm not sure my RC2 install is 100% good seeing I couldn't play any kind of video with Banshee or Totem no matter what I did. We'll see what happens when it's released.

[loukingjr]

me again

I just installed the most recent version of Peppermint Linux. I had been using the previous version for quite a long time with no issue. However, the new version is having some issue with shared folders. If I select automount, VB does create the sf_Media (in this case) folder in /media but it's empty when I look in it. Since that didn't work I unchecked automount and added "mount -t vboxsf Media /mnt/Multimedia" to /etc/rc.local. That did nothing. It is the same command I use in the other version that does work. "mount -t vboxsf Media /mnt/Multimedia" does work in a terminal however.

any thoughts? thanks.

[Perryg]

Are you in the vboxsf group on the guest?

[loukingjr]

Are you in the vboxsf group on the guest?

I was. I had actually deleted the vboxsf group once it wasn't working but I re-added it later. I'm not sure I re-added myself however. I will check. There's something odd going on with that version though. It uses nearly three times the memory of the previous version and the only real difference is a change of kernel and an update to PCManFM.

well that didn't help and I had forgotten to re-add myself. Usually in other guests, if you don't have yourself added the folder is locked and you have to add yourself. But when I did the automount originally, it created sf_Media in /media but it wasn't locked, it was just empty.

and threes times the memory was a stretch. It does use twice the memory though.