VirtualBox Plugin error 0x80070005 after changing HDD

    • OMV 2.x
    • VirtualBox Plugin error 0x80070005 after changing HDD

      Hi,

      hopefully this is the right category for this topic.

      I had to replace one of my drives with a bigger one. I configured my Virtual Boxes and lots of FTP and SMB shares on this drive.
      After migrating all files with

      Source Code

      1. ​cp -a
      to the new HDD and adjusting the system shares afterwards, SMB and FTP are working fine.

      Just the VirtualBox Plugin ran into an issue:

      Source Code

      1. VirtualBox error: rc=0x80070005 The object functionality is limited (0x80070005)
      2. Fehler #0:
      3. SoapFault exception: [SOAP-ENV:Client] VirtualBox error: rc=0x80070005 The object functionality is limited (0x80070005) in /usr/share/phpvirtualbox/lib/vboxServiceWrappers.php:2614
      4. Stack trace:
      5. #0 /usr/share/phpvirtualbox/lib/vboxServiceWrappers.php(2614): SoapClient->__soapCall('IMachine_getNam...', Array)
      6. #1 /usr/share/phpvirtualbox/lib/vboxServiceWrappers.php(54): IMachine->getName()
      7. #2 /usr/share/openmediavault/engined/rpc/virtualbox.inc(181): VBox_ManagedObject->__get('name')
      8. #3 [internal function]: OMVRpcServiceVirtualBox->getMachines(Array, Array)
      9. #4 /usr/share/php/openmediavault/rpcservice.inc(125): call_user_func_array(Array, Array)
      10. #5 /usr/share/php/openmediavault/rpc.inc(79): OMVRpcServiceAbstract->callMethod('getMachines', Array, Array)
      11. #6 /usr/sbin/omv-engined(500): OMVRpc::exec('VirtualBox', 'getMachines', Array, Array, 1)
      12. #7 {main}​
      Display All


      So, like I read in some other topics here, I uninstalled the plugin, removed the share, rebooted, reinstalled the plugin, recreated the share and copied the VBox data back.
      Afterwards I adjusted the ACL for the files (because the error was still existent):

      Source Code

      1. ​root@omv:/media/sonstiges/virtualbox# ls -la
      2. insgesamt 2076
      3. drwxrwsr-x+ 3 vbox vboxusers 4096 Mär 1 10:06 .
      4. drwxr-sr-x 17 root users 4096 Mär 1 10:04 ..
      5. drwxrwsr-x+ 4 vbox vboxusers 4096 Mär 1 10:06 MySQL
      6. -rwxrwxr-x 1 vbox vboxusers 7791 Feb 18 22:02 mysql.vbox
      7. -rwxrwxr-x 1 vbox vboxusers 7791 Feb 18 22:02 mysql.vbox-prev
      8. -rwxrwxr-x 1 vbox vboxusers 2097152 Feb 18 22:02 mysql.vdi


      But the error still keeps showing up. Also if I remove all VBox data so no VBox is existent.

      Has anyone an idea about this?

      Thanks in advance.
    • The error you are getting is an access denied error. You shouldn't have ACLs on the files. Run setfacl -b on all of the files and folders. The .vbox files should have 600 permissions and all folders should have 700 permissions. Everything should be owned by vbox:vboxusers.
      omv 4.1.19 arrakis | 64 bit | 4.15 proxmox kernel | omvextrasorg 4.1.15
      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!
    • Thanks for your answer, my listing above shows, that everything is owned by vbox:vboxusers and that the rights are 775 (I think), so it should work anyway?

      After running your command nothing changed:

      Source Code

      1. ​root@hpn:/media/sonstiges# setfacl -bR virtualbox
      2. root@hpn:/media/sonstiges# ls -la virtualbox
      3. insgesamt 2076
      4. drwxrwsr-x 3 vbox vboxusers 4096 Mär 1 10:06 .
      5. drwxr-sr-x 17 root users 4096 Mär 1 10:04 ..
      6. drwxrwsr-x 4 vbox vboxusers 4096 Mär 1 10:06 MySQL
      7. -rwxrwxr-x 1 vbox vboxusers 7791 Feb 18 22:02 mysql.vbox
      8. -rwxrwxr-x 1 vbox vboxusers 7791 Feb 18 22:02 mysql.vbox-prev
      9. -rwxrwxr-x 1 vbox vboxusers 2097152 Feb 18 22:02 mysql.vdi
    • While 700 does not equal 775, I don't think virtualbox cares if it is world-readable (some things do).

      What is the output of: ps aux | grep virt
      omv 4.1.19 arrakis | 64 bit | 4.15 proxmox kernel | omvextrasorg 4.1.15
      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!
    • Sorry for my late response:

      Source Code

      1. root@hpn:~# ps aux | grep virt
      2. root 5371 0.0 0.0 9904 892 pts/0 S+ 00:14 0:00 grep virt


      But maybe I should mention, that I deactived the plugin atm.

      Shall I change ACL to 700? I only kept the ones from ​cp -a and changed root with vbox, because the owner was changed from vbox:vboxusers to root:vboxuser during cp -a

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

    • The output of ps doesn't do any good if it isn't running. I was wondering if one of the virtualbox services was running as the wrong user.

      700 is a permission not and ACL.

      I would purge the virtualbox package and plugin, delete the vbox user, and delete the virtualbox files in /etc/default/. Then I would reinstall the plugin and change the ownership of all of your VM files to the new vbox user that the plugin creates.
      omv 4.1.19 arrakis | 64 bit | 4.15 proxmox kernel | omvextrasorg 4.1.15
      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!
    • Ok after starting the service it shows:

      Source Code

      1. ​root@hpn:/# ps aux | grep virt
      2. vbox 8646 0.0 0.0 104780 5688 ? S 00:32 0:00 /usr/lib/virtualbox/VBoxXPCOMIPCD
      3. vbox 8651 0.2 0.1 193956 8680 ? Sl 00:32 0:00 /usr/lib/virtualbox/VBoxSVC --auto-shutdown
      4. 999 8740 0.0 0.0 138568 4244 ? S 00:32 0:00 php-fpm: pool openmediavault-virtualbox
      5. 999 8741 0.0 0.0 138568 4244 ? S 00:32 0:00 php-fpm: pool openmediavault-virtualbox
      6. vbox 8809 0.2 0.0 210532 7004 ? Sl 00:32 0:00 /usr/lib/virtualbox/vboxwebsrv --background -H 127.0.0.1
      7. root 8963 0.0 0.0 9904 896 pts/0 S+ 00:33 0:00 grep virt


      now I'll try the other things you wrote.
    • I don't see any difference between your ps output and mine. Hopefully, the other things work.
      omv 4.1.19 arrakis | 64 bit | 4.15 proxmox kernel | omvextrasorg 4.1.15
      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 removed the plugin via WebGui (or was there anything else by "purge"?) and rebooted because the user was still in use (even if I deactivated the plugin before uninstalling it).
      Then:

      Source Code

      1. root@hpn:~# deluser --remove-home vbox
      2. Suche Dateien zum Sichern/Löschen ...
      3. »/var/lib/vbox« wurde nicht gesichert/gelöscht, da es mit ^/var/.* übereinstimmt.
      4. Entferne Benutzer »vbox« ...
      5. Warnung: Die Gruppe »vboxusers« hat keine Mitglieder mehr.
      6. Fertig.

      And:

      Source Code

      1. root@hpn:~# delgroup vboxusers
      2. Entferne Gruppe »vboxusers« ...
      3. Fertig.

      Afterwards:

      Source Code

      1. root@hpn:~# cd /etc/default
      2. root@hpn:/etc/default# dir | grep virt
      3. console-setup loadcpufreq openmediavault-virtualbox tftpd-hpa

      And:

      Source Code

      1. root@hpn:/etc/default# rm openmediavault-virtualbox

      Then I reinstalled the plugin and cat /etc/passwd | cut -d: -f1 told me, that vbox was created again.

      So I used chown -R vbox:vboxusers /media/sonstiges/virtualbox and chmod -r 700 /media/sonstiges/virtualbox, configured and started the plugin, and received the same error again, when I change to “Virtual Machine” Tab.

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

    • Uninstalling from the web interface does remove but doesn't purge the plugin.

      apt-get purge virtualbox phpvirtualbox openmediavault-virtualbox
      apt-get autoremove

      I would try it. If it doesn't work, I would use this script to upgrade to virtualbox 5.0 (if you didn't already).
      omv 4.1.19 arrakis | 64 bit | 4.15 proxmox kernel | omvextrasorg 4.1.15
      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!
    • With v5 the error is another one.
      First I was not able to log in to WebGui any more (wrong user or password)
      What I’ve done:
      1) deactivate the plugin
      2) run apt-get purge virtualbox phpvirtualbox openmediavault-virtualbox
      3) apt-get autoremove
      4) reboot
      5) delete the user and group: deluser --remove-home vbox delgroup vboxusers
      6) download and run the script for vbox 5 sh <path_to_script>/vb5_install.sh
      7) reboot

      During install I received the warning (for guest additions I think?)

      Source Code

      1. WARNING: The vboxdrv kernel module is not loaded. Either there is no module
      2. available for the current kernel (3.2.0-4-amd64) or it failed to
      3. load. Please recompile the kernel module and install it by
      4. sudo /sbin/vboxconfig
      5. You will not be able to start VMs until this problem is fixed.


      After another reboot I was able to log in again.

      Then I chown and chmoded the rights again to 700 for vbox:vboxusers but the error remains:

      Source Code

      1. ​Could not connect to host (http://127.0.0.1:18083/)
      2. Fehler #64:
      3. exception 'Exception' with message 'Could not connect to host (http://127.0.0.1:18083/)' in /usr/share/phpvirtualbox/endpoints/lib/vboxconnector.php:220
      4. Stack trace:
      5. #0 /usr/share/openmediavault/engined/rpc/virtualbox.inc(176): vboxconnector->connect()
      6. #1 [internal function]: OMVRpcServiceVirtualBox->getMachines(Array, Array)
      7. #2 /usr/share/php/openmediavault/rpcservice.inc(125): call_user_func_array(Array, Array)
      8. #3 /usr/share/php/openmediavault/rpc.inc(79): OMVRpcServiceAbstract->callMethod('getMachines', Array, Array)
      9. #4 /usr/sbin/omv-engined(500): OMVRpc::exec('VirtualBox', 'getMachines', Array, Array, 1)
      10. #5 {main}

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

    • Did you recompile the vboxdrv? If the fix modules button is still in the virtualbox plugin, use it. Otherwise, try invoke-rc.d vboxdrv setup

      Can't connect is a different issue. Looks like your vboxwebsrv is not running because it can't load the module.
      omv 4.1.19 arrakis | 64 bit | 4.15 proxmox kernel | omvextrasorg 4.1.15
      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!
    • Ok I tried the "fix module..." button but it failed:

      Source Code

      1. Install build-essential.
      2. Reading package lists...
      3. Building dependency tree...
      4. Reading state information...
      5. build-essential is already the newest version.
      6. build-essential set to manually installed.
      7. 0 upgraded, 0 newly installed, 0 to remove and 0 not upgraded.
      8. Recompile VirtualBox module.
      9. Stopping VirtualBox kernel modules ...done.
      10. Recompiling VirtualBox kernel modules ...failed!
      11. (Look at /var/log/vbox-install.log to find out what went wrong)
      12. Load VirtualBox module.
      13. Starting VirtualBox kernel modules ...failed!
      14. (modprobe vboxdrv failed. Please use 'dmesg' to find out why)
      15. Restart vboxweb-service
      16. Starting VirtualBox web service ...fail!
      Display All


      So I assumed I needed backports kernel, installed it from OMV-Extras Plugin and rebooted to set it active.
      Then tried "fix module.." again and it succeeded:

      Source Code

      1. Install build-essential.
      2. Reading package lists...
      3. Building dependency tree...
      4. Reading state information...
      5. build-essential is already the newest version.
      6. 0 upgraded, 0 newly installed, 0 to remove and 12 not upgraded.
      7. Recompile VirtualBox module.
      8. Stopping VirtualBox kernel modules ...done.
      9. Recompiling VirtualBox kernel modules ...done.
      10. Starting VirtualBox kernel modules ...done.
      11. Load VirtualBox module.
      12. Starting VirtualBox kernel modules ...done.
      13. Restart vboxweb-service
      14. Starting VirtualBox web service ...done.
      Display All


      Just to make sure I rebooted again.
      And oh wonder the old error 0x80070005 is back :(

      Source Code

      1. VirtualBox error: rc=0x80070005 The object functionality is limited (0x80070005)
      2. Fehler #0:
      3. SoapFault exception: [SOAP-ENV:Client] VirtualBox error: rc=0x80070005 The object functionality is limited (0x80070005) in /usr/share/phpvirtualbox/endpoints/lib/vboxServiceWrappers.php:2728
      4. Stack trace:
      5. #0 /usr/share/phpvirtualbox/endpoints/lib/vboxServiceWrappers.php(2728): SoapClient->__soapCall('IMachine_getNam...', Array)
      6. #1 /usr/share/phpvirtualbox/endpoints/lib/vboxServiceWrappers.php(54): IMachine->getName()
      7. #2 /usr/share/openmediavault/engined/rpc/virtualbox.inc(181): VBox_ManagedObject->__get('name')
      8. #3 [internal function]: OMVRpcServiceVirtualBox->getMachines(Array, Array)
      9. #4 /usr/share/php/openmediavault/rpcservice.inc(125): call_user_func_array(Array, Array)
      10. #5 /usr/share/php/openmediavault/rpc.inc(79): OMVRpcServiceAbstract->callMethod('getMachines', Array, Array)
      11. #6 /usr/sbin/omv-engined(500): OMVRpc::exec('VirtualBox', 'getMachines', Array, Array, 1)
      12. #7 {main}
      Display All


      ps aux remains the same

      Source Code

      1. root@hpn:~# ps aux | grep virt
      2. 999 3156 0.0 0.0 138576 6356 ? S 09:19 0:00 php-fpm: pool openmediavault-virtualbox
      3. 999 3157 0.0 0.0 138576 6356 ? S 09:19 0:00 php-fpm: pool openmediavault-virtualbox
      4. vbox 3408 0.0 0.1 148064 15240 ? Sl 09:19 0:00 /usr/lib/virtualbox/vboxwebsrv --background -H 127.0.0.1
      5. vbox 3412 0.0 0.1 104832 9472 ? S 09:19 0:00 /usr/lib/virtualbox/VBoxXPCOMIPCD
      6. vbox 3420 0.0 0.1 199688 15296 ? Sl 09:19 0:00 /usr/lib/virtualbox/VBoxSVC --auto-shutdown
      7. root 6707 0.0 0.0 9916 1860 pts/0 S+ 09:24 0:00 grep virt​


      BTW: Am I going to have some issues/considerations upgrading OMV if I use another than the official kernel?
    • You shouldn't need the backports kernel but it does work for me. Did you look at /var/log/vbox-install.log?

      Virtualbox has to compile its drivers for most kernels. So, it should work with other kernels but I haven't tried.

      I still have no idea why you are getting this error.
      omv 4.1.19 arrakis | 64 bit | 4.15 proxmox kernel | omvextrasorg 4.1.15
      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!
    • Ok, so sadly it seems that I have to reinstall omv or at least the vm (didn't remember the test on that)
      I had the same issues before with the MySql plugin, so I decided to run it inside a VM, but this now has problems, too. Wonder if I'll get a stable environment someday :-).
      Anyway thanks a lot for your help.

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

    • Hi ryecoaaron,

      just to complete this topic, I wanted to try it again with another new share and vm, so I uninstalled vbox again, switched back to the normal kernel and installed vbox 5 again as described above. All went well even the driver package.

      But after restarting OMV and loading VirtualBox, it tells me "Some error has occured" and soon afterwards "0x80070005" is back. So I think I have to do a clean install of OMV. Maybe with the release of V3.

      Regards.
    • I would love for you to try a clean install (even on a different system or VM) to see if you can get it working with everything else eliminated.
      omv 4.1.19 arrakis | 64 bit | 4.15 proxmox kernel | omvextrasorg 4.1.15
      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!