Hi,

Since the server update, I'm getting a bunch of errors from the new boinc2docker client. Units will stop after 10 minutes at ~50% with the following error message: "Postponed: VM hypervisor failed to enter an online state in a timely fashion".

In my unit logs, Boinc complains that VT-X is not enabled in the BIOS, although it definitely is enabled and correctly detected by Intel Processor ID Utility and Microsoft HAV Detection Tool. I will also add that the Milkyway client runs perfectly on VirtualBox.

My config: Core2 Quad 3.0 GHz, Win7-64, Boinc 7.6.9, VirtualBox 4.3.12

I followed the FAQ procedure to no avail. For now, I have no choice but to revert to the legacy client.

---

Try to install new version of VirtualBox

https://www.virtualbox.org/

Try to install new version of VirtualBox

https://www.virtualbox.org/

Same problem here.

Really, I am not sure if this is problem of Virtual Box version. It can be problem, related to Windows 10. I updated my computer to this OS two days ago, and now time to time I can notice these error messages.
Anyway, I updated Virtual Box and now checking if it solved this problem.

We are waiting results

Thanks for the heads-up.

I've updated VirtualBox to 5.0.8, and it seems to have fixed my issue so far. C@H has just completed its first boinc2docker unit (which took 28 minutes for an initial estimation of 14 minutes) and it's ready to report. I have a few more units in the pipeline and will report later if something goes wrong.

---

We are waiting results

Update to new Virtual Box version also solved problem for me.

Anyway, on my Windows 7 machine, 4.3 version still working without problems.

Aurimas Rapecka: Yea, Windows 10.00.10240.00 which is the version you have requires Virtualbox at least 5.0.8 (I should put this in FAQ)

Ryusennin: Your problem is completely different, but I don't really understand what's going on. From the logs it almost looks like the VM ran successfully but vboxwrapper somehow "didn't notice." Anyway, helpful to know that upgrading seemed to solve your problem. Let me know if something similar returns.

Hi Marius,

Unfortunately the problem has returned with the same error message. Once again I upgraded VirtualBox to the latest version, but this time it didn't fix the issue. Strangely enough it worked three days ago for just one unit, but since then every further unit is freezing at ~43% with the message "Postponed: VM Hypervisor failed etc". The smoking gun seems to be that VB is taking 0% CPU time while it's supposed to be crunching on 4 cores.

---

Hi Marius,

Unfortunately the problem has returned with the same error message. Once again I upgraded VirtualBox to the latest version, but this time it didn't fix the issue. Strangely enough it worked three days ago for just one unit, but since then every further unit is freezing at ~43% with the message "Postponed: VM Hypervisor failed etc". The smoking gun seems to be that VB is taking 0% CPU time while it's supposed to be crunching on 4 cores.

Thanks for letting me know. Can you point me to exactly one of the jobs that failed like this? (click the task, go to properties, and tell me the workunit name)

http://www.cosmologyathome.org/result.php?resultid=34803669

The incriminated units don't output any error log on my account, they just keep displaying "in progress".

Sorry but VB/docker appears to be too much trouble on my Core2 system, I'll keep using the legacy app for now. Thanks anyway for the help.

---

hi Marius,

I am too having Windows 10. Facing the same issue. I believe the issue occurs when Boinc switch to a different task and later upon return, the vmbox is not getting started or meeting the SLA. Tasks when run in a single stretch is getting completed.

Using default Vmbox coming with Boinc - v4.3.12 r93733

Three units in my machine are with current status "Postponed : VM Hypervisor failed to enter an online state in a timely fashion. (3 CPUs)". I am leaving them untouched.

Unit Name: camb_boinc2docker_24973_1451264044.657457 (currently postponed at 89.240% , Elapsed time 1:10:20)
Unit Name: camb_boinc2docker_22371_1451263775.774557 (currently postponed at 32.815%, Elapsed time 00:10:08)
Unit Name: camb_boinc2docker_24564_1451264038.177400 (currently postponed at 32.808%, Elapsed time 00:10:08)

Regards,
Kiran George B.

Hi Marius,

I see that the postponed tasks resumed and got completed successfully.

Regards,
Kiran George B.

I still have 9 tasks stuck in "Postponed" state (for days). This seems to have happened when I upgraded BOINC to the current (recommended) version which included VirtualBox 3.0.10.

This is the message in VirtualBox for all of the tasks:

Runtime error opening 'C:\ProgramData\BOINC\slots\0\boinc_eeb247ae6f5aa0b8\boinc_eeb247ae6f5aa0b8.vbox' for reading: -103(Path not found.).
F:\tinderbox\win-5.0\src\VBox\Main\src-server\MachineImpl.cpp[740] (long __cdecl Machine::i_registeredInit(void)).
Result Code:
E_FAIL (0x80004005)
Component:
MachineWrap
Interface:
IMachine {f30138d4-e5ea-4b3a-8858-a059de4c93fd}

I rebooted the computer with 15-20 hypervisor postponed tasks, all of which had about 10 minutes, and all of them reset and reran and again failed at about 10 minutes - goodbye boinc2docker units - they are all being aborted on this computer!

Same here...stuck at about 10 minutes. I'm aborting the stuck tasks and turning off boinc2docker until fixed.

Thanks for the bug reports everyone and sorry about the hassle. I'm looking into it.

Tim, can you point me to exactly on which of your hosts you're seeing this? (via PM is fine if you'd like).

I'm not too familiar with this error message, but e.g. this suggests it might have to do with RAM. Is it possible your systems are low on RAM at the point when the job is trying to start?

I don't have any indication of a RAM issue. The VirtualBox (v5.0.10) message in the previous post would seem to indicate a file path problem, but I have no experience with that software.

I'm getting the "Postponed: Detection of VM Hypervisor failed" problem with RNA World, but not with Cosmology@Home. It happened immediately after I rebooted after updating BOINC to 7.6.22. Oracle VM was updated to 5.0.10 r104061.

So it ain't C@H's problem.

I don't think the problem is anything to do with lack of RAM as I have 11gig installed.

There is a message that has variations on:

Runtime error opening 'C:\ProgramData\BOINC\slots\6\boinc_31f647b8ed083c75\boinc_31f647b8ed083c75.vbox' for reading: -103(Path not found.).

for each failure line (the number after the word 'slots' and the codes after that are different for each failure), and then

F:\tinderbox\win-5.0\src\VBox\Main\src-server\MachineImpl.cpp[740] (long __cdecl Machine::i_registeredInit(void)).
Result Code:
E_FAIL (0x80004005)
Component:
MachineWrap
Interface:
IMachine {f30138d4-e5ea-4b3a-8858-a059de4c93fd}

which is the same for each failure. I actually have a removable disk drive already installed as the F drive so I don't know if that causes a conflict.

I'm running Windows 10 Pro 64 bit with an AMD Athlon II x3 450 processor.