[SOLVED] Cannot install Virtualbox on Slackware 15
SlackwareThis Forum is for the discussion of Slackware Linux.
Notices
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.
If you have any problems with the registration process or your account login, please contact us. If you need to reset your password, click here.
Having a problem logging in? Please visit this page to clear all LQ-related cookies.
Get a virtual cloud desktop with the Linux distro that you want in less than five minutes with Shells! With over 10 pre-installed distros to choose from, the worry-free installation life is here! Whether you are a digital nomad or just looking for flexibility, Shells can put your Linux machine on the device that you want to use.
Exclusive for LQ members, get up to 45% off per month. Click here for more info.
I am trying to install virtualbox on my Slackware 15, but so far no success. I've tried with Sbopkg, Sbotools (sboinstall), and directly downloading the files from Slackbuilds. In the Slackbuilds site, there is a README.SLACKWARE informing that I need to add some lines in /etc/rc.d/rc.local and /etc/rc.d/rc.local_shutdown, which I've done.
With the three options of installing virtualbox, the build starts returning warnings such as:
Code:
/tmp/SBo/VirtualBox-6.1.44/doc/manual/en_US/UserManual.xml:6: warning: failed to load external entity "http://www.oasis-open.org/docbook/xml/4.5/docbookx.dtd"
I haven't tried virtualbox, but in my experience qemu works fine. Qemu might be less userfriendly as it is more command line orientated than point and click to configure your virtual machine, but I prefer qemu for the follwing reasons:
qemu uses the kvm kernel module included in the Linux sources. If you upgrade your kernel you do not need to worry about yet another third party kernel module.
Qemu is able to emulate more than just x86 guest machines. It can also emulate things like ARM, PowerPC and Sparc machines.
VirtualBox 7.0 (active maintenance)
VirtualBox 6.1 (no longer supported, support ended 2024/01)
VirtualBox 6.0 (no longer supported, support ended 2020/07)
VirtualBox 5.2 (no longer supported, support ended 2020/07)
VirtualBox 5.1 (no longer supported, support ended 2018/04)
VirtualBox 5.0 (no longer supported, support ended 2017/05)
VirtualBox 4.3 (no longer supported, support ended 2015/12)
VirtualBox 4.2 (no longer supported, support ended 2015/12)
VirtualBox 4.1 (no longer supported, support ended 2015/12)
VirtualBox 4.0 (no longer supported, support ended 2015/12) https://www.virtualbox.org/wiki/Download_Old_Builds
Last edited by Andersen; 02-11-2024 at 12:19 PM.
Reason: adding new info
Some of us have got a working Virtualbox 7.0 SlackBuild while we wait for ppr:kut to update his. But the easiest solution, as mentioned above, is to just download the installer oracle provides located here
I haven't tried virtualbox, but in my experience qemu works fine. Qemu might be less userfriendly as it is more command line orientated than point and click to configure your virtual machine, but I prefer qemu for the follwing reasons:
qemu uses the kvm kernel module included in the Linux sources. If you upgrade your kernel you do not need to worry about yet another third party kernel module.
Qemu is able to emulate more than just x86 guest machines. It can also emulate things like ARM, PowerPC and Sparc machines.
regards Henrik
Use virt-manager and it becomes basically as easy to use as Virtualbox.
Then install the virtualbox-kernel package from SBo.
Other thoughts: ensure the build output environment, usually /tmp, is large enough to build packages. Many people use tmpfs for /tmp but on older systems with less RAM this might limit the storage space for compiling.
I found a bug report that might be related to libxml2-2.11.x and virtualbox 6.1.44. I can't confirm the report because I compiled 6.1.44 when libxml2-2.9.x was installed on my 15.0. The libxml2 packages has been patched several times on 15.0 since the original release. If actually related, then a quick test would be to install libxml2-2.9.x from the original 15.0 release and see if 6.1.44 compiles.
Following the links in the previously mentioned gentoo bug report, this patch allowed me to compile 6.1.44 on 15.0 with the latest patched libxml2-2.11.x.
Code:
diff -urN VirtualBox-6.1.44/doc/manual/en_US/user_Frontends.xml VirtualBox-6.1.44.new/doc/manual/en_US/user_Frontends.xml
--- VirtualBox-6.1.44/doc/manual/en_US/user_Frontends.xml 2023-04-13 04:15:15.000000000 -0500
+++ VirtualBox-6.1.44.new/doc/manual/en_US/user_Frontends.xml 2024-02-11 17:35:12.806444672 -0600
@@ -1205,6 +1205,6 @@
</sect1>
- <xi:include href="user_man_VBoxHeadless.xml" xpointer="element(/1)" xmlns:xi="http://www.w3.org/2001/XInclude" />
+ <xi:include href="user_man_VBoxHeadless.xml" xpointer="element(/1)" xmlns:xi="http://www.w3.org/2001/XInclude" ><xi:fallback/></xi:include>
</chapter>
diff -urN VirtualBox-6.1.44/doc/manual/en_US/user_VBoxManage.xml VirtualBox-6.1.44.new/doc/manual/en_US/user_VBoxManage.xml
--- VirtualBox-6.1.44/doc/manual/en_US/user_VBoxManage.xml 2023-04-13 04:15:15.000000000 -0500
+++ VirtualBox-6.1.44.new/doc/manual/en_US/user_VBoxManage.xml 2024-02-11 17:42:46.135268138 -0600
@@ -8975,6 +8975,6 @@
<!-- TODO: Figure out how we can handle other manpages. The xml is bolted to
sect1, so it's not possible to have them "in place" -->
- <xi:include href="user_man_vboximg-mount.xml" xpointer="element(/1)" xmlns:xi="http://www.w3.org/2001/XInclude" />
+ <xi:include href="user_man_vboximg-mount.xml" xpointer="element(/1)" xmlns:xi="http://www.w3.org/2001/XInclude" ><xi:fallback/></xi:include>
</chapter>
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.