I'm running Salix 14.1 and I would like to install Virtualbox but when I tried to run the package from SBOPKG it didn't install. I got a few messages. So, I'm trying to find an easy way to install Virtualbox. Is there an easy procedure out there to run? Should I just grab the file(s) from Oracle and install it that way instead of trying the packages from slackbuilds?

Any help would be appreciated.

I found this link. http://forum.salixos.org/viewtopic.p...tualbox#p37653
I'm going to try it later on today. I will let you know if this works ok.

You just have to download the file from:

https://www.virtualbox.org/wiki/Linux_Downloads" (choose "All distributions" and your architecture - amd64 or i386)

Make it executable

#chmod +x VirtualBox-(...).run

And then, to install:

#sh VirtualBox(...).run

It will be installed.

To run Virtualbox, type "virtualbox" on console as root.

1 members found this post helpful.

^ What gauchao said above ^, plus be sure to download the appropriate extension pack.

1 members found this post helpful.

It takes a little more work, but you should also consider building a proper slackware package. Then it is easier to "undo" whatever you do later on. Also, updating when virtualbox is updated is perhaps a bit cleaner.

It this interests you, be sure to read the slackbuilds howto to actually build the package, then read to learn how to install it.

Personally I use sbopkg to maintain packages built from slackbuilds.org (including virtualbox), it makes it all pretty easy and I haven't had any major difficulties.

Note also that if you want to build and install virtualbox using slackbuilds.org, 2 other packages need to be built and installed first: acpcia and virtualbox-kernel (see the README and also the README.SLACKWARE for important setup information).

Cheers,

Michael

1 members found this post helpful.

Over the years I have installed (and updated when notified) VirtualBox from both Sun and Oracle. The installation instructions given above (with the addition of the extension pack -- you do want that) will get installed and working.

Note that the Oracle installer places VirtualBox in /opt (which, in my opinion, is exactly where it belongs rather than in the /usr tree). The installer builds and installs the kernel modules and installs start/stop scripts in /etc/rc.d for you.

If you wish to remove VirtualBox completely from your system simply use the uninstaller:
and it's gone.

When a new version of VirtualBox is released, you'll be notified when you start it. You download the two files (as above) and execute the ".run" which will uninstall the existing version and replace it with the new one.

Hope this helps some.

3 members found this post helpful.

Hey guys, sorry I took a long time to reply. But I was able to install the virtualbox just fine. Here is the problem I have, I haven't been able to install Windows or any other distributions. I was able to install zenwalk but it takes like super LONG to respond. Also, I was never able to install the VirtualBox 4.3.26 Oracle VM VirtualBox Extension Pack. I'm going to give it another shot tomorrow. I'm going to try to write down all the errors but it doesn't seem to work properly. I might try a different version of virtualbox tomorrow.

Do you guys know if we can install vmware instead of virtualbox?

Here you go:

http://www.microlinux.fr/microlinux/...bit/slackware/

http://www.microlinux.fr/microlinux/...t/slackware64/

Actually it is not completely gone but almost

https://www.virtualbox.org/ticket/10752

1 members found this post helpful.

A couple of things to be aware of: you really do need to install the extension pack (before you install any virtual machines) and you need to allocate RAM. You will also want to install the Guest Additions in each virtual machine.

The Extension Pack is installed once for VirtualBox itself, the Guest Additions are installed in individual virtual machines.

First off, the User Manual can be found in /opt/VirtualBox/UserManual.pdf. It's a good idea to take a look though it simply because installation and configuration can be a little confusing and it won't hurt to have a reference to look at.

If you downloaded, for example, Oracle_VM_VirtualBox_Extension_Pack-4.3.26-98988.vbox-extpack, you would start VirtualBox, just VirtualBox, no virtual machines, click on File, then on Preferences, then Extensions. Over to the right of the window is a blue box with a down-pointing arrow. Click that and navigate to where the Extension Pack downloaded file is, highlight it and click OK to install. You only do this once when you install a new version of VirtualBox.

Once you've done that you'll be able to easily install a virtual machine.

RAM: your virtual machines use RAM that you allocate from your total RAM pool. You do that by, when you have a virtual machine installed, clicking on the Settings icon on the Oracle VM VirtualBox Manager (it's the window that pops up when you start VirtualBox). That is, you've installed a virtual machine and you don't start it until you do the settings.

The one you need to fiddle with first is the RAM and it's a balancing act: keep in mind that you've got your Linux system and your virtual machine that are separate. Whatever you allocate to the virtual machine will not be available to the system, so don't give the virtual machine any more that half of the total RAM installed in your box. And, if you do allocate half the RAM to more than one virtual machine, don't ever start two of them because the system will be unusable. The balancing comes into play when you're allocating enough RAM to the virtual machine to make it usable (Win7, for example, is a pig dog with only a gig of RAM) without crippling your Linux system.

The box I use for virtual machines has 8G in it, I allocate 4G to a Win7 virtual machine and things work well (I don't actually use Win7 for much of anything except, you know, critical updates). If you've got wads of RAM, say, 16G or better, it's a little easier to balance things so they all work well, just be careful what you wish for.

Note that one you have installed a virtual machine and have it running you will not need to do all the settings again when you install a VirtualBoxc update -- extension pack and guest additions, yes, virtual machine configuration, no. The virtual machine retains you settings.

Take some time to read through the User Manual about installing and configuring just to get a feel for what to do and why to do it for your particular needs. VirtualBox does work quite well if you let it.

Hope this helps some.

2 members found this post helpful.

Sort of echoing tronayne. Use the same version of VirtualBox

How much memory on your host computer. Things will run slow if you don't have a lot or don't give the guest OS enough. The default for Linux should be enough (512 MB) but I always at least give in 1024 MB. I have 8 GB on memory on my host machine. Things run quite well and similar to tronayne I give my Windows 7 machine 4608 MB. My Windows 10 machine only gets 2048 MB.

Once VirtualBox is installed you can install the Extension Pack from the VirtualBox Manager via File, Preferences..., Extensions.

Another way is via a terminal. Make sure you are in the directory that the extension pack file was downloaded to and then enter:
NOTE: Leave out --replace if this is a new install.

If you don't have enogh memory switching to vmware won't help much.

1 members found this post helpful.

OK... thanks for the info guys. I did read the user's manual but only the portion pertaining to Linux. Chris, I followed the procedure that you mentioned. That wasn't the problem. I'm getting an IO error. I will post it later on today.
As far as memory is concern, you might be right. I took the default and never increased it. I'm going to change the vm size and give it a shot later on today.

OK... sorry it took a while to get back but the issue was resolved. What I had to do was increase the memory size on the VM like some people have suggested. I was also able to install the Extension Pack. All I had to do is open VB as root, select the extension pack, install it and issue was resolved.

Thanks for all your help/Info...

Aparently there is more than just installing it, just tried myself. Once I add myself to the group it created it won't run because my UID is not root.

@enine

As far as I know, you must add the USER to the vboxusers group as below:

(to add the user "user" to the group "vboxusers")

or

1 members found this post helpful.