LHC@home

LHC@home sends tasks directly from HTCondor to your VirtualBox, BOINC server only sends you pseudo-task that just means there is something to do using VirtualBox. I can't believe Folding@home is more complex than LHC@home, and yet LHC@home is a BOINC project.

It's the vboxwrapper that is visible to the BOINC client, nothing else.
There's no online communication between BOINC or vboxwrapper and the processes inside the VM.

Hence, BOINC never knows whether CMS (and ATM it's only CMS) gets it's subtasks via HTCondor.

Vboxwrapper creates/starts a VM and then just waits until a special file appears or a timeout limit is reached.
It then stops/destroys the VM and reports a few values, e.g. CPU time, back to the BOINC client.
Beside that pausing/resuming a VM are done via vboxwrapper.
This is also the reason why BOINC never knows anything about the real calculation status.

LHC@home sends tasks directly from HTCondor to your VirtualBox, BOINC server only sends you pseudo-task that just means there is something to do using VirtualBox. I can't believe Folding@home is more complex than LHC@home, and yet LHC@home is a BOINC project.

LHC is more difficult to get to run than others though. You have to get Virtualbox running properly for a start. I have 6 machines, and 3 of them don't run virtualbox very well, 50% of LHC tasks result in an error, so I stopped doing all but the non-VB sixtrack tasks on those. I can only assume it's the age of the CPUs. The three that work are newer and/or more powerful CPUs.

---