Manjaro Linux -Forum Italiano-

virtualbox mi segnala errore "modulo kernel fallito"

0 Utenti e 1 Visitatore stanno visualizzando questo topic.

virtualbox mi segnala errore "modulo kernel fallito"
« il: Maggio 25, 2017, 10:19:13 am »
Ciao a tutti, avviando virtualbox mi segnala errore al modulo del kernel, in allegato riporto l'immagine:
di seguito l'output di:
Codice: [Seleziona]
[skiava@skiava-pc ~]$ systemctl -t service
  UNIT                           LOAD   ACTIVE SUB     DESCRIPTION             
  accounts-daemon.service        loaded active running Accounts Service         
  alsa-restore.service           loaded active exited  Save/Restore Sound Card S
  colord.service                 loaded active running Manage, Install and Gener
  cronie.service                 loaded active running Periodic Command Schedule
  dbus.service                   loaded active running D-Bus System Message Bus
  gdm.service                    loaded active running GNOME Display Manager   
  geoclue.service                loaded active running Location Lookup Service 
  kmod-static-nodes.service      loaded active exited  Create list of required s
  lvm2-lvmetad.service           loaded active running LVM2 metadata daemon     
  lvm2-pvscan@8:2.service        loaded active exited  LVM2 PV scan on device 8:
  ModemManager.service           loaded active running Modem Manager           
  NetworkManager.service         loaded active running Network Manager         
  ntpd.service                   loaded active running Network Time Service     
  org.cups.cupsd.service         loaded active running CUPS Scheduler           
  polkit.service                 loaded active running Authorization Manager   
  rtkit-daemon.service           loaded active running RealtimeKit Scheduling Po
  systemd-journal-flush.service  loaded active exited  Flush Journal to Persiste
  systemd-journald.service       loaded active running Journal Service         
  systemd-logind.service         loaded active running Login Service           
● systemd-modules-load.service   loaded failed failed  Load Kernel Modules     
  systemd-random-seed.service    loaded active exited  Load/Save Random Seed   
  systemd-remount-fs.service     loaded active exited  Remount Root and Kernel F
  systemd-sysctl.service         loaded active exited  Apply Kernel Variables   
  systemd-tmpfiles-setup-dev.service loaded active exited  Create Static Device
  systemd-tmpfiles-setup.service loaded active exited  Create Volatile Files and
  systemd-udev-trigger.service   loaded active exited  udev Coldplug all Devices
  systemd-udevd.service          loaded active running udev Kernel Device Manage
  systemd-update-utmp.service    loaded active exited  Update UTMP about System
  systemd-user-sessions.service  loaded active exited  Permit User Sessions     
  tlp.service                    loaded active exited  TLP system startup/shutdo
  udisks2.service                loaded active running Disk Manager             
  upower.service                 loaded active running Daemon for power manageme
  user@1000.service              loaded active running User Manager for UID 1000
  user@120.service               loaded active running User Manager for UID 120
  wpa_supplicant.service         loaded active running WPA supplicant           

LOAD   = Reflects whether the unit definition was properly loaded.
ACTIVE = The high-level unit activation state, i.e. generalization of SUB.
SUB    = The low-level unit activation state, values depend on unit type.

35 loaded units listed. Pass --all to see loaded but inactive units, too.
To show all installed unit files use 'systemctl list-unit-files'.
lines 21-43/43 (END)

[skiava@skiava-pc ~]$ systemctl status systemd-modules-load.service
● systemd-modules-load.service - Load Kernel Modules
   Loaded: loaded (/usr/lib/systemd/system/systemd-modules-load.service; static; vendor preset: disabled)
   Active: failed (Result: exit-code) since Thu 2017-05-25 09:47:26 CEST; 1min 20s ago
     Docs: man:systemd-modules-load.service(8)
           man:modules-load.d(5)
 Main PID: 8728 (code=exited, status=1/FAILURE)

mag 25 09:47:26 skiava-pc systemd[1]: Starting Load Kernel Modules...
mag 25 09:47:26 skiava-pc systemd[1]: systemd-modules-load.service: Main process exited, code=exited, status=1/FAILURE
mag 25 09:47:26 skiava-pc systemd[1]: Failed to start Load Kernel Modules.
mag 25 09:47:26 skiava-pc systemd[1]: systemd-modules-load.service: Unit entered failed state.
mag 25 09:47:26 skiava-pc systemd[1]: systemd-modules-load.service: Failed with result 'exit-code'.
[skiava@skiava-pc ~]$ journalctl -xe
mag 25 09:45:01 skiava-pc org.gnome.Shell.desktop[7665]: Window manager warning: Invalid WM_TRANSIENT_FOR window 0x3e00007 specified for 0x3e00005 (VirtualBox).
mag 25 09:45:03 skiava-pc VirtualBox[8690]: <html><b>Kernel driver not installed (rc=-1908)</b><br/><br/>The VirtualBox Linux kernel driver (vboxdrv) is either not loaded or there is a permission problem w
                                            what:  3
                                            VERR_VM_DRIVER_NOT_INSTALLED (-1908) - The support driver is not installed. On linux, open returned ENOENT.
                                            </html>
mag 25 09:45:27 skiava-pc VirtualBox[8714]: qt5ct: using qt5ct plugin
mag 25 09:45:29 skiava-pc org.gnome.Shell.desktop[7665]: Window manager warning: Invalid WM_TRANSIENT_FOR window 0x3e00007 specified for 0x3e00005 (VirtualBox).
mag 25 09:45:30 skiava-pc org.gnome.Shell.desktop[7665]: Window manager warning: last_focus_time (869275) is greater than comparison timestamp (869262).  This most likely represents a buggy client sending
mag 25 09:46:14 skiava-pc systemd[1]: Starting Cleanup of Temporary Directories...
-- Subject: L'unit systemd-tmpfiles-clean.service inizia la fase di avvio
-- Defined-By: systemd
-- Support: http://lists.freedesktop.org/mailman/listinfo/systemd-devel
--
-- L'unit systemd-tmpfiles-clean.service ha iniziato la fase di avvio.
mag 25 09:46:14 skiava-pc systemd[1]: Started Cleanup of Temporary Directories.
-- Subject: L'unit systemd-tmpfiles-clean.service termina la fase di avvio
-- Defined-By: systemd
-- Support: http://lists.freedesktop.org/mailman/listinfo/systemd-devel
--
-- L'unit systemd-tmpfiles-clean.service ha terminato la fase di avvio.
--
-- La fase di avvio done.
mag 25 09:47:26 skiava-pc sudo[8725]:   skiava : TTY=pts/0 ; PWD=/home/skiava ; USER=root ; COMMAND=/usr/bin/systemctl start systemd-modules-load.service
mag 25 09:47:26 skiava-pc sudo[8725]: pam_unix(sudo:session): session opened for user root by (uid=0)
mag 25 09:47:26 skiava-pc systemd[1]: Starting Load Kernel Modules...
-- Subject: L'unit systemd-modules-load.service inizia la fase di avvio
-- Defined-By: systemd
-- Support: http://lists.freedesktop.org/mailman/listinfo/systemd-devel
--
-- L'unit systemd-modules-load.service ha iniziato la fase di avvio.
mag 25 09:47:26 skiava-pc systemd-modules-load[8728]: Failed to find module 'vboxdrv'
mag 25 09:47:26 skiava-pc systemd-modules-load[8728]: Failed to find module 'vboxnetadp'
mag 25 09:47:26 skiava-pc systemd-modules-load[8728]: Failed to find module 'vboxnetflt'
mag 25 09:47:26 skiava-pc systemd-modules-load[8728]: Failed to find module 'vboxpci'
mag 25 09:47:26 skiava-pc systemd[1]: systemd-modules-load.service: Main process exited, code=exited, status=1/FAILURE
mag 25 09:47:26 skiava-pc systemd[1]: Failed to start Load Kernel Modules.
-- Subject: L'unit systemd-modules-load.service fallita
-- Defined-By: systemd
-- Support: http://lists.freedesktop.org/mailman/listinfo/systemd-devel
--
-- L'unit systemd-modules-load.service fallita.
--
-- Il risultato failed.
mag 25 09:47:26 skiava-pc systemd[1]: systemd-modules-load.service: Unit entered failed state.
mag 25 09:47:26 skiava-pc systemd[1]: systemd-modules-load.service: Failed with result 'exit-code'.
mag 25 09:47:26 skiava-pc sudo[8725]: pam_unix(sudo:session): session closed for user root
mag 25 09:47:34 skiava-pc gnome-terminal-[7908]: Allocating size to GtkScrollbar 0x1a04310 without calling gtk_widget_get_preferred_width/height(). How does the code know the size to allocate?
mag 25 09:48:12 skiava-pc polkitd[523]: Registered Authentication Agent for unix-process:8733:103131 (system bus name :1.112 [/usr/bin/pkttyagent --notify-fd 5 --fallback], object path /org/freedesktop/Pol
mag 25 09:48:18 skiava-pc polkitd[523]: Operator of unix-session:c2 successfully authenticated as unix-user:skiava to gain TEMPORARY authorization for action org.freedesktop.systemd1.manage-unit-files for
mag 25 09:48:28 skiava-pc polkit-agent-helper-1[8743]: pam_unix(polkit-1:auth): authentication failure; logname= uid=1000 euid=0 tty= ruser=skiava rhost=  user=skiava
mag 25 09:48:30 skiava-pc org.gnome.Shell.desktop[7665]: polkit-agent-helper-1: pam_authenticate failed: Authentication failure
mag 25 09:48:36 skiava-pc polkitd[523]: Operator of unix-session:c2 successfully authenticated as unix-user:skiava to gain TEMPORARY authorization for action org.freedesktop.systemd1.reload-daemon for syst
mag 25 09:48:36 skiava-pc systemd[1]: Reloading.
mag 25 09:48:36 skiava-pc polkitd[523]: Unregistered Authentication Agent for unix-process:8733:103131 (system bus name :1.112, object path /org/freedesktop/PolicyKit1/AuthenticationAgent, locale it_IT.UTF

[skiava@skiava-pc ~]$
ho provato ad attivare il modulo con i seguenti comandi:
Codice: [Seleziona]
[skiava@skiava-pc ~]$ sudo systemctl start systemd-modules-load.service
Job for systemd-modules-load.service failed because the control process exited with error code.
See "systemctl status systemd-modules-load.service" and "journalctl -xe" for details.
[skiava@skiava-pc ~]$ systemctl enable systemd-modules-load.service
The unit files have no installation config (WantedBy, RequiredBy, Also, Alias
settings in the [Install] section, and DefaultInstance for template units).
This means they are not meant to be enabled using systemctl.
Possible reasons for having this kind of units are:
1) A unit may be statically enabled by being symlinked from another unit's
   .wants/ or .requires/ directory.
2) A unit's purpose may be to act as a helper for some other unit which has
   a requirement dependency on it.
3) A unit may be started when needed via activation (socket, path, timer,
   D-Bus, udev, scripted systemctl call, ...).
4) In case of template units, the unit is meant to be enabled with some
   instance name specified.
[skiava@skiava-pc ~]$ journalctl _PID=8728
-- Logs begin at Tue 2017-05-09 18:26:58 CEST, end at Thu 2017-05-25 10:32:54 CEST. --
mag 25 09:47:26 skiava-pc systemd-modules-load[8728]: Failed to find module 'vboxdrv'
mag 25 09:47:26 skiava-pc systemd-modules-load[8728]: Failed to find module 'vboxnetadp'
mag 25 09:47:26 skiava-pc systemd-modules-load[8728]: Failed to find module 'vboxnetflt'
mag 25 09:47:26 skiava-pc systemd-modules-load[8728]: Failed to find module 'vboxpci'
[skiava@skiava-pc ~]$ pacman -Q | grep virtualbox
linux310-virtualbox-host-modules 5.1.22-1
virtualbox 5.1.22-2
[skiava@skiava-pc ~]$
come dovrei procedere?
grazie in anticipo.
« Ultima modifica: Maggio 25, 2017, 10:42:27 am da skiava7 »

Cubanpit

  • *****
  • 1347
    • GitHub
Re:virtualbox mi segnala errore "modulo kernel fallito"
« Risposta #1 il: Maggio 28, 2017, 11:47:17 am »
Come mai usi il kernel versione 3.10? il pi vecchio in circolazione su Manjaro!
Hai riavviato il sistema dopo aver installato il pacchetto contenente i moduli necessari a Virtualbox?
Se non funziona, puoi provare ad installare virtualbox-host-dkms invece di linux310-virtualbox-host-modules, magari funziona meglio.

Re:virtualbox mi segnala errore "modulo kernel fallito"
« Risposta #2 il: Maggio 29, 2017, 09:49:52 am »
Ciao, mi sa che ti stai confondendo..... cmq io sto usando l'ultima versione di manjaro DE gnome in seguito l'output di:
Codice: [Seleziona]
[skiava@skiava-pc ~]$ uname -r
4.9.28-1-MANJARO
[skiava@skiava-pc ~]$
ho provato ad installare il pacchetto, come da te richiesto, (virtualbox-host-dkms) ma il problema persiste....cosa mi suggerisci di fare?
riporto l'output di:
Codice: [Seleziona]
[skiava@skiava-pc ~]$ sudo pacman -S virtualbox-host-dkms
[sudo] password di skiava:
risoluzione delle dipendenze in corso...
ricerca dei pacchetti in conflitto in corso...

Pacchetti (1) virtualbox-host-dkms-5.1.22-2

Dimensione totale dei pacchetti da scaricare:    0,62 MiB
Dimensione totale dei pacchetti da installare:  10,92 MiB

:: Vuoi procedere con l'installazione? [S/n] s
:: Download dei pacchetti in corso...
 virtualbox-host-dkm...   634,4 KiB  7,46M/s 00:00 [######################] 100%
(1/1) verifica delle chiavi presenti nel porta...  [######################] 100%
(1/1) verifica dell'integrit dei pacchetti        [######################] 100%
(1/1) caricamento dei file dei pacchetti           [######################] 100%
(1/1) controllo dei conflitti in corso             [######################] 100%
(1/1) controllo dello spazio disponibile sul d...  [######################] 100%
:: Elaborazione delle modifiche al pacchetto...
(1/1) installazione in corso di virtualbox-hos...  [######################] 100%
Dipendenze opzionali di virtualbox-host-dkms
    linux-headers: build modules against Arch kernel
    linux-lts-headers: build modules against LTS kernel
    linux-zen-headers: build modules against ZEN kernel
:: Esecuzione degli hook di post-transazione...
(1/2) Install DKMS modules
==> No kernel 4.9.30-1-MANJARO headers. You must install them to use DKMS!
(2/2) Arming ConditionNeedsUpdate...
[skiava@skiava-pc ~]$ sudo pacman -R linux310-virtualbox-host-modules
controllo delle dipendenze in corso...

Pacchetti (1) linux310-virtualbox-host-modules-5.1.22-1

Dimensione totale dei pacchetti rimossi:  0,21 MiB

:: Vuoi rimuovere questi pacchetti? [S/n] s
:: Elaborazione delle modifiche al pacchetto...
(1/1) rimozione in corso di linux310-virtualbo...  [######################] 100%
:: Esecuzione degli hook di post-transazione...
(1/1) Arming ConditionNeedsUpdate...
[skiava@skiava-pc ~]$ systemctl -t service
  UNIT                           LOAD   ACTIVE SUB     DESCRIPTION             
  accounts-daemon.service        loaded active running Accounts Service         
  alsa-restore.service           loaded active exited  Save/Restore Sound Card S
  colord.service                 loaded active running Manage, Install and Gener
  cronie.service                 loaded active running Periodic Command Schedule
  dbus.service                   loaded active running D-Bus System Message Bus
  gdm.service                    loaded active running GNOME Display Manager   
  geoclue.service                loaded active running Location Lookup Service 
  kmod-static-nodes.service      loaded active exited  Create list of required s
  ldconfig.service               loaded active exited  Rebuild Dynamic Linker Ca
  lvm2-lvmetad.service           loaded active running LVM2 metadata daemon     
  lvm2-pvscan@8:2.service        loaded active exited  LVM2 PV scan on device 8:
  ModemManager.service           loaded active running Modem Manager           
  NetworkManager.service         loaded active running Network Manager         
  ntpd.service                   loaded active running Network Time Service     
  org.cups.cupsd.service         loaded active running CUPS Scheduler           
  pamac.service                  loaded active running Pamac                   
  polkit.service                 loaded active running Authorization Manager   
  rtkit-daemon.service           loaded active running RealtimeKit Scheduling Po
  systemd-journal-catalog-update.service loaded active exited  Rebuild Journal C
  systemd-journal-flush.service  loaded active exited  Flush Journal to Persiste
  systemd-journald.service       loaded active running Journal Service         
  systemd-logind.service         loaded active running Login Service           
● systemd-modules-load.service   loaded failed failed  Load Kernel Modules     
  systemd-random-seed.service    loaded active exited  Load/Save Random Seed   
  systemd-remount-fs.service     loaded active exited  Remount Root and Kernel F
  systemd-sysctl.service         loaded active exited  Apply Kernel Variables   
  systemd-sysusers.service       loaded active exited  Create System Users     
  systemd-tmpfiles-setup-dev.service loaded active exited  Create Static Device
  systemd-tmpfiles-setup.service loaded active exited  Create Volatile Files and
  systemd-udev-trigger.service   loaded active exited  udev Coldplug all Devices
  systemd-udevd.service          loaded active running udev Kernel Device Manage
  systemd-update-done.service    loaded active exited  Update is Completed     
  systemd-update-utmp.service    loaded active exited  Update UTMP about System
  systemd-user-sessions.service  loaded active exited  Permit User Sessions     
  tlp.service                    loaded active exited  TLP system startup/shutdo
  udisks2.service                loaded active running Disk Manager             
  upower.service                 loaded active running Daemon for power manageme
  user@1000.service              loaded active running User Manager for UID 1000
  user@120.service               loaded active running User Manager for UID 120
  wpa_supplicant.service         loaded active running WPA supplicant           

LOAD   = Reflects whether the unit definition was properly loaded.
ACTIVE = The high-level unit activation state, i.e. generalization of SUB.
SUB    = The low-level unit activation state, values depend on unit type.

40 loaded units listed. Pass --all to see loaded but inactive units, too.
To show all installed unit files use 'systemctl list-unit-files'.
lines 26-48/48 (END)
[skiava@skiava-pc ~]$
« Ultima modifica: Maggio 29, 2017, 09:52:29 am da skiava7 »

Cubanpit

  • *****
  • 1347
    • GitHub
Re:virtualbox mi segnala errore "modulo kernel fallito"
« Risposta #3 il: Maggio 29, 2017, 10:29:31 am »
Citazione
Codice: [Seleziona]
[skiava@skiava-pc ~]$ pacman -Q | grep virtualbox
linux310-virtualbox-host-modules 5.1.22-1
virtualbox 5.1.22-2
[...]
Ciao, mi sa che ti stai confondendo.....
Allora hai un modulo installato che non corrisponde a nessun kernel in uso, puoi rimuoverlo (se hai anche il kernel 3.10 installato rimuovilo pure che vecchio ormai).

Citazione
Codice: [Seleziona]
[...]
(1/2) Install DKMS modules
==> No kernel 4.9.30-1-MANJARO headers. You must install them to use DKMS!
[...]
Mi sono dimenticato di dirti che devi installare anche gli headers dei kernel che utilizzi, per esempio per il kernel 4.9
Codice: [Seleziona]
sudo pacman -S linux49-headers

Re:virtualbox mi segnala errore "modulo kernel fallito"
« Risposta #4 il: Maggio 29, 2017, 11:17:07 am »
Adesso mi trovo con:
Codice: [Seleziona]
[skiava@skiava-pc ~]$ pacman -Q | grep virtualbox
linux49-virtualbox-guest-modules 5.1.22-5
linux49-virtualbox-host-modules 5.1.22-5
virtualbox 5.1.22-2
virtualbox-host-dkms 5.1.22-2
[skiava@skiava-pc ~]$
ma il problema persiste ancora....cosa manca?
Codice: [Seleziona]
[skiava@skiava-pc ~]$ pacman -Q | grep linux
archlinux-keyring 20170320-1
lib32-util-linux 2.29.2-1
libutil-linux 2.29.2-2
linux-api-headers 4.10.1-1
linux-firmware 20170422.ade8332-1
linux310 3.10.105-1
linux49 4.9.30-1
linux49-headers 4.9.30-1
linux49-r8168 8.044.02-5
linux49-virtualbox-guest-modules 5.1.22-5
linux49-virtualbox-host-modules 5.1.22-5
util-linux 2.29.2-2
[skiava@skiava-pc ~]$
« Ultima modifica: Maggio 29, 2017, 11:18:51 am da skiava7 »

Cubanpit

  • *****
  • 1347
    • GitHub
Re:virtualbox mi segnala errore "modulo kernel fallito"
« Risposta #5 il: Maggio 29, 2017, 11:47:48 am »
linux49-virtualbox-guest-modules non serve, il modulo per il sistema ospitato (guest), installarlo sul sistema ospitante (host) penso che impedisca il corretto funzionamento di Virtualbox.
linux49-virtualbox-host-modules un'alternativa a virtualbox-host-dkms + linuxNN-headers, puoi scegliere tra i due metodi, io preferisco il secondo perch si occupa il sistema locale di ricompilare il modulo per ogni kernel, ma ci mette un pochino di pi ad aggiornare.
Una volta rimossi i pacchetti non necessari o dannosi citati sopra puoi (tanto per esser sicuro di avere tutto configurato nel modo corretto) reinstallare il kernel corrente e riavviare il sistema
Codice: [Seleziona]
sudo pacman -S linux49
EDIT:
Aggiungo, ti consiglio di rimuovere il kernel 3.10, piuttosto installa un kernel LTS pi recente come il 4.4
Codice: [Seleziona]
sudo mhwd-kernel -r linux310
sudo mhwd-kernel -i linux 44
« Ultima modifica: Maggio 29, 2017, 11:49:30 am da Cubanpit »

Re:virtualbox mi segnala errore "modulo kernel fallito"
« Risposta #6 il: Maggio 29, 2017, 01:41:33 pm »
Ho seguito la tua ultima procedura e finalmente il problema si risolto!
grazie