Virtualbox 2.1.2 Slackbuild
 

Any plans on "updating" the current 2.0.6 slackbuild to 2.1.2, or have someone here tried using the 2.0.6 script with the 2.1.2 sources with Slackware 12.1 and actually made it work?

I did a quick test, but it died on me. I ran into some libcap issues and some source filename issues.

:)
/Thomas

I've "wimped out" on VBox and just started using the binary builds that upstream provides. I don't know what Heinz's status is with the build script though.

So, the official Virtualbox binary build "just works" with Slackware, or does it need a lot of tinkering to get going?

It's worked fine for me on at least 12.0, 12.1 and 12.2. Run the .bin as root and it'll install to /opt by default, though you can specify another directory if you want (info on this in the User Guide).

On a stock installation, yeah, it "just works," and as pwc101 said, it goes to /opt/somewhereoranother.

The computer on which I install VBox has one purpose only - it runs VBox to provide development virtual machines.

Hi,

To use on Slackware 12.2 with Intel dual core 64 bit E6750

Which VirtualBox binary, the 32 or the 64 bit?

http://www.virtualbox.org/wiki/Linux_Downloads

I've an Pentium 4 Intel E6750 cpu

dual core 64 bit. According to the VirtualBox doc:

VT and EPT

which both of those are in my cpu

And then that I enable hardware virtualization in VirtualBox.

--
Alan.

If you're running Slackware (which is 32-bit) you need the 32-bit installer.

I have a very rough next week so don't expect any quick update on virtualbox for SBo. However, I expect to have a lot more time again the week after so updates to my scripts should start to appear within the first days in February. I plan to start with VirtualBox so we should have an updated script in at least two weeks time.

With my Core 2 Duo processor, if I enable VT I find that I cannot connect my Win98 virtual machine via Samba. Just an observation I have made using VirtualBox 2.0.6 OSE using the Slackbuild by ppr:kut. If I disable VT, all works just fine. This may or may not be relevant depending on your virtualisation needs and how your hardware behaves.

Thanks for the offer of continued work on this. I greatly appreciate being able to use VirtualBox as it allows me to run a proprietary Windows based application that I need to use for work and that I cannot get to install under Wine.
Please do not interpret this as an attempt to apply pressure to meet your self imposed timeline. I am a firm believer that "deadlines are not death lines".
I am really using this as an opportunity to bump your Thanked count. Your Slackbuild scripts for nVidia and VirtualBox are an essential part of my Slackware setup.

just hit pending, should be in one of the next updates :)

Dear ppr:kut

Some more instructions in the README file might save installers some time.

Will you please include the instruction to check that /etc/rc.d/rc.vbox* have the executable permissions.

It might also be helpful to include the (obvious) comment that they need to start /etc/rc.d/rc.local (or reboot) before running virtualbox.

I would also inform the installers that the /etc/rc.d/rc.vbox* files need to be removed manually if they need to remove the virtualbox-ose package completely.

Chris

Sorry, but no. This is nothing vbox specific, but common amongst all packages
that install rc-scripts, ie "default behaviour".

(In other words: "Slackers are meant to know that stuff....")

which would be wrong, as rc.local has no connection to vbox apart from
the README telling it would be a good place to call the actual rc-scripts
for virtualbox. And a note to start vbox' rc-scripts to start vbox.....I mean...
really?

Same as comment one. Default behaviour.

Out of curiosity I installed the clamav Slackbuild as it was the first that came up from my Google search and this is the result of the package I just installed:

root@darkstar:~/slackbuilds/clamav# ls -ltr /etc/rc.d/ | tail -1
-rwxr-xr-- 1 root root 1458 2009-02-07 21:05 rc.clamav*

There do not seem to be consistency in the default permissions of the rc-scripts installed via Slackbuilds.

Chris

Virtualbox version 2.1.2 is released @ slackbuilds.org
 

Chris, please follow instructions about bug reports @ slackbuilds.org

Not related to that, in the [Slackbuilds-users] Updates - 20090207:

This is the /media/SlackDVD/extra/wicd/README.SLACKWARE

OpenGL under VirtualBox
 

Has anyone managed to get the OpenGL support working under VBox 2.1.2 on Slackware?

Maybe my hardware is a bit old:

CPU: 3.2GHz Pentium 4 Prescott (socket 478 version)
Video Card: NVidia GeForce FX 5700LE 256Mb RAM, AGP 8x
RAM: 2 Gigabytes

...but OpenGL support under VBox flat out refuses to work for me.

I have OpenGL support enabled and working 100% under the host OS (Slackware) with the NVidia driver set.

Should it be working?

Everything I've read about it says nothing more than the fact that you have to tick the checkbox to "Enable 3D Acceleration," which I have done, but to no avail.

Is there something I'm missing?

I haven't tried it myself yet, but what guest os are you using? I think VirtualBox 2.1.2 does OpenGL only on Windows Guests.
Direct3D on Windows guests is in svn, but I don't know if it's in 2.1.2 already. Doubt it though. AFAIK there's no graphics acceleration on Linux guests for now.

Thanks for the quick reply!

This is with an xp guest.

I'm trying it with OpenGL games, not ones which require Direct3D.

Hmm. I don't know. Possible things:
- latest guest additions installed?
- running compiz as window manager?
- using an OpenGL application to test and not an DirectX app?

Apart from that I have no idea, sorry.

Yes
No
Yes

Could my hardware be too old?

Doubt it. A Geforce 5 should be new enough to handle that. I would start thinking about it with a Geforce 3 or lower....

VirtualBox 2.1.2 works well (thanks Heinz) and I was able to install Windows 7 beta 1 in it. What can I do with it is still to be determined but I just wanted to try it. ;)

I solved my problem.

I had upgraded from VirtualBox 1.4.0 to 2.1.2 and kept my old config files. All I had to do was wipe them out and start from scratch. Now OpenGL works.

There must've been some incompatibility with the older configs.