I am running SuSE 11.3 n Virtualbx on Win7. I have created a 29GB FAT partion in Windows intended to be a shared folder with SuSE Linux.
In VirtualBox settings for the VM I have specified the shared folder and checked “tilslut automatisk” (it is Danish, in English I think it is “automount”). When I start the VM there is a blue folder icon in the Virtualbox program window status line. So it seems that Virtualbox passes te information to Suse.
However, I do not see the folder in the file system. Will I need to do anything to mount it. Or am I just not able to locate the mounting point?
Or can it be a version mismatch between my Virtualbox version and the client extension in SusE? “virtualbox-guest-tools” installed is verson 4.2.18 and Virtualbox installed in Wndows is 4.3.12.
First remove the existing extension (with YasT as they wre installed with YaST)
Mount the extenson .iso
execute
linux-6np2:/mnt/vbcliext # ls -l
totalt 57127
dr-xr-xr-x 2 root root 2048 16 maj 14:21 32Bit
dr-xr-xr-x 2 root root 2048 16 maj 14:21 64Bit
-r-xr-xr-x 1 root root 647 8 okt 2013 AUTORUN.INF
-r-xr-xr-x 1 root root 6966 16 maj 14:12 autorun.sh
dr-xr-xr-x 2 root root 2048 16 maj 14:21 cert
dr-xr-xr-x 2 root root 2048 16 maj 14:21 OS2
-r-xr-xr-x 1 root root 5523 16 maj 14:12 runasroot.sh
-r-xr-xr-x 1 root root 9942477 16 maj 14:17 VBoxLinuxAdditions.run
-r-xr-xr-x 1 root root 20831744 16 maj 14:35 VBoxSolarisAdditions.pkg
-r-xr-xr-x 1 root root 16917984 16 maj 14:10 VBoxWindowsAdditions-amd64.
-r-xr-xr-x 1 root root 311584 16 maj 14:01 VBoxWindowsAdditions.exe
-r-xr-xr-x 1 root root 10471664 16 maj 14:02 VBoxWindowsAdditions-x86.ex
linux-6np2:/mnt/vbcliext # ./VBoxLinuxAdditions.run
Verifying archive integrity… All good.
Uncompressing VirtualBox 4.3.12 Guest Additions for Linux…
VirtualBox Guest Additions installer
Copying additional installer modules …
Installing additional modules …
Removing existing VirtualBox non-DKMS kernel modules don
Building the VirtualBox Guest Additions kernel modules
Building the main Guest Additions module don
Building the shared folder support module don
Building the OpenGL support module don
Doing non-kernel setup of the Guest Additions don
You should restart your guest to make sure the new modules are actually
Installing the Window System drivers
Installing X.Org Server 1.14 modules don
Setting up the Window System to use the Guest Additions don
You may need to restart the hal service and the Window System (or just r
the guest system) to enable the Guest Additions.
Installing graphics libraries and desktop services components don
linux-6np2:/mnt/vbcliext #
… and as ‘root’ I can now write to and read from the folder. However the usergroup was not created. Anyway I shold be able to figure out to CHMOD the folder for my access … even after having been almost away from Linux for 5 years.
On Sun, 08 Jun 2014 11:56:03 +0000, jazcykel wrote:
> SuSE 11.3
openSUSE 11.3 has been out of support for some time now - it was EOL in
January 2012.
Do you perhaps mean SUSE Linux Enterprise Server/Desktop 11 SP3? That is
actually currently in support.
If that’s what you are using, you’ll want the forums at http:// forums.suse.com - openSUSE and SUSE Linux Enterprise are related, but
they are different enough (not just in the support cycle) that you will
probably get better help there.
If the User really is using SLES or SLED and not openSUSE they should be in the other forums
The topic “as is” actually is independent of the version of openSUSE/SUSE (or other distro for that matter)
I find it interesting it was possible to install VBox additions by simply mounting something called “vbcliext” (is that a typo?). Ordinarily, the easy way to do this is to “Run” the GuestOS from within VBox Manager and either point the virtual CDROM to the VBox additions iso file or use the Menu option (which I’ve found only usually works).
> Although…
> - If the User really is using SLES or SLED and not openSUSE they should
> be in the other forums - The topic “as is” actually is independent of
> the version of openSUSE/SUSE (or other distro for that matter)
I think what I was thinking was if it was something to do with the startup
scripts - SLE uses sysvinit, openSUSE now uses systemd, so the solution
would be different to some extent. But also, if it’s a module issue, the
kernels are quite different at this point.
It’s also important that the user know to make the distinction between
openSUSE and SUSE Linux Enterprise, because they’re not the same.
> I find it interesting it was possible to install VBox additions by
> simply mounting something called “vbcliext” (is that a typo?).
> Ordinarily, the easy way to do this is to “Run” the GuestOS from within
> VBox Manager and either point the virtual CDROM to the VBox additions
> iso file or use the Menu option (which I’ve found only usually works).
But this is interesting to me - I’m not seeing this sort of reference
anywhere, though; can you point me to where you saw this?
The only way I’ve found to install the addons is to have downloaded the
ISO. I’ve actually scripted a first login script that builds them in the
guest for a SUSE Studio image I’m using for some work stuff (the guest is
in fact SLE, and there doesn’t appear to be a pre-compiled set of guest
modules for that guest).
