VirtualBox for Slackware Users
 

They have yet to update their web site, but the tarball for VirtualBox 6.1.18 is available from this
link, http://download.virtualbox.org/virtu...6.1.18.tar.bz2

Thanks :hattip: It's working with kernel 5.10.8 (installed from .run file).

Thanks. Good to know.

They updated their web site overnight.

The change log, https://www.virtualbox.org/wiki/Changelog-6.1#v18

The download link, https://www.virtualbox.org/wiki/Downloads

Edit in: Well..... I downloaded the 6.1.18 .run file and installed it and have the exact same problems as outlined in these two posts, https://www.linuxquestions.org/quest...ml#post6205854 and https://www.linuxquestions.org/quest...ml#post6206107.
It will not run as root, but using the information in this post https://www.linuxquestions.org/quest...ml#post6206107, I was able, as root, to installed the extension pack and then run VirtualBox as user.
As root it seg faults as per this post, https://www.linuxquestions.org/quest...ml#post6205854

VirtualBox-6.1.18-142142-Linux_amd64.run is causing the segmentation fault bug that other people have reported above. It happens to me as both root and user. Dropping back down to the testbuild version VirtualBox-6.1.97-141967-Linux_amd64.run works fine for me.

Due to issues with VirtualBox and the 5.10 kernel I had decided to stay with kernel 5.4 until VBox at least runs in a more predictable / stable manner

In regards to the errors posted by @cwizardone

Has anyone receiving this error tried the resolution (post #2) from https://www.linuxquestions.org/quest...lt-4175657749/ ??

Running -current (kernel 5.10.9 and multilib glibc 2.32) and Virtual Box works ok as user, but indeed login as root and running it in a terminal,
vbox crashes with segmentation fault. There isn't any other message.


edit- I realized that my root account isn't in the vboxusers group.
But adding root to that group and running 'VirtualBox' in a terminal
gives exactly what bitfuzzy posted above https://www.linuxquestions.org/quest...ml#post6209920

There is something definitely amiss, and I'm not sure Kernel 5.10 is the problem

Slackware -Current64 - Kernel 5.4.84 - VirtualBox 6.1.16 r140961

As Root w/ root added to vboxusers group

Root can run VBox and create a vm in Slackware 14.2, I'm just creating a FreeBSD vm (VBox is 6.0.24).
(and root isn't in the vboxusers group)


Could it be some VirtualBox or kernel policy against? Or some problem with permissions.

No custom policies, and it's not a problem really as I don't run VirtualBox as root anyway.


I was curious to see if root would run it without any issues (it didn't)
Root was added to the group after the first attempt to run as root resulted in errors, to see if it made a difference (it didn't)

OK. The test builds page has been updated and this is what I've found so far:

Test build 6.1.x revision 142299 along with its companion extension pack, does NOT fix the problem, i.e., it won't run as root, but once the extension pack is installed, see the last line in post #5 above, it runs as user.

Development revision 142300 and Extension Pack development revision 142298
WILL run both as root and as user.

https://www.virtualbox.org/wiki/Testbuilds

It seems that the problem is with VBox then, no worries about kernel or anything else.

VBox 6.1.18 works ok as user. I have a Debian vm for home banking that I save the state and
resume sometimes a month and it is working ok.

This version works for me as both root and user. Thanks for the heads up cwizardone.

I also have been experiencing this.

I had been running VirtualBox-6.1.97-141967 on a AMD Ryzen 5 3400G with Radeon Vega Graphics with 32 GB RAM on Slackware64 Current fully updated including Updates of Wed Jan 20 03:08:10 UTC 2021 and 5.10.9 huge kernel. Everything was working fine.

I updated to VirtualBox-6.1.18-142142 and have been experiencing Seg Faults for VirtualBox.

Jan 21 12:48:52 kyiv kernel: UINetworkReplyP[2448]: segfault at 10 ip 00007fa0981370c2 sp 00007fa04fffc850 error 4 in libnm.so.0.1.0[7fa0980fe000+a2000]
Jan 21 12:48:52 kyiv kernel: Code: ff ff e9 54 ff ff ff 90 41 57 41 56 49 89 f6 41 55 41 89 fd 48 89 d7 41 54 55 53 48 81 ec d8 00 00 00 e8 31 b3 fc ff 49 89 c7 <8b> 40 10 85 c0 74 49 31 db 49 89 e4 66 90 89 d8 4c 89 f1 be c8 00
Jan 21 12:49:19 kyiv kernel: UINetworkReplyP[2527]: segfault at 10 ip 00007fc23c5710c2 sp 00007fc213d8a850 error 4 in libnm.so.0.1.0[7fc23c538000+a2000]
Jan 21 12:49:19 kyiv kernel: Code: ff ff e9 54 ff ff ff 90 41 57 41 56 49 89 f6 41 55 41 89 fd 48 89 d7 41 54 55 53 48 81 ec d8 00 00 00 e8 31 b3 fc ff 49 89 c7 <8b> 40 10 85 c0 74 49 31 db 49 89 e4 66 90 89 d8 4c 89 f1 be c8 00
Jan 21 12:50:06 kyiv kernel: fuse: init (API version 7.32)
Jan 21 12:49:28 kyiv kernel: UINetworkReplyP[3180]: segfault at 10 ip 00007fa15458b0c2 sp 00007fa136d88850 error 4 in libnm.so.0.1.0[7fa154552000+a2000]
Jan 21 12:49:28 kyiv kernel: Code: ff ff e9 54 ff ff ff 90 41 57 41 56 49 89 f6 41 55 41 89 fd 48 89 d7 41 54 55 53 48 81 ec d8 00 00 00 e8 31 b3 fc ff 49 89 c7 <8b> 40 10 85 c0 74 49 31 db 49 89 e4 66 90 89 d8 4c 89 f1 be c8 00

I gather this is a Oracle issue.

And yet it works with 6.1.18-142142 if I remove NetworkManager-1.28.0-x86_64-2.txz

I did this before in December and had the same affect. Recompiling NetworkManager & libproxy did not resolve the problem. It is something deeper down that is affecting this in one of the dependent libraries.

In the end I went to the Development Stream and everything worked with the standard NetworkManager package installed.

At that particular time I tried the Test Build Stream and got

bash-5.1$ strace -o out-1.log virtualbox
(process:2516): GLib-GObject-WARNING **: 10:26:34.792: cannot register existing type 'NMAgentManagerError'
(process:2516): GLib-CRITICAL **: 10:26:34.792: g_once_init_leave: assertion 'result != 0' failed
(process:2516): GLib-GObject-WARNING **: 10:26:34.792: cannot retrieve class for invalid (unclassed) type '<invalid>'
Segmentation fault

but found I could go to the Development stream of VirtualBox and it worked and with the NetworkManager package installed.

There is something that the Testbuilds & 6.1.17 & 6.1.18 does not work well with the Slackware64 Current NetworkManager and/or one of it's dependencies.

I am getting a similar error with VirtualBox 6.1.18 r142142 , however the kernel panic scrolls a few times so there all sorts of errors - so I could only get a screenshot - also after installing --Current - I was able to boot just fine, but the trouble started after installing the guest additions.

I updated Slackware64 Current to the level including the Massive Rebuild of Fri Jan 22 19:17:44 UTC 2021

I had VirtualBox 6.1.18-142142 installed and I had re-installed NetworkManager-1.28.0-x86_64-3 and here are no more SegFaults

So something in the system-wide recompile fixed the incompatibilities that I and a few others had experienced between VirtualBox & NetworkManager.

So whatever the problem was, it went away.

[EDIT] Correct dyslexic VirtualBox Version number

I still have compilation breaks here, always the same since I switched to current. But I'm on multilib and I know that Sbo are not garanteed in this case... I'm patching the code as suggested below, anyway if someone have an hint on what can be the cause I would be glad to know, as this is one of a few issues remained in my -current installation.

This command should fix Virtualbox crashing on startup:
At startup, Virtualbox checks for updates; disabling this check avoids the crash. As far as i understand this is caused by Virtualbox bundling its own version of the Qt5 libraries.

I downloaded --Current again made another iso and reinstalled --Current in virtualbox - still getting a kernal panic again; but only after installing the guest additions. :scratch:

Virtualbox 6.1.18 r142142 (installed using .run file) seems to be running fine me on -Current64 with 5.10.9 Kernel when ran as a "user"

Attempts to run as "root" still segfaults, but for me that's a non-issue as I don't run VBox as root anyway

Same here on a fresh install of the new -current. Works as user but not as root. Thats good enough for me, but I wll try the newest development version later just to test.

I just tried the latest VirtualBox-6.1.97-142300-Linux_amd64.run development build and it works in both root and user. However when you actually go to create a VM the next and back buttons are greyed out. So I basically cant create any VM's. SMH

UPDATE:

Creating VM's work if I use expert mode.

6.1.18 is out already and it worked fine

That's done the trick. Thanks!

What about the guest additions. I am still on 6.1.18 r142142 - and all is well if I don't install guest additions - if I do, --Current(VM) boots into a kernel panic.

Well, no it doesn't.
Please see posts #3 and #10 in this thread.

I too am having the segmentation faults as indicated in previous posts once I install VBoxGuestAdditions-6.1.18.iso. Reading the changelogs previous releases haven't been patched for kernel 5.10.x.

Decided to install a fresh guest with the iso obtained from https://slackware.uk/people/alien-cu...4-current-iso/

Got the guest up and running as expected kde (level 4), screen resizing and shared folders worked out of the box. Bi-directional copy/paste didn't

As I quite like Bi-directional copy/paste so went to install VBoxGuestAdditions-6.1.18.iso got this message

This was my first attempt at installing VBoxGuestAdditions in a clean system so I answered yes. Rebooted and the guest failed to start for the reasons described in previous posts.Tried init 3 - same problem.

Then tried the recovery console (single) that started, but was very troubled

Not sure if this helps, but something to think about.

Just out of pure curiosity, for those having issues with running "guests"

What Guest OS's are seeing issues?

So far I'm not seeing any with W10 guests

I have unfortunately bit the bullet and legally acquired Win10 Pro for my school classes. As of now, no issue with the guest additions. I also have a FreeBSD VM , but I haven't messed with it yet, and the only Linux VM I have right now is Slackware --Current, and thats where I have the kernel panic if guest additions are installed.

The kernel panic is on the guest? or host??

I am also noticing that I can only get sound to play in both my Linux and Windows guests if I set the Host Audio Driver to Alsa instead of PulseAudio. Is anyone else having this issue?

Guest.

I was in the middle of the mass upgrade, and all of a sudden I was getting file corruption errors. I decided to safest way to proceed was to do a clean install. Went swimmingly. Now all is well. Super-performant and rock-solid, as I would expect from Slackware.

Rock on!

I have Gentoo, antiX, Slackware and Artix running only with Alsa. In contrast FreeBSD and OpenBSD run with PulseAudio.

Ever so briefly this morning I fell across a web page that mentioned that vboxsf support is new to the kernel starting with the 5.10 series.

Retraced my browsing history, but couldn't find that reference again.

Wondering if I need to use VBoxGuestAdditions do I need to blacklist the Linux kernel modules vboxvideo, vboxguest and vboxsf?

I've got a fully update kubuntu 20.04 vboxguest, it was working perfectly well screen resizing, shared folders and bi-directional copy/paste. The host is Slackware-14.2 running VirtualBox 5.0.40 r115130

I've taken a clone of it and upgraded it to use the 5.10 kernel following the instructions here https://sypalo.com/how-to-upgrade-ubuntu

I removed the VBoxGuestAdditions-6.0.22 and installed VBoxGuestAdditions-6.1.18.

Rebooted the guest and it fails in similar fashion to how Slackware-current fails as reported in this thread.

I've attached a screenshot with the point of failure.

Well I think until Oracle addresses this issue, there is nothing we can really do other than suggest not installing guest additions. I would have to theorize that this is not just affecting Slackware as a guest, but any other Linux distro running the 5.10.x kernel. *shrug>

Well I don't know what is going on to be honest. I booted just fine after installing guest additions on 5.10.10 - so I thought maybe the issue was resolved - as soon as I logged as root I got a weird kernel panic (stupid me didn't screenshot). So I rebooted again, I got a kernel panic - so I rebooted yet again, and this time I was able to boot with another weird error, and logged into as root with no error, so SOMETHING is up still... What I don't know but everything seems suspect to me:




-edit

So basically I don't know what to expect each time I boot the VM, I could either boot into it just fine - or get a kernel panic for some random reason; this is even more weird now.

Ok --- SO; I rebooted a few times and this confirms my theory - sometimes the VM will get all the way to a login prompt, I tried to get into root and got another kernel panic - so really this is all over the place now. So here are some incoming threads with screenshots:

And then the next time I rebooted:


I actually made it to the login prompt - logged into root and then kernel panic again. SO... Yea I don't know how useful all this is - but this is what I have seen with 5.10.10 and guest additions for VirtualBox 6.1.18 r142142. Sometimes you can boot all the way, sometimes you won't - and sometimes you will still boot even after the kernel panic. It makes no sense.

-edit

Forgot to mention this is --Current up to today's updates (changelog) too.

FWIW, as I said in post #10,
Now, I only use it to run winXp-sp3, so I can run the HP drivers for my flatbed scanner, but for that purpose the VirtualBox versions mentioned above are working perfectly.

I was also facing the same issue (with same version of Linux kernel and VirtualBox). This issue was because of NetworkManager library.

I uninstalled the NetworkManager and then run VirtualBox. After that I installed the NetworkManager.
And disbled Preferences -> Update -> Check for updates option in VirtualBox. After that I had not facing issue while running the VirtualBox. Now I am running both NetworkManager and VirtualBox together.

I don't know what was the exact issue. But What I understand is, Everyday first time when I start VirtualBox, it was checking for update and get crash because of that library. I don't know this is right or wrong. But it is working for me.

This looks to only be an issues when starting, using virtualbox from a console session with -current as the host. This is not an issue (as far as I can see from my own testing) when using virtualbox as a user. Did I get that right?

Thank you
 

Thank you - this worked for me..

My scenario, the hose is 14.2 64-Bit, and --Current is the guest. That is where I am experiencing these random kernel panics in --Current as the guest.

Is this with running virtualbox as root? This is what I was alluding to as a common thread here.

This computer is the host, it' Slackware64-current. I run VirtualBox from my user account. I did test starting virtualbox from a root Konsole and got this. I also logged in as root and tried starting virtualbox from Konsole with same result.
When running virtuialbox as a user I have no issues, this is with five Slackware virtual machines. Two are 14.2 x86 and x86_64 machines. The remaining three are -current, one x86 and two x86_64. All but one are clean installs of Slackware. All machines are with default settings except for disk size, memory and network (set to bridged). The x86 machines have PAE/NX enabled.

I tested the VirtualBox extensions on a x86_64 and a x86 machine with no issues except that the vbox kernel modules are rebuilt on every boot (annoying). It is a possibility the drivers might actually be removed on a reboot or shutdown because of this line in the shutdown messages "VirtualBox Guest Additions: You may need to restart your guest system to finish removing guest drivers." I have not verified this, but that would explain why the kernel modules are built on every boot.

there are two issues with the latest Virtualbox 6.1.18:
ad1) running host VB as user vs root
ad2) virtualbox client crashing kernel 5.10.x

these are independent but somehow mixed up:

@Jeebizz refers to ad2)
he has a problem (as I do on antiX, Gentoo, Artix, Venom, Slackware clients) with virtualbox crashing VB client kernel 5.10.x
It does not matter what kernel version VB host is using:
in my case my host VB runs Slackware-current-64 kernel 5.10.x and Virtualbox 6.1.18 without any issues

my solution to ad2) use kernel 5.4.x
This way I have current kernel without crashing VB client

ad1) I have no idea, how to fix this I don't have the problem

My issue is as a user - I have no reason to try it as root.

Okay thanks @Aeterna and @Jeebizz, just trying to sort this out in my head.

With the exception of that 6.1.16 version, after upgrading to a testing version and now the 6.1.18 version I have had no issues with kernel 5.10.x, currently at 5.10.11 running on the host and also -current guest machines. The only problem (more of an annoyance) I've had with the guest additions is the rebuild the vbox modules on every boot I mentioned above.

@Jeebizz, I too have no reason to use virtualbox as root. Sort of puzzled me at first why anyone would, then I realized that there are a few who seem prefer to use root for everything. I'm okay with that.

Strange as in puzzling to me, this issue.

I don't normally install guest additions to my slackware virtual machines anyway. I've been testing on one of my virtual machines since I first noticed this issue over in The Latest Kernel Release thread.

I do install the guest additions to my Windows 10 virtual machine, no issues there.

I can install VirtualBox client with kernel 5.10.x and this works fine. However after installing Vbox client additions kernels 5.10.x crash with the error messages as posted by Jeebizz.

Without VboxClient additions I can't use copy/paste between clients or client and host which is quite convenient for me. So the trade off is Vbox client additions installed with kernel 5.4.x