1)
Message boards :
ATLAS application :
ATLAS vbox v2.02
(Message 47170)
Posted 24 Aug 2022 by EeqMC252 Post: Thank you I'm seeing the same issue. |
2)
Questions and Answers :
Getting started :
CPU does not have hardware virtualization support?
(Message 46480)
Posted 19 Mar 2022 by EeqMC252 Post: LeoMoon reports that Hardware Virtualization is supported, and is ENABLED. But the BOINC tasks all show "Virualization Virtualbox (6.1.12) installed, CPU does not have hardware virtualization support" Can anyone explain this. Thanks [/img] |
3)
Message boards :
Number crunching :
VM Applications Errors
(Message 46444)
Posted 16 Mar 2022 by EeqMC252 Post: What version of VirtualBox should be run with LHC@Home? The BOINC kit indicates 6.1.12, but when you install the software, 6.0.14 is actually installed. It doesn't work, I manually upgraded to 6.1.12 and it doesn't work, I've tried 6.1.22, which I think has worked in the distant past and it doesn't work, and I've tried 6.1.32 and it doesn't work either. Extension packs installed for each. I've gone through the Yeti Check List multiple times and cannot find any obvious configuration mistakes that would prevent CMS, ATLAS and Theory Simulation tasks from downloading. Are these now GPU only tasks? I just keep getting message that no tasks are available. Yet, a week ago I downloaded 40 CMS tasks that all failed because my AMD based virtualization setting in BIOS was not enabled. This was corrected but can't get CMS to download since. Is there a trick to get LHC and BOINC to recognize VirtualBox or vise-versa? I'm showing no evidence that any tasks have arrived or run in VB. (BOINC 7.16.20(x64), 6.1.12 r139181(Qt5.6.2),Win10, AMD processor 32 threads, 64Gb Ram, plenty of disk space) |
4)
Message boards :
News :
Aborted Work Units
(Message 31613)
Posted 25 Jul 2017 by EeqMC252 Post: I had the same problems, it would come and go but eventually became very severe affecting 100% of the LHC tasks. I resolved my issues by modifying the "Disk and memory" settings under "Computing preferences" in BOINC. I increased the "Use no more than x GB" value and decreased the "Leave at least x GB free" value. My computer has worked perfectly since allowing additional resources for BONIC projects. |
5)
Message boards :
Cafe LHC :
Whatever happened to LHC@home....apologies and thanks.
(Message 22523)
Posted 7 Sep 2010 by EeqMC252 Post: FEED ME!!!!!! |
6)
Message boards :
Number crunching :
LHC still requires Boinc 4.45?
(Message 12336)
Posted 23 Jan 2006 by EeqMC252 Post: If you want to know a project that has problems, rosetta@home is TERRIBLE! They should have stayed alpha for a much longer time. Signup for Einstein@home - it's almost 100% error free and never runs out of work. Your CPU cycles will be put to good use there!!! |
7)
Message boards :
Number crunching :
LHC still requires Boinc 4.45?
(Message 12305)
Posted 23 Jan 2006 by EeqMC252 Post:
I upgraded to 5.2.13 and still have loads of Ghost Work Units. Any suggestions on how to get these little bastards under control? |
8)
Message boards :
Number crunching :
Stats Page
(Message 12115)
Posted 17 Jan 2006 by EeqMC252 Post: Is there any chance the stats pages could be sorted in reverse chronological order? The test number mean nothing to me, but having the latest issued work units at the top of the list just seems to make more sense. Thanks. |
9)
Message boards :
Cafe LHC :
LHC@home needs more publicity
(Message 12113)
Posted 17 Jan 2006 by EeqMC252 Post: I feel greater efforts are needed to make students & teachers around the world aware of LHC@home. It still has very few members compared to SETI@home. I am pretty much sure that many more would like to join this project once they become aware of it. What do you say ? LHC@Home needs more work units first !! |
10)
Message boards :
Number crunching :
LHC still requires Boinc 4.45?
(Message 12112)
Posted 17 Jan 2006 by EeqMC252 Post:
I am using 5.2.7 and having a terrible time with Ghost Work Units from download errors. Einstein@home is perfect - someone needs to take some leasons from those folks! |
11)
Message boards :
Number crunching :
Attention LHC Developers!
(Message 11354)
Posted 14 Nov 2005 by EeqMC252 Post: Bionics works great with Einstein@Home - LHC@home and Rosetta@home and Seti@home and Predictor@home all need to talk to the Einstein developers or managers and find out what they are doing so well. I've virtually had zero problems from Einstein@home since day one. The rest of the Bionic locations need to take a lesson from these guys/gals! Ghost Work Units - Massive numbers of Ghost Work Units!!!! |
12)
Message boards :
Number crunching :
Attention LHC Developers!
(Message 11335)
Posted 12 Nov 2005 by EeqMC252 Post: Bionics works great with Einstein@Home - LHC@home and Rosetta@home and Seti@home and Predictor@home all need to talk to the Einstein developers or managers and find out what they are doing so well. I've virtually had zero problems from Einstein@home since day one. The rest of the Bionic locations need to take a lesson from these guys/gals! |
13)
Message boards :
Number crunching :
Error - Return value of 500
(Message 11195)
Posted 4 Nov 2005 by EeqMC252 Post: It looks like the job scheduler at LHC didn't answer your machine when it tried to contact it. This may not be an issue - the scheduler may simply have been busy. Your PC will try again after a while. My problem is that I've got dozens of ghost work units on my list at LHC@home but none of them are actually on my PC's Bonics list. This is the first time I've seen this magnitude of ghost WUs on LHC. I just upgraded to the lastest Bonics software and wonder if this might be the reason. Historically, I've seen this type of problems with SETI and PREDICTOR but have never had any significant problems on LHC or EINSTEIN in the past. |
14)
Message boards :
Number crunching :
Error - Return value of 500
(Message 11192)
Posted 4 Nov 2005 by EeqMC252 Post: Can anyone tell me what this message means? 11/4/2005 1:16:21 AM|LHC@home|Scheduler request to http://lhcathome-sched1.cern.ch/scheduler/cgi failed with a return value of 500 11/4/2005 1:16:21 AM|LHC@home|No schedulers responded |
©2023 CERN