SlackwareThis Forum is for the discussion of Slackware Linux.
Welcome to LinuxQuestions.org, a friendly and active Linux Community.
You are currently viewing LQ as a guest. By joining our community you will have the ability to post topics, receive our newsletter, use the advanced search, subscribe to threads and access many other special features. Registration is quick, simple and absolutely free. Join our community today!
Note that registered members see fewer ads, and ContentLink is completely disabled once you log in.
Before version 4.0, there were two editions of VirtualBox: a full binary containing all features and an "Open Source Edition" (OSE) with source code. With version 4.0, there is only one version any more, which is open source, and the closed-source components have been moved to a separate extension pack.
Host OS Slackware 14.0 32 bit
Virtualbox 4.2.4, installed with the Oracle installer
CPU AMD Athlon QL-66 (supports hardware virtualization, otherwise I couldn't have run the 64 bit VM)
Tested it with a Win2K VM, kernel complains about 32 bit CPU.
EDIT: Just made a short test with Slackware 14.0 64 Bit host OS on a Phenom II CPU, behaves like you have described it.
So I change my conclusion to:
So setting the correct template seems to be mandatory if you are using a 32 bit host OS.
I have also been playing around with choosing different templates. I found that with the generic Linux 64 template, you will have no access to other NIC then the e1000. I did not find a way to add them manually. In other words, it seems the templates do have some "magic"
That VirtualBox installs and functions properly on Slackware 64-bit 14.0 and 14.1.
You can then install any 32-bit or 64-bit OS as a guest in that 64-bit installation.
You do not need nor do you require Multilib to install or use 64-bit VirtualBox.
You can install 32-bit VirtualBox on a 64-bit machine but... why?
In spite of the religious controversy about the binary version or the compile-it-yourself version, the one from Oracle works the other way sometimes has problems with useful things like USB... I prefer "works," you mileage may vary.
+1. No problem to run a 64 bit VM on a 32 bit host, easier to manage, and doesn't make my Thinkpad overheat as VirtualBox does.
If a software is able to overheat your machine there is a flaw in that machine's cooling system. Virtualbox can not go for more then 100% CPU load, which your cooling system should be able to handle, regardless which software runs the CPU at 100%.
Having said that, I use both, Virtualbox and VMware Player and until now I had no driver problems with any of them.
For some reason VMware Player thinks it encountered an error when installing on Slackware. Only that there is no error, it is running fine after a forced install with --ignore-errors.
Thanks very much for the tip! It now installs. The problem might be that the installer can't setup the bridged virtual net. My guest system actually cannot connect to anywhere when I choose "bridged networking".
This can be fixed by killing the vmnet-bridge process and re-launch it with the correct "-i" option. I've searched /etc/rc.d/init.d but found vmnet-bridge in nowhere. Any idea how to keep this settings across system restart? Thanks!