Virtuelle Maschinen können nicht gestartet werden (OMV 4.1.22 + OMV-Extras + Virtualbox (4.1.1))

    • Virtuelle Maschinen können nicht gestartet werden (OMV 4.1.22 + OMV-Extras + Virtualbox (4.1.1))

      Hallo zusammen,

      ich habe einen HP Microserver neu mit OMV aufgesetzt. Das aktuell verfügbare Image 4.1.22 lässt sich relativ problemlos installieren. Auch der Upload und die Installation von OMV-Extras bereitete keine Schwierigkeiten.
      Die Installation von Virtualbox-Plugin ist da schon etwas anderes.

      Es lassen sich keine virtuellen starten.
      Google hilft. Das Problem kündigt sich schon im Log der Plugin-Installation an:

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

      You will not be able to start VMs until this problem is fixed.

      Mich würde zunächst interessieren, ob dieses Verhalten bei einer neuen Installation von OMV im Zusammenhang mit einer Plugin-Installation aus einem OMV-Extras heraus zu erwarten ist.

      Hat jemand eine hinreichend einfache Empfehlung für mich, wie zu verfahren ist?
      Wenn ich das richtig sehe, verwendet OMV 4.1.22 die Kernelversion 4.19.0-0.bpo.4-amd64.
      Hiermit scheint Virtualbox nicht klar zu kommen.

      Für Tipps wäre ich sehr dankbar.
    • It is failing to compile the kernel module. There are quite a few threads about this on the forum.

      sudo dpkg-reconfigure virtualbox-dkms
      sudo modprobe vboxdrv
      omv 5.0.14 usul | 64 bit | 5.0 proxmox kernel | omvextrasorg 5.1.5
      omv-extras.org plugins source code and issue tracker - github

      Please read this before posting a question and this and this for docker questions.
      Please don't PM for support... Too many PMs!
    • Thank you ryecoaaron,


      sudo dpkg-reconfigure virtualbox-dkms
      results in

      Module build for kernel 4.19.0-0.bpo.4-amd64 was skipped since the kernel headers for this kernel does not seem to be installed.

      sudo modprobe vboxdrv
      results in

      modprobe: FATAL: Module vboxdrv not found in directory /lib/modules/4.19.0-0bpo.4-amd64

      Any other suggestions are highly appreciated!


      Since I failed to identify recent threads on the subject, please feel free to suggest threads that are of relevance for this kind of problem.

      regards

      The post was edited 1 time, last by tavik: welcoming pointers to existing solutions ().

    • Your kernel needs to be updated. bpo.6 has been out a long time. Have you installed all the updates from the Updates tab?
      omv 5.0.14 usul | 64 bit | 5.0 proxmox kernel | omvextrasorg 5.1.5
      omv-extras.org plugins source code and issue tracker - github

      Please read this before posting a question and this and this for docker questions.
      Please don't PM for support... Too many PMs!
    • So I checked for more recent kernel versions via

      sudo apt-get install aptitude
      sudo aptitude update
      aptitude search linux-image

      sudo aptitude update ran into errors concerning the File "/usr/lib"python3.5/weakref.py"
      I checked the forum, read some suggestions concerning solutions but I remain puzzled that a fixed bug comes up in fresh installation of OMV. The ISO was released this month!

      The most recent image I was offered with out the -dbg extension was 4.19.0-0.bpo.5-amd64

      When I try to install this image, I get
      Error! Your kernel headers for kernel 4.19.0-0.bpo.5-amd64 cannot be found.

      I did that.

      After I updated the headers, the kernel update once more provoked the exceptions concerning weakref.py.

      I applied the fix mentioned here:
      Python 3.5 issue during apt-

      Afterwards
      sudo aptitude install linux-image-4.19.0-0.bpo.5-amd64
      worked

      I reinstalled Virtualbox via GUI.
      Warning concerning character device /dev/vboxdrv remains.

      Suggestions?

      The post was edited 1 time, last by tavik ().

    • tavik wrote:

      So I checked for more recent kernel versions via
      You installed aptitude to do the same thing apt does?

      tavik wrote:

      sudo aptitude update ran into errors concerning the File "/usr/lib"python3.5/weakref.py"
      This has been mentioned many, many times that it is just a warning and nothing OMV can fixed.

      tavik wrote:

      The most recent image I was offered with out the -dbg extension was 4.19.0-0.bpo.5-amd64
      Your system is either not updating properly and/or you disabled backports. You can enable backports in omv-extras and then click the apt clean button. You have to have the bpo.6 kernel. 4 and 5 are too old. Until you get the newer kernel installed, don't proceed to the next steps.
      omv 5.0.14 usul | 64 bit | 5.0 proxmox kernel | omvextrasorg 5.1.5
      omv-extras.org plugins source code and issue tracker - github

      Please read this before posting a question and this and this for docker questions.
      Please don't PM for support... Too many PMs!
    • As you can probably guess, I am not a seasoned linux user.
      When given suggestions how to fix a certain problem, I tend to stick to the steps laid out. Since the solution relied on aptitude, I did not second guess it.

      Completely reinstalled OMV this morning.

      Backports are enabled.

      upgrade lead to

      The following packages have been kept back:
      linux-image-amd64
    • of course. here you go

      OMV-Extras --> upgrade

      Reading package lists...
      Building dependency tree...
      Reading state Information...
      Calculating upgrade...
      The following packages have been kept back:
      linux-image-amd64
      0 upgraded, 0 newly installed, 0 to remove and 1 not upgraded.
      Fertig...


      OMV-Extras --> dist-upgrade

      Reading package lists...
      Building dependency tree...
      Reading state Information...
      Calculating upgrade...
      0 upgraded, 0 newly installed, 0 to remove and 0 not upgraded.
      Fertig...

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

    • How are you installing? Are you using the OMV iso?

      sudo apt-mark unhold linux-image-amd64 should fix the problem but I don't know why it is held in the first place. Maybe you need to try different repos too?
      omv 5.0.14 usul | 64 bit | 5.0 proxmox kernel | omvextrasorg 5.1.5
      omv-extras.org plugins source code and issue tracker - github

      Please read this before posting a question and this and this for docker questions.
      Please don't PM for support... Too many PMs!
    • You need to change your repos in /etc/apt/sources.list. Something is wrong with the repo you are using. There is a post or two about how to do this somewhere on the forum.
      omv 5.0.14 usul | 64 bit | 5.0 proxmox kernel | omvextrasorg 5.1.5
      omv-extras.org plugins source code and issue tracker - github

      Please read this before posting a question and this and this for docker questions.
      Please don't PM for support... Too many PMs!
    • tavik wrote:

      I guess you are aware of this
      post
      I posted on it. Debian removed the .bpo6 package from the repo but didn't update the meta package linux-image-amd64.
      omv 5.0.14 usul | 64 bit | 5.0 proxmox kernel | omvextrasorg 5.1.5
      omv-extras.org plugins source code and issue tracker - github

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

      The post was edited 1 time, last by ryecoaaron ().