busted virtualboxes

[Stevo]

We suggest you wait until we get newer releases of virtualbox in our own test repo instead of getting and installing the deb from Oracle, which is the root cause of your issue with 6.1.0. We're waiting for Debian to get it upstream.

Edit: Debian just added it in Sid today, so I'm backporting it now.

[toto]

Ok Stevo.

Please keep me updated.

Thank you!

[Stevo]

OK, packages are built and on the way to the test repo. I also added them to my Vbox backports for Buster repo on the OBS: https://build.opensuse.org/project/show ... box-buster

[toto]

I tried to install virtualbox_6.1.0-dfsg-2~obs_amd64.deb but I get the following error:

Error:
Dependency is not satisfiable: python3(>=3.7~)

[Stevo]

Toto, you must be running MX 17 or 18, based on Stretch. That OBS repo is strictly for Debian Buster and distros based on it, like MX 19.

It should also be in the MX 17/18 test repo now, so you can install it with MX Package Installer--Test Repo tab--search for virtualbox. It should automatically remove the Oracle version if you still have that installed.

[toto]

I am indeed using MX Linux 18.3.

I installed virtualbox with MX Package Installer--Test Repo tab but I still get the same errors.

[Stevo]

What happens when you try and build the virtualbox-dkms kernel drivers manually?

Code: Select all

sudo dpkg-reconfigure virtualbox-dkms

[toto]

I still get modprobe vboxdrv failing

Code: Select all

-------- Uninstall Beginning --------
Module:  virtualbox
Version: 6.1.0
Kernel:  4.19.0-5-amd64 (x86_64)
-------------------------------------

Status: Before uninstall, this module version was ACTIVE on this kernel.

vboxdrv.ko:
 - Uninstallation
   - Deleting from: /lib/modules/4.19.0-5-amd64/updates/
 - Original module
   - No original module was found for this module on this kernel.
   - Use the dkms install command to reinstall any previous module version.


vboxnetadp.ko:
 - Uninstallation
   - Deleting from: /lib/modules/4.19.0-5-amd64/updates/
 - Original module
   - No original module was found for this module on this kernel.
   - Use the dkms install command to reinstall any previous module version.


vboxnetflt.ko:
 - Uninstallation
   - Deleting from: /lib/modules/4.19.0-5-amd64/updates/
 - Original module
   - No original module was found for this module on this kernel.
   - Use the dkms install command to reinstall any previous module version.

depmod...

DKMS: uninstall completed.

------------------------------
Deleting module version: 6.1.0
completely from the DKMS tree.
------------------------------
Done.
Loading new virtualbox-6.1.0 DKMS files...
Building for 4.19.0-5-amd64
Building initial module for 4.19.0-5-amd64
Done.

vboxdrv:
Running module version sanity check.
 - Original module
   - No original module exists within this kernel
 - Installation
   - Installing to /lib/modules/4.19.0-5-amd64/updates/

vboxnetadp.ko:
Running module version sanity check.
 - Original module
   - No original module exists within this kernel
 - Installation
   - Installing to /lib/modules/4.19.0-5-amd64/updates/

vboxnetflt.ko:
Running module version sanity check.
 - Original module
   - No original module exists within this kernel
 - Installation
   - Installing to /lib/modules/4.19.0-5-amd64/updates/

depmod...

DKMS: install completed.
[ ok ] Unloading VirtualBox kernel modules....
[....] Loading VirtualBox kernel modules...[....] modprobe vboxdrv failed. Please use 'dmesg' to fin[FAIL why ... failed!
 failed!
invoke-rc.d: initscript virtualbox, action "restart" failed.

[figueroa]

Consider downgrading to stable, well-tested, VirtualBox 5.2.24. Then you should be able to count on virtualbox-dkms rebuilding modules for your current kernel.

[asqwerth]

From my MX17/18 usage, it seems to me that if you move to VB6+, it's better to be on the Liquorix 5+ kernels found in Test Repo.

If you are on kernel 4.19, stay with VB5+.

Even if VB6 works with 4.19 kernel, there may be issues within your Virtual machines (with shared folder). That happened for one of my MX17/18 installs where I chose the Virtualbox 6 entry from MXPI >> Popular Apps (or maybe Test repo???) tab. In the end I had to upgrade to Liquorix 5+ kernel and then everything worked.

I can't recall fully, but I think for the second MX17/18 install, I had simply used Synaptic to install that monolithic Oracle Virtualbox 6 entry (not the debian repo versions of VB), replacing my then-current VB5. I didn't change or update the initial mx/debian guest-additions-iso package, which remained at version 5+. That seemed to work ok with 4.19 kernel.

YMMV.

This was some time ago so I might have recalled imperfectly. I think I previously posted a bit on my experiences.