LinuxQuestions.org - VirtualBox for Slackware Users

- Slackware (https://www.linuxquestions.org/questions/slackware-14/)

- - VirtualBox for Slackware Users (https://www.linuxquestions.org/questions/slackware-14/virtualbox-for-slackware-users-4175689027/)

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.

Code:

In file included from /ext/tmp/SBo/VirtualBox-6.1.18/src/VBox/Devices/Graphics/DevVGA-SVGA3d.cpp:39:

/ext/tmp/SBo/VirtualBox-6.1.18/src/VBox/Devices/Graphics/DevVGA-SVGA3d-internal.h:1073:9: error: ‘PFNGLVERTEXATTRIBDIVISORPROC’ does not name a type; did you mean ‘PFNGLVERTEXATTRIBDIVISORARBPROC’?

 1073 |        PFNGLVERTEXATTRIBDIVISORPROC                    glVertexAttribDivisor;

      |        ^~~~~~~~~~~~~~~~~~~~~~~~~~~~

      |        PFNGLVERTEXATTRIBDIVISORARBPROC

This command should fix Virtualbox crashing on startup:

Code:

VBoxManage setextradata global GUI/UpdateDate never

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

Quote:

Originally Posted by bitfuzzy (Post 6211130)

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

Quote:

Originally Posted by ctrlaltca (Post 6211093)

This command should fix Virtualbox crashing on startup:
Code:
VBoxManage setextradata global GUI/UpdateDate never

That's done the trick. Thanks!

Quote:

Originally Posted by willysr (Post 6211176)

6.1.18 is out already and it worked fine

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.

Quote:

Originally Posted by willysr (Post 6211176)

6.1.18 is out already and it worked fine

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

Quote:

Verifying archive integrity... All good.
Uncompressing VirtualBox 6.1.18 Guest Additions for Linux........
VirtualBox Guest Additions installer
./install.sh: line 143: VBoxControl: command not found
This system appears to have a version of the VirtualBox Guest Additions
already installed. If it is part of the operating system and kept up-to-date,
there is most likely no need to replace it. If it is not up-to-date, you
should get a notification when you start the system. If you wish to replace
it with this version, please do not continue with this installation now, but
instead remove the current version first, following the instructions for the
operating system.

If your system simply has the remains of a version of the Additions you could
not remove you should probably continue now, and these will be removed during
installation.

Do you wish to continue? [yes or no]

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

Quote:

Originally Posted by bitfuzzy (Post 6211312)

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.

Quote:

--Current, and thats where I have the kernel panic if guest additions are installed

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