virtualbox install issue headers?

  • I'm trying to install virtualbox on OMV 4-1.17-1 but keep getting this error


    WARNING: The character device /dev/vboxdrv does not exist.
    Please install the virtualbox-dkms package and the appropriate
    headers, most likely linux-headers-amd64


    uname -r
    4.14.0-0.bpo.3-amd64


    dpkg -l | grep -i headers
    ii libacl1-dev 2.2.52-3+b1 amd64 Access control list static libraries and headers
    ii libattr1-dev:amd64 1:2.4.47-2+b2 amd64 Extended attribute static libraries and headers
    ii linux-headers-4.19.0-0.bpo.1-amd64 4.19.12-1~bpo9+1 amd64 Header files for Linux 4.19.0-0.bpo.1-amd64
    ii linux-headers-4.19.0-0.bpo.1-common 4.19.12-1~bpo9+1 all Common header files for Linux 4.19.0-0.bpo.1
    ii linux-headers-amd64 4.19+101~bpo9+1 amd64 Header files for Linux amd64 configuration (meta-package)
    ii linux-libc-dev:amd64 4.9.110-3+deb9u4 amd64 Linux support headers for userspace development


    apt-get install linux-headers-$(uname -r)
    Reading package lists... Done
    Building dependency tree
    Reading state information... Done
    E: Unable to locate package linux-headers-4.14.0-0.bpo.3-amd64
    E: Couldn't find any package by glob 'linux-headers-4.14.0-0.bpo.3-amd64'
    E: Couldn't find any package by regex 'linux-headers-4.14.0-0.bpo.3-amd64'


    dpkg --list | grep linux-image
    ii linux-image-4.14.0-0.bpo.3-amd64 4.14.13-1~bpo9+1 amd64 Linux 4.14 for 64-bit PCs
    ii linux-image-amd64 4.14+89~bpo9+1 amd64 Linux for 64-bit PCs (meta-package)

    • Offizieller Beitrag

    The plugin is dependent on linux-headers-adm64 which means you will have to run the latest kernel (4.19 now). Is there a reason you are still on such an old kernel?

    omv 7.0.5-1 sandworm | 64 bit | 6.8 proxmox kernel

    plugins :: omvextrasorg 7.0 | kvm 7.0.13 | compose 7.1.4 | k8s 7.1.0-3 | cputemp 7.0.1 | mergerfs 7.0.4


    omv-extras.org plugins source code and issue tracker - github - changelogs


    Please try ctrl-shift-R and read this before posting a question.

    Please put your OMV system details in your signature.
    Please don't PM for support... Too many PMs!

    • Offizieller Beitrag

    Is it just a case of select this and click upgrade?

    Yep. I recommend installing all of the updates in the Updates tab.

    omv 7.0.5-1 sandworm | 64 bit | 6.8 proxmox kernel

    plugins :: omvextrasorg 7.0 | kvm 7.0.13 | compose 7.1.4 | k8s 7.1.0-3 | cputemp 7.0.1 | mergerfs 7.0.4


    omv-extras.org plugins source code and issue tracker - github - changelogs


    Please try ctrl-shift-R and read this before posting a question.

    Please put your OMV system details in your signature.
    Please don't PM for support... Too many PMs!

  • done that, now getting


    Linux machine4.19.0-0.bpo.1-amd64 #1 SMP Debian 4.19.12-1~bpo9+1 (2018-12-30) x86_64 GNU/Linux


    apt-get install linux-headers-$(uname -r)
    Reading package lists... Done
    Building dependency tree
    Reading state information... Done
    linux-headers-4.19.0-0.bpo.1-amd64 is already the newest version (4.19.12-1~bpo9+1).
    0 upgraded, 0 newly installed, 0 to remove and 0 not upgraded.


    apt-get install virtualbox-dkms
    Reading package lists... Done
    Building dependency tree
    Reading state information... Done
    virtualbox-dkms is already the newest version (5.2.22-dfsg-1~bpo9+1).
    0 upgraded, 0 newly installed, 0 to remove and 0 not upgraded.



    Setting up virtualbox (5.2.22-dfsg-1~bpo9+1) ...
    vboxweb.service is a disabled or a static unit, not starting it.
    Job for virtualbox.service failed because the control process exited with error code.
    See "systemctl status virtualbox.service" and "journalctl -xe" for details.
    invoke-rc.d: initscript virtualbox, action "restart" failed.
    ● virtualbox.service - LSB: VirtualBox Linux kernel module
    Loaded: loaded (/etc/init.d/virtualbox; generated; vendor preset: enabled)
    Active: failed (Result: exit-code) since Sun 2019-01-20 16:19:39 GMT; 3ms ago
    Docs: man:systemd-sysv-generator(8)
    Process: 8556 ExecStart=/etc/init.d/virtualbox start (code=exited, status=1/FAILURE)


    Jan 20 16:19:39 systemd[1]: Starting LSB: VirtualBox Linux kernel module...
    Jan 20 16:19:39 virtualbox[8556]: Loading VirtualBox kernel modules...…led!
    Jan 20 16:19:39 virtualbox[8556]: failed!
    Jan 20 16:19:39 systemd[1]: virtualbox.service: Control process exited…us=1
    Jan 20 16:19:39 systemd[1]: Failed to start LSB: VirtualBox Linux kern…ule.
    Jan 20 16:19:39 systemd[1]: virtualbox.service: Unit entered failed state.
    Jan 20 16:19:39 systemd[1]: virtualbox.service: Failed with result 'ex…de'.
    Hint: Some lines were ellipsized, use -l to show in full.
    Setting up phpvirtualbox (5.2-1) ...
    Setting up virtualbox-ext-pack-installer (5.2.18) ...
    --2019-01-20 16:19:39-- http://download.virtualbox.org…_Pack-5.2.18.vbox-extpack
    Resolving download.virtualbox.org (download.virtualbox.org)... 92.122.164.143
    Connecting to download.virtualbox.org (download.virtualbox.org)|92.122.164.143|:80... connected.
    HTTP request sent, awaiting response... 200 OK
    Length: 19592275 (19M) [text/plain]
    Saving to: ‘/tmp/Oracle_VM_VirtualBox_Extension_Pack-5.2.18.k9demQ5rYD.vbox-extpack’


    to the VBoxManage command line.


    WARNING: The character device /dev/vboxdrv does not exist.
    Please install the virtualbox-dkms package and the appropriate
    headers, most likely linux-headers-amd64


    0%...
    >>> *************** Error ***************
    Bad Gateway
    <<< *************************************
    10%...20%...30%...40%...50%...60%...70%...80%...90%...100%
    Successfully installed "Oracle VM VirtualBox Extension Pack".
    Setting up openmediavault-virtualbox (4.1.1) ...
    Updating configuration database ...
    Processing triggers for libc-bin (2.24-11+deb9u3) ...
    Processing triggers for systemd (232-25+deb9u8) ...
    Processing triggers for php7.0-fpm (7.0.33-0+deb9u1) ...
    Processing triggers for openmediavault (4.1.17-1) ...
    Updating locale files ...
    Updating file permissions ...
    Purging internal cache ...
    Restarting engine daemon ...
    Exception ignored in: <function WeakValueDictionary.__init__.<locals>.remove at 0x7f4beb9117b8>
    Traceback (most recent call last):
    File "/usr/lib/python3.5/weakref.py", line 117, in remove
    TypeError: 'NoneType' object is not callable
    Exception ignored in: <function WeakValueDictionary.__init__.<locals>.remove at 0x7f4beb9117b8>
    Traceback (most recent call last):
    File "/usr/lib/python3.5/weakref.py", line 117, in remove
    TypeError: 'NoneType' object is not callable
    Done ...

Jetzt mitmachen!

Sie haben noch kein Benutzerkonto auf unserer Seite? Registrieren Sie sich kostenlos und nehmen Sie an unserer Community teil!