Virtual Box Error

y2kdread · 14. März 2013

Hi,

I am getting the following error when trying to get into virtual box after installing:

Code

Error #3003:
exception 'OMVException' with message 'Failed to get configuration (xpath=//services/virtualbox)' in /var/www/openmediavault/rpc/virtualbox.inc:126
Stack trace:
#0 /var/www/openmediavault/rpc/virtualbox.inc(177): VirtualBoxRpc->__call('configGet', Array)
#1 /var/www/openmediavault/rpc/virtualbox.inc(177): VirtualBoxRpc->configGet('//services/virt...')
#2 [internal function]: VirtualBoxRpc->get(NULL)
#3 /usr/share/php/openmediavault/rpc.inc(265): call_user_func_array(Array, Array)
#4 /usr/share/php/openmediavault/rpc.inc(98): OMVRpc::exec('VirtualBox', 'get', NULL)
#5 /var/www/openmediavault/rpc.php(44): OMVJsonRpcServer->handle()
#6 {main}

Any ideas on ways to resolve?

ryecoaaron · 14. März 2013

Just to warn you, there have been lots of issue with the virtualbox plugin since it is not being actively updated. We are working on that.

Did you reboot? Clear browser cache? What is the output of the following:

cat /etc/default/virtualbox
ps aux | grep vbox

y2kdread · 14. März 2013

I did all of the rebooting, clearing cache, and what-not. Here are the outputs I get from those commands you listed:

Code

root@BookNAS:~# cat /etc/default/virtualbox
# defaults for virtualbox
# sourced by vboxweb-service on startup


VBOXWEB_USER=vbox
VBOXWEB_HOST=127.0.0.1

Code

root@BookNAS:~# ps aux | grep vbox
root     27332  0.0  0.0   7548   828 pts/0    S+   15:08   0:00 grep vbox

y2kdread · 14. März 2013

Also, this is what I get when I try to re-installed the plugin:

Code

Reading package lists...
Building dependency tree...
Reading state information...
0 upgraded, 0 newly installed, 1 reinstalled, 0 to remove and 0 not upgraded.
2 not fully installed or removed.
After this operation, 0 B of additional disk space will be used.
Setting up virtualbox-4.2 (4.2.4-81684~Debian~squeeze) ...
debconf: unable to initialize frontend: Dialog
debconf: (Dialog frontend will not work on a dumb terminal, an emacs shell buffer, or without a controlling terminal.)
debconf: falling back to frontend: Readline
debconf: unable to initialize frontend: Readline
debconf: (This frontend requires a controlling tty.)
debconf: falling back to frontend: Teletype
addgroup: The group `vboxusers' already exists as a system group. Exiting.
Stopping VirtualBox kernel modules:.
Starting VirtualBox kernel modules:.
Starting VirtualBox web service:
 failed!
invoke-rc.d: initscript vboxweb-service, action "start" failed.
dpkg: error processing virtualbox-4.2 (--configure):
 subprocess installed post-installation script returned error exit status 1
configured to not write apport reports
dpkg: dependency problems prevent configuration of openmediavault-virtualbox:
 openmediavault-virtualbox depends on virtualbox-4.2; however:
  Package virtualbox-4.2 is not configured yet.
dpkg: error processing openmediavault-virtualbox (--configure):
 dependency problems - leaving unconfigured
configured to not write apport reports
Processing triggers for python-central ...
Errors were encountered while processing:
 virtualbox-4.2
 openmediavault-virtualbox
E: Sub-process /usr/bin/dpkg returned an error code (1)
Done ...

Alles anzeigen

Sodden · 15. März 2013

Zitat von "y2kdread"

Also, this is what I get when I try to re-installed the plugin:

Code

Reading package lists...
Building dependency tree...
Reading state information...
0 upgraded, 0 newly installed, 1 reinstalled, 0 to remove and 0 not upgraded.
2 not fully installed or removed.
After this operation, 0 B of additional disk space will be used.
Setting up virtualbox-4.2 (4.2.4-81684~Debian~squeeze) ...
debconf: unable to initialize frontend: Dialog
debconf: (Dialog frontend will not work on a dumb terminal, an emacs shell buffer, or without a controlling terminal.)
debconf: falling back to frontend: Readline
debconf: unable to initialize frontend: Readline
debconf: (This frontend requires a controlling tty.)
debconf: falling back to frontend: Teletype
addgroup: The group `vboxusers' already exists as a system group. Exiting.
Stopping VirtualBox kernel modules:.
Starting VirtualBox kernel modules:.
Starting VirtualBox web service:
 failed!
invoke-rc.d: initscript vboxweb-service, action "start" failed.
dpkg: error processing virtualbox-4.2 (--configure):
 subprocess installed post-installation script returned error exit status 1
configured to not write apport reports
dpkg: dependency problems prevent configuration of openmediavault-virtualbox:
 openmediavault-virtualbox depends on virtualbox-4.2; however:
  Package virtualbox-4.2 is not configured yet.
dpkg: error processing openmediavault-virtualbox (--configure):
 dependency problems - leaving unconfigured
configured to not write apport reports
Processing triggers for python-central ...
Errors were encountered while processing:
 virtualbox-4.2
 openmediavault-virtualbox
E: Sub-process /usr/bin/dpkg returned an error code (1)
Done ...

Alles anzeigen

Hi,

I'm getting the same errors after trying to reinstall the vbox plugin. One other thing that I noticed is that the vbox user is not created during install.
I'm also getting a weird kernel error when installing/purging the virtualbox package via apt-get.

Zitat

kernel:[ 1715.012216] RTSpinlockReleaseNoInts: ffff880037830a10 (magic=0x19480428)

I just installed it a few weeks ago and haven't really done anything to the system since then, besides updates of course.

tekkb · 16. März 2013

First make sure this file exists /etc/default/virtualbox with these contents:

Code

# defaults for virtualbox
# sourced by vboxweb-service on startup


VBOXWEB_USER=vbox
VBOXWEB_HOST=127.0.0.1

if it is not there create it.

Then in command line:
modprobe vboxdrv
reboot

Then after reboot run this command to make sure Vbox services are running:
ps aux | grep virtualbox

Results of this command should look like this:

Code

root@OMVbase:~# ps aux | grep virtualbox
vbox      1410  0.0  0.2 116040  5496 ?        Sl   20:37   0:00 /usr/lib/virtualbox/vboxwebsrv --background -H 127.0.0.1
vbox      1412  0.0  0.2  84584  5284 ?        S    20:37   0:00 /usr/lib/virtualbox/VBoxXPCOMIPCD
vbox      1417  0.0  0.3 104976  7372 ?        Sl   20:37   0:00 /usr/lib/virtualbox/VBoxSVC --auto-shutdown
root      1599  0.0  0.0   7552   832 pts/0    S+   20:38   0:00 grep virtualbox
root@OMVbase:~#

Then make sure Vbox extension pack is installed with this command:
VBoxManage list extpacks

It should be but if not let us know.

Then:
cd /var/www/openmediavault/js/omv/module/admin/
mv virtualbox.js Virtualbox.js

Done!!!!

Sodden · 16. März 2013

It's still not starting properly. I'd tell you what I did but the forum won't let me, says my message is spam ?!?

Well anyway. Even after following your steps I still haven't got a vbox user and it seems that this is keeping the other services from starting properly.

Edit:

Code

root@omv:/etc/apt# ps aux | grep virtualbox
root      7292  0.0  0.0   9108   856 pts/0    S+   14:46   0:00 grep virtualbox

tekkb · 16. März 2013

Sodden, create a topic. Start by showing me this file. /etc/apt/sources.list

Please don't post on this thread Sodden. Most people's problems are different.

Jetzt mitmachen!