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.

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.

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