LHC@home

Whoo, lets see how the 285K is with WUs :)

Set your pref back to unlimited if you want full power to the project now the issues are worked out, as someone said you can do 10 min for CMS til it fails.

Interesting, how do you set BOINC up with DOCKER in windows?

---

Why would CMS fail after 10 minutes? Is that an error on my end or with the project? Any work around?

---

I'm getting computational errors now.

---

Updated VB and added the updated extensions. Now it's processing.

---

Interesting, I get up to about 0.5% and it all restarts. is that normal?

---

You are now running nothing but empty CMS envelopes without any scientific value.
It's not your fault, but you should stop this until the project team has fixed some issues with deeper level scripts.
Watch the CMS message board for further advice.

Okay will do. should I disable SixTrack, sixtracktest & CMS Simulation and just run ATLAS and Theory in the LHC Preferences? or just stop all work completely?

---

What about that link? All of the projects are just crashing. It's all a computational error.
Do I just select ATLAS and Thewory and turn off the others, then restart the LHC@home project on BOINC?

---

2024-11-26 18:45:29 (3112): Guest Log: [ERROR] Could not connect to eoscms-ns-ip563.cern.ch on port 1094
2024-11-26 18:45:30 (3112): Guest Log: [INFO] Testing connection to CMS-Factory
2024-11-26 18:45:30 (3112): Guest Log: [INFO] Testing connection to CMS-Frontier
2024-11-26 18:45:30 (3112): Guest Log: [INFO] Testing connection to Frontier
2024-11-26 18:45:30 (3112): Guest Log: [DEBUG] Check your firewall and your network load

whats this error you showed me?

---

This are Infos from your Task and there is a problem with your Firewall.

Okay, I've disabled my windows firewall.

---

Toby Broom wrote on Nov. 26, 2024:

I think its a bug in windows, I checked the registery and it was still enabled even though the switch for memory intergrity was off.

I edtied the registry now its good.

Set-ItemProperty HKLM:\SYSTEM\CurrentControlSet\Control\DeviceGuard\ -Name EnableVirtualizationBasedSecurity -Value 0

thanks, Toby, for this hint.
I checked the registry; and indeed: although I had switched off the memory integrity under "core isolation", the entry in the registry was "1" instead of "0" - so obviously a bug in Windows 11.
I put the value to "0". and when opening again "core isolation", there now is the yellow triangle with the warning that the memory integrity is not on. This warning did NOT show up before. So no it's definitely off.

However, virtualization is still NOT working on my AMD Ryzen 7 7735HS :-( No idea what else I could do.
Anyone any information on further bugs in Windows 11 which prevent virtualization from running?

However, virtualization is still NOT working on my AMD Ryzen 7 7735HS :-( No idea what else I could do.
Anyone any information on further bugs in Windows 11 which prevent virtualization from running?

problem solved !

There was a very valuable hint in this posting from computezrmle:

https://lhcathome.cern.ch/lhcathome/forum_thread.php?id=6276&postid=51409#51409

so I made the suggested change in the registry, and now virtualization works fine!