busted virtualboxes

[JayM]

I fired up my laptop today (just to install the latest MX updates and charge the battery) and for grins I installed the 4.9.193 antiX kernel and booted with it (even though the default MX 4.19.0-6 kernel was working fine) then opened VirtualBox, which is 6.0.12, and ran a Xubuntu 19.10 guest OS with no problems. This is in MX-19 though, but even on my old desktop PC with MX-18.3 and a 4.9 kernel I was able to run VB 6.0.x IIRC.

Host QSI:

Code: Select all

System:    Host: mx-19 Kernel: 4.9.193-antix.1-amd64-smp x86_64 bits: 64 compiler: gcc v: 8.3.0 
           parameters: BOOT_IMAGE=/vmlinuz-4.9.193-antix.1-amd64-smp 
           root=UUID=9fb8104e-61fd-4f54-bfb7-e7d68d124ca1 ro quiet splash 
           Desktop: Xfce 4.14.1 tk: Gtk 3.24.5 info: xfce4-panel wm: xfwm4 dm: LightDM 1.26.0 
           Distro: MX-19_x64 patito feo October 15  2019 base: Debian GNU/Linux 10 (buster) 
Machine:   Type: Laptop System: Hewlett-Packard product: HP Pavilion dv6 Notebook PC 
           v: 049D210000241210000020000 serial: <filter> Chassis: type: 10 serial: <filter> 
           Mobo: Hewlett-Packard model: 3659 v: 32.25 serial: <filter> BIOS: Hewlett-Packard 
           v: F.1B date: 04/23/2010 
Battery:   ID-1: BAT0 charge: 27.3 Wh condition: 30.1/47.5 Wh (63%) volts: 12.6/10.8 
           model: Hewlett-Packard Primary type: NiMH serial: <filter> status: Charging 
CPU:       Topology: Dual Core model: Intel Core i5 M 430 bits: 64 type: MT MCP arch: Nehalem 
           family: 6 model-id: 25 (37) stepping: 2 microcode: 11 L2 cache: 3072 KiB 
           flags: lm nx pae sse sse2 sse3 sse4_1 sse4_2 ssse3 vmx bogomips: 18088 
           Speed: 1199 MHz min/max: 1199/2267 MHz boost: enabled Core speeds (MHz): 1: 1199 
           2: 1199 3: 1199 4: 1199 
           Vulnerabilities: Type: l1tf 
           mitigation: PTE Inversion; VMX: conditional cache flushes, SMT vulnerable 
           Type: mds 
           status: Vulnerable: Clear CPU buffers attempted, no microcode; SMT vulnerable 
           Type: meltdown mitigation: PTI 
           Type: spec_store_bypass 
           mitigation: Speculative Store Bypass disabled via prctl and seccomp 
           Type: spectre_v1 mitigation: usercopy/swapgs barriers and __user pointer sanitization 
           Type: spectre_v2 mitigation: Full generic retpoline, IBPB: conditional, IBRS_FW, 
           STIBP: conditional, RSB filling 
Graphics:  Device-1: NVIDIA GT216M [GeForce GT 230M] vendor: Hewlett-Packard driver: nouveau 
           v: kernel bus ID: 01:00.0 chip ID: 10de:0a28 
           Display: x11 server: X.Org 1.20.4 driver: modesetting unloaded: fbdev,vesa 
           resolution: 1366x768~60Hz 
           OpenGL: renderer: NVA5 v: 3.3 Mesa 18.3.6 direct render: Yes 
Audio:     Device-1: Intel 5 Series/3400 Series High Definition Audio vendor: Hewlett-Packard 
           driver: snd_hda_intel v: kernel bus ID: 00:1b.0 chip ID: 8086:3b56 
           Device-2: NVIDIA GT216 HDMI Audio vendor: Hewlett-Packard driver: snd_hda_intel 
           v: kernel bus ID: 01:00.1 chip ID: 10de:0be2 
           Device-3: Philips s SAA7160 vendor: Avermedia driver: N/A bus ID: 04:00.0 
           chip ID: 1131:7160 
           Sound Server: ALSA v: k4.9.193-antix.1-amd64-smp 
Network:   Device-1: Broadcom Limited BCM43225 802.11b/g/n vendor: Hewlett-Packard driver: wl 
           v: kernel port: 7000 bus ID: 02:00.0 chip ID: 14e4:4357 
           IF: wlan0 state: up mac: <filter> 
           Device-2: Realtek RTL8111/8168/8411 PCI Express Gigabit Ethernet 
           vendor: Hewlett-Packard driver: r8169 v: 2.3LK-NAPI port: 5000 bus ID: 03:00.0 
           chip ID: 10ec:8168 
           IF: eth0 state: down mac: <filter> 
Drives:    Local Storage: total: 465.76 GiB used: 281.32 GiB (60.4%) 
           ID-1: /dev/sda vendor: Seagate model: ST9500325AS size: 465.76 GiB block size: 
           physical: 512 B logical: 512 B speed: 3.0 Gb/s rotation: 5400 rpm serial: <filter> 
           rev: SDM1 scheme: MBR 
Partition: ID-1: / raw size: 463.21 GiB size: 454.94 GiB (98.21%) used: 281.08 GiB (61.8%) 
           fs: ext4 dev: /dev/dm-0 
           ID-2: /boot raw size: 512.0 MiB size: 487.9 MiB (95.30%) used: 245.1 MiB (50.2%) 
           fs: ext4 dev: /dev/sda1 
           ID-3: swap-1 size: 1.98 GiB used: 0 KiB (0.0%) fs: swap swappiness: 15 (default 60) 
           cache pressure: 100 (default) dev: /dev/dm-1 
Sensors:   System Temperatures: cpu: 63.0 C mobo: N/A gpu: nouveau temp: 75 C 
           Fan Speeds (RPM): N/A 
Repos:     No active apt repos in: /etc/apt/sources.list 
           Active apt repos in: /etc/apt/sources.list.d/antix.list 
           1: deb https://mirror.pregi.net/mx-linux-packages/antix/buster/ buster main
           Active apt repos in: /etc/apt/sources.list.d/debian-stable-updates.list 
           1: deb http://mirror.pregi.net/debian/ buster-updates main contrib non-free
           Active apt repos in: /etc/apt/sources.list.d/debian.list 
           1: deb http://mirror.pregi.net/debian/ buster main contrib non-free
           2: deb http://deb.debian.org/debian-security buster/updates main contrib non-free
           Active apt repos in: /etc/apt/sources.list.d/mx.list 
           1: deb https://mirror.pregi.net/mx-linux-packages/mx/repo/ buster main non-free
           No active apt repos in: /etc/apt/sources.list.d/various.list 
Info:      Processes: 282 Uptime: 14m Memory: 3.79 GiB used: 1.66 GiB (43.8%) Init: SysVinit 
           v: 2.93 runlevel: 5 default: 5 Compilers: gcc: 8.3.0 alt: 8 Shell: bash v: 5.0.3 
           running in: quick-system-in inxi: 3.0.36 

Guest inxi -Fxxxza:

Code: Select all

System:
  Host: jay Kernel: 5.3.0-19-generic x86_64 bits: 64 compiler: gcc v: 9.2.1 
  parameters: BOOT_IMAGE=/boot/vmlinuz-5.3.0-19-generic 
  root=UUID=6f7e2d89-442c-472a-8031-673626d7248a ro quiet splash 
  Desktop: Xfce 4.14.1 tk: Gtk 3.24.10 info: xfce4-panel wm: xfwm4 
  dm: LightDM 1.30.0 Distro: Ubuntu 19.10 (Eoan Ermine) 
Machine:
  Type: Virtualbox System: innotek product: VirtualBox v: 1.2 
  serial: <filter> Chassis: Oracle Corporation type: 1 serial: <filter> 
  Mobo: Oracle model: VirtualBox v: 1.2 serial: <filter> BIOS: innotek 
  v: VirtualBox date: 12/01/2006 
Battery:
  ID-1: BAT0 charge: 50.0 Wh condition: 50.0/50.0 Wh (100%) volts: 10.0/10.0 
  model: innotek 1 type: Unknown serial: N/A status: Full 
CPU:
  Topology: Single Core model: Intel Core i5 M 430 bits: 64 type: MCP 
  arch: Nehalem family: 6 model-id: 25 (37) stepping: 2 microcode: 616 
  L2 cache: 3072 KiB 
  flags: lm nx pae sse sse2 sse3 sse4_1 sse4_2 ssse3 bogomips: 4522 
  Speed: 2261 MHz min/max: N/A Core speed (MHz): 1: 2261 
  Vulnerabilities: Type: l1tf mitigation: PTE Inversion 
  Type: mds status: Vulnerable: Clear CPU buffers attempted, no microcode; 
  SMT Host state unknown 
  Type: meltdown mitigation: PTI 
  Type: spec_store_bypass status: Vulnerable 
  Type: spectre_v1 
  mitigation: usercopy/swapgs barriers and __user pointer sanitization 
  Type: spectre_v2 
  mitigation: Full generic retpoline, STIBP: disabled, RSB filling 
Graphics:
  Device-1: VMware SVGA II Adapter driver: vmwgfx v: 2.15.0.0 
  bus ID: 00:02.0 chip ID: 15ad:0405 
  Display: x11 server: X.Org 1.20.5 driver: vmware 
  unloaded: fbdev,modesetting,vesa resolution: 1331x645~60Hz 
  OpenGL: renderer: SVGA3D; build v: 2.1 Mesa 19.2.1 direct render: Yes 
Audio:
  Device-1: Intel 82801AA AC97 Audio vendor: Dell driver: snd_intel8x0 
  v: kernel bus ID: 00:05.0 chip ID: 8086:2415 
  Sound Server: ALSA v: k5.3.0-19-generic 
Network:
  Device-1: Intel 82540EM Gigabit Ethernet driver: e1000 v: 7.3.21-k8-NAPI 
  port: d020 bus ID: 00:03.0 chip ID: 8086:100e 
  IF: enp0s3 state: up speed: 1000 Mbps duplex: full mac: <filter> 
  Device-2: Intel 82371AB/EB/MB PIIX4 ACPI type: network bridge 
  driver: piix4_smbus v: N/A port: d200 bus ID: 00:07.0 chip ID: 8086:7113 
Drives:
  Local Storage: total: 10.00 GiB used: 5.76 GiB (57.6%) 
  ID-1: /dev/sda vendor: VirtualBox model: VBOX HARDDISK size: 10.00 GiB 
  block size: physical: 512 B logical: 512 B speed: 3.0 Gb/s 
  serial: <filter> rev: 1.0 scheme: MBR 
Partition:
  ID-1: / raw size: 10.00 GiB size: 9.78 GiB (97.80%) used: 5.76 GiB (58.9%) 
  fs: ext4 dev: /dev/sda1 
Sensors:
  Message: No sensors data was found. Is sensors configured? 
Info:
  Processes: 153 Uptime: 2m Memory: 1.94 GiB used: 462.8 MiB (23.3%) 
  Init: systemd v: 242 runlevel: 5 Compilers: gcc: 9.2.1 alt: 9 Shell: bash 
  v: 5.0.3 running in: xfce4-terminal inxi: 3.0.36 

[asqwerth]

What version is your guest-additions-iso, JayM?

[JayM]

What version is your guest-additions-iso, JayM?

6.0.12-mx19+1

[toto]

I installed Virtualbox 5.2.24 and I ran

Code: Select all

sudo dpkg-reconfigure virtualbox-dkms

Here is the output I get

Code: Select all

-------- Uninstall Beginning --------
Module:  virtualbox
Version: 5.2.24
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.


vboxpci.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: 5.2.24
completely from the DKMS tree.
------------------------------
Done.
Loading new virtualbox-5.2.24 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/

vboxpci.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.

However, Virtualbox is still not working as I get the same error message

Code: Select all

Kernel driver not installed (rc=-1908)

The VirtualBox Linux kernel driver (vboxdrv) is either not loaded or there is a permission problem with /dev/vboxdrv. Please reinstall virtualbox-dkms package and load the kernel module by executing

'modprobe vboxdrv'

as root.

where: suplibOsInit what: 3 VERR_VM_DRIVER_NOT_INSTALLED (-1908) - The support driver is not installed. On linux, open returned ENOENT. 

[JayM]

Have you tried going to

Code: Select all

/usr/share/mx-packageinstaller-pkglist

then running

Code: Select all

./rebuild_dkms_packages.sh

as root (su)?

[toto]

I ran the script and here is what I get

Code: Select all

-------- Uninstall Beginning --------
Module:  broadcom-sta
Version: 6.30.223.271
Kernel:  4.19.0-5-amd64 (x86_64)
-------------------------------------

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

wl.ko:
 - Uninstallation
   - Deleting from: /lib/modules/4.19.0-5-amd64/updates/dkms/
 - 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...

Backing up initrd.img-4.19.0-5-amd64 to /boot/initrd.img-4.19.0-5-amd64.old-dkms
Making new initrd.img-4.19.0-5-amd64
(If next boot fails, revert to initrd.img-4.19.0-5-amd64.old-dkms image)
update-initramfs.............

DKMS: uninstall completed.

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

wl:
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/dkms/

depmod...

Backing up initrd.img-4.19.0-5-amd64 to /boot/initrd.img-4.19.0-5-amd64.old-dkms
Making new initrd.img-4.19.0-5-amd64
(If next boot fails, revert to initrd.img-4.19.0-5-amd64.old-dkms image)
update-initramfs.........

DKMS: install completed.

-------- Uninstall Beginning --------
Module:  ndiswrapper
Version: 1.62
Kernel:  4.19.0-5-amd64 (x86_64)
-------------------------------------

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

ndiswrapper.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: 1.62
completely from the DKMS tree.
------------------------------
Done.
Loading new ndiswrapper-1.62 DKMS files...
Building for 4.19.0-5-amd64
Building initial module for 4.19.0-5-amd64
Done.

ndiswrapper:
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.

-------- Uninstall Beginning --------
Module:  virtualbox
Version: 5.2.24
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.


vboxpci.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: 5.2.24
completely from the DKMS tree.
------------------------------
Done.
Loading new virtualbox-5.2.24 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/

vboxpci.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.

Still getting the same error when I try to run Virtualbox

[Stevo]

Does running

Code: Select all

sudo modprobe vboxdrv

as they suggest fix it?

If not, I think you may still have problems left over from installing the Oracle version. If you use Synaptic with the Installed status tab, and search for "virtualbox", what does it say is installed?

The Debian Vbox wiki also lists your errors under troubleshooting, so you could try their fixes: https://wiki.debian.org/VirtualBox

[toto]

Code: Select all

sudo modprobe vboxdrv

gives me the error

Code: Select all

modprobe: ERROR: could not insert 'vboxdrv': Exec format error

I used Synaptic with the Installed status tab and searched for "virtualbox": see attachment.

[Stevo]

OK...and what does "uname -a" report for you in the terminal?

[figueroa]

I think the modprobe error means it's trying to load a module built for a different kernel.

Look in /lib/modules/ for kernel drivers that match your running kernel, which you get with uname -a. There, with a little searching, you should find:
vboxdrv.ko
vboxnetadp.ko
vboxnetflt.ko
vboxpci.ko

For a quick check you can do:

Code: Select all

ls /lib/modules/[YOUR KERNEL]/* | grep vbox

If it doesn't return a list of those modules, they haven't been build for the running kernel. If the modules ARE found, then at least the not-built problem has been eliminated.