Discussion:
Fw: Installing VirtualBox on Debian Jessie - Problem with Linux kernel Name
Add Reply
gilesaj
2017-02-04 21:00:19 UTC
Reply
Permalink
Raw Message
Hello
 During installation of VirtualBox I got this error.  It seems to be a problem with the way the OVH dedicated server displays the Linux Kernel name as 3.14.32-xxxx-grs-ipv6-64.


-----------------------------------------------------
Loading new virtualbox-4.3.36 DKMS files...First Installation: checking all kernels...dpkg: warning: version '*-*' has bad syntax: version number does not start with                                                                                                                                                      digitIt is likely that 3.14.32-xxxx-grs-ipv6-64 belongs to a chroot's hostBuilding initial module for 3.16.0-4-amd64Done.
vboxdrv:Running module version sanity check. - Original module   - No original module exists within this kernel - Installation   - Installing to /lib/modules/3.16.0-4-amd64/updates/dkms/
vboxnetadp.ko:Running module version sanity check. - Original module   - No original module exists within this kernel - Installation   - Installing to /lib/modules/3.16.0-4-amd64/updates/dkms/
vboxnetflt.ko:Running module version sanity check. - Original module   - No original module exists within this kernel - Installation   - Installing to /lib/modules/3.16.0-4-amd64/updates/dkms/
vboxpci.ko:Running module version sanity check. - Original module   - No original module exists within this kernel - Installation   - Installing to /lib/modules/3.16.0-4-amd64/updates/dkms/
depmod....
DKMS: install completed.Job for virtualbox.service failed. See 'systemctl status virtualbox.service' and                                                                                                                                                      'journalctl -xn' for details.invoke-rc.d: initscript virtualbox, action "restart" failed.Setting up virtualbox (4.3.36-dfsg-1+deb8u1) ...insserv: warning: script 'K01boinc' missing LSB tags and overridesinsserv: warning: script 'boinc' missing LSB tags and overridesJob for virtualbox.service failed. See 'systemctl status virtualbox.service' and                                                                                                                                                      'journalctl -xn' for details.invoke-rc.d: initscript virtualbox, action "restart" failed.Setting up virtualbox-qt (4.3.36-dfsg-1+deb8u1) ...Processing triggers for menu (2.1.47) ...
---------------------------------------------------------------------
I ran both the suggested commands and they are as follows.

***@ns527415:~# systemctl status virtualbox.service? virtualbox.service - LSB: VirtualBox Linux kernel module   Loaded: loaded (/etc/init.d/virtualbox)   Active: failed (Result: exit-code) since Sat 2017-02-04 15:31:03 EST; 7min ago  Process: 3477 ExecStart=/etc/init.d/virtualbox start (code=exited, status=1/FAILURE)
Feb 04 15:31:03 ns527415.ip-192-99-6.net virtualbox[3477]: Starting VirtualBox kernel moduleslibkmod: ERROR ../libkmod/libkmod-module.c:1638 kmod_module_new_from_loaded: could not open /proc/modules: No such file or directoryFeb 04 15:31:03 ns527415.ip-192-99-6.net virtualbox[3477]: Error: could not get list of modules: No such file or directoryFeb 04 15:31:03 ns527415.ip-192-99-6.net virtualbox[3477]: No suitable module for running kernel found ... failed!Feb 04 15:31:03 ns527415.ip-192-99-6.net virtualbox[3477]: failed!Feb 04 15:31:03 ns527415.ip-192-99-6.net systemd[1]: virtualbox.service: control process exited, code=exited status=1Feb 04 15:31:03 ns527415.ip-192-99-6.net systemd[1]: Failed to start LSB: VirtualBox Linux kernel module.Feb 04 15:31:03 ns527415.ip-192-99-6.net systemd[1]: Unit virtualbox.service entered failed state.

--------------------------------------------------------------------------------


***@ns527415:~#journalctl -xn-- The start-up result is done.Feb 04 15:31:03 ns527415.ip-192-99-6.net systemd[1]: Starting LSB: VirtualBox Linux kernel module...-- Subject: Unit virtualbox.service has begun with start-up-- Defined-By: systemd-- Support: http://lists.freedesktop.org/mailman/listinfo/systemd-devel---- Unit virtualbox.service has begun starting up.Feb 04 15:31:03 ns527415.ip-192-99-6.net virtualbox[3477]: Starting VirtualBox kernel moduleslibkmod: ERROR ../libkmod/libkmod-module.c:1638 kmod_module_new_from_loaded: could not open /proc/modules: No such file or directoryFeb 04 15:31:03 ns527415.ip-192-99-6.net virtualbox[3477]: Error: could not get list of modules: No such file or directoryFeb 04 15:31:03 ns527415.ip-192-99-6.net virtualbox[3477]: No suitable module for running kernel found ... failed!Feb 04 15:31:03 ns527415.ip-192-99-6.net virtualbox[3477]: failed!Feb 04 15:31:03 ns527415.ip-192-99-6.net systemd[1]: virtualbox.service: control process exited, code=exited status=1Feb 04 15:31:03 ns527415.ip-192-99-6.net systemd[1]: Failed to start LSB: VirtualBox Linux kernel module.-- Subject: Unit virtualbox.service has failed-- Defined-By: systemd-- Support: http://lists.freedesktop.org/mailman/listinfo/systemd-devel---- Unit virtualbox.service has failed.---- The result is failed.Feb 04 15:31:03 ns527415.ip-192-99-6.net systemd[1]: Unit virtualbox.service entered failed state.Feb 04 15:31:18 ns527415.ip-192-99-6.net sshd[3507]: Connection closed by 92.63.58.60 [preauth]lines 8-30/30 (END)--------------------------------------------------------------------------

So is there a way to get around this problem ?
Cheers,
Giles
Reindl Harald
2017-02-04 21:17:38 UTC
Reply
Permalink
Raw Message
During installation of VirtualBox I got this error. It seems to be a
problem with the way the OVH dedicated server displays the Linux Kernel
name as 3.14.32-xxxx-grs-ipv6-64.
how is that a systemd problem at all?
contact OVH and/or Oracle....

http://www.phoronix.com/scan.php?page=news_item&px=OTk5Mw
-----------------------------------------------------
Loading new virtualbox-4.3.36 DKMS files...
First Installation: checking all kernels...
dpkg: warning: version '*-*' has bad syntax: version number does not
start with
digit
It is likely that 3.14.32-xxxx-grs-ipv6-64 belongs to a chroot's host
Building initial module for 3.16.0-4-amd64
Done.
Running module version sanity check.
- Original module
- No original module exists within this kernel
- Installation
- Installing to /lib/modules/3.16.0-4-amd64/updates/dkms/
Running module version sanity check.
- Original module
- No original module exists within this kernel
- Installation
- Installing to /lib/modules/3.16.0-4-amd64/updates/dkms/
Running module version sanity check.
- Original module
- No original module exists within this kernel
- Installation
- Installing to /lib/modules/3.16.0-4-amd64/updates/dkms/
Running module version sanity check.
- Original module
- No original module exists within this kernel
- Installation
- Installing to /lib/modules/3.16.0-4-amd64/updates/dkms/
gilesaj
2017-02-04 22:34:39 UTC
Reply
Permalink
Raw Message
The only reason I posted here is because that is what is in the text of the error.

***@ns527415:~#journalctl -xn-- The start-up result is done.Feb 04 15:31:03 ns527415.ip-192-99-6.net systemd[1]: Starting LSB: VirtualBox Linux kernel module...-- Subject: Unit virtualbox.service has begun with start-up-- Defined-By: systemd-- Support: systemd-devel Info Page

|
|
|
| | |

|

|
|
| |
systemd-devel Info Page
| |

|

|


 Close this or whatever you do if this is not the right place.Cheers,

From: Reindl Harald <***@thelounge.net>
To: systemd-***@lists.freedesktop.org
Sent: Saturday, February 4, 2017 2:17 PM
Subject: Re: [systemd-devel] Fw: Installing VirtualBox on Debian Jessie - Problem with Linux kernel Name
During installation of VirtualBox I got this error.  It seems to be a
problem with the way the OVH dedicated server displays the Linux Kernel
name as 3.14.32-xxxx-grs-ipv6-64.
how is that a systemd problem at all?
contact OVH and/or Oracle....

http://www.phoronix.com/scan.php?page=news_item&px=OTk5Mw
-----------------------------------------------------
Loading new virtualbox-4.3.36 DKMS files...
First Installation: checking all kernels...
dpkg: warning: version '*-*' has bad syntax: version number does not
start with
                digit
It is likely that 3.14.32-xxxx-grs-ipv6-64 belongs to a chroot's host
Building initial module for 3.16.0-4-amd64
Done.
Running module version sanity check.
  - Original module
    - No original module exists within this kernel
  - Installation
    - Installing to /lib/modules/3.16.0-4-amd64/updates/dkms/
Running module version sanity check.
  - Original module
    - No original module exists within this kernel
  - Installation
    - Installing to /lib/modules/3.16.0-4-amd64/updates/dkms/
Running module version sanity check.
  - Original module
    - No original module exists within this kernel
  - Installation
    - Installing to /lib/modules/3.16.0-4-amd64/updates/dkms/
Running module version sanity check.
  - Original module
    - No original module exists within this kernel
  - Installation
    - Installing to /lib/modules/3.16.0-4-amd64/updates/dkms/
Tomasz Torcz
2017-02-04 22:48:19 UTC
Reply
Permalink
Raw Message
Post by gilesaj
The only reason I posted here is because that is what is in the text of the error.
systemd-devel Info Page
This misleading message was removed from systemd in July last year.
Maybe it is worth opening bugs with popular distribution and asking them
to backport 4b930ded8391c7552820f8f162b4e6ceebf50ca4 into their supported
branches? How do you think?
--
Tomasz Torcz "Never underestimate the bandwidth of a station
xmpp: ***@chrome.pl wagon filled with backup tapes." -- Jim Gray
Reindl Harald
2017-02-05 00:33:24 UTC
Reply
Permalink
Raw Message
Post by Tomasz Torcz
Post by gilesaj
The only reason I posted here is because that is what is in the text of the error.
systemd-devel Info Page
This misleading message was removed from systemd in July last year.
Maybe it is worth opening bugs with popular distribution and asking them
to backport 4b930ded8391c7552820f8f162b4e6ceebf50ca4 into their supported
branches? How do you think?
it was long overdue looking at the amount of threads in the past years
where people instead trying to understand error messages asking the
messenger

Loading...