SlackwareThis Forum is for the discussion of Slackware Linux.
Notices
Welcome to LinuxQuestions.org, a friendly and active Linux Community.
You are currently viewing LQ as a guest. By joining our community you will have the ability to post topics, receive our newsletter, use the advanced search, subscribe to threads and access many other special features. Registration is quick, simple and absolutely free. Join our community today!
Note that registered members see fewer ads, and ContentLink is completely disabled once you log in.
Unix
ACPI CA - Unix Build Environment (.TAR.GZ 819KB)
This provides the basic implementation, which OSV's may integrate into their products as they see fit.
5) Make the following symlink (unless you find a better way):
Code:
cd /usr
mkdir qt
cd qt
ln -s /usr/lib/qt-3.3.6 3
or that last line could be
Code:
ln -s /usr/lib/qt 3
as long as '/usr/lib/qt' is linked to some version of qt-3.x.x
6) You are ready to build Vbox, so compile it as follows:
Code:
LIBRARY_PATH=/usr/X11R6/lib ./configure
For the rest you can follow the guide here starting with step 2 (you can also find all dependencies there in case you need them, most should already come with slackware standard install): http://www.virtualbox.org/wiki/Linux...20instructions
Which would be, after the configure above:
Code:
source ./env.sh
kmk
# or 'kmk all' which will take a while as this is the compile step
# the following builds a kernel module, so make sure you installed the kernel sources
cd out/linux.x86/release/bin/src
make
su
<Enter root password>
make install
cd ..
modprobe vboxdrv
# now you should give yourself read/write access to /dev/vboxdrv, I think the best way to do this is to chown it, but you can also chmod it, so you can do either or both:
chmod a+rw /dev/vboxdrv
# AND/OR
chown $USER:users /dev/vboxdrv
exit # back to regular user so you can't mess too much up
LD_LIBRARY_PATH=. ./VBoxSVC&
LD_LIBRARY_PATH=. ./VirtualBox
And now it should work. Good Luck with all that
Last edited by H_TeXMeX_H; 01-22-2007 at 08:24 PM.
A third way to get the required access writes to /dev/vboxdrv is to make your user a member of group vboxdrv.
(However, that's what I did, and I still don't have it working the way I want; VirtualBox GUI runs, creating a virtual machine was smooth, but I am unable to install a system on it; I am just asking for help on the vbox users newsgroup, and report back, when I have a solution)
Seems I got my problem solved, thanks to the really great support from the InnoTek guys on their users newsgroup. Very competent, responsive and friendly!
It's not 100% assured, but most likely some notifying daemon of KDE blocked the VBox daemon from accessing the installation CD.
To confirm (or deny) this, I'd be interested, what desktops/window managers you use, as you don't seem to have the same problem. I suspect it's not Gnome or KDE, is it?
That seems to confirm my guess: My problem was caused by some KDE daemon. After stopping the daemon it worked.
Fluxbox runs no such daemon, so that's why it worked better for you than me.
5) Make the following symlink (unless you find a better way):
Code:
cd /usr
mkdir qt
cd qt
ln -s /usr/lib/qt-3.3.6 3
or that last line could be
Code:
ln -s /usr/lib/qt 3
as long as '/usr/lib/qt' is linked to some version of qt-3.x.x
6) You are ready to build Vbox, so compile it as follows:
Code:
LIBRARY_PATH=/usr/X11R6/lib ./configure
For the rest you can follow the guide here starting with step 2 (you can also find all dependencies there in case you need them, most should already come with slackware standard install): http://www.virtualbox.org/wiki/Linux...20instructions
Which would be, after the configure above:
Code:
source ./env.sh
kmk
# or 'kmk all' which will take a while as this is the compile step
# the following builds a kernel module, so make sure you installed the kernel sources
cd out/linux.x86/release/bin/src
make
su
<Enter root password>
make install
cd ..
modprobe vboxdrv
# now you should give yourself read/write access to /dev/vboxdrv, I think the best way to do this is to chown it, but you can also chmod it, so you can do either or both:
chmod a+rw /dev/vboxdrv
# AND/OR
chown $USER:users /dev/vboxdrv
Or you make your user a member of group vboxusers:
Code:
# usermod -G vboxusers <username>
Note that you should list all groups your users is supposed to be a member of. If you only mention one group, the user will be removed from any other groups he's currently a member of.
In case you want to use a CD or DVD drive from within your guest, no media must be mounted and your user must have read/write access to the device file. Usually there's a softlink /dev/cdrom or /dev/dvd or /dev/dvdwriter pointing to the relevant device file, so you should be able to easily identify it.
Depending on your environment, you are all set now. If you are using Fluxbox or any other window manager that doesn't run its own damons, skip the next paragraph.
However, if you use KDE (and for Gnome I would expect the same, but haven't tried it), read on here.
Even if no media is mounted (it may be inserted), and your user has read/write access to the device file, it still may happen that the VirtualBox daemon cannot access it. This indicated by error messages containing the string "VERR_ACCESS_DENIED". This may be an indication that some daemon in your system is trying to access the device, thus blocking the VirtualBox daemon from doing so. Typical examples are the media management and device notifying daemons in KDE. In case you see error messages with "VERR_ACCESS_DENIED" try stopping these daemons, stop VirtualBox GUI and daemon, log off from your X session, have a cup of tea, and maybe another one, and then log in again. The cup of tea is vital, as it can the system well take a few minutes to remove lock files etc.
Quote:
Originally Posted by H_TeXMeX_H
Code:
exit # back to regular user so you can't mess too much up
LD_LIBRARY_PATH=. ./VBoxSVC&
LD_LIBRARY_PATH=. ./VirtualBox
And now it should work. Good Luck with all that
Setting up a guest shouldn't be too complicated, from here. Just have the GUI application guide you.
However, when your guest is up and running you might want to exchange data between it and your host. However, the open source edition 1.3.3 of VirtualBox doesn't support USB or CD/DVD writing. But you can use scp. It's up to you, which scp program you want to use. I prefer 'the real thing', so downloaded and installed the Cygwin tools in my guest. Note, that the connection can only be originated on the guest.
If you have a NAT configuration, Windows XP will get something like 10.0.2.15. This address is not 'seen' by the host. But the host address is seen by the guest. Assuming the host address is 192.168.22.10, a command like
Code:
scp file user@host:/target/directory/
should work just fine. With this simple and familiar command you can transfer data created on the guest to your host, for backups, archiving and further processing.
I managed that also. I just renamed a tgz cd image to iso and VirtualBox accepted it without any problems.
But when I start the vm (windows xp), I get following error
1908 VERR_VM_DIRVER_NOT_INSTALLED
but in my lsmod, I can see the vboxdrv is loaded.
I know this is more a question for the VBox forum, and I will surely ask it there itself, but from my office I dont have access to those forums, so I will ask it after I am back home.
I managed that also. I just renamed a tgz cd image to iso and VirtualBox accepted it without any problems.
But when I start the vm (windows xp), I get following error
1908 VERR_VM_DIRVER_NOT_INSTALLED
but in my lsmod, I can see the vboxdrv is loaded.
I know this is more a question for the VBox forum, and I will surely ask it there itself, but from my office I dont have access to those forums, so I will ask it after I am back home.
thanks and regards,
Hardik
Actually I'd expect a different error message, if this was the problem, but does your user have read/write access to /dev/vboxdrv?
There is already a (french) SlackBuild here : forum.slackbuilds.net/viewtopic.php?id=328
[Sorry, that's my first reply and I can't post a link :-(]
Thanks for the pointer, however, although my French is ... absent, to say the least, if get it right, this SlackBuild script is intended for repackaging the closed source version, and not for building the open source edition of Virtual Box. I may be wrong, though.
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.
