|
1)
Message boards :
Questions and problems :
Postphoned: VM Hypervisor failed to enter an online state in a timely fashion
(Message 66824)
Posted 13 Jan 2016 by Rob Lilley Post: There is a discussion on the Cosmology@home message boards: http://www.cosmologyathome.org/forum_thread.php?id=7332 The suggestion seems to be that it's to do with the version of VirtualBox. My experience is that BOINC 7.622 with virtualbox 5.0.10 caused every work unit to fail on my Windows 10 machine, but so far it seems to be working since I went back to BOIMC 7.6.9 and virtualbox 4.3.12 - however, it might purely be the version of virtualbox. |
|
2)
Message boards :
BOINC client :
Unrecognized tag in cc_config.xml
(Message 44707)
Posted 3 Jul 2012 by Rob Lilley Post: Yes, it I think that the notice may have started appearing after I added exclusive apps on version 7.25 , where before I wasn't using Computing Preferences. In any case, the notice hasn't appeared again since I added another exclusive app using version 7.28, so thanks for the suggestion. |
|
3)
Message boards :
BOINC client :
Unrecognized tag in cc_config.xml
(Message 44685)
Posted 1 Jul 2012 by Rob Lilley Post: I upgraded from Boinc Version 7.25 to 7.27 on one of my machines because of a bug in 7.25 that caused some Milkyway work units to run in high priority mode as soon as they were downloaded. Version 7.27 corrected this problem, but always came up with the notice "Unrecognized tag in cc_config.xml: <zero_debts>" on startup. I have since upgraded from Boinc Version 7.25 to 7.28 on my other machine, and the new version on this machine comes up with the same notice on startup. In neither machine did this notice appear on Boinc versions 7.25 and earlier. AFAIK this is no more than a small annoyance, but I don't know if this has caused problems for anyone else. The first machine is an AuthenticAMD AMD Turion(tm) II Dual-Core Mobile M520 [Family 16 Model 6 Stepping 2] (2 processors) laptop running 64 bit Windows 7 Home Premium SP1, and the second is an AuthenticAMD AMD Athlon(tm) II X3 450 Processor [Family 16 Model 5 Stepping 3] (3 processors) desktop running 64 bit Windows 7 Professional SP1 |
|
4)
Message boards :
News :
BOINC 6.12.33 released to public
(Message 39310)
Posted 27 Jul 2011 by Rob Lilley Post: The screen saver diagnostics error was identified by the developers and is fixed in an upcoming 6.12 version. Fair enough! |
|
5)
Message boards :
News :
BOINC 6.12.33 released to public
(Message 39303)
Posted 27 Jul 2011 by Rob Lilley Post: I sometimes get this error message after my machine has started up, although I am not using the BOINC screensaver (or any other screensaver for that matter). I am running BOINC version 6.12.33 on Windows XP SP3, and BOINC is installed so as to be usable by all users, although I only have one user account on this mashine. I have uninstalled BOINC, restarted the machine and re-installed it again to no apparent effect, although I did notice that it had the option to use the BOINC screensaver ticked by default as I was re-installing it, and so I un-ticked it. (The last time I used the BOINC Screensaver was probably at least 7 years and 2 machines ago!) As this problem seems so far only to be happening when QMC is the project that starts up first, I am also posting this on the QMC forums, although I have not experienced it on previous BOINC versions. |
|
6)
Message boards :
Questions and problems :
Should BOINC still request jobs when a project is project is in "high priority" mode?
(Message 38619)
Posted 21 Jun 2011 by Rob Lilley Post: A Cosmology WU was running in "high priority" mode, and then Boinc switched to QMC, still running "high priority". At the same time, it requested a Rosetta WU, which after downloading started in (you guessed it) "high priority" mode. Am I misunderstanding something, or should Boinc not allow work fetch from any project when another project is in danger of missing its deadline, or is it just Rosetta that's not playing nice? My machine is a Celeron 2.53MhZ running on Windows XP SP3 Boinc version is 6.12.26 |
|
7)
Message boards :
Questions and problems :
local host disconnect
(Message 27991)
Posted 14 Oct 2009 by Rob Lilley Post: I had the same problem, and I'm not connected to Sztaki or Lattice Project, although I was having problems with a parameter file download for Cosmology. The problem was solved by installing 6.4.7 as well, but then my QMC WU kept exiting with zero status but no finished file. I then went back to 6.6.38 and that seems to be working now. Seems as though reverting to an earlier version of BOINC Manager allows the problem to clear, and once that's done then it's possible to go back to the latest version again. |
|
8)
Message boards :
BOINC client :
BOINC 6.10.0 posted
(Message 26698)
Posted 20 Aug 2009 by Rob Lilley Post: Test on a computer with a CUDA card, but the CPU project stay in "waiting to run", and the GPU is running. Please note that you should not post details of suspected bugs in alpha clients to the BOINC message boards. You need to use the alpha email list, as per this post. |
|
9)
Message boards :
BOINC Manager :
High Priority projects
(Message 13087)
Posted 15 Oct 2007 by Rob Lilley Post: I have also noticed that Einstein@home has extremely large time requirements. This has a tendency to block other projects from downloading work units to run, so it takes a high priority status by being the only project on the system. There should be some way to control maximum work unit time size and work unit priority. QMC is even worse! On the machine I run it on (a 2.53 ghz Celeron), it comes up with estimates of up to 120 hrs, as against up to about 60 for Einstein, but the deadlines for QMC units don't vary with estimated crunching time. QMC then actually takes less than half of the estimated time, which, together with the tight deadlines, rather cleverly ensures that each work unit runs high priority from day 1, and means that the machine has to crunch for at least 3 hours per day before it is allowed to switch to any other project. However, any project with long crunching times will have built up a large negative long term debt by the time the work unit is finished, meaning that your machine will crunch for other projects in between large indigestible chunks of work. The only problem may be if QMC or Einstein gives you a large work unit while you still have short work units in progress for other projects. What I do then is keep my machine switched on for long enough each day to do the required number of hours per day of crunching. Serves me right for running so many projects on one machine I guess... |
|
10)
Message boards :
BOINC Manager :
Client Downloads to many Wu's
(Message 12054)
Posted 13 Aug 2007 by Rob Lilley Post: I tried your 1000 to 1 Resource Share & the Project with the 1 Downloaded 12 hours of work by my estimates, so much for Resource Share ... It may take a while for changes in Resource Share to have an effect on the amount of work each project fetches, as I think it affects how quickly Long Term Debt accumulates for each project. The Long Term Debt then determines which projects request work, and how much they request - that's my understanding of it anyway. In any case as your background project has recently requested a large amount of work, it should have accumulated a fairly large negative Long Term Debt, which means that it should not request more work until quite a while after your machine has finished crunching work for that project. In the meantime, there's probably not much you can do except maybe temporarily set the background project to "no new tasks" and perhaps abort some of the unwanted work units. Anyone else got any ideas, as I'm not an expert, so I may be talking out of my posterior...? |
|
11)
Message boards :
BOINC Manager :
Client Downloads to many Wu's
(Message 12051)
Posted 13 Aug 2007 by Rob Lilley Post: I usually only have 1 Project running on my PC's & set the Resource Share to a high # like 30000 or even higher I thought if you set resource share to anything over 1000, BOINC reduced it to 1000. I know BAM does this, but I'm not sure if this is enforced either by BOINC or by the projects. In theory this should give your secondary project a minimum possible resource share of 0.1%. However, this assumes that using out-of-range values doesn't cause BOINC to behave unpredictably, and that resource share actually does still work :-/ I have Xtremlab set up as a backup project, but the estimated crunching times are so far off for that project these days that I can't tell whether it works for me or not :-S |
|
12)
Message boards :
BOINC Manager :
BOINC Manager window position & size doesn't "stick"
(Message 11806)
Posted 27 Jul 2007 by Rob Lilley Post: This has been a continuing problem with BOINC (and many windows programs). Using file->exit will sometimes save the settings but is not reliable. That works for me as long as I don't reboot the computer - a lot to ask for a Windows XP box! I have desktop machine and a laptop, neither of which ever preserves window width of BOINC Manager after a reboot, even after a file/ exit. |
|
13)
Message boards :
BOINC client :
BOINC 5.10 has now been released to public.
(Message 11442)
Posted 2 Jul 2007 by Rob Lilley Post: Usually if you exit the manager via file->exit the settings will be remembered but not always. Works for me on both my Windows XP machines unless I power the machine down :-) |
|
14)
Message boards :
BOINC client :
BOINC 5.10 has now been released to public.
(Message 11330)
Posted 27 Jun 2007 by Rob Lilley Post: Also 5.10.7 (which was an official build up to recently) does not preserve width of window if you open BOINC Manager after a reboot in Windows XP SP2 - 5.8.16 does not have this problem. To explain further - in advanced view, I normally set the width of the BOINC Manager window to be wide enough to see all columns. However, 5.10.7 resets the window width to something approximating the width of the Simple View. It then retains the dimensions I have set for the window as long as the machine is on, but reverts to the annoying narrow window after I restart the machine. I am reporting this here on the grounds that 5.10.7 was briefly in the wild, even though it has now been put back in the alpha cage! |
|
15)
Message boards :
BOINC Manager :
Testing 5.10.x versions of BOINC
(Message 10621)
Posted 2 Jun 2007 by Rob Lilley Post: Just couple of small problems with 5.10.0 version - It doesn't remember any alterations to column widths when you restart it, which means that you can't see the Status column if you don't have the window maximised. - On "snooze" it just went ahead and finished an Xtremlab unit I was crunching at the time (could be an Xtremlab problem, but I haven't noticed it on previous versions of BOINC Manager) Still, in view of the benchnarking problems, I'll go back to the previous version anyway... |
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.