Advanced search

Forums : Technical Support : postponed VM hypervisor failed to enter and online state in a timely fashion
Message board moderation

To post messages, you must log in.

AuthorMessage
Cameron

Send message
Joined: 2 Dec 07
Posts: 7
Credit: 145,565
RAC: 0
Message 21374 - Posted: 1 May 2017, 10:42:23 UTC

The docker application appears to be suspending work partway through.

Multithreading is using 4 CPUs and estimated runtime at start is 15 minutes.
Network connection is allowed.

6 postpostponed already.

1/05/2017 7:38:34 PM | Cosmology@Home | Finished download of boinc_app_39215b124a534b1abe27943fa1e1db97
1/05/2017 7:43:29 PM | | Suspending network activity - user request
1/05/2017 7:44:41 PM | | Resuming network activity
1/05/2017 7:47:56 PM | Cosmology@Home | task postponed 86400.000000 sec: VM Hypervisor failed to enter an online state in a timely fashion.
1/05/2017 7:47:56 PM | Cosmology@Home | Starting task camb_boinc2docker_17606_1493631288.806810_0
1/05/2017 7:51:09 PM | Einstein@Home | Computation for task LATeah0027L_820.0_0_0.0_2640520_0 finished
1/05/2017 7:51:10 PM | Einstein@Home | Starting task LATeah0027L_820.0_0_0.0_2644285_0
1/05/2017 7:51:12 PM | Einstein@Home | Started upload of LATeah0027L_820.0_0_0.0_2640520_0_0
1/05/2017 7:51:12 PM | Einstein@Home | Started upload of LATeah0027L_820.0_0_0.0_2640520_0_1
1/05/2017 7:51:14 PM | Einstein@Home | Finished upload of LATeah0027L_820.0_0_0.0_2640520_0_0
1/05/2017 7:51:14 PM | Einstein@Home | Finished upload of LATeah0027L_820.0_0_0.0_2640520_0_1
1/05/2017 7:58:10 PM | Cosmology@Home | task postponed 86400.000000 sec: VM Hypervisor failed to enter an online state in a timely fashion.
1/05/2017 7:58:10 PM | Cosmology@Home | Starting task camb_boinc2docker_17259_1493631282.087640_0
ID: 21374 · Report as offensive     Reply Quote
mmonnin

Send message
Joined: 29 Dec 16
Posts: 35
Credit: 1,013,434
RAC: 1,094
Message 21377 - Posted: 1 May 2017, 12:05:08 UTC - in response to Message 21374.  

1/05/2017 7:43:29 PM | | Suspending network activity - user request
ID: 21377 · Report as offensive     Reply Quote
Cameron

Send message
Joined: 2 Dec 07
Posts: 7
Credit: 145,565
RAC: 0
Message 21380 - Posted: 1 May 2017, 15:01:39 UTC
Last modified: 1 May 2017, 15:44:23 UTC

It appears to have to do with the version of VirtualBox from what I read in a related thread in Technical Support.
The Thread is here for those interested

My machine is a Windows 10
Running Boinc 7.6.33
and was running Virtual Box 5.0.18

The Technical Support Thread suggested to try a 5.1 version of Virtual Box

Downloaded 5.1.18 from Virtual Box Website (to match the development Boinc 7.7.2 VBox pairing)
Installed and it now appears to be working as expected returning completed tasks.

So Now My machine is a Windows 10
Running Boinc 7.6.33
and running Virtual Box 5.1.18


currently returned a dozen units which includes the postponed 6.
ID: 21380 · Report as offensive     Reply Quote
xii5ku

Send message
Joined: 1 May 17
Posts: 5
Credit: 2,437,391
RAC: 11,742
Message 21645 - Posted: 3 Mar 2018, 22:53:14 UTC
Last modified: 3 Mar 2018, 23:42:32 UTC

I have been running "camb_boinc2docker 2.05 (vbox64_mt)" with good success on host 309722 during the last 19 days. I had about 2 tasks per day which got stuck in state "postponed: VM Hypervisor failed to enter an online state in a timely fashion". I aborted these tasks automatically by means of a script which periodically looks for such tasks and weeds them out.

Unfortunately, since today at 17:00 UTC I got a very high rate of such failures. Here is the list of failing tasks since the beginning of the high failure rate. (225 tasks, and apparently more of such failures to come from what I downloaded already. Sorry for the long post. I would have enclosed the list in SPOILER tags if this board had them. Edit: List removed.) I still have some tasks succeeding, but they seem to be the minority now.

Edit: Solved!

Or worked around at least. Here is what really happened:

I now noticed that the high rate of failures began about at the same time when a second boinc-client instance on the same host began running MindModeling@Home tasks. I cured the problem by shutting down both boinc-client instances, and then restarting only the instance which runs Cosmology@Home.

Apparently vboxwrapper has got some big issue with multiple boinc-client instances on the same host.

(That's a shame. I like using different client instances for running projects in parallel for which I want to control the work buffers independently. E.g. run one project with a shallow queue and another with a deep queue. Or avoid that a project with steady task supply prevents the requesting of tasks from a project with intermittent task supply; like Cosmo vs. MindModeling.)
ID: 21645 · Report as offensive     Reply Quote
xii5ku

Send message
Joined: 1 May 17
Posts: 5
Credit: 2,437,391
RAC: 11,742
Message 21653 - Posted: 7 Mar 2018, 7:37:44 UTC - in response to Message 21645.  
Last modified: 7 Mar 2018, 7:38:15 UTC

The problem between camb_boinc2docker and MindModeling@Home from my previous message turned out unrelated to the use of two boinc client instances. If MindModeling runs in the same client instance as camb_boinc2docker, the latter gets stuck in "postponed: VM Hypervisor failed to enter an online state in a timely fashion" too.
ID: 21653 · Report as offensive     Reply Quote
Jesse Viviano

Send message
Joined: 29 Nov 14
Posts: 33
Credit: 638,350
RAC: 236
Message 21665 - Posted: 18 Mar 2018, 4:15:41 UTC

This error goes away for me when I shut down BOINC and all of the computing apps, and then restart it.
ID: 21665 · Report as offensive     Reply Quote

Forums : Technical Support : postponed VM hypervisor failed to enter and online state in a timely fashion