OMV 3.0.51 Virtualbox upgraded to 5.1.8 and will not work anymore

  • The version of the Extensions and Vbox does not match. I tried everything (uninstall, different versions, different kernel, recompiling) but had no success. Even a fresh installation from the 3.0.36 ISO has the same problem, if I install the virtualbox via web interface.
    It had worked before the 2. of November.
    I can not start the service. Message is

    Code
    Failed to execute XPath query '/config/services/virtualbox'.



    And

    Code
    vboxmanage -v

    gives me

    Code
    The character device /dev/vboxdrv does not exist.
    Please install the virtualbox-dkms package and the approbiate
    headers, most likely linux-headers-amd64.
    • Offizieller Beitrag

    I updated the virtualbox-ext-pack-installer package to 5.1.8 and added build-essential to the dependencies of the plugin. Works on my VM now. You will still get a message about needing phpvirtualbox 5.1 but that doesn't exist and 5.0 seems to work.

    omv 7.1.0-2 sandworm | 64 bit | 6.8 proxmox kernel

    plugins :: omvextrasorg 7.0 | kvm 7.0.13 | compose 7.2 | k8s 7.1.0-3 | cputemp 7.0.1 | mergerfs 7.0.5 | scripts 7.0.5


    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

    No offense but I prefer to stick with Ian's official releases. If his release stops working, I would consider it.

    omv 7.1.0-2 sandworm | 64 bit | 6.8 proxmox kernel

    plugins :: omvextrasorg 7.0 | kvm 7.0.13 | compose 7.2 | k8s 7.1.0-3 | cputemp 7.0.1 | mergerfs 7.0.5 | scripts 7.0.5


    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!

  • ryecoaaron thanks for the VBox update.


    Now I have OMV 3.51 with VBox 5.1.8 and phpVirtualVox 5.0.5.
    I also get the phpVirtualBox warning.


    Here I found a workaround:
    https://sourceforge.net/p/phpv…/general/thread/565b7f31/


    In/usr/share/phpvirtualbox/endpoints/api.php
    # $response['data']['responseData']['phpvboxver'] =@constant('PHPVBOX_VER');
    $response['data']['responseData']['phpvboxver']= "5.1-0";


    Optical workaround, ugly but works.

    Productive OMV 2.x on iomega iConnect (Marvel Kirkwood 1 Core ARM CPU @1GHz, 250MB RAM), Debian Wheezy, Kernel 3.17.1 (congenio)
    Test OMV 3.x on iomega iConnect (Marvel Kirkwood 1 Core ARM CPU @1GHz, 250MB RAM), Debian Jessie, Kernel 4.4.2 (congenio)
    Test2 OMV 3.x on Intel NUC i3 (Intel i3-5010, 4GB RAM, 120GB Intel SSD), OMV 3.0.51beta

    • Offizieller Beitrag

    I'm not worried about the warning unless it causes functional issues. The virtualbox plugin is not supposed to even be maintained anymore. I definitely don't want spending my time patching something that really isn't broken.

    omv 7.1.0-2 sandworm | 64 bit | 6.8 proxmox kernel

    plugins :: omvextrasorg 7.0 | kvm 7.0.13 | compose 7.2 | k8s 7.1.0-3 | cputemp 7.0.1 | mergerfs 7.0.5 | scripts 7.0.5


    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!

Jetzt mitmachen!

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