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 It's working with kernel 5.10.8 (installed from .run file).

3 members found this post helpful.

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

1 members found this post helpful.

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.

2 members found this post helpful.

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/ ??

1 members found this post helpful.

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

1 members found this post helpful.

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

1 members found this post helpful.

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.

Attached Thumbnails

   

1 members found this post helpful.

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)

1 members found this post helpful.

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

2 members found this post helpful.

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.

1 members found this post helpful.

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

1 members found this post helpful.

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.

1 members found this post helpful.

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.

1 members found this post helpful.

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.

1 members found this post helpful.