VBoxWebService problem on powerUp
Posted: 16. Feb 2012, 13:40
Hi.
I am using VBoxWebSrv.exe to access VirtualBox functionallity.
I login, lock, power up a machine, power off, unlock and log out.
The second time I do that it fails:
00:00:13.703 SQW01 calling COM method PowerUp
API return code: 0x80004005 (E_FAIL)
COM error info result code: 0x0
COM error info text:
Observations:
1. After the first time on calling powerUp, the output on the cmd windows from where I launch the WebServer freezes
(but not the log in the VM directory)
2. The seconf time I try to call powerUp, it fails. In the log it says:
00:00:42.000 ERROR [COM]: aRC=E_FAIL (0x80004005) aIID={1968b7d3-e3bf-4ceb-99e0-cb7c913317bb} aComponent={Console} aText={Failed to open release log (could not open file 'D:\VMs\msim\Logs\VBox.log' (fOpen=0x322), VERR_SHARING_VIOLATION)}, preserve=false
This is what I am doing:
LOGIN
16.02.2012 11:55:43: CREATED new session: b5f9e528c4b55df3-0000000000000001
16.02.2012 11:55:43: CREATED virtualBoxMOR: b5f9e528c4b55df3-0000000000000002
16.02.2012 11:55:43: machineMOR created: b5f9e528c4b55df3-0000000000000003
16.02.2012 11:55:43: Console got: b5f9e528c4b55df3-0000000000000004
16.02.2012 11:55:43: Powering Up, the beginning of the problems. VBoxWebService output freezes
16.02.2012 11:55:43: progressMOR for powering Up: b5f9e528c4b55df3-0000000000000005
16.02.2012 11:55:45: Elapsed time to launch VM process: 1962 miliseconds
16.02.2012 11:56:11: progressMOR for closing VM: b5f9e528c4b55df3-0000000000000007
16.02.2012 11:56:11: Unlocking after switching off
LOGOFF
LOGIN
16.02.2012 11:56:11: CREATED new session: bfc70ce5651faf19-0000000000000008
16.02.2012 11:56:11: CREATED virtualBoxMOR: bfc70ce5651faf19-0000000000000009
16.02.2012 11:56:11: machineMOR created: bfc70ce5651faf19-000000000000000a
16.02.2012 11:56:11: Console got: bfc70ce5651faf19-000000000000000b
16.02.2012 11:56:11: Powering Up, the beginning of the problems.
16.02.2012 11:56:11: VirtualBox error: (0x80004005)
Is this a bug? Any idea/suggestions?
This doesn't happens when using one of the standard frontends provided by VBox.
I am using VBoxWebSrv.exe to access VirtualBox functionallity.
I login, lock, power up a machine, power off, unlock and log out.
The second time I do that it fails:
00:00:13.703 SQW01 calling COM method PowerUp
API return code: 0x80004005 (E_FAIL)
COM error info result code: 0x0
COM error info text:
Observations:
1. After the first time on calling powerUp, the output on the cmd windows from where I launch the WebServer freezes
(but not the log in the VM directory)
2. The seconf time I try to call powerUp, it fails. In the log it says:
00:00:42.000 ERROR [COM]: aRC=E_FAIL (0x80004005) aIID={1968b7d3-e3bf-4ceb-99e0-cb7c913317bb} aComponent={Console} aText={Failed to open release log (could not open file 'D:\VMs\msim\Logs\VBox.log' (fOpen=0x322), VERR_SHARING_VIOLATION)}, preserve=false
This is what I am doing:
LOGIN
16.02.2012 11:55:43: CREATED new session: b5f9e528c4b55df3-0000000000000001
16.02.2012 11:55:43: CREATED virtualBoxMOR: b5f9e528c4b55df3-0000000000000002
16.02.2012 11:55:43: machineMOR created: b5f9e528c4b55df3-0000000000000003
16.02.2012 11:55:43: Console got: b5f9e528c4b55df3-0000000000000004
16.02.2012 11:55:43: Powering Up, the beginning of the problems. VBoxWebService output freezes
16.02.2012 11:55:43: progressMOR for powering Up: b5f9e528c4b55df3-0000000000000005
16.02.2012 11:55:45: Elapsed time to launch VM process: 1962 miliseconds
16.02.2012 11:56:11: progressMOR for closing VM: b5f9e528c4b55df3-0000000000000007
16.02.2012 11:56:11: Unlocking after switching off
LOGOFF
LOGIN
16.02.2012 11:56:11: CREATED new session: bfc70ce5651faf19-0000000000000008
16.02.2012 11:56:11: CREATED virtualBoxMOR: bfc70ce5651faf19-0000000000000009
16.02.2012 11:56:11: machineMOR created: bfc70ce5651faf19-000000000000000a
16.02.2012 11:56:11: Console got: bfc70ce5651faf19-000000000000000b
16.02.2012 11:56:11: Powering Up, the beginning of the problems.
16.02.2012 11:56:11: VirtualBox error: (0x80004005)
Is this a bug? Any idea/suggestions?
This doesn't happens when using one of the standard frontends provided by VBox.