Posts by Bradders

1) Questions and Answers : Windows : Dual CPU Xeon Windows 10 - configuration for LHC? (Message 43054) Posted 13 Jul 2020 by Bradders Post: Thanks everyone. It's going to take me a while to work through all of your comments and suggestions. I did reduce LHC to 1 job but left it at 8 CPUs. My internet connection is 50mbps fibre to the premises, but that is shared with several other computers and smart TVs. The Theory Simulation started and did a some processing (13m 49s), but then it stopped with the same 'probing' error is before. VB also says that the display virtual memory needs to be 9MB and the controller should be VMSVGA. (I just updated both.) I haven't looked at VB network or Windows firewall except to add the BOINC data directory to exclusions in Windows Defender. Here's the BOINC Properties of my last Theory run: Application Theory Simulation 300.06 (vbox64_theory) Name Theory_2390-1093844-26 State Running Received 14/07/2020 4:09:12 Report deadline 24/07/2020 4:09:15 Estimated computation size 3,600 GFLOPs CPU time 00:13:49 CPU time since checkpoint 00:00:01 Elapsed time 05:14:03 Estimated time remaining 9d 19:43:09 Fraction done 2.172% Virtual memory size 77.99 MB Working set size 667.57 MB Directory slots/0 Process ID 2792 Progress rate 0.360% per hour Executable vboxwrapper_26198ab7_windows_x86_64.exe I'll let you know how I get on.
2) Questions and Answers : Windows : Dual CPU Xeon Windows 10 - configuration for LHC? (Message 42994) Posted 10 Jul 2020 by Bradders Post: And another 8 WUs have just started, and all have the same 'probing functions' errors. I'll disable LHC until I can get it configured.[/img]
3) Questions and Answers : Windows : Dual CPU Xeon Windows 10 - configuration for LHC? (Message 42982) Posted 9 Jul 2020 by Bradders Post: Sadly, there were all in that 'probing failed' state. I shut them all down and updated BOINC to clear them out. My Account shows run time and CPU times. Example: Run Time 474,926.15 CPU Time 10,107.56 I'll keep working through the configuration list, and I'll post here if/when I get another LHC job. Thanks for your guidance.
4) Questions and Answers : Windows : Dual CPU Xeon Windows 10 - configuration for LHC? (Message 42979) Posted 8 Jul 2020 by Bradders Post: Sample log output from one of the WU. (The other 7 WU don't have the last two lines in their VBox.log.n logs, but otherwise look similar.): VBox.log 00:00:48.722666 Display::i_handleDisplayResize: uScreenId=0 pvVRAM=0000000007d10000 w=800 h=600 bpp=32 cbLine=0xC80 flags=0x1 origin=0,0 00:00:48.723117 Changing the VM state from 'LOADING' to 'SUSPENDED' 00:00:48.723224 Changing the VM state from 'SUSPENDED' to 'RESUMING' 00:00:48.723471 NAT: Link down 00:00:48.723504 Changing the VM state from 'RESUMING' to 'RUNNING' 00:00:48.723583 Console: Machine state changed to 'Running' 00:00:51.905008 NAT: Link up 00:00:51.910992 NAT: DNS#0: 192.168.178.1 00:00:53.514000 NAT: IPv6 not supported 03:39:25.016189 NAT: DHCP offered IP address 10.0.2.15 13:33:26.537610 NAT: DHCP offered IP address 10.0.2.15 23:41:27.358912 NAT: DHCP offered IP address 10.0.2.15 34:04:21.029286 NAT: DHCP offered IP address 10.0.2.15 43:18:55.491941 NAT: DHCP offered IP address 10.0.2.15 VBoxHardening.log 1ca4.1448: supR3HardenedWinVerifyCacheScheduleImports: Import todo: #21 'ws2_32.dll'. 1ca4.1448: supR3HardenedWinVerifyCacheScheduleImports: Import todo: #23 'nsi.dll'. 1ca4.1448: supHardenedWinVerifyImageByHandle: -> 0 (\Device\HarddiskVolume2\Windows\System32\dnsapi.dll) 1ca4.1448: supR3HardenedWinVerifyCacheInsert: \Device\HarddiskVolume2\Windows\System32\dnsapi.dll 1ca4.1448: supR3HardenedDllNotificationCallback: load 00007ffab5500000 LB 0x000cb000 C:\Windows\SYSTEM32\DNSAPI.dll [fFlags=0x0] 1ca4.1448: supR3HardenedScreenImage/LdrLoadDll: cache hit (VINF_SUCCESS) on \Device\HarddiskVolume2\Windows\System32\dnsapi.dll [avoiding WinVerifyTrust] 1ca4.295c: '\Device\HarddiskVolume2\Windows\System32\tzres.dll' has no imports 1ca4.295c: supHardenedWinVerifyImageByHandle: -> 22900 (\Device\HarddiskVolume2\Windows\System32\tzres.dll) 1ca4.295c: supR3HardenedWinVerifyCacheInsert: \Device\HarddiskVolume2\Windows\System32\tzres.dll 1ca4.295c: supR3HardenedMonitor_NtCreateSection: NtMapViewOfSection failed on 0000000000000ddc (hFile=0000000000000dfc) with 0xc0000022 -> STATUS_TRUST_FAILURE 1ca4.295c: supR3HardenedScreenImage/NtCreateSection: cache hit (Unknown Status 22900 (0x5974)) on \Device\HarddiskVolume2\Windows\System32\tzres.dll [avoiding WinVerifyTrust] 1ca4.295c: supR3HardenedMonitor_NtCreateSection: NtMapViewOfSection failed on 0000000000000dfc (hFile=0000000000000ddc) with 0xc0000022 -> STATUS_TRUST_FAILURE VBox.log.1 00:02:56.742450 GIM: KVM: Resetting MSRs 00:02:56.743897 Changing the VM state from 'DESTROYING' to 'TERMINATED' 00:02:56.746486 Console: Machine state changed to 'Saved' 00:02:57.548213 GUI: Passing request to close Runtime UI from machine-logic to UI session. 00:02:57.548373 GUI: UIMediumEnumerator: Medium-enumeration finished! VBox.log.2 00:04:56.067672 GIM: KVM: Resetting MSRs 00:04:56.069116 Changing the VM state from 'DESTROYING' to 'TERMINATED' 00:04:56.071432 Console: Machine state changed to 'Saved' 00:04:56.967180 GUI: Passing request to close Runtime UI from machine-logic to UI session. 00:04:56.967888 GUI: UIMediumEnumerator: Medium-enumeration finished! VBox.log.3 00:23:28.762098 GIM: KVM: Resetting MSRs 00:23:28.763427 Changing the VM state from 'DESTROYING' to 'TERMINATED' 00:23:28.765871 Console: Machine state changed to 'Saved' 00:23:29.832781 GUI: Passing request to close Runtime UI from machine-logic to UI session. 00:23:29.842720 GUI: UIMediumEnumerator: Medium-enumeration finished!
5) Questions and Answers : Windows : Dual CPU Xeon Windows 10 - configuration for LHC? (Message 42978) Posted 8 Jul 2020 by Bradders Post: I opened VB and looked at the logs. I have no idea what to look for. Task Manager was at 100% across the 8 cores. BOINC showed 8 WUs ticking along. (The expected time was 11 days.) I had to restart that PC, so I suspended BOINC first and waited until the VB jobs to 'suspend' (I can't remember the exact term.) After restart, the VB Manager says that the 8 WU are running, but there is not much CPU action; just a blip across all 8 cores every 20s or so. Task Manager shows BOINC tasks (12), VB Manager and about 20 VB Headless Frontend tasks, but not a lot of action. Did I kill the delicate flowers?
6) Questions and Answers : Windows : Dual CPU Xeon Windows 10 - configuration for LHC? (Message 42949) Posted 3 Jul 2020 by Bradders Post: I now have 8 Theory jobs running in parallel. They have run for about 1 day and have about 9 days left to run. (I've just marked other projects as "no new work", which might speed things up a bit.) Memory used is 16 GB of 32 GB. So far so good.
7) Questions and Answers : Windows : Dual CPU Xeon Windows 10 - configuration for LHC? (Message 42944) Posted 1 Jul 2020 by Bradders Post: Thanks Since those failed jobs I've installed VB 6.1.10 (latest version) and I just installed its extension pack. Awaiting a job from LHC...
8) Questions and Answers : Windows : Dual CPU Xeon Windows 10 - configuration for LHC? (Message 42932) Posted 1 Jul 2020 by Bradders Post: I previously had issues running large WU in part because 8 CPUs (2 physical x 4 cores) need more than 8GB to share. https://lhcathome.cern.ch/lhcathome/forum_thread.php?id=4281#30435 At the time I followed the Checklist 3 from Yeti, but only went so far before the lack of RAM became the limit, so I disconnected from LHC. https://lhcathome.cern.ch/lhcathome/forum_thread.php?id=4161#29359 Since then (2017) I have rebuilt on a clean install of Windows 10 Pro and I now have 32GB. But just then, the PC just spat out a bunch of Theory Simulation v300.06 (vbox64_theory) windows_x86_64 WUs after only 7.8s. Note: It does seem that everyone who has tried one of those WU has finished with an error. I'll work through the rest of checklist 3 to see if I can get it working again. Is there a more recent checklist to configure a Windows PC for LHC?
9) Message boards : ATLAS application : Status: Waiting for memory (5 CPUs) - finished but won't upload (Message 30485) Posted 24 May 2017 by Bradders Post: This is the checklist from Yeti: https://lhcathome.cern.ch/lhcathome/forum_thread.php?id=4161#29359 Thanks Here is what I found going through the checklist: 4. Virtualbox is 5.1.12, which is behind the 5.1.16 recommendation. 5.1.22 downloaded. 6. I have 8 cores and 8GB of memory. I changed my settings to use a maximum of 2 CPUs, aborted the 5CPU WU and updated BOINC. 14. Yeah, there is a big difference between 12d and 4h! I have kept ATLAS on the list of WU, but I won't be running a 5CPU job unless I double the RAM. Thanks again everyone.
10) Message boards : ATLAS application : Status: Waiting for memory (5 CPUs) - finished but won't upload (Message 30440) Posted 20 May 2017 by Bradders Post: I have a new 5 CPU WU. It estimates about 3 hours, not 12 days! I should leave the PC unattended for 2 weeks!
11) Message boards : ATLAS application : Status: Waiting for memory (5 CPUs) - finished but won't upload (Message 30439) Posted 20 May 2017 by Bradders Post: I have run an ALTAS Simulation 1.01 (vbox64_mt_mcore_atlas) WU on my dual Xeon CPU quad core PC. E5345 @ 2.33GHz with 8GB RAM. The WU progress is 100%, Elapsed time is 12d 19:36:09 and Remaining time reads --- and the deadline is 20/05/2017 2:49:25. However, the WU won't upload. The Status reads "Waiting for memory (5 CPUs)". Any ideas how to make it upload? A 5-core WU requests 6.6 GB RAM. This is >80% on your 8 GB host. You may check if your BOINC client is allowed to use more than 80 % RAM. The error will reoccur if your client runs WUs (or keeps paused WUs in RAM) with a total RAM requirement that exceeds your preferences. I changed the memory limit to 85%. Sadly, it looks like the job aborted.
12) Message boards : ATLAS application : Status: Waiting for memory (5 CPUs) - finished but won't upload (Message 30438) Posted 20 May 2017 by Bradders Post: in Boinc-manager under Transfers - retry now for this task. Otherwise save Boinc-manager and wait until Virtualbox have saved the boinc-task. Then restart Boinc-manager again. I should have explained that it was not in the Transfers list. I closed BOINC, opened VBox Manager v5.1.12 and re-opened BOINC. The WU now has status Running (5 CPUs). The elapsed time is running, but the WU is still at 100.000%
13) Message boards : ATLAS application : Status: Waiting for memory (5 CPUs) - finished but won't upload (Message 30435) Posted 20 May 2017 by Bradders Post: I have run an ALTAS Simulation 1.01 (vbox64_mt_mcore_atlas) WU on my dual Xeon CPU quad core PC. E5345 @ 2.33GHz with 8GB RAM. The WU progress is 100%, Elapsed time is 12d 19:36:09 and Remaining time reads --- and the deadline is 20/05/2017 2:49:25. However, the WU won't upload. The Status reads "Waiting for memory (5 CPUs)". Any ideas how to make it upload?

LHC@home