log in


If you would like to join this project you will need to get an invitation code first.
In order to get an invitation code, please check out this post.

This is a project that utilizes the CERN-developed CernVM virtual machine and the BOINC virtualization layer to harness volunteer cloud computing power for full-fledged LHC event physics simulation on volunteer computers.
This is just a BOINC server. Please visit the LHC@home information for more information. If you have any problems or questions please visit the Message Boards, Questions and Answers and FAQ.

Join vLHCathome-dev

  • Read our rules and policies
  • Create an account on this page, for this you will need an invitation code. In order to get an invitation code, please check out this post.
  • This project uses BOINC. If you're already running BOINC, select Add Project. If not, download BOINC.
  • When prompted, enter
  • If you're running a command-line version of BOINC, create an account first.
  • If you have any problems, get help here.

User of the day

User profile Profile ritterm
I'm a telco network engineer and an active father with four kids. I enjoy racquet sports, bicycling, hiking, sailing, the performing arts, messing with...


Migration to SSL
The scheduler and web pages of this dev project are now also published on the URL:


Please detach and re-attach to this new URL with your BOINC clients. The old project server is still running, and also the file upload and validation daemons run on the old server for now.

Later on after a test period, we will redirect the old URL. Then we will proceed in a similar way with our production project.
16 Sep 2016, 14:18:50 UTC · Comment

Task Tracker
I have added a task tracker to the top left of the page so everyone can see what issues we know about, which one are being worked on and what is being done right now. It still needs populating with a few items. 3 Aug 2016, 10:08:09 UTC · Comment

Task and CPU limiter
The server has just been updated to add the feature that limits Tasks and CPUs per user. This limit can be controlled in the project preferences.

Together with my changes to the scheduler, per-project limits on jobs in progress and #CPUs should now work. But I haven't actually tested this. Laurence, please try it and tell me if it doesn't work.
-- David

Please post any feedback in this thread. 31 Jul 2016, 7:48:14 UTC · Comment

Server Upgrade Tomorrow Morning
The server will be upgrade tomorrow morning. 28 Jul 2016, 14:07:33 UTC · Comment

David Anderson, Rom Walton and myself had a conference call yesterday where we discussed limiting tasks per user, why we want to do this, mutli-core VMs and the VT-x issues.

One of the reasons why we would like to limit tasks is that machines can be assigned more tasks that they can handle or is desired, which leads to problems. David pointed out that BOINC should respect the resource constraints and if not the issue needs to be looked into. Feedback on this would be welcome so I have created a new thread where you can paste any scenarios where BOINC is not respecting the constraints.

Implementing a task limit per user should be straight forward. I will provide an updated php file for the project preferences and David will update the scheduler code to take this into consideration.

Similarly for multi-core, we can set a flag in the project preference on whether or not you would like BOINC provide multi-core VMs. This is an area where we probably still need to experiment.

Finally, the VT-x issue was discussed as over 30% of our failed tasks are VMs that fail to boot due to this setting not being available or enabled. It was pointed out that tasks should not be provided if the machine is not capable of running them. This will also be investigated.
28 Jul 2016, 13:03:56 UTC · Comment

... more

News is available as an RSS feed   RSS