Skip to main content
Topic: The constant incompatibilities of virtualbox -- how to cure them (Read 456 times) previous topic - next topic
0 Members and 1 Guest are viewing this topic.

Re: The constant incompatibilities of virtualbox -- how to cure them

Reply #15
All current upgrades work:

local/linux 4.20.4.artix1-1
local/linux-headers 4.20.4.artix1-1
local/virtualbox 6.0.4-1
local/virtualbox-guest-modules-artix 6.0.2-4
local/virtualbox-host-modules-artix 6.0.2-4

Not for me.  Just tried upgrading again this morning and back to the same error.

EDIT:  Didn't see my kernel was updated.  On 4.20.6-artix1-1-ARTIX

EDIT2:
Code: [Select]
The VirtualBox kernel modules do not match this version of VirtualBox. The installation of VirtualBox was apparently not successful. Executing

'/sbin/vboxconfig'

may correct this. Make sure that you do not mix the OSE version and the PUEL version of VirtualBox.

where: supR3HardenedMainInitRuntime what: 4 VERR_VM_DRIVER_VERSION_MISMATCH (-1912) - The installed support driver doesn't match the version of the user.

Code: [Select]
linux 4.20.6.artix1-1
linux-headers 4.20.6.artix1-1
virtualbox 6.0.4-1
virtualbox-guest-iso 6.0.4-1
virtualbox-host-modules-artix 6.0.4-3

These are the only packages I have available to me because I missed the 6.0.2-4 packages and only have 6.0.2-1 left over from the previous attempts and don't see your combination available :-/

EDIT3: Yes I tried dkms as well.

Re: The constant incompatibilities of virtualbox -- how to cure them

Reply #16
Code: [Select]
linux 4.20.6.artix1-1
linux-headers 4.20.6.artix1-1
local/virtualbox 6.0.4-1
local/virtualbox-guest-modules-artix 6.0.4-3
local/virtualbox-host-modules-artix 6.0.4-3

This combination works fine in my system, I wonder what else can make the difference.

Re: The constant incompatibilities of virtualbox -- how to cure them

Reply #17
Dunno.  I'm pretty vanilla.  Artix + VirtualBox + Firefox + Google Chrome + Spotify + pamac (for the update notifications "ONLY".  I do all the updates manually with pacman) + Nvidia DKMS.  that's the only things I've added. 


Re: The constant incompatibilities of virtualbox -- how to cure them

Reply #19
5.2.22 for life I guess....... ::)

Re: The constant incompatibilities of virtualbox -- how to cure them

Reply #20
5.2.22 for life I guess....... ::)

Nope, vbox works, just use dkms.
For dkms to work, you need to have base-devel group and the kernel headers installed.
I seriously don't get the trouble with dkms.

Re: The constant incompatibilities of virtualbox -- how to cure them

Reply #21
I have been using DKMS since I came over to Artix.  The 6 branch of Virtualbox has not worked no matter what combination I use.  Fungalnet had the good fortune of downloading the 2-4 packages which I didn't so no Virtualbox 6 for me as I only had older and newer versions and not the combination that worked for him.  But now, it appears that he found that the new QT5 update borks it so I'm holding off again.

Re: The constant incompatibilities of virtualbox -- how to cure them

Reply #22
The previous error about qt5 was my mistake, the upgrade was done with qt5-base being held back, hence the incompatibility.
I tried to delete the comment but couldn't so I replaced it with "delete" for an admin to do it.

I tried with DKMS and it works as well.

Code: [Select]
local/virtualbox 6.0.4-1
local/virtualbox-host-dkms 6.0.4-1
local/linux 4.20.6.artix1-1 (base)
local/linux-headers 4.20.6.artix1-1

Re: The constant incompatibilities of virtualbox -- how to cure them

Reply #23
Ok I'll give it a whirl tomorrow.  Thanks Fungalnet.

Re: The constant incompatibilities of virtualbox -- how to cure them

Reply #24
I don't know if it makes a difference in any dependencies but I use gremlins repositories.
Code: [Select]
Name            : virtualbox
Version         : 6.0.4-1
Depends On      : glibc  openssl  curl  gcc-libs  libpng  python  sdl  libvpx  libxml2  procps-ng
                  shared-mime-info  zlib  libxcursor  libxinerama  libx11  libxext  libxmu  libxt  opus
                  qt5-base  qt5-x11extras  VIRTUALBOX-HOST-MODULES

None of the above seem to come from gremlins now, but I'm not sure if their dependencies do.  Just mentioning it in case we can locate the incompatibility difference.

Re: The constant incompatibilities of virtualbox -- how to cure them

Reply #25
I don't know if it makes a difference in any dependencies but I use gremlins repositories.

That I'm not using.  I only run from the stable repos so maybe the issues have been fixed but they're still in Gremlins?

Re: The constant incompatibilities of virtualbox -- how to cure them

Reply #26
Here goes nothing again:

Code: [Select]
Packages (3) virtualbox-6.0.4-1  virtualbox-guest-iso-6.0.4-1  virtualbox-host-dkms-6.0.4-1

Total Installed Size:  270.85 MiB

:: Proceed with installation? [Y/n] Y
(3/3) checking keys in keyring                                 [##################################] 100%
(3/3) checking package integrity                               [##################################] 100%
(3/3) loading package files                                    [##################################] 100%
(3/3) checking for file conflicts                              [##################################] 100%
(3/3) checking available disk space                            [##################################] 100%
:: Processing package changes...
(1/3) installing virtualbox-host-dkms                          [##################################] 100%
Optional dependencies for virtualbox-host-dkms
    linux-headers: build modules against Arch kernel [installed]
    linux-lts-headers: build modules against LTS kernel
    linux-zen-headers: build modules against ZEN kernel
(2/3) installing virtualbox                                    [##################################] 100%
Optional dependencies for virtualbox
    vde2: Virtual Distributed Ethernet support
    virtualbox-guest-iso: Guest Additions CD image [pending]
    virtualbox-ext-vnc: VNC server support
    virtualbox-sdk: Developer kit
(3/3) installing virtualbox-guest-iso                          [##################################] 100%

===> virtualbox-guest-iso post install message:
===>
===> Redistribution of VBoxGuestAdditions.iso from the binary packages
===> on www.virtualbox.org with Arch Linux has been granted by
===> InnoTek Systemberatung GmbH.
===>
===> By using this package you accept
===> the VirtualBox Personal Use and Evaluation License (PUEL)
===> which can be found here: http://virtualbox.org/wiki/VirtualBox_PUEL
===>
===> If you do not accept this license, you must remove the package immediately.
===>

:: Running post-transaction hooks...
(1/6) Install DKMS modules
==> dkms install vboxhost/6.0.4_OSE -k 4.20.6-artix1-1-ARTIX
(2/6) Updating icon theme caches...
(3/6) Updating system users and groups
(4/6) Reloading device manager configuration...
(5/6) Updating the desktop file MIME type cache...
(6/6) Updating the MIME type database...

Removed or moved all old config directories just in case as well.

And after the reboot:

Code: [Select]
[Wed Feb  6 10:19:15 2019] vboxdrv: loading out-of-tree module taints kernel.
[Wed Feb  6 10:19:15 2019] vboxdrv: module verification failed: signature and/or required key missing - tainting kernel
[Wed Feb  6 10:19:15 2019] vboxdrv: Found 8 processor cores
[Wed Feb  6 10:19:15 2019] vboxdrv: TSC mode is Invariant, tentative frequency 2903997793 Hz
[Wed Feb  6 10:19:15 2019] vboxdrv: Successfully loaded version 5.2.22 (interface 0x00290001)
[Wed Feb  6 10:19:15 2019] VBoxNetFlt: Successfully started.
[Wed Feb  6 10:19:15 2019] VBoxNetAdp: Successfully started.
[Wed Feb  6 10:19:15 2019] VBoxPciLinuxInit
[Wed Feb  6 10:19:15 2019] vboxpci: IOMMU not found (not registered)

Code: [Select]
RTR3InitEx failed with rc=-1912 (rc=-1912)

The VirtualBox kernel modules do not match this version of VirtualBox. The installation of VirtualBox was apparently not successful. Executing

'/sbin/vboxconfig'

may correct this. Make sure that you do not mix the OSE version and the PUEL version of VirtualBox.

where: supR3HardenedMainInitRuntime what: 4 VERR_VM_DRIVER_VERSION_MISMATCH (-1912) - The installed support driver doesn't match the version of the user.

Back in the same hole.

Think I'm getting further:
Code: [Select]
cat /sys/modules/vboxdrv/version

5.2.22 r126257 (0x00290001)

It doesn't look like the modules were updated unless I'm just looking in the totally wrong place.

This is what the stack looks like now:

Code: [Select]
linux 4.20.6.artix1-1
linux-headers 4.20.6.artix1-1
dkms 2.5-4
virtualbox 6.0.4-1
virtualbox-guest-iso 6.0.4-1
virtualbox-host-dkms 6.0.4-1

Code: [Select]
dkms status
nvidia, 415.27, 4.20.6-artix1-1-ARTIX, x86_64: installed
vboxhost, 6.0.4_OSE, 4.20.6-artix1-1-ARTIX, x86_64: installed

Re: The constant incompatibilities of virtualbox -- how to cure them

Reply #27
Ok now the problem is completely beyond me.  I totally purged anything to do with virtualbox and the kernel modules and verified by checking the whole file system for anything named vboxdrv,vboxpci,vboxnetadp & vboxnetflt and made sure there was nothing and  rebooted.  Reinstalled the virtualbox packages and rebooted again.  When the machine was booting back up, I watched rc start loading kernel modules and saw both success and failures for the virtualbox modules.  When it was finally back up I checked /sys/modules/vboxdrv and somehow the  5.2.22 r126257 (0x00290001) was loaded again!!  I rmmoded all the modules and manually modprobed them back in and the correct versions loaded.  How can I correct this now.  It is the root of the problem and now virtualbox 6 works but I need to get the correct versioned modules loaded.  Any ideas on how the old versions are getting added?

Re: The constant incompatibilities of virtualbox -- how to cure them

Reply #28
Ok you can mark this solved.  The issue was self inflicted.  I had manually added the modules to mkinitcpio.conf way back in the early Artix days because they weren't loading by themselves at the time.  Once I removed them from mkinitcpio.conf and regenerated the config and rebooted, the proper modules loaded automagically.