Virtualbox server cannot start after UPDATE

    • OMV 4.x
    • Resolved

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

    • Ok after some invstigate here we have :

      - As alwyas I set virtualbox create in a drive share folder named "Virtualbox". So if a VM is created it must appears here.
      IMG 001.png

      - Instead the VM entire folder appear in root/Virtualbox VMs
      IMG 002.png

      This change in plugins config make all my VM crush after its update (manually done in update manager) very probably !

      To compare, this is a "standard" configuration that VM are in correct folder : srv/dev-disk-by+label-.../Virtualbox
      IMG 003.png

      My config was like this [IMG 003.png] before all crush after the "famous" update !

      Question : Can someone please clarify this situation ? Should I continue to use omv3.x and Virtbox ? Will this occur again and again in future ?
      This is important we know that because it DANGEROUS !!
      Images
      • 001.png

        8.52 kB, 603×267, viewed 82 times
      • 002.png

        39.7 kB, 545×435, viewed 72 times
      • 003.png

        18.81 kB, 373×274, viewed 83 times
      Omv 4.x
      Fanless Celeron J1800 RAM 2Gb | boot mSATA 32Gb | Orico 5 Bays (Black) 6Tb

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

    • caseyj wrote:

      Should I continue to use omv3.x and Virtbox ?
      If that is what works for you, yes. I can't replicate most of these problems people are having. So, it is very hard to fix or recommend a fix.
      omv 4.1.15 arrakis | 64 bit | 4.15 proxmox kernel | omvextrasorg 4.1.13
      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!
    • we see clearly that before the VM are in
      srv/dev-disk-by+label-.../Virtualbox
      Now they are in
      root/Virtualbox VMs
      So that normal that it all crash after update. The system cannot find the VM folders...

      Question : could u update the plugin and set the VM folder like before... srv/dev-disk-by+label-.../ (NOT root/Virtualbox VMs ) ??

      Thx.
      Omv 4.x
      Fanless Celeron J1800 RAM 2Gb | boot mSATA 32Gb | Orico 5 Bays (Black) 6Tb

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

    • caseyj wrote:

      Now they are in
      I have read through this from the start and for someone who has had their own problems with VB and got them sorted VB is not referenced via /root/Virtualbox VM's I have that on my own system.

      Start by moving the Windows 7.vdi (I moved/copied mine to my W10 laptop using WinSCP) then remove the plugin and do apt-clean form the omv-extras menu.

      Then have a look at my own solution here what you also need to do is to deleted any folders related to Windows 7 in your Virtualbox share. When that's done copy the Windows 7.vdi back to your Virtualbox folder. Install the plugin and start the setup of Windows 7 at the point of asking for a vdi select use existing and point the .vdi you have upload, this should now work.

      My own remaining problem was to get RDP working as VB defaults to VNC but the info is on here.
      Raid is not a backup! Would you go skydiving without a parachute?
    • caseyj wrote:

      now if we can more just a plugin function just like before.
      The plugin hasn't changed.

      caseyj wrote:

      could u update the plugin and set the VM folder like before... srv/dev-disk-by+label-.../ (NOT root/Virtualbox VMs ) ??
      The plugin isn't doing this. Something is wrong with your system. As you can see here, the code that sets the VM folder hasn't changed in over a year.
      omv 4.1.15 arrakis | 64 bit | 4.15 proxmox kernel | omvextrasorg 4.1.13
      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!
    • Install a clean OMV3 to a new machine new HDD. After install extras and update (CLI apt-get update then apt-get upgrade) I would install Virtualbox :


      Reading package lists...

      Building dependency tree...
      >>> *************** Error ***************
      Failed to execute command 'export PATH=/bin:/sbin:/usr/bin:/usr/sbin:/usr/local/bin:/usr/local/sbin; export LANG=C; export DEBIAN_FRONTEND=noninteractive; apt-get --yes --force-yes --fix-missing --allow-unauthenticated --reinstall install openmediavault-virtualbox 2>&1' with exit code '100': Reading package lists...

      Building dependency tree...

      Reading state information...

      Some packages could not be installed. This may mean that you have
      requested an impossible situation or if you are using the unstable
      distribution that some required packages have not yet been created
      or been moved out of Incoming.
      The following information may help to resolve the situation:

      The following packages have unmet dependencies:
      openmediavault-virtualbox : Depends: linux-headers-686-pae but it is not installable or
      linux-headers-amd64 but it is not going to be installed
      E
      :
      Unable to correct problems, you have held broken packages.
      || || ||
      Omv 4.x
      Fanless Celeron J1800 RAM 2Gb | boot mSATA 32Gb | Orico 5 Bays (Black) 6Tb

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

    • I install clean (not upgrade !) OMV4 then Virtualbox (clean). All clean with HDD totally blank. So here we are : try for 1st VM and BAM! VM cannot start .... !!!

      Exception Object

      (
      [message:protected] => The virtual machine 'Windows Saven' has terminated unexpectedly during startup with exit code 1 (0x1)
      [string:Exception:private] =>
      [code:protected] => 0
      [file:protected] => /usr/share/phpvirtualbox/endpoints/lib/vboxconnector.php
      [line:protected] => 2429
      [trace:Exception:private] => Array
      (
      [0] => Array
      (
      [file] => /usr/share/phpvirtualbox/endpoints/lib/vboxconnector.php
      [line] => 951
      [function] => remote_progressGet
      [class] => vboxconnector
      [type] => ->
      [args] => Array
      (
      [0] => Array
      (
      [progress] => cd7454fa76fca0f9-0000000000000005
      )

      )

      )

      [1] => Array
      (
      [file] => /usr/share/phpvirtualbox/endpoints/api.php
      [line] => 316
      [function] => __call
      [class] => vboxconnector
      [type] => ->
      [args] => Array
      (
      [0] => progressGet
      [1] => Array
      (
      [0] => Array
      (
      [progress] => cd7454fa76fca0f9-0000000000000005
      )

      [1] => Array
      (
      [0] => Array
      (
      [data] => Array
      (
      [responseData] => Array
      (
      [progress] => cd7454fa76fca0f9-0000000000000005
      [info] => Array
      (
      [completed] => 1
      [canceled] =>
      [description] => Starting VM
      [operationDescription] => Creating process for virtual machine "Windows Saven" (headless)
      [timeRemaining] => Array
      (
      )

      [timeElapsed] => Array
      (
      [days] => 17686
      [hours] => 11
      [minutes] => 7
      [seconds] => 51
      )

      [percent] => 0
      )

      )

      [success] => 1
      [key] => 53474945cfd7ac0bf8114767c209c2a6
      )

      [errors] => Array
      (
      )

      [persist] => Array
      (
      )

      [messages] => Array
      (
      )

      )

      )

      )

      )

      )

      )

      [previous:Exception:private] =>
      )
      Problem is endless these time with OMV.. Its just me or...... ??

      || || || || ||
      Images
      • Region.png

        8.39 kB, 469×226, viewed 70 times
      Omv 4.x
      Fanless Celeron J1800 RAM 2Gb | boot mSATA 32Gb | Orico 5 Bays (Black) 6Tb