SliTaz Forum
You are not logged in.
Installing VirtualBox Guest Additions in slitaz 5.0 rc2 and rolling:
(tested with VirtualBox 4.3.18 installed on Host, including the Extensions Pack)
(tested with slitaz-5.0-rc2.iso dated 20140519)
(tested with slitaz-rolling.iso dated 20141025)
- In the slitaz virtual machine make sure you have a working internet connection. I sometimes need to stop/restart eth0 using TazPanel (Slitaz Panel) the first time to get a connection.
- open Package Manager and recharge the package list.
- install the following packages:
[c]linux-module-headers (3.2.53)
mesa-dri
bzip2[/c]
- mount the VBoxAdditions iso using the VirtualBox menu option Devices->Insert Guest Additions CD image...
- in terminal, change directory to the mount point for the VBoxAdditions iso e.g.
[c]cd /media/cdrom/[/c]
- run as root the following command:
[c]sh ./VBoxLinuxAdditions.run[/c]
- ignore text about scripts added to /etc/init.d (installer does not recognize your Linux Distribution etc)
- ignore text about kernel headers for current running version not found
- open terminal as root and issue the following commands:
[c]adduser -h /var/run/vboxadd -G daemon -S -s /bin/false vboxadd >/dev/null 2>&1
addgroup -S vboxsf >/dev/null 2>&1[/c]
- open as root /etc/rcS.conf and add "vboxguest vboxsf vboxvideo" to the LOAD_MODULES line, e.g.
[c]LOAD_MODULES=" vboxguest vboxsf vboxvideo"[/c]
- open as root /etc/slim.conf and change the login_cmd line to start VBoxClient-all before it executes ~./xinitrc, e.g.
[c]login_cmd VBoxClient-all & exec /bin/sh -l ~/.xinitrc %session[/c]
***Note: instead of editing /etc/slim.conf, you could add "VBoxClient-all &" without the quotes to a new line above the CASE 1$ line in each users ~/.xinitrc file.
- reboot
To check that the vbox modules are loaded, open terminal and type
[c]lsmod | grep vbox[/c]
That should show:
[c]vboxguest
vboxsf
vboxvideo
(as well as drm using vboxvideo)[/c]
Also, you can install the mesa-demos package to get the glxgears and glxinfo utilities.
After you install mesa-demos, open terminal and type
[c]glxinfo | grep render[/c]
That should show:
[c]direct rendering: Yes
OpenGL renderer string: Chromium[/c]
glxinfo and glxgears will show a false error:
[c]libGL error: failed to load driver: vboxvideo[/c]
which according to the VirtualBox bugtracker is due to the way vboxvideo hooks itself into the Mesa library instead of being loaded in the normal way by Mesa... so ignore it... if you have OpenGL render = Chromium and direct rendering = Yes then accelerated 3D is supported.
Clipboard sharing Host<=>Guest works if you enable it in the VirtualBox menus or in your virtual machine settings.
Shared folders work (I manually mount the shared folders as/when I need them). For instance, if I wanted to mount the (hypothetical) share called pubdoc and access it as a desktop folder called Docs (make sure the folder exists first) then I issue the following command in terminal as root:
[c]mount -t vboxsf pubdoc /home/tux/Desktop/Docs[/c]
Offline
Does not work with slitaz-rolling-core64.iso dated 20141201.
Do not set VBoxAdditions. 
Offline
I haven't been using the 64 bit version so far so I'm not yet familiar enough with it to know which workarounds are needed (or what is due to any current instability). However, it seems that the steps will eventually be similar to the instructions given in the first post, but you would likely need to install:
[c]linux64-module-headers (instead of linux-module-headers)[/c]
and you would additionally need:
[c]uclibc-cross-compiler-x86_64[/c]
A quick look at the slitaz-rolling-core64.iso dated 20141201, suggests that things are currently a bit unstable (installation to HD required copying the kernel manually from the iso, there seems to be at least a few conf files in /etc which have been trashed and there were some suspect errors/warnings in the logs... which is nothing unusual in a rolling development).
There could possibly be some packages which have yet to be updated/tested/fine-tuned for 64 bit as well.
I'll keep checking back and try to update this topic.
Offline
Hi, pipein!
Work with slitaz-rolling-core.iso dated 01.12.2014.
Next, I set slitaz-rolling-core64 dated 05.12.2014
I installed packages linux64-module-headers, mesa-dri, bzip2, uclibc-cross-compiler-x86_64-prebuilt.
But, unfortunately, did not happen again.
Messages from the terminal Sakura:
Offline
Many thanks Pipein. Very accurate doco and no problems getting it all working.
Offline
pipein,
what are these commands:
[c]adduser -h /var/run/vboxadd -G daemon -S -s /bin/false vboxadd >/dev/null 2>&1
addgroup -S vboxsf >/dev/null 2>&1[/c]
Secondly:
I install the following packages:
[c]1. bzip2;
2. linux-api-headers;
3. linux-module-headers.
[/c]
works with slitaz-rolling-core.iso dated 05.12.2014.
Offline
Ref:
http://forum.slitaz.org/topic/question-about-50#post-32722
Note:
* slitaz-roll-core64
1. Distro: rolling-core64
http://cook.slitaz.org/cookiso.cgi?distro=rolling-core64
Description: 64 bits kernel with a fully featured 32 bits desktop.
Offline
@black dog
the adduser command adds user ID vboxadd as a System user to the daemon group... this (or similar) is normally done by the installer for supported distros.
the addgroup command adds a new System group <vboxsf> for the shared folder service... this (or similar) is normally done by the installer for supported distros.
You don't (shouldn't) need to install the linux-api-headers package as it is a dependency of linux-module-headers (and also a dependency of linux64-module-headers) so it will be automatically installed if you use the Package Manager or tazpkg -gi packagename.
The instructions (for 32bit versions of SliTaz which are at least at Release Candidate stage) in the first post will give you working shared folders, bidirectional clipboard, mouse integration, hardware direct rendering (3d support) etc. The mesa-dri package provides 2 files which help enable the direct rendering (firstly it provides the software direct rendering library, but also the Guest Additions installer looks for these files when setting up some links to the VBox DRI files etc so that Xorg loads the DRI modules).
The 64bit version of SliTaz doesn't seem to have reached Release Candidate stage yet so the chances of an immediate solution are probably slim at the moment. Currently it seems to use a mix of 64 bit kernel and 32 bit userland (at least some), which isn't supported by VirtualBox (or wasn't last time I looked). They support "Pure 64 bit" only.
Maybe combining the 64bit VirtualBox kernel modules, and 32 bit everything else will work to some extent... it wouldn't be advised.
I'll keep checking back.
Offline
@alanyih
I should've waited a few minutes and I would've seen your reply! Thanks for the reference to the 64bit/32bit mix.
Offline
If you specifically need a 64bit OS for some reason, then it could be a matter of either waiting for VirtualBox to start to support mixed systems (64bit Kernel with 32bit userspace), or waiting for a pure 64bit flavor of SliTaz if it happens in the future (or multilib support?), or maybe some patches will come along.
Otherwise, if you only wanted a 64bit OS to address more than 4gig of RAM, then a 32bit PAE kernel could offer you something (with working guest additions).
I haven't been able to find any patches or workarounds for getting the Guest Additions to work in environments similar to the current 64bit SliTaz environment. Brutally copying the /opt/VBoxGuestAdditions-X.Y.Z folder from a 32bit build (and keeping the 64bit kernel modules in /lib/modules/3.2.53-slitaz64) did improve things slightly, but the install includes several precompiled architecture specific files which aren't entirely happy being transplanted, such as VBoxControl and VBoxService.
I'm only a user (not a developer) so I'm not familiar with the VBox code itself or the specifics of the 64bit/32bit situation in it... and I haven't yet needed a 64bit version of SliTaz in a virtual machine with guest additions.
I'll check some more when I get some time and see if anything turns up.
Offline
What concerns me.
I would not want anyone to think that a 64-bit version Slitaz for me a matter of life or death. That's not it.
I have a machine supports 64-bit architecture and has 16 GB of memory. I installed Slitaz on VirtualBox. I learn Slitaz, as we say, in Russia, of "purely sporting interest." In real life, I use Lubuntu-14.04.
Now version slitaz-rolling-core64 dated 05.12.2014.
tux@slitaz:~$ lsmod | grep vbox
vboxvideo 1733 0
drm 154213 1 vboxvideo
vboxsf 29925 0
vboxguest 161269 1 vboxsf
But it works only mouse integration.
I apologize. I forgot to thank pipein and alanyih. 
Offline
Ref:
boot2docker
# Build VBox guest additions
# For future reference, we have to use x86 versions of several of these bits because TCL doesn't support ELFCLASS64
# (... and we can't use VBoxControl or VBoxService at all because of this)
ENV VBOX_VERSION 4.3.18
RUN mkdir -p /vboxguest && \
cd /vboxguest && \
\
curl -L -o vboxguest.iso http://download.virtualbox.org/virtualbox/${VBOX_VERSION}/VBoxGuestAdditions_${VBOX_VERSION}.iso && \
7z x vboxguest.iso -ir'!VBoxLinuxAdditions.run' && \
rm vboxguest.iso && \
\
sh VBoxLinuxAdditions.run --noexec --target . && \
mkdir amd64 && tar -C amd64 -xjf VBoxGuestAdditions-amd64.tar.bz2 && \
mkdir x86 && tar -C x86 -xjf VBoxGuestAdditions-x86.tar.bz2 && \
rm VBoxGuestAdditions*.tar.bz2 && \
\
KERN_DIR=/linux-kernel/ make -C amd64/src/vboxguest-${VBOX_VERSION} && \
cp amd64/src/vboxguest-${VBOX_VERSION}/*.ko $ROOTFS/lib/modules/$KERNEL_VERSION-tinycore64/ && \
\
mkdir -p $ROOTFS/sbin && \
cp x86/lib/VBoxGuestAdditions/mount.vboxsf $ROOTFS/sbin/
# Make sure that all the modules we might have added are recognized (especially VBox guest additions)
RUN depmod -a -b $ROOTFS $KERNEL_VERSION-tinycore64
Offline
@black dog - thanks. Pity there is no complete solution for you so far. Those modules you listed are the 64 bit kernel modules which build and load successfully, however much functionality will be missing as there are a number of other components of the install which are precompiled and are not compatible with the mixed 64bit/32bit environment as it currently stands (or so it seems).
@alanyih - thanks for the find. I take that to confirm the findings so far (... ie currently no complete solution for a 64bit kernel/32bit userland system). That script describes a similar process that I had tried (though I was much less elegant) in using the default 64bit kernel modules but replacing the components in /opt/VBoxGuestAddition-x.y.z with the 32bit versions from the tarball. Without working VBoxControl and VBoxService there is a lot of functionality still missing (although mouse integration and shared folders work).
If that is the case then I don't know how to get around this without either the VirtualBox code becoming "bit clean", or SliTaz64 having a pure 64bit flavor, or a flavor which supports both 32 and 64 bit (with the issues of dual paths, dual glibc etc... which could be in conflict with the intention of SliTaz being a small).
Of course, I could be missing the obvious here.
Offline
@pipein
or SliTaz64 having a pure 64bit flavor
http://forum.slitaz.org/topic/slitaz-50-release-date/page/2#post-29501
root@slitaz:~# spk info
Spk info
================================================================================
Architecture : x86_64
Database : /var/lib/tazpkg/installed
Cache info : 0 /var/cache/tazpkg
Mirror URL : http://192.168.1.42/slitaz/x86_64/packages/
Extra mirrors : 0
Installed : 20
Mirror : 121
packages-x86_64-178-list
http://goo.gl/ipYRQN
20140306-x86_64-packages-178.tar.gz
http://goo.gl/qeKt6o
Offline
20140306-x86_64-packages-178.tar.gz
Ref:
http://forum.slitaz.org/topic/slitaz-docker-support/page/2#post-35096
Offline
Yes !!
It Works very well
thanks a lot and viva Slitaz
:-)
Franck
Offline
Gents,
I was following this quite good HowTo, but unfortunately the modules that are compiled do not load.
Looks like they are compiled for a wrong version, which is more recent that the kernel 5.0-RC3.
When I start the VBoxLinuxAdditions.run it gives me:
.....
Starting the VirtualBox Guest Additions ...fail!
(modprobe vboxguest failed)
....
and dmesg is saying:
vboxguest: version magic '3.2.71-slitaz SMP mod_unload 386 ' should be '3.2.53-slitaz SMP mod_unload 386 '
I have loaded the packages from the official repository via the tazpkg manager, so how can it be that the version is not matching ?
modprobe is coming back withthe famous:
modprobe: ERROR: could not insert 'vboxguest': Exec format error
Anyone having had this before ? uname -r is confirming Iḿ on kernel "3.2.53-slitaz", so I don know how I can get the wrong modules compiled ...
Did some Linux in my earlier days, but just started on Slitaz (qiote inetersting !)
Any advice is highly appreciated !
Offline
please allow me to correct my own stupid mistake here ....
the kernel simply had to be upgraded as well, so upgrading the package "Linux" was enough to solve it.
All perfect now, thanks for your Patience.
Offline
[ Generated in 0.016 seconds, 7 queries executed - Memory usage: 1.58 MiB (Peak: 1.77 MiB) ]