hi i try install virtualbox founded some problem so i need the easy way to install virtualbox

Hi...

First, please read here and here. Then, if you would, please provide the necessary details.

Regards...

2 members found this post helpful.

hi.

From your package manager or Oracle's site?

this my problem when i installed virtualbox and run appear this problem

Attached Thumbnails

 

I see the KonSolo opendid not work?

I personally would uninstall it and use their web site https://www.virtualbox.org/wiki/Linux_Downloads
but that's just as I'm use "testing" and "stable versions" of Debian.

This just came to mind: https://www.linuxquestions.org/quest...en-4175558089/ ...

I do not recommend running version 5.0 of VirtualBox. It is very new and likely to have a lot of problems. The version that I recommend using is 4.3.28. Use the Linux download from the VirtualBox web site that is for "All distributions".

I have been using VitualBox for a very long time with Slackware Linux. Some versions of VirtualBox just don't work or don't install when they are first released. Problems are much more likely when the main version number is changed (4.3.x to 5.0.x). If you decide to use version 5.0 or 4.3.32 then read the VirtualBox forums to see what problems are currently being seen and how to work around those. I have not tested 4.3.32 with Slackware yet. I have been running 4.3.28 for a long time. There are still minor bugs that I know of in VirtualBox mostly relating to KDE and graphics display.

Installing VirtualBox requires the Linux header files. You must install them if they are not present, or use the configuration file in the "/boot" folder to build the Linux kernel to create the header files. You can usually stop the kernel build after a few minutes since the header files are created by then.

Here are some installation tips. Copy the installation package to a folder in your Linux partition. Run a root command shell. Make sure that the installation package is executable. After you run the installation package you must reboot Linux. Check the console to make sure that the VirtualBox modules started successfully. The error you saw indicates that the kernel modules for VirtualBox did not install or failed to load and start.

The Extension Pack must be in a folder that is readable by non-root users if they will install the Extension Pack. You must use the same version of Extension Pack as the VirtualBox version. Remove the old Extension Pack and add the new Extension Pack.

If you are going to use the shared clipboard then you need to edit some of your user profile scripts. Read the VirtualBox manual for information about how to do that.

Everyone has a different experience I have been using VirtualBox for a number of years. I say use the latest version, it has a lot of fixes (some Linux related) and some additional features. I upgraded to version 5 as soon as it was available. Right now I am at VirtualBox Version 5.0.8 r103449. It runs on a Slackware64-current host. I have zero issues right now. I do recall an issue a few versions back that caused problems with Windows guest related to folder sharing, that was fairly quickly resolved by Oracle.

I currently have two Slackware64-current virtual machines. One of them is for testing Alien Bobs KDE5 ktown. It runs as expected and fairly well at that (Thanks Eric!). I am curious as to what these minor bugs related to KDE and graphics display. All seems well to me.

Regarding installation. If you did the recommended Full Installation of Slackware nothing additional is needed. Here is what I do to install VirtualBox on my Slackware64-current machines. This should also work just fine with Slackware64 14.1.

Download the Oracle installation file and extension pack to a directory of your choice. I prefer use a directory off of /home, specifically /home/non-slack/other/virtualbox/

The VirtualBox installation file is available from this page: https://www.virtualbox.org/wiki/Linux_Downloads

Since I use Slackware64 I would download the AMD64 choice from "All distributions i386 | AMD64". If you are using Slackware (32-bit) download the i386 file.

The Extension Pack is available from this page: https://www.virtualbox.org/wiki/Downloads

Regardless of 32 or 64 download "VirtualBox 5.0.8 Oracle VM VirtualBox Extension Pack All supported platforms"

If you are at runlevel 3 (default after installing Slackware) then log in as root (or if you don't like that, log in as your self and then "su -" to root. If your at the desktop open a terminal and "su -" to root.

Change to the directory you downloaded the installation file and extension pack.

NOTE: The installation program will create the vboxusers group with GID of 999. If you don't like this create the group first:

groupadd -g 215 vboxusers

Start the installer (if you downloaded 32 bit substitute with VirtualBox-5.0.8-103449-Linux_x86.run:
sh VirtualBox-5.0.8-103449-Linux_amd64.run

You could also:
chomd u+x VirtualBox-5.0.8-103449-Linux_amd64.run
./VirtualBox-5.0.8-103449-Linux_amd64.run

This is the output I get from the installer:
Next install the extension pack: (You don't need "--replace" if extension pack not installed yet):
vboxmanage extpack install --replace Oracle_VM_VirtualBox_Extension_Pack-5.0.8-103449.vbox-extpack

And the output I get:
Next if you are planing on accessing USB devices from a guest you need to add yourself (and other users as appropriate) to this group. Example:

usermod -a -G vboxusers username

That's it. Works for me, perhaps for you too.

3 members found this post helpful.

To save time a post I just put .../chromium-vs-firefox-which-is-better-4175524322/page7.html#post5446982 (at lest the middle part) seems to fit in with what my response would be here, newest works best for me.

Kiki Novaks and his MLED distribution has vbox packages which are slackware compatible.
http://www.microlinux.fr/microlinux/...t/slackware64/

I am using 2 VM's from 3 months and had no problems so far.

Also MLED repository is slackpkg+ compatible!

There are three KDE graphics problems that I run into often.

Resizing a VM window (not in integrated mode) does not always adjust the display resolution and the panel/taskbar may be cut off by the bottom of the window. Resizing the window again usually fixes that problem.

In integrated mode, VM guest windows are not always repainted if they are covered and uncovered by host OS windows. The problem happens more frequently on a Windows host than a Slackware host.

Using a Slackware VM guest, the KDE panel sometimes turns solid white or solid black instead of the correct (silver) color. That usually happens when resizing or moving the guest windows.

There are a few other problems that I am aware of and expect might not be fixed yet.

Using a VM with no guest additions, the "USB Tablet" pointing device does not work properly. The guest mouse pointer can't be moved to the edge of the guest window. Setting the pointing device to PS2 works. This problem mostly affects people who test boot disks that do not include the Guest Additions and require a USB mouse.

In a Linux guest, the text mouse cursor (gpm) does not always work after the guest additions have been started. Stopping and unloading the guest additions allows the mouse to work in text mode.

In a Linux guest using guest additions, the text mouse cursor (gpm) does not position correctly using the "USB Tablet" device. The cursor can't be moved to the edge of the text display area.

Shared folders do not work properly if a guest's Windows OS is set to use offline files.

Windows XP guests sometimes blue screen when using both the SATA driver and the USB driver. This problem has been in VirtualBox since about version 2. My work around is to not use SATA with Windows XP guests since I need USB support. The SATA driver for XP has to be downloaded from the Intel site and this could be a problem with Intel's driver. I haven't tested this problem recently.

VirtualBox network filter drivers do not install correctly when using Kaspersky Antivirus. VirtualBox gets an error whenever you use a bridged network interface. It is necessary to completely reinstall Kaspersky Antivirus after installing VirtualBox. I am still trying to find a better work around for this because it makes updating VirtualBox difficult.

Recently, the 3D support does not work with KDE in a Slackware guest. This might be a configuration issue but I haven't had time to investigate it. I don't really need 3D support and even when it worked it was rather slow.

The other problems that I run into are very version dependent and they tend to be fixed (or changed) in each release version. I keep using the same version because I know the problems with that version and the work around. There's nothing wrong with using the latest VirtualBox version. Just keep in mind that it is more "experimental" than previous major versions. I usually wait until a version has been out for a year before I use it. So, I'll be looking at version 5 in 2016.

I do software development in a Windows XP guest on a Windows 7 host. So I use the version that does that the best. I occasionally send in bug reports for VirtualBox if the problem is severe or affects something I use a lot.

I will say that Oracle does a good job fixing bugs and VirtualBox is very reliable and useful. It is challenging to test all the possible combinations of host and guest OS. I can't compare VirtualBox with commercial products since I have not used them.

@Erik_FL Thanks for the details.

My host is SLackware64-currernt. I primarily use a virtual machine for Windows XP and Windows 7 (more 7 than XP these days). I also run some Slackware test guest, like the KDE5 one I mentioned above. I am certainly not problem free. I ran in to several issues with Windows 10, mostly video related.


A few of your issues that I can check, I just don't see. Probably has a lot to do with hardware differences and virtual machine setups and of course version differences. For example I use an USB mouse, I have never encounter the USB tablet not working problem with guest without guest additions. I do recall the gpm mouse cursor problem, but have not see noticed it recently in my Linux CLI sessions.

When you say integrated mode, are you referring to seamless or scaled mode? I recently started using seamless mode with my Windows virtual machines, it really improved over the last time I tried it.

Just upgraded to 5.0.10. https://www.virtualbox.org/wiki/Changelog