I have a problem: The vboxdrv kernel module is not loaded....

[asir214]

I get this error message:

WARNING: The vboxdrv kernel module is not loaded. Either there is no module
         available for the current kernel (4.13.0-43-generic) or it failed to
         load. Please recompile the kernel module and install it by

           sudo /sbin/vboxconfig

         You will not be able to start VMs until this problem is fixed.

When I try to start vb from the console, and it does not let me run Genymotion.

Can someone help me? Any ideas?

Thank you very much

[socratis]

You will not be able to start VMs until this problem is fixed.

So, why are you trying to start a VM when you didn't try to fix the problem?

Please recompile the kernel module and install it by
sudo /sbin/vboxconfig

Did you do that? What was the terminal output of that process? Any errors?

[asir214]

This shows me the terminal

Created symlink /etc/systemd/system/multi-user.target.wants/vboxdrv.service → /lib/systemd/system/vboxdrv.service.
Created symlink /etc/systemd/system/multi-user.target.wants/vboxballoonctrl-service.service → /lib/systemd/system/vboxballoonctrl-service.service.
Created symlink /etc/systemd/system/multi-user.target.wants/vboxautostart-service.service → /lib/systemd/system/vboxautostart-service.service.
Created symlink /etc/systemd/system/multi-user.target.wants/vboxweb-service.service → /lib/systemd/system/vboxweb-service.service.
vboxdrv.sh: Stopping VirtualBox services.
vboxdrv.sh: Building VirtualBox kernel modules.
vboxdrv.sh: Starting VirtualBox services.
vboxdrv.sh: Building VirtualBox kernel modules.
vboxdrv.sh: failed: modprobe vboxdrv failed. Please use 'dmesg' to find out why.

There were problems setting up VirtualBox.  To re-start the set-up process, run
  /sbin/vboxconfig
as root.

[socratis]

vboxdrv.sh: failed: modprobe vboxdrv failed. Please use 'dmesg' to find out why.

[asir214]

Shows this the dmesg order:
A series of errors

[18509.610812] [drm:intel_pipe_update_end [i915]] *ERROR* Atomic update failure on pipe B (start=96819 end=96820) time 406 us, min 1073, max 1079, scanline start 1071, end 1098
[19537.254768] [drm:intel_pipe_update_end [i915]] *ERROR* Atomic update failure on pipe B (start=25014 end=25015) time 126 us, min 1073, max 1079, scanline start 1072, end 1080
[19587.338315] [drm:intel_pipe_update_end [i915]] *ERROR* Atomic update failure on pipe B (start=28019 end=28020) time 385 us, min 1073, max 1079, scanline start 1062, end 1064
[19695.106573] [drm:intel_pipe_update_end [i915]] *ERROR* Atomic update failure on pipe A (start=34491 end=34492) time 201 us, min 763, max 767, scanline start 759, end 762
[19774.717586] [drm:intel_pipe_update_end [i915]] *ERROR* Atomic update failure on pipe A (start=39268 end=39269) time 421 us, min 763, max 767, scanline start 760, end 764
[19793.065991] [drm:intel_pipe_update_end [i915]] *ERROR* Atomic update failure on pipe A (start=40369 end=40370) time 167 us, min 763, max 767, scanline start 760, end 768
[19841.704767] [drm:intel_pipe_update_end [i915]] *ERROR* Atomic update failure on pipe B (start=43281 end=43282) time 355 us, min 1073, max 1079, scanline start 1060, end 1084
[19903.374715] [drm:intel_pipe_update_end [i915]] *ERROR* Atomic update failure on pipe A (start=46988 end=46989) time 208 us, min 763, max 767, scanline start 762, end 772
[19905.221640] [drm:intel_pipe_update_end [i915]] *ERROR* Atomic update failure on pipe B (start=47092 end=47093) time 400 us, min 1073, max 1079, scanline start 1072, end 1099
[19917.988426] [drm:intel_pipe_update_end [i915]] *ERROR* Atomic update failure on pipe B (start=47858 end=47859) time 539 us, min 1073, max 1079, scanline start 1070, end 1097
[19960.053694] [drm:intel_pipe_update_end [i915]] *ERROR* Atomic update failure on pipe A (start=50389 end=50390) time 379 us, min 763, max 767, scanline start 751, end 769
[19973.919339] [drm:intel_pipe_update_end [i915]] *ERROR* Atomic update failure on pipe A (start=51221 end=51222) time 387 us, min 763, max 767, scanline start 751, end 769
[19993.354719] [drm:intel_pipe_update_end [i915]] *ERROR* Atomic update failure on pipe B (start=52380 end=52381) time 385 us, min 1073, max 1079, scanline start 1056, end 1082
[20052.388504] [drm:intel_pipe_update_end [i915]] *ERROR* Atomic update failure on pipe B (start=55922 end=55923) time 356 us, min 1073, max 1079, scanline start 1062, end 1086
[20056.354913] [drm:intel_pipe_update_end [i915]] *ERROR* Atomic update failure on pipe B (start=56160 end=56161) time 392 us, min 1073, max 1079, scanline start 1069, end 1095
[20168.388819] [drm:intel_pipe_update_end [i915]] *ERROR* Atomic update failure on pipe A (start=62890 end=62891) time 721 us, min 763, max 767, scanline start 759, end 3
[20192.588192] [drm:intel_pipe_update_end [i915]] *ERROR* Atomic update failure on pipe B (start=64334 end=64335) time 178 us, min 1073, max 1079, scanline start 1069, end 1081
[20207.485425] [drm:intel_pipe_update_end [i915]] *ERROR* Atomic update failure on pipe A (start=65236 end=65237) time 375 us, min 763, max 767, scanline start 751, end 753
[20214.888531] [drm:intel_pipe_update_end [i915]] *ERROR* Atomic update failure on pipe B (start=65672 end=65673) time 421 us, min 1073, max 1079, scanline start 1062, end 1090
[20426.003031] [drm:intel_pipe_update_end [i915]] *ERROR* Atomic update failure on pipe A (start=78348 end=78349) time 354 us, min 763, max 767, scanline start 758, end 775
[20431.252370] [drm:intel_pipe_update_end [i915]] *ERROR* Atomic update failure on pipe A (start=78663 end=78664) time 439 us, min 763, max 767, scanline start 754, end 775
[20456.355234] [drm:intel_pipe_update_end [i915]] *ERROR* Atomic update failure on pipe B (start=80160 end=80161) time 408 us, min 1073, max 1079, scanline start 1055, end 1060
[20504.413586] [drm:intel_pipe_update_end [i915]] *ERROR* Atomic update failure on pipe A (start=83053 end=83054) time 413 us, min 763, max 767, scanline start 753, end 756
[20580.505071] [drm:intel_pipe_update_end [i915]] *ERROR* Atomic update failure on pipe B (start=87609 end=87610) time 446 us, min 1073, max 1079, scanline start 1056, end 1086
[20875.488087] [drm:intel_pipe_update_end [i915]] *ERROR* Atomic update failure on pipe B (start=105308 end=105309) time 383 us, min 1073, max 1079, scanline start 1065, end 1091
[20878.252726] [drm:intel_pipe_update_end [i915]] *ERROR* Atomic update failure on pipe A (start=105485 end=105486) time 385 us, min 763, max 767, scanline start 757, end 775
[20879.554619] [drm:intel_pipe_update_end [i915]] *ERROR* Atomic update failure on pipe B (start=105552 end=105553) time 150 us, min 1073, max 1079, scanline start 1070, end 1080

[socratis]

You have to run 'dmesg' as soon as the failure to install vboxdrv happens, not at a random time. For more information, please run "man dmesg" to see why...

[WnT]

Hi,

I think, i have similiar problem. but the only different is, mine is only fail on startup. thus vboxweb service fail to start. the weird thing is, as soon as the boot is done, i can start vboxweb smoothly without any error whatsover.

This is my systemctl status vboxweb.service log after startup, before doing a manual vboxweb-service start

Code: Select all

● vboxweb.service - VirtualBox Web Service
     Loaded: loaded (/lib/systemd/system/vboxweb.service; enabled; vendor preset: enabled)
     Active: failed (Result: protocol) since Tue 2021-02-02 01:12:40 UTC; 33s ago
    Process: 925 ExecStart=/usr/lib/virtualbox/vboxweb-service.sh start (code=exited, status=0/SUCCESS)

Feb 02 01:07:03 wkubuntu systemd[1]: Starting VirtualBox Web Service...
Feb 02 01:07:03 wkubuntu vboxweb-service.sh[923]: vboxweb-service.sh: Starting VirtualBox web service.
Feb 02 01:07:03 wkubuntu vboxweb-service.sh[923]: vboxweb-service.sh: failed: VirtualBox kernel module not loaded!.
Feb 02 01:07:03 wkubuntu systemd[1]: vboxweb.service: Can't open PID file /run/vboxweb-service.sh (yet?) after start: Operation not permitted
Feb 02 01:07:03 wkubuntu systemd[1]: vboxweb.service: Failed with result 'protocol'.
Feb 02 01:07:03 wkubuntu systemd[1]: Failed to start VirtualBox Web Service.

This is my systemctl status vboxweb.service log after doing a manual vboxweb-service start ( systemctl start vboxweb )

Code: Select all

● vboxweb.service - VirtualBox Web Service
     Loaded: loaded (/lib/systemd/system/vboxweb.service; enabled; vendor preset: enabled)
     Active: active (running) since Tue 2021-02-02 01:08:06 UTC; 1min 11s ago
    Process: 1738 ExecStart=/usr/lib/virtualbox/vboxweb-service.sh start (code=exited, status=0/SUCCESS)
   Main PID: 1758 (vboxwebsrv)
      Tasks: 20 (limit: 9402)
     Memory: 42.7M
     CGroup: /system.slice/vboxweb.service
             ├─1758 /usr/lib/virtualbox/vboxwebsrv --background -H 127.0.0.1 -F /home/wk/vboxweb/vboxweb.log
             ├─1762 /usr/lib/virtualbox/VBoxXPCOMIPCD
             └─1768 /usr/lib/virtualbox/VBoxSVC --auto-shutdown

Feb 02 01:08:05 wkubuntu systemd[1]: Starting VirtualBox Web Service...
Feb 02 01:08:05 wkubuntu vboxweb-service.sh[1738]: vboxweb-service.sh: Starting VirtualBox web service.
Feb 02 01:08:06 wkubuntu systemd[1]: Started VirtualBox Web Service.

As you can see, on the first log, it mentioned:

Code: Select all

vboxweb-service.sh[923]: vboxweb-service.sh: failed: VirtualBox kernel module not loaded!.

so i tried dmesg with dmesg | grep "vbox", and the result is:

Code: Select all

[   10.774380] vboxdrv: loading out-of-tree module taints kernel.
[   10.774624] vboxdrv: module verification failed: signature and/or required key missing - tainting kernel
[   10.782880] vboxdrv: Found 8 processor cores
[   10.807066] vboxdrv: TSC mode is Invariant, tentative frequency 2294784280 Hz
[   10.807067] vboxdrv: Successfully loaded version 6.1.16_Ubuntu (interface 0x00300000)

i don't know what is wrong, but i suspect it is probably related to tmpfs paths i've set on my fstab:

Code: Select all

tmpfs   /tmp       tmpfs   defaults,noatime,mode=1777   0 0
tmpfs   /var/tmp   tmpfs   defaults,noatime,mode=1777   0 0
tmpfs /var/log tmpfs defaults,noatime,mode=1777 0 0

does vbox accessed any of the mentioned path above? i have redirected log file with adding this line on to /etc/default/virtualbox

Code: Select all

VBOXWEB_LOGFILE=/home/wk/vboxweb/vboxweb.log

as i had it on error (which is solved by now).

so does vbox access any other file mentioned on path above (tmpfs)? any suggestion/help is appreciated, thanks.

Regards,
William.