Ah.
I didn't pay much attention to the difference before I downloaded. Thanks for pointing it out. When it works it's nice. After my previous post I had to modify my script a bit - just take off the last line that says ./VirtualBox because it was killing the daemon. It can also be modified to add any VBOX_FLOPPY or VBOX_CDROM lines.

The licensed version of VirtualBox is now available in version 1.3.4 with a modified installer for Slackware. The only thing to do is to add some lines to /etc/rc.d/rc.local, but these lines are shown at the end of the installation process.

Fluxx.

P. S.: USB is working quite good within the guest system.

I just found out a this morning when checking the site. Indeed, it installs onto Slackware without any errors (I still haven't had to add libxalan-c and libxerces-c) and displays the lines to add to rc.local. I haven't had a chance to try it yet, but when I do I'm gonna check out the improved usb device filters, alsa sound and see if I can share host folders. I couldn't get folder sharing to work with 1.3.2.

Where can I find the modified installer for Slackware to download ?

On the virtual.org website I can only find the following versions for Linux:

VirtualBox 1.3.4 for Linux Hosts:
* Ubuntu 6.10 ("Edgy Eft")
* Ubuntu 6.06 LTS ("Dapper Drake")
* Debian 3.1 ("Sarge")
* Debian 4.0 ("Etch")
* All distributions

Can you please post the link for the Slackware version ?

Thanks in advance.

Under

* All distributions

you will find the package/file "VirtualBox_1.3.4_Linux_x86.run".

Download this file and run it with

and the installer will install the files and binaries to /opt/Virtualbox-1.3.4 ...

Fluxx.

OK. Thanks.

I will do it.

See you.

I've installed the binary version of VirtualBox 1.3.8. But it didn't work. Each time i start a vm, it's just a black screen, nothing happen.
Can any one help me ?

Have you tried to install anything yet? When you start a new vm it's just like a new computer - no os until you install one.

I don't think i can install anything while it's just a black screen.
I've tried Ubuntu CD and some ISO liveCD image but nothing happened.

1) Go into the vm settings in the CD section and check to mount the cd drive or iso?

2) Right-click on the CD icon in the status bar and select the the cd drive or iso, then reboot with RCtrl+R.

You have to do one of those or it's going to ignore a CD. Same goes with booting a floppy disk.

EDIT: I should've asked this first. Are you getting the INNOTEK logo before the screen goes blank?

No ! It's just black screen.

I haven't seen that happen without displaying an error to indicate the cause. Do you have the kernel module loaded? Is your user a member of the vboxusers group? Did you start VboxSVC before VirtualBox? For mine, before running VBoxSVC I have to run

export LD_LIBRARY_PATH=/opt/VirtualBox

/opt/VirtualBox is really a link to /opt/VirtualBox-1.3.8 and I just change the link whenever I upgrade. I made a small script to start the daemon

#!/bin/bash
export LD_LIBRARY_PATH=/opt/VirtualBox
cd /opt/VirtualBox
VBoxSVC &


and run it before running the VirtualBox executable. I hope this helps.

Hi all,

I just found VirtualBox yesterday, and it really looks cool.......

Then I had a thought about using some minimal Linux install for a VB server to run all my OSes in......FreeBSD, Linux, and WinXP MCE......

There are times when I have to switch between one or the other, quite a bit recently, and I'm hoping to be able to run them in virtual mode and be able to use the host as a fileserver as well as a VB server....

The main requirements for the host would be to have a very small memory footprint, yet not be dependant on the Busybox binary, although using ulibc or dietlib would be okay, and be able to run ftp/web servers.......

I've narrowed the field down to two contenders, PuppyLinux and RIPLinux..........They both have X servers (a requirement for VB), both run entirely in RAM, thus freeing up any needed devices (and not to mention being very fast and responsive), and both can be configured to boot from a USB device which is also a highly attractive feature..........

PuppyLinux has a smaller footprint due to running a compressed root filesystem in RAM, but is not up to par for running any type of server (according to developer, but it's still a young distro) and is more a lightweight desktop-oriented distro......It does take a modular approach where you can add apps to it easily enough, though, without having to remaster it and can save any custom configurations to disk (even to a multisession CD/DVD).......

RIPLinux, being a Slackware-based rescue distro, has the ability to run servers, with the added benefit of being able to rescue/repair other OSes, is also modular in that to add anything you must remaster it, yet provides an easy to use script to do so........But ,AFAIK, it doesn't have the ability to save any custom configurations, since it's role is more a rescue OS, not an desktop one......

But I don't know enough about VB to venture a guess about being able to run it as a virtual firewall "router" (using the term router somewhat loosely, here), which is also another feature I'm looking for..........I mean, hosting businesses do have virtual dedicated servers running UML on one single machine, why not a virtual firewall "router" running various OSes on the same machine, too?.........

This idea also appeals to me if I also want to try out other distros/OSes very easily, and developers can also test their code on different OSes without having to reboot or use another machine...........In fact, I can see virtual technology as being the future of computing........

I think I'm going to start with RIPLinux for the hosting OS, and am very interested in any input anyone has to offer............And I'll also keep you posted on my progress, probably starting another thread dedicated to this project I'm starting......

:-)
---thegeekster

It still a black green. :confused:

I'd say that although virtualbox, and other virtual machine are quite good. They don't always run right. Some distros just have problems running in a VM, or rather the virtual machine has problems running them.

As for the black or green screen. Try the virtualbox forums. They are specialized in dealing with this type of stuff.

Of course there will be rough edges, but it can only get better as time goes on...... :)

In the meantime, I'm going to do what little I can to help the technology mature (and get in on the ground floor).... ;)

Just for the record, I'm about to try VirtualBOX on the fresh 12.0 this week.
las night I did make a try but failed to fetch xalan-c (no internet on that box :-(,... so today reload and redo...
I'll post anything new here, and if I mak it run, may be I'll post the packaged vesion somewhere too...

Great thread.

I found xalan or xerces not necessary. It might be different if you use the open source version as opposed to the binary. The binary is free for non-commercial use and is fully functional. The "any distribution" version works perfectly i Slackware. The only thing I have trouble with is shared directories. I've only gotten it to work between a linux host and windows guest. I just haven't messed with samba to try it with a linux guest. Internet sharing works perfectly with minimal effort under the guest as long as you use NAT for the virtual nic.

Virtual machine
 

Well I wanted few things:
I want:
1. Virtual host that has servers accepting connections (game server)
2. Guest OS that is portable in spite of hardware-bound by license/md5 ( eg. Xp or MikroTik OS)
3. Virtual to real interface routing/mapping
4. I might want to run multiple virtual hosts at once
I do not want:
1. to carry the cost of development by paying expensive licenses
2. To have a binary VMsoftware that breaks when upgrading the host OS
3. Limitation of commercial/educational use

The question:

Can I compile VirtualBOX on Slackware 12.0 with gcc 4.1.x as it seems unsupported by the developers?
Is there a option for gcc4.1.x to make the V-BOX (a special option or something)?

yes, there is, you can use gcc 3.4 that can be found at http://slackware.com/~alien/slackbuilds/gcc34/pkg/12.0/

as this topic seems to be out of date, i won't write anything else;)
anyway, i managed to compile and run vbox from sources (OSE) on Slackware 12.0. if anybody is interested, please post here.

best regards

An step by step guide is missed every since.

I made the VMWare server, but missed the VirtualBox as it wouldn't bild

:-(

atelszewski, this thread isn't out of date :).
So how did you managed to get vbox from source working under Slack 12.0 ?
I use 2.6.24 and i installed all dependencies, but kmk fails:

kBuild: Compiling VBoxREM - /home/def/VirtualBox-1.5.4_OSE/out/linux.x86/release/obj/src/recompiler/VBoxREM/op.S
kBuild: dyngen VBoxREM - /home/def/VirtualBox-1.5.4_OSE/out/linux.x86/release/obj/src/recompiler/VBoxREM/gen/op.o
kBuild: dyngen VBoxREM - /home/def/VirtualBox-1.5.4_OSE/out/linux.x86/release/obj/src/recompiler/VBoxREM/gen/op.o
kBuild: dyngen VBoxREM - /home/def/VirtualBox-1.5.4_OSE/out/linux.x86/release/obj/src/recompiler/VBoxREM/gen/op.o
kBuild: Compiling VBoxREM - translate-all.c
kBuild: Compiling VBoxREM - translate-op.c
kBuild: Compiling VBoxREM - target-i386/translate.c
In file included from /home/def/VirtualBox-1.5.4_OSE/src/recompiler/translate-op.c:70:
/home/def/VirtualBox-1.5.4_OSE/out/linux.x86/release/obj/src/recompiler/VBoxREM/op.h: In function ‘dyngen_code’:
/home/def/VirtualBox-1.5.4_OSE/out/linux.x86/release/obj/src/recompiler/VBoxREM/op.h:4686: erreur: ‘memcpy’ redeclared as different kind of symbol
/home/def/VirtualBox-1.5.4_OSE/out/linux.x86/release/obj/src/recompiler/VBoxREM/op.h:4687: erreur: called object ‘memcpy’ is not a function
/home/def/VirtualBox-1.5.4_OSE/out/linux.x86/release/obj/src/recompiler/VBoxREM/op.h:4703: erreur: called object ‘memcpy’ is not a function
/home/def/VirtualBox-1.5.4_OSE/out/linux.x86/release/obj/src/recompiler/VBoxREM/op.h:4720: erreur: called object ‘memcpy’ is not a function
/home/def/VirtualBox-1.5.4_OSE/out/linux.x86/release/obj/src/recompiler/VBoxREM/op.h:4736: erreur: called object ‘memcpy’ is not a function
/home/def/VirtualBox-1.5.4_OSE/out/linux.x86/release/obj/src/recompiler/VBoxREM/op.h:4752: erreur: called object ‘memcpy’ is not a function
/home/def/VirtualBox-1.5.4_OSE/out/linux.x86/release/obj/src/recompiler/VBoxREM/op.h:4893: erreur: called object ‘memcpy’ is not a function
/home/def/VirtualBox-1.5.4_OSE/out/linux.x86/release/obj/src/recompiler/VBoxREM/op.h:4909: erreur: called object ‘memcpy’ is not a function
/home/def/VirtualBox-1.5.4_OSE/out/linux.x86/release/obj/src/recompiler/VBoxREM/op.h:4925: erreur: called object ‘memcpy’ is not a function
/home/def/VirtualBox-1.5.4_OSE/out/linux.x86/release/obj/src/recompiler/VBoxREM/op.h:4941: erreur: called object ‘memcpy’ is not a function
/home/def/VirtualBox-1.5.4_OSE/out/linux.x86/release/obj/src/recompiler/VBoxREM/op.h:5041: erreur: called object ‘memcpy’ is not a function
/home/def/VirtualBox-1.5.4_OSE/out/linux.x86/release/obj/src/recompiler/VBoxREM/op.h:5057: erreur: called object ‘memcpy’ is not a function
/home/def/VirtualBox-1.5.4_OSE/out/linux.x86/release/obj/src/recompiler/VBoxREM/op.h:5073: erreur: called object ‘memcpy’ is not a function
/home/def/VirtualBox-1.5.4_OSE/out/linux.x86/release/obj/src/recompiler/VBoxREM/op.h:5089: erreur: called object ‘memcpy’ is not a function
/home/def/VirtualBox-1.5.4_OSE/out/linux.x86/release/obj/src/recompiler/VBoxREM/op.h:5106: erreur: called object ‘memcpy’ is not a function
/home/def/VirtualBox-1.5.4_OSE/out/linux.x86/release/obj/src/recompiler/VBoxREM/op.h:5120: erreur: called object ‘memcpy’ is not a function
/home/def/VirtualBox-1.5.4_OSE/out/linux.x86/release/obj/src/recompiler/VBoxREM/op.h:5134: erreur: called object ‘memcpy’ is not a function
/home/def/VirtualBox-1.5.4_OSE/out/linux.x86/release/obj/src/recompiler/VBoxREM/op.h:5148: erreur: called object ‘memcpy’ is not a function
/home/def/VirtualBox-1.5.4_OSE/out/linux.x86/release/obj/src/recompiler/VBoxREM/op.h:7129: erreur: called object ‘memcpy’ is not a function
/home/def/VirtualBox-1.5.4_OSE/out/linux.x86/release/obj/src/recompiler/VBoxREM/op.h:7218: erreur: called object ‘memcpy’ is not a function
/home/def/VirtualBox-1.5.4_OSE/out/linux.x86/release/obj/src/recompiler/VBoxREM/op.h:7307: erreur: called object ‘memcpy’ is not a function
kmk[2]: *** [/home/def/VirtualBox-1.5.4_OSE/out/linux.x86/release/obj/src/recompiler/VBoxREM/translate-op.o] Error 1
The failing command:
@gcc -c -O2 -Wall -g -fomit-frame-pointer -fno-gcse -IInnoTek -IInnoTek/crt -Itarget-i386 -Ifpu -I/home/def/VirtualBox-1.5.4_OSE/out/linux.x86/release/obj/src/recompiler/VBoxREM -I/home/def/VirtualBox-1.5.4_OSE/src/VBox/VMM -I/home/def/VirtualBox-1.5.4_OSE/src/recompiler -I/home/def/VirtualBox-1.5.4_OSE/include -I/home/def/VirtualBox-1.5.4_OSE/out/linux.x86/release -DVBOX -DVBOX_WITHOUT_IDT_PATCHING -DVBOX_OSE -DRT_OS_LINUX -D__LINUX__ -D_FILE_OFFSET_BITS=64 -DRT_ARCH_X86 -D__X86__ -DIN_REM_R3 -DREM_INCLUDE_CPU_H -DIN_RING3 -DLOG_USE_C99 -D_GNU_SOURCE -D_FILE_OFFSET_BITS=64 -D_LARGEFILE_SOURCE -D_REENTRANT -Wp,-MD,/home/def/VirtualBox-1.5.4_OSE/out/linux.x86/release/obj/src/recompiler/VBoxREM/translate-op.o.dep -Wp,-MT,/home/def/VirtualBox-1.5.4_OSE/out/linux.x86/release/obj/src/recompiler/VBoxREM/translate-op.o -Wp,-MP -o /home/def/VirtualBox-1.5.4_OSE/out/linux.x86/release/obj/src/recompiler/VBoxREM/translate-op.o /home/def/VirtualBox-1.5.4_OSE/src/recompiler/translate-op.c
kmk[2]: *** Waiting for unfinished jobs....
kmk[2]: Leaving directory `/home/def/VirtualBox-1.5.4_OSE/src/recompiler'
kmk[1]: *** [pass_dlls_before] Error 2
kmk[1]: Leaving directory `/home/def/VirtualBox-1.5.4_OSE/src'
kmk: *** [pass_dlls_before] Error 2
bash-3.1$

hi,
what about gcc version? do you use the default (4.1.2) shipped whit slackware? if so, then the compilation will surely fail. try using gcc 3.4.

best regards,
atelszewski

Indeed ! gcc 3.4 did it perfectly and i can see the difference with the pre-built version.
Many thanks, atelszewski !!!

Hi,

I'm glad I could help:) I'm thinking of writing SlackBuild, but here comes my studies to eat up all my time;)

Best regards

Hi,

I choose the difficult part of compiling my own Virtual Box. I am able to follow the procedures given in the beginning of the thread. However, I compiled stalled due to the IASL (Intel ACPI compiler).

It does not have a make install and hence I do not know how to tell the Virutualbox ./configure how to find the IASAL. Can anyone let me know how you do it ?

Thanks.


distrubtion: migrated from fedora to slackware

You can use my SlackBuild from SlackBuilds.org.

http://slackbuilds.org/repository/12...opment/acpica/

Most of the other deps are there as well, only one missing for the most recent version is pulseaudio and its dependencies.
I have a made a SlackBuild for those too, but don't consider them stable yet. A build script for VirtualBox is also in the works :).

Good Luck!

wow, great work. i guess one day this will became the repository for slackware. one suggestion you could provide compressed packgage for slax as well.

another thing i noticed is ..
if i change the url http://slackbuilds.org/repository/12...opment/acpica/
to http://slackbuilds.org/repository/11...opment/acpica/

the page has empty values for
Approved by:

may be the webmaster can remove it dynamically.

i have another doubt. what is a slacbuild ? please let me know if you have time.

best regards

That's because there is no version for Slackware 11. But you're right. Some indication for that might be good.

No problem, but I'm really bad in describing such things. Take a look at http://slackwiki.org/SlackBuild_Scripts.
It's a really good description.

Cheers

Hi,

I'm interested:) Where are you going to put binaries? I mean under /opt or /usr? I know that the output files of vbox build process are quite weird... But also found that, moving *.la under /usr/lib and running ldconfig works, so maybe it is possible to keep files tight and having them under /usr?

Best regards

Here it is: http://hw.3kisses.net/sbo/sbo.php

For pulseaudio-support, you'll need the liboil, libatomic_ops and pulseaudio package from the same site.
If you don't want support for it, you can call the build-script like that: "PULSE=no ./virtualbox-ose.SlackBuild"
It uses alienBOB's gcc34 compat packages.

The necessary kernel-module is a separate package, which makes it easier to upgrade to a new kernel.

You can probably see now yourself ;). All the stuff is under /opt/vbox, with links to a wrapper script in /usr/bin.

I'm thankful for any feedback :).
Have fun!

A few weekends ago I successfully installed VirtualBox 1.5.6. I used the script package from slacky.eu. I had to modify the build script to use GCC 3.4:

--with-gcc=/usr/gcc34/bin/gcc34 \
--with-g++=/usr/gcc34/bin/g++34 \

With that modification the script ran without error. I recommend others who are interested in VirtualBox to try the build package at slacky.eu, which contains all the dependency files too.

I tried to get qemu to work with my new box, but I never got kqemu working. I never had error messages, and info kqemu always showed kqemu running. Yet the on screen response I received indicated the accelerator was not working.

My new box uses an AMD BE-2400, which supports hardware virtualization. Enabling the kvm-amd module was straightforward and VirtualBox uses that module if found. Fast and nice.

I am impressed with the VirtualBox user interface. I don't mind the command line, but I like seeing a well designed interface for those who don't like the command line.

I realize there are front-ends for qemu, but VirtualBox is a joy to experiment with. Very fast on my new box.

Eventually I expect to migrate my Windows box to my new box. I still need to maintain Windows for professional and personal reasons, but VirtualBox will finally allow me to migrate to Slackware as my primary OS and run Windows in a virtual machine. :)

Many thanks to the slacky.eu community. :cool::Pengy:

Hi there,
Now I came into some problematic situation, and can't compile vbox anymore;)
GCC version 3.4 of course, slackware 12 up-to-date. While compiling I get:
And here's some lines from configure.log:
Any ideas?

Best regards,
atelszewski

On my box /usr/lib/qt is soft linked to qt-3.3.8 (/usr/lib/qt-3.3.8).
Check for that same soft link and check for /usr/lib/qt-3.3.8. If the latter does not exist, you can install the package from the stock Slackware packages. qt-3.3.8 is in the l set of packages.

Hi,

I've got that link and qt properly installed, and it doesn't help. Furthermore, if I don't pass the gcc location to ./configure, it configures without problems (but gcc version remains 4.x so it will fail to compile). When I pass gcc 3.4 location, then I also need to pass the location of xalan and xerces, even though they are in default locations (/usr/lib). Any ideas?;)

Best regards,
atelszewski

Is /usr/gcc34/bin in your path?

I did a bit of research on the net. What I found is that it is a gcc issue. Solution posted was to remove all but one gcc but I guess that doesn't count here ;). It might be that gcc34 is trying to build with a wrong libstdc++, but this is just a guess. Maybe someone with more insight on such things can help.

Bug report to gentoo with a similar issue: http://bugs.gentoo.org/show_bug.cgi?id=200923
duplicate of: http://bugs.gentoo.org/show_bug.cgi?id=64615

Hi,

Yes, it is (was).

Every working solution counts;)
I removed the GCC 4 and installed GCC 3 from /pasture on Slackware CD. Now compilation fails at this point:
And probably here is the answer. I actually use 2.6.25. Now I'll try to downgrade and see what'll happen. I found that, some binaries were built.

Best regards,
atelszewski

It would probably be easier to setup Slackware 12.0 in a VM, downgrade what is needed there, build a package, and then copy the package to your real setup (just so you won't mess something up -- after all, you're downgrading some major packages here). Just a suggestion though.

This sounds like a really cool suggestion ;). Problem about it is, that the app he probably uses for such VMs doesn't compile...
( He could use vmware though)

tgz package - http://www.slacky.eu/index.php?optio...5232&Itemid=56

ppr:kut, lol, I must have been loopy when I wrote that. You know, just use the VM you are hoping to compile in order to compile your VM. Simple stuff really. ;)

Hi,

Sounds nice;) Actually, it is possible, with success I'm using the slacky.eu package mentioned before, but it looks like it misses VRDP. And what is more, I want it compiled on my own;) Seems like I'm not so far to reach it.
vmware works very slowly for me (laptop, 512mb, P4-M 2.66GHz), probably because of disk. The friend of mine runs vmware on some 1GHz+ celeron, and it works quite well, so I'm not going to make a comparison here (but still, vbox works faster for me).
Yes and no:) Because in Slackware there are no dependencies, so uninstalling GCC4 and installing GCC3 seems like simple file exchange, the same applies to the kernel, when you know what you're doing.

Ok, many words up there:) If I successfully compile vbox, just will let you know (in a case you were curious:)).

Best regards,
atelszewski

Finally, I was able to compile, providing the followings were met:
- Linux kernel 2.6.24.5 (custom)
- kernel-headers 2.6.21.5 (Slackware 12.0 default)
- acpica-20080213 (slackbuilds.org)
- dev86-0.16.15 (slackbuilds.org)
- icu4c-3.8.1 (slackbuilds.org)
- xerces-c-2.8.0 (slackbuilds.org)
- xalan-c-1.10.0 (slackbuilds.org)
All above were compiled with GCC 4.1.2. I don't know if the xalan, xereces, etc. versions matter, I used those found at slackbuilds.org at the moment.

And just before compiling vbox itself, I uninstalled GCC4 and installed GCC 3.4.6 from /pasture.

Best regards,
atelszewski

Now I get that error too when trying to compile Virtualbox on current. However, I will not go through the process of switching gcc just to compile Virtualbox ;).
I tried the current SVN-version of Virtualbox and it does compile.... Yeah, that's well put. It does compile (with gcc34 compat). It still fails with gcc4. But as there is now a bug report open stating this issue, there's hope ;).
Other benefits of the svn-version: no more dependency on xalan/xerces and a qt4 gui (though qt-4.3 is not found by configure...).