LHC@home

well, it seems that Sixtrack is no longer alive :-(

What are you waiting on to be restarted?

Hence, you may need to completely remove VirtualBox before you install it again (most recent version is recommended).

It's an error of the lhc site.

No.

Hence, you may need to completely remove VirtualBox before you install it again (most recent version is recommended).

After removal and before a fresh installation you should also remove the directory "C:\Users\<your_user_name>\.VirtualBox\" to allow VirtualBox to create a fresh profile.

AMD Ryzen 5 5500U with Radeon Graphics [Family 23 Model 104 Stepping 1]
Virtualisierung Virtualbox (7.1.4) installiert, Prozessor besitzt keine hardwareseitige Unterstützung für Virtualisierung
Your second PC have AMD-V disabled.

Your second PC have AMD-V disabled.

<message>
Function not correct
(0x1) - exit code 1 (0x1)</message>
<stderr_txt>
2025-02-09 16:59:16 (4928): Detected: vboxwrapper 26206
2025-02-09 16:59:16 (4928): Detected: BOINC client v8.0.2
2025-02-09 16:59:19 (4928): Detected: VirtualBox VboxManage Interface (Version: 6.1.50)
.....
Command:
VBoxManage -q startvm "boinc_07632fdb59dcd957" --type headless
Output:
Waiting for VM "boinc_07632fdb59dcd957" to power on...
VBoxManage.exe: error: The virtual machine 'boinc_07632fdb59dcd957' has terminated unexpectedly during startup with exit code 1 (0x1). More details may be available in 'C:\ProgramData\BOINC\slots\0\boinc_07632fdb59dcd957\Logs\VBoxHardening.log'
VBoxManage.exe: error: Details: code E_FAIL (0x80004005), component MachineWrap, interface IMachine

2025-02-09 16:59:32 (4928): VM failed to start.
2025-02-09 16:59:32 (4928): Could not start
2025-02-09 16:59:32 (4928): ERROR: VM failed to start
2025-02-09 16:59:32 (4928): Powering off VM.

Hypervisor System Log:

00:00:09.511207 Saving settings file "C:\ProgramData\BOINC\slots\0\boinc_07632fdb59dcd957\boinc_07632fdb59dcd957.vbox" with version "1.16-windows"
00:00:10.050092 ERROR [COM]: aRC=VBOX_E_OBJECT_NOT_FOUND (0x80bb0001) aIID={85632c68-b5bb-4316-a900-5eb28d3413df} aComponent={SessionMachine} aText={No storage device attached to device slot 0 on port 0 of controller 'Hard Disk Controller'}, preserve=false aResultDetail=0
00:00:10.050517 ERROR [COM]: aRC=VBOX_E_OBJECT_NOT_FOUND (0x80bb0001) aIID={85632c68-b5bb-4316-a900-5eb28d3413df} aComponent={SessionMachine} aText={No storage device attached to device slot 0 on port 0 of controller 'Hard Disk Controller'}, preserve=false aResultDetail=0
00:00:10.050706 Saving settings file "C:\Users\Stefano\.VirtualBox\VirtualBox.xml" with version "1.12-windows"
00:00:10.056155 Saving settings file "C:\ProgramData\BOINC\slots\0\boinc_07632fdb59dcd957\boinc_07632fdb59dcd957.vbox" with version "1.16-windows"
00:00:10.320995 Saving settings file "C:\ProgramData\BOINC\slots\0\boinc_07632fdb59dcd957\boinc_07632fdb59dcd957.vbox" with version "1.16-windows"
00:00:10.592491 ERROR [COM]: aRC=VBOX_E_OBJECT_NOT_FOUND (0x80bb0001) aIID={85632c68-b5bb-4316-a900-5eb28d3413df} aComponent={SessionMachine} aText={No storage device attached to device slot 0 on port 0 of controller 'Hard Disk Controller'}, preserve=false aResultDetail=0
00:00:10.593014 Saving settings file "C:\ProgramData\BOINC\slots\0\boinc_07632fdb59dcd957\boinc_07632fdb59dcd957.vbox" with version "1.16-windows"
00:00:10.797865 ERROR [COM]: aRC=VBOX_E_OBJECT_NOT_FOUND (0x80bb0001) aIID={85632c68-b5bb-4316-a900-5eb28d3413df} aComponent={SessionMachine} aText={No storage device attached to device slot 0 on port 0 of controller 'Hard Disk Controller'}, preserve=false aResultDetail=0
00:00:10.869903 Saving settings file "C:\ProgramData\BOINC\slots\0\boinc_07632fdb59dcd957\boinc_07632fdb59dcd957.vbox" with version "1.16-windows"
00:00:11.021825 Saving settings file "C:\ProgramData\BOINC\slots\0\boinc_07632fdb59dcd957\boinc_07632fdb59dcd957.vbox" with version "1.16-windows"
00:00:11.369586 ERROR [COM]: aRC=VBOX_E_OBJECT_NOT_FOUND (0x80bb0001) aIID={85632c68-b5bb-4316-a900-5eb28d3413df} aComponent={SessionMachine} aText={No storage device attached to device slot 0 on port 1 of controller 'Hard Disk Controller'}, preserve=false aResultDetail=0
00:00:11.370892 ERROR [COM]: aRC=VBOX_E_OBJECT_NOT_FOUND (0x80bb0001) aIID={85632c68-b5bb-4316-a900-5eb28d3413df} aComponent={SessionMachine} aText={No storage device attached to device slot 0 on port 1 of controller 'Hard Disk Controller'}, preserve=false aResultDetail=0
00:00:11.371028 Saving settings file "C:\Users\Stefano\.VirtualBox\VirtualBox.xml" with version "1.12-windows"

Have Virtualbox 7.0.22 from Boinc-Website with Extensionpack 7.0.22.
Atlas is running for me in Win11pro.
vboxwrapper is difficult, because of Theory, CMS AND Atlas in Windows.

Registry key "Computer\HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\DeviceGuard\Scenarios\WindowsHello\Enable"? Does not exist

If the key does not exist, create it and set it's value to "0"?

In addition ensure "Run native if available? (Not recommended for Windows)" at the prefs page is not checked for the venue your Windows computers are attached to.

Do you have newest BIOS update and Chipset driver installed?

I have some running at -dev but that site needs to be poked with a stick since it is just blank pages for everything so we can't see what is going on.

web and scheduler: enable plan classes for BUDA

If you make a variant of a BUDA app for a plan class
(e.g. NVIDIA GPU with CUDA)
this ensures that jobs submitted to that variant are sent
only to capable hosts,
and that the host usage and projected FLOPS are set correctly.

On the web side, we add a <plan_class> element to workunit.xml_doc.
This gets sent to the scheduler.

On the scheduler this required some reorganization.
As the scheduler scans jobs, it finds and caches
a BEST_APP_VERSION for each app.
This contains a HOST_USAGE.

In the case of BUDA, the host usage depends on the workunit,
not the app version.
We might scan several BUDA jobs
they'll all use the same APP_VERSION,
but they could have different plan classes
and therefore different HOST_USAGE.

The integrated luminosity of the proton run, which denotes the number of collisions recorded, reached almost double the best performance achieved in previous runs, with124 inverse femtobarns for both the @atlasexperiment and the @cmsexperiment. Later, during the 17-day lead-ion run, an integrated luminosity of 1.98 inverse nanobarns was delivered to the @alice_experiment, an equivalent amount to last year.

Particles are set to return to the accelerator chain at the beginning of March 2025 and to the LHC at the beginning of April.

the singular reason to switch Windows machines from VBox to Docker, which is unnecessary anyway, would be to shut you up.