Closed GoogleCodeExporter closed 8 years ago
GoogleCodeExporter
commented
8 years ago I hit this issue too, I had restarted the host after upgrading. I manually
killed the vboxwebsrv process and started it again via the console - then it
works. Not sure why, but my error output was the exact same as the one above.Original comment by spm...@foxwd.com on 5 Dec 2012 at 4:39
GoogleCodeExporter
commented
8 years ago As a follow up, not sure if this matters, but I seem to only hit this when the
host comes up and the virtualbox directory is not present. I keep my virtualbox
directory on a separate encrypted drive, which is manually mounted after boot -
this never was a problem before, it used to just complain about the VM's being
"inaccessible", then after clicking on each one they came up. Now I get this
error, the only way to resolve it is to bounce the vboxweb-service.Original comment by spm...@foxwd.com on 5 Dec 2012 at 4:46
GoogleCodeExporter
commented
8 years ago I dont know if this helps but I looking at the vboxwebsrv log and got
'E_ACCESSDENIED' error everytime I got this issue: The following is an extract
of the log:
00:03:40.031675 SQW03 Processing connection from IP=127.0.0.1 socket=15 (1
out of 6 threads idle)
00:03:40.257511 SQPmp Request 100 on socket 16 queued for processing (1
items on Q)
00:03:40.257568 SQW02 Processing connection from IP=127.0.0.1 socket=16 (4
out of 6 threads idle)
00:03:40.259481 SQPmp Request 101 on socket 10 queued for processing (1
items on Q)
00:03:40.259522 SQW01 Processing connection from IP=127.0.0.1 socket=10 (3
out of 6 threads idle)
00:03:40.300970 SQPmp Request 102 on socket 11 queued for processing (1
items on Q)
00:03:40.301029 SQW03 Processing connection from IP=127.0.0.1 socket=11 (4
out of 6 threads idle)
00:03:40.305885 SQW03 API return code: 0x80070005 (E_ACCESSDENIED)
00:03:40.305915 SQW03 COM error info result code: 0x80070005
00:03:40.305924 SQW03 COM error info text: The object functionality
is limited
00:03:40.306749 SQPmp Request 103 on socket 10 queued for processing (1
items on Q)
Original comment by bigblack...@me.com on 13 Dec 2012 at 1:50
GoogleCodeExporter
commented
8 years ago Same issue, if start it from console, it works fine. If by service, always get
this error.Original comment by gupeim...@gmail.com on 23 Dec 2012 at 2:06
GoogleCodeExporter
commented
8 years ago Same problem here, on every system restart I have the same issueOriginal comment by emi...@gmail.com on 9 Jan 2013 at 12:54
GoogleCodeExporter
commented
8 years ago My system is: Linux acerX3900 3.2.0-35-generic
And vbox:
vbox@acerX3900:~$ vboxmanage -v
4.2.6r82870
and phpvbox: 4.2Original comment by emi...@gmail.com on 9 Jan 2013 at 12:58
GoogleCodeExporter
commented
8 years ago Same issue.Original comment by jonathan...@alkaidconsulting.com on 5 Feb 2013 at 3:34
GoogleCodeExporter
commented
8 years ago Same issue.Original comment by amado...@gmail.com on 14 Feb 2013 at 6:31
GoogleCodeExporter
commented
8 years ago Same issue on System A (32-bit), not on System B (64-bit).
System A:
# VBoxManage --version
4.2.6r82870
# uname -a
Linux A 3.2.0-29-generic-pae #46-Ubuntu SMP Fri Jul 27 17:25:43 UTC 2012 i686
i686 i386 GNU/Linux
System B
# VBoxManage --version
4.2.6r82870
# uname -a
Linux B 3.2.0-23-generic #36-Ubuntu SMP Tue Apr 10 20:39:51 UTC 2012 x86_64
x86_64 x86_64 GNU/LinuxOriginal comment by jer...@vikingco.com on 19 Feb 2013 at 7:46
GoogleCodeExporter
commented
8 years ago I got the same issue with Virtualbox 4.2.6_OSE compiled from ports on FreeBSD
9.1.
Running vboxwebsrv from terminal shows the same errors as described by message
#3.Original comment by Lars.Vel...@gmail.com on 22 Feb 2013 at 3:03
GoogleCodeExporter
commented
8 years ago Same issue.
phpvirtualbox: 4.2-5
# vboxmanage -version
4.2.6r82870
# uname -a
Linux ************** 2.6.18-308.16.1.el5 #1 SMP Tue Oct 2 22:01:43 EDT 2012
x86_64 x86_64 x86_64 GNU/Linux
# cat /etc/redhat-release
CentOS release 5.8 (Final)Original comment by m.t.t.k.1AE@gmail.com on 25 Feb 2013 at 8:23
GoogleCodeExporter
commented
8 years ago Same issue.
# /usr/local/bin/VBoxManage --version
4.2.6_OSEr82870
# uname -a
FreeBSD *** 9.1-RELEASE FreeBSD 9.1-RELEASE #0 r243825: Tue Dec 4 09:23:10 UTC
2012 GENERIC amd64
Original comment by JohnnyGe...@gmail.com on 16 Mar 2013 at 2:29
GoogleCodeExporter
commented
8 years ago same issue
# uname -a
Linux ++++ 3.5.0-26-generic #42-Ubuntu SMP Fri Mar 8 23:18:20 UTC 2013 x86_64
x86_64 x86_64 GNU/Linux
# vboxmanage --version
4.2.10r84104
I have another box and this is working ok! ==>
# vboxmanage --version
4.2.10r84104
$ uname -a
Linux +++ 3.5.0-26-generic #42-Ubuntu SMP Fri Mar 8 23:18:20 UTC 2013 x86_64
x86_64 x86_64 GNU/Linux
Original comment by emiliano...@gmail.com on 4 Apr 2013 at 1:53
GoogleCodeExporter
commented
8 years ago Hello,
My configuration is:
- CPU AMD Athlon(tm) II X2 250
- Memory 8 Gb
- Ubuntu 12.04.1 LTS (GNU/Linux 3.2.0-29-generic x86_64)
- VirtualBox 4.2.10(84104)
- phpvirtualbox 4.2.4
In the beginning everything worked out fine but then something went wrong
Same issue -> The object functionality is limited (0x80070005)
Then with the command -> vboxmanage list systemproperties
in the list, the row -> Default machine folder:
i found the value -> /root/VirtualBox VMs
WHY??? The installer user is "myuser" so i changed the value with the command
VBoxManage setproperty machinefolder /home/myuser
and after reboot there is no error message :-)
Now, after seven days, it is still working!
ByeOriginal comment by armandov...@gmail.com on 4 Apr 2013 at 4:20
GoogleCodeExporter
commented
8 years ago Thanks. Your suggestion helps vor me!Original comment by bernhard...@gmail.com on 7 Apr 2013 at 11:54
GoogleCodeExporter
commented
8 years ago I still have this issue on one of my machines after an upgrade. I can create
new machines, stop and start machines etc... but cannot view the host machine
details.
I will try wiping all configurations and starting over but am very confused. I
did not have this problem upgrading the other server so am wondering whether
there may be another cause.
Original comment by scmurc...@gmail.com on 7 Apr 2013 at 7:31
GoogleCodeExporter
commented
8 years ago Hello,
I also got exactly this error.
It was also wrong setting of Default machine folder:
VBoxManage list systemproperties
Then I fixed it with:
VBoxManage setproperty machinefolder /home/VM
And it did not fixed the problem.
Then after some more investigation I found in log file:
08:20:00.593286 nspr-4 ERROR [COM]: aRC=VBOX_E_OBJECT_NOT_FOUND (0x80bb0001)
aIID={22781af3-1c96-4126-9edf-67a020e0e858} aComponent={SessionMachine}
aText={No storage device attached to device slot 0 on port 15 of controller
'SCSI Controller'}, preserve=false
So decided to investigate VBox side, and after frying to get info about IID:
VBoxManage showvminfo {0e6a45b7-da15-4b82-a9b5-76327576672d}
Name: <inaccessible!>
UUID: 0e6a45b7-da15-4b82-a9b5-76327576672d
Config file: /home/VM/test5k/test5k.vbox
Access error details:
VBoxManage: error: Runtime error opening '/home/VM/test5k/test5k.vbox' for
reading: -102 (File not found.).
VBoxManage: error:
/home/vbox/vbox-4.2.12/src/VBox/Main/src-server/MachineImpl.cpp[725] (nsresult
Machine::registeredInit())
VBoxManage: error: Details: code NS_ERROR_FAILURE (0x80004005), component
Machine, interface IMachine
This showed up, that I have some problem in configuration with olde deleted VM:
VBoxManage list vms
"<inaccessible>" {0e6a45b7-da15-4b82-a9b5-76327576672d}
.....
Thats it!
just run
VBoxManage unregistervm {0e6a45b7-da15-4b82-a9b5-76327576672d}
and problem was fixed!
Happy using!
Original comment by arunassp...@gmail.com on 13 Apr 2013 at 3:33
GoogleCodeExporter
commented
8 years ago I had the exact same problem. Deleting old VMs was the solution for me as well.
Thank you so much!Original comment by audun.bj...@gmail.com on 13 Apr 2013 at 7:13
GoogleCodeExporter
commented
8 years ago This issue occured after killing vbox processes which caused one of the .vbox
config files to be empty. Simply copying the vbox-prev to to .vbox fixed the
issue.Original comment by bendi...@gmail.com on 13 May 2013 at 12:47
GoogleCodeExporter
commented
8 years ago Unfortunately, after .vbox restoration, pb still the same...Original comment by form....@gmail.com on 21 Jun 2013 at 12:33
GoogleCodeExporter
commented
8 years ago Please open a new issue if any of you are still having this problemOriginal comment by imooreya...@gmail.com on 12 Jul 2013 at 4:51
GoogleCodeExporter
commented
8 years ago Same problem.
List of VM machines no longer appears and Host info is not reachable:
Ubuntu 13.04 (GNU/Linux 3.8.0-27-generic x86_64)
Virtual Box 4.2.10_Ubuntu (84101)
phpVirtualBox 4.2-6 -/- VirtualBox 4.2.x compatible
ERROR:
SoapFault Object
(
[message:protected] => VirtualBox error: The object functionality is limited (0x80070005)
[string:Exception:private] =>
[code:protected] => 0
[file:protected] => /var/www/lib/vboxServiceWrappers.php
[line:protected] => 2015
[trace:Exception:private] => Array
(
[0] => Array
(
[file] => /var/www/lib/vboxServiceWrappers.php
[line] => 2015
[function] => __soapCall
[class] => SoapClient
[type] => ->
[args] => Array
(
[0] => IMachine_getName
[1] => Array
(
[0] => Array
(
[_this] => 7d7dd2af385aceec-0000000000000386
)
)
)
)
[1] => Array
(
[file] => /var/www/lib/vboxServiceWrappers.php
[line] => 54
[function] => getName
[class] => IMachine
[type] => ->
[args] => Array
(
)
)
[2] => Array
(
[file] => /var/www/lib/vboxconnector.php
[line] => 2690
[function] => __get
[class] => VBox_ManagedObject
[type] => ->
[args] => Array
(
[0] => name
)
)
[3] => Array
(
[file] => /var/www/lib/vboxconnector.php
[line] => 3274
[function] => remote_hostGetNetworking
[class] => vboxconnector
[type] => ->
[args] => Array
(
[0] => Array
(
[vm] => host
[fn] => machineGetDetails
)
)
)
[4] => Array
(
[file] => /var/www/lib/vboxconnector.php
[line] => 923
[function] => remote_machineGetDetails
[class] => vboxconnector
[type] => ->
[args] => Array
(
[0] => Array
(
[vm] => host
[fn] => machineGetDetails
)
)
)
[5] => Array
(
[file] => /var/www/lib/ajax.php
[line] => 309
[function] => __call
[class] => vboxconnector
[type] => ->
[args] => Array
(
[0] => machineGetDetails
[1] => Array
(
[0] => Array
(
[vm] => host
[fn] => machineGetDetails
)
[1] => Array
(
[0] => Array
(
[data] => Array
(
[responseData] => Array
(
)
)
[errors] => Array
(
)
[persist] => Array
(
)
[messages] => Array
(
)
)
)
)
)
)
[6] => Array
(
[file] => /var/www/lib/ajax.php
[line] => 309
[function] => machineGetDetails
[class] => vboxconnector
[type] => ->
[args] => Array
(
[0] => Array
(
[vm] => host
[fn] => machineGetDetails
)
[1] => Array
(
[0] => Array
(
[data] => Array
(
[responseData] => Array
(
)
)
[errors] => Array
(
)
[persist] => Array
(
)
[messages] => Array
(
)
)
)
)
)
)
[previous:Exception:private] =>
[faultstring] => VirtualBox error: The object functionality is limited (0x80070005)
[faultcode] => SOAP-ENV:Client
[detail] => stdClass Object
(
[RuntimeFault] => stdClass Object
(
[resultCode] => -2147024891
[interfaceID] => 22781af3-1c96-4126-9edf-67a020e0e858
[component] => Machine
[text] => The object functionality is limited
)
)
)
Original comment by broadsco...@gmail.com on 24 Sep 2013 at 10:06
GoogleCodeExporter
commented
8 years ago OK i've resolved with this method:
1) Stop all Vbox service
sudo /etc/init.d/vboxweb-service stop
sudo /etc/init.d/vboxdrv stop
sudo /etc/init.d/vboxdrv vboxballoonctrl-service stop
sudo /etc/init.d/vboxdrv vboxautostart-service stop
2) Go to /home/virtbox/.VirtualBox#+
Then backup your Virtualbox.xml with the command
cp Virtualbox.xml VirtualBox.xml.bk
Then
nano Virtualbox.xml
So, in my case i've found 2 "Wrong/Fake/Not Exist" VMS and i've found a lot of
wrong paths.
I've deleted all of that erros then i restart the services (first the sudo
/etc/init.d/vboxdrv stop)
Now all work fine :)
Give me a Feedback or confirmation!Original comment by i...@bdevil.it on 23 Dec 2013 at 5:02
GoogleCodeExporter
commented
8 years ago It works ...
1) Stop all Vbox services
sudo /etc/init.d/vboxweb-service stop
sudo /etc/init.d/vboxdrv stop
2) Check the configuration stored in VirtualBox.xml and repair
3) Start all Vbox services
sudo /etc/init.d/vboxdrv start
sudo /etc/init.d/vboxweb-service startOriginal comment by quadrat....@gmail.com on 7 Aug 2014 at 5:00
Original issue reported on code.google.com by
kvantar...@gmail.comon 26 Nov 2012 at 7:20