Kernel Update breaks VirtualBox Plugin

    This site uses cookies. By continuing to browse this site, you are agreeing to our Cookie Policy.

    • Kernel Update breaks VirtualBox Plugin

      Hello,

      after installing some (all pending) updates and rebooting, Virtual Box Plugin is broken. I get this error message when logging into omv gui.

      Could not connect to host ([url]http://127.0.0.1:18083/[/url])

      Source Code: Could not connect to host (http://127.0.0.1:18083/)

      1. Fehler #0:
      2. Exception: Could not connect to host (http://127.0.0.1:18083/) in /usr/share/phpvirtualbox/endpoints/lib/vboxconnector.php:220
      3. Stack trace:
      4. #0 /usr/share/openmediavault/engined/rpc/virtualbox.inc(136): vboxconnector->connect()
      5. #1 [internal function]: OMV\Engined\Rpc\VirtualBox->getMachines(Array, Array)
      6. #2 /usr/share/php/openmediavault/rpc/serviceabstract.inc(123): call_user_func_array(Array, Array)
      7. #3 /usr/share/php/openmediavault/rpc/rpc.inc(86): OMV\Rpc\ServiceAbstract->callMethod('getMachines', Array, Array)
      8. #4 /usr/sbin/omv-engined(536): OMV\Rpc\Rpc::call('VirtualBox', 'getMachines', Array, Array, 1)
      9. #5 {main}


      Starting PHPVirtualBox gives me:

      An error occurred communicating with your vboxwebsrv. No more requests will be sent by phpVirtualBox until the error is corrected and this page is refreshed. The details of this connection error should be displayed in a subsequent dialog box.

      followed by:

      Source Code: Could not connect to host (http://127.0.0.1:18083/)

      1. Exception Object
      2. (
      3. [message:protected] => Could not connect to host (http://127.0.0.1:18083/)
      4. [string:Exception:private] =>
      5. [code:protected] => 64
      6. [file:protected] => /usr/share/phpvirtualbox/endpoints/lib/vboxconnector.php
      7. [line:protected] => 220
      8. [trace:Exception:private] => Array
      9. (
      10. [0] => Array
      11. (
      12. [file] => /usr/share/phpvirtualbox/endpoints/lib/vboxconnector.php
      13. [line] => 3147
      14. [function] => connect
      15. [class] => vboxconnector
      16. [type] => ->
      17. [args] => Array
      18. (
      19. )
      20. )
      21. [1] => Array
      22. (
      23. [file] => /usr/share/phpvirtualbox/endpoints/lib/vboxconnector.php
      24. [line] => 951
      25. [function] => remote_vboxGetGuestOSTypes
      26. [class] => vboxconnector
      27. [type] => ->
      28. [args] => Array
      29. (
      30. [0] =>
      31. )
      32. )
      33. [2] => Array
      34. (
      35. [file] => /usr/share/phpvirtualbox/endpoints/api.php
      36. [line] => 316
      37. [function] => __call
      38. [class] => vboxconnector
      39. [type] => ->
      40. [args] => Array
      41. (
      42. [0] => vboxGetGuestOSTypes
      43. [1] => Array
      44. (
      45. [0] =>
      46. [1] => Array
      47. (
      48. [0] => Array
      49. (
      50. [data] => Array
      51. (
      52. [responseData] => Array
      53. (
      54. )
      55. )
      56. [errors] => Array
      57. (
      58. )
      59. [persist] => Array
      60. (
      61. )
      62. [messages] => Array
      63. (
      64. )
      65. )
      66. )
      67. )
      68. )
      69. )
      70. )
      71. [previous:Exception:private] =>
      72. )
      73. Location:http://127.0.0.1:18083/
      Display All


      A new kernel has been installed recently: Debian GNU/Linux, with Linux 4.16.0-0.bpo.2-amd64.

      Switching back to Debian GNU/Linux, with Linux 4.16.0-0.bpo.1-amd64 in OMV-Extras fixes the problem for now.

      Would you please tell me what to do to fix that (now and in future)? And is there a way to automate this fixing for future kernel updates? (at least for minor updates like this one)

      Thanks in advance.

      The post was edited 2 times, last by Mr Smile ().

    • Mr Smile wrote:

      Would you please tell me what to do to fix that (now and in future)? And is there a way to automate this fixing for future kernel updates? (at least for minor updates like this one)
      You probably don't have the kernel headers installed for the new kernel. Not sure why. The plugin depends on linux-image-amd64 which should automatically update when you update the kernel. My systems did.

      Mr Smile wrote:

      Would you please tell me what to do to fix that (now and in future)?
      I think this has been discussed many, many times. I have tried to make the plugins do the right thing by depending on the meta package for the kernel and headers. The virtualbox-dkms package is supposed to be triggered on kernel upgrades to compile a new module. We didn't create these packages . If they aren't working, I really don't know what to tell you. There is *very* little the plugin can do about it. All I can suggest is test on a different system before upgrading on your main system.

      Mr Smile wrote:

      (at least for minor updates like this one)
      When Debian creates a different package for a kernel (even though they are both 4.16), it isn't really a minor update. Minor updates will be the same package name.
      omv 4.1.8.2 arrakis | 64 bit | 4.15 proxmox kernel | omvextrasorg 4.1.8
      omv-extras.org plugins source code and issue tracker - github.com/OpenMediaVault-Plugin-Developers

      Please read this before posting a question.
      Please don't PM for support... Too many PMs!
    • Hmm. Didn't touch anything kernel related since installation of omv. I uninstalled VirtualBox Plugin, switched to Debian GNU/Linux, with Linux 4.16.0-0.bpo.2-amd64 again and after a reboot I reinstalled VirtualBox. And now the error is gone. Any idea why virtualbox-dkms was not triggered during kernel upgrade? This is really a very standard omv installation. ?(
    • Mr Smile wrote:

      And now the error is gone. Any idea why virtualbox-dkms was not triggered during kernel upgrade? This is really a very standard omv installation
      Unfortunately, I have no idea.
      omv 4.1.8.2 arrakis | 64 bit | 4.15 proxmox kernel | omvextrasorg 4.1.8
      omv-extras.org plugins source code and issue tracker - github.com/OpenMediaVault-Plugin-Developers

      Please read this before posting a question.
      Please don't PM for support... Too many PMs!
    • New

      Unfortunately this happened again. I don't know what (days before installed) update broke it this time but after a restart I had the same problem. I had no ssh access when it happened. So I decided to uninstall and install Virtualbox-Plugin again and this solved the issue. So it seems that virtualbox-dkms was not triggered again after kernel update.

      Could you please help me to identify and fix the reason for that? This problem is very annoying. Thanks. :)
    • New

      What kernel update did you install? Unfortunately, this is not a package we maintain. Uninstalling the plugin only worked because it uninstalled virtualbox and re-installed. dpkg-reconfigure virtualbox-dkms should work. I had added a button to the plugin to do this step but it didn't seem necessary in OMV 4.x. Maybe it needs to come back. Otherwise, I don't have a solution if dkms isn't doing its job.
      omv 4.1.8.2 arrakis | 64 bit | 4.15 proxmox kernel | omvextrasorg 4.1.8
      omv-extras.org plugins source code and issue tracker - github.com/OpenMediaVault-Plugin-Developers

      Please read this before posting a question.
      Please don't PM for support... Too many PMs!