Timing Issues in machine operation verification (was: The log has an error, but the vbox starts OK.)

[GoogleCodeExporter]

What steps will reproduce the problem?
1. Start Vbox in services control
2.
3.

What is the expected output? What do you see instead?
The log has an error, but the vbox starts OK.
-- Log snippet
VirtualBoxService.MachineController Verbose: 20230 : [3/17/2012 11:19:27 PM] 
Remaining time for current operation: 00:00:01
VirtualBoxService.MachineController Warning: 20201 : [3/17/2012 11:19:37 PM] 
Boot on machine "OEL1" timed out.

What version of the product are you using? On what operating system?
virtualboxservice v0.1
Vbox 4.1.10
Windows 7 64bit

Please provide any additional information below.
Best vbox service utility yet, thanx

I am running this on my laptop so it starts slow. I think I just need
to be able to set the start timeout longer.

Original issue reported on code.google.com by mr.brian...@gmail.com on 18 Mar 2012 at 6:40

[GoogleCodeExporter]

The timeout is determined dynamically during runtime. Virtualbox does give some 
estimates about the time needed to complete a certain process. Especially if 
the operation is very short, the value "0 seconds" is returned as remaining 
time, while in reality it is some milliseconds. The problem is in the file 
http://code.google.com/p/virtualboxservice/source/browse/VBoxWrapper/VBoxWrapper
/COMInterface/ComMachineProxy.cs in sub-class IProgressProgressToken, which is 
basically an adapter to the Virtualbox-API. The method EstimateRemainingTime() 
needs to be reviewed.

Original comment by Felix.Ru...@gmail.com on 28 Mar 2012 at 1:29

• Changed title: Timing Issues in machine operation verification (was: The log has an error, but the vbox starts OK.)
• Changed state: Accepted

[GoogleCodeExporter]

No, seems, I was wrong. The constant DEFAULT_TIMEOUT seems to be set too short.

Original comment by Felix.Ru...@gmail.com on 28 Mar 2012 at 1:55