A new test build was posted this afternoon at,
https://www.virtualbox.org/wiki/Testbuilds

Version "Linux 64-bit, 6.1.x revision 142917" along with the "6.1.x revision 142894" extension pack, functions properly as user and/or root with the 5.11.1 kernel.

Finally! Runs here as both root and user with out having to run the update check segmentation fault fix. So far so good.

1 members found this post helpful.

Still have the segfault
both 5.10.18 / 5.11.1
both user / root
revision 142894 / 142917 or snapshot 142300

Slackware current
Plasma 5.21

1 members found this post helpful.

I don't know if you have new hardware, or need anything from the newer kernels. But a pragmatic solution for me is that I use the latest 5.4.x kernel on slackware current. On Slackware-Current everything related to virtualbox, or any 3rd party stuff that requires compiling kernel stuff, just works with that kernel.

I have a Lenovo laptop, no so old but not new. At least, compatible enough in most cases (full Intel/Realtek hardware)
I will try that
Thx

Exactly the same with :-(
Kernel 5.4.100
VBox 6.1.18-142142 / 6.1.19-142917

That's a shame. Here virtualbox 6.1.18-142142 is working fine with kernel 5.4.99, on a completely updated (except for the kernel) slackware current-multilib (I also used SOFTWARE_VIRTUALIZATION=yes). Bridged networking, client tools, etc, all working fine. :/. Used ponce github slackbuilds for it.

Weird

Curiously, I remember everything was working fine with Vbox beta (I don't remember the version) and the first releases of the kernel 5.10.x

Solved with that command ( comment #18 )

As non-root user

For now with :
kernel 5.4.100
vbox 6.1.19-142917

3 members found this post helpful.

idem with 5.10.18

1 members found this post helpful.

Slackers,

Just now I started using VirtualBox 6.1.18 on my Slackware Alpha 1 system for testing and programming purpose.

I don't install VirtualBox Guest Addition on other Linux distro.

Installation of VirtualBox guest addition is necessary for Slackware VM? Or is it optional?

Because I don't need extra functionality like, share clipboard between host and guest system and share folder using VirtualBox "Shared Folders" functionality.

When I tried to install Guest Addition on Slackware VMs, it display prompt it is already install.

Please suggest.

Thanks in advance.

Without the guest addition, you would also lack the ability to run the guest session in the screen resolution you want. If you don't care about that, you probably don't need it.

Now I don't know if you run Slackware current, but the slackbuild script of virtualbox at current github at ponce, includes the guest additions. And it's not like it's a huge amount of extras diskspace.

VirtualBox "Shared Folders" require Guest Additions to be installed (or VBox options enabled in the kernel?):
ref:
https://www.virtualbox.org/manual/ch...#sharedfolders

In other words, you have VB client additions installed or Slackware kernel has kernel VBoxFS enabled (this would completely block share folders functionality if you would install VirtualBoxGuest Additions so I doubt that VBox options are enabled in Slackware kernel. I don't have Slackware kernel at all so can't really confirm this)

I had the same problem running 6.1.18 with kernel 5.10.18 and ran the suggested code on a Ryzen3-3100 system and now have VBox running as both root and user.

Attached Files

Code-Fix-VB6.1.18.txt (52 Bytes, 34 views)

Optional. I don't install the Guest Additions on Slackware, unless I am playing with them. I don't like the way it installs anyway. I do my sharing via NFS shares. I am fine with 800x600 resolution. All most everything I do in a Slackware VM is via the CLI anyway.

This is because of "xf86-video-vboxvideo" package that is part of Slackware. If you want to install the Guest Additions you need to remove this package.

2 members found this post helpful.