Issues with Boinc and VirtualBox

Message boards : Questions and problems : Issues with Boinc and VirtualBox
Message board moderation

To post messages, you must log in.

AuthorMessage
Profile sam6321

Send message
Joined: 29 Mar 17
Posts: 4
Australia
Message 76998 - Posted: 29 Mar 2017, 1:57:12 UTC

Hi Everyone,

Over on the Sourcefinder project, we've been having various issues with VirtualBox.
I've compiled a list of the most reported / problematic issues, and I hope someone on here can either provide me with solutions to said issues, or point me to where I can find solutions :).

Here's a list of the issues:
Vboxwrapper lost communicaion with VirtualBox, rescheduling task for a later time.
The task had technically completed, but according to the logs and the user, virtualbox fully re-started the work unit.
Reported: http://54.196.169.236/duchamp/forum_thread.php?id=168

Error 194 (0xC2).
Work units end computation with that error code whenever the computer is restarted without first closing Boinc and waiting for VirtualBox to suspend the application.
This may be un-avoidable, I’m not 100% sure.
Reported: http://54.196.169.236/duchamp/forum_thread.php?id=36
Stderr: http://54.196.169.236/duchamp/result.php?resultid=13106

Some work units don’t seem to actually do anything.
Looking at the stderr output from some work units, the actual client application simply doesn’t start.
This example result had almost no CPU time, despite running for several hours: http://54.196.169.236/duchamp/result.php?resultid=6504
Another user reported work units that appear to continue forever without progressing:
http://54.196.169.236/duchamp/forum_thread.php?id=28

Suspended work units wont re-start.
One user reported that if they paused work units, they would never resume.
Reported: http://54.196.169.236/duchamp/forum_thread.php?id=17
ID: 76998 · Report as offensive
Profile Jord
Volunteer tester
Help desk expert
Avatar

Send message
Joined: 29 Aug 05
Posts: 15477
Netherlands
Message 77001 - Posted: 29 Mar 2017, 7:12:36 UTC - in response to Message 76998.  

Hi Sam,

I have forwarded this to the BOINC developers, but so that they can easier answer you or ask more information, and for all of the present (volunteer) BOINC/wrapper developers/users to see this, I ask you that you repost this on the BOINC development email list: https://lists.ssl.berkeley.edu/mailman/listinfo/boinc_dev (the list requires registration to post on it).
ID: 77001 · Report as offensive
Profile sam6321

Send message
Joined: 29 Mar 17
Posts: 4
Australia
Message 77053 - Posted: 30 Mar 2017, 23:55:07 UTC - in response to Message 77001.  

Thanks Ageless, I posted the list of issues to the boinc_dev mailing list.
ID: 77053 · Report as offensive
Jim1348

Send message
Joined: 8 Nov 10
Posts: 310
United States
Message 77079 - Posted: 31 Mar 2017, 14:31:39 UTC - in response to Message 76998.  

Error 194 (0xC2).
Work units end computation with that error code whenever the computer is restarted without first closing Boinc and waiting for VirtualBox to suspend the application.
This may be un-avoidable, I’m not 100% sure.
Reported: http://54.196.169.236/duchamp/forum_thread.php?id=36
Stderr: http://54.196.169.236/duchamp/result.php?resultid=13106

I had that when running Cosmology and ATLAS (and the other CERN projects). The newer versions of VirtualBox (5.1.16 and 5.1.18) solved it for me with Cosmology and Windows 7, but I have not tried it with the CERN projects yet, which may be harder to close as they are said to require frequent contact with the servers.
ID: 77079 · Report as offensive

Message boards : Questions and problems : Issues with Boinc and VirtualBox

Copyright © 2024 University of California.
Permission is granted to copy, distribute and/or modify this document under the terms of the GNU Free Documentation License, Version 1.2 or any later version published by the Free Software Foundation.