Frequently Asked Questions
- What is VirtualBox?
- Where can I find help?
- What is Virtualization?
- Why are we using desktop computers instead of the Grid?
- What do I need to participate in LHC@home?
- Can I run LHC@home projects offline?
- What simulation packages are included in CernVM?
- How do I report an error or a bug?
- VirtualBox crashes and does not respond at all to BOINC. What can I do?
- What is CernVM?
- Why do we need a virtualization application?
- I'm getting lots of errors and I have BOINC installed as a service/daemon, is this a problem?
- I'm getting the following message: Computation Error output file absent. What can I do?
- The Virtual Machine uses my CPU too intensively. How can I change this?
- I installed BOINC in Windows with the "Protected Application Execution" option. Could this be a problem?
- I'm using a Proxy for my Internet connections. Could this be a problem?
- Does LHC@home support GPUs?
- Message boxes keep popping up from Virtualbox. How can I remove them?
- My keyboard and mouse do not respond to me. How can I get them back?
- VirtualBox shows me the following runtime error message: "cannot access the kernel driver!" What can I do?
- Is it possible to configure the maximum amount of data that can be downloaded/uploaded by the project per month?
- Are any of my personal data sent to CERN when I install the software?
- I tried to install it, but it was too complex I gave up...
- Can I simply shut down my computer or is a special procedure necessary?
- Why is the Virtual Machine not using all my CPU cores?
- Why is my old web browser not supported?
- My firewall is complaining. Which ports does this project use?
- I've updated VirtualBox and now I cannot see the VM console. How can I fix it?
VirtualBox is a powerful x86 and AMD64/Intel64 virtualization hypervisor for enterprise as well as home use. A hypervisor allows your computer to host one or more Virtual Machines, running different operating systems than your own computer runs. This is essential for all our projects (except for Sixtrack).
See Contact Us where you'll find links to the forums, the Q&A for each project, and a contact form if you're really stuck.
We have a great community that will try to help you.
Virtualization, in computing, is the creation of a virtual computer that can run an operating system, applications, etc. within your real hardware. You can obtain more information about this topic in the Wikipedia.
The computing needs of the LHC, especially when it comes to comparing various theories with experimental results, are enormous. Basically, the physicists' appetite for computing power expands to fill all available resources, because there are always more theories to test than there are computers to test them with.
Since budgets are constrained, especially in these economically difficult times, access to volunteer resources is seen by CERN as a great opportunity to expand computing capacity. We'll never replace the Grid's core function of managing the data mountains, but we could augment its computing power considerably. While the LHC World-Wide Computing grid is used at full capacity to handle the analysis of LHC data, there is need for additional capacity for simulations of LHC physics, ranging from theory to simulations of detectors as well as design improvements for future accelerators.
It's also clear to everyone in our community that getting the public more directly involved in LHC physics has great outreach benefits as well. So we see this as a win-win situation. And who knows, perhaps one day we'll be able to announce an important discovery that will have been made in part thanks to the volunteers. That would be cool!
You need a computer connected to the Internet with at least 512MB of RAM and 9GB of free hard disk space. It can run Windows, MacOSX or Linux.
To run any of our LHC@home projects, you will need to install BOINC.
For all projects except Sixtrack, you will also need to install VirtualBox.
For more information, see our installation guide.
See the forum thread here: http://lhcathome2.cern.ch/vLHCathome/forum_thread.php?id=1681. In a nutshell:
You will need to have an open internet connection while running project tasks. You cannot run the tasks if not connected to the internet.
The task starts up a VM, then the VM runs a series of tasks that each run for about 60 to 90 minutes each. At the beginning of each task inside the VM, it downloads some data, crunches the numbers, and uploads the result, then the next VM task starts and downloads more data.
If you have found an error or a bug in the application, the experiments, the project, etc. please write a post about the error in the message boards so the administrators and volunteers can participate in solving the problem.
If the virtual machine named "boinc_wu_xxxx_..." in the VBox Manager window does not respond at all to BOINC (i.e. you suspend the BOINC task but the VM is still running) you can try the following steps to recover the project:
- Abort the running WU and exit BOINC. Then, you will have to manually kill or quit the VirtualBox process from a command line. It will be different in each operating system, but usually:
- In Mac OS X: you can kill it using the Terminal interface and running the kill -9 command to kill the PID of the process "VBoxHeadless.exe".
- In GNU/Linux: you can kill the VirtualBox process using your Desktop manager or from a terminal using the kill -9 command to kill the PID of the process called "VBox Headless".
- In Windows: open the Windows task manager and kill the VirtualBox process.
- Restart BOINC: it should receive a new clean WU and everything should be working OK again. If at this point you are still having problems, please use the message boards to get more help.
CernVM is a Virtual Software Appliance for the participants of CERN LHC experiments. The Appliance represents an extensible, portable and easy to configure user environment for developing and running LHC physics software both locally, on Grids and on Clouds, independently of Operating System software and hardware platforms (GNU/Linux, Windows, MacOSX).
The goal is to remove a need for the installation of the experiment software on each target platform, and thus to minimize the number of platforms (compiler-OS combinations) on which experiment software needs to be supported and tested. Visit the CernVM homepage for further details.
All our projects (except for Sixtrack) run very large CERN software packages with complex dependencies that cannot be easily ported to all the volunteers' operating systems (Windows, GNU/Linux and Mac OS X).
For this reason, we use a virtualization solution, which enables us to run complex codes independently of your platform.
Additionally, using virtualization adds an extra layer of security, as if something goes wrong in the code execution this will not affect your computer.
BOINC must not be installed as a service (Windows) or a daemon (GNU/Linux) because this project uses Virtual Machines. When BOINC is installed as a service or a daemon it runs as an unprivileged user and cannot run any virtual machine.
The best solution to solve this problem under Windows is to install BOINC disabling the Service option in the Windows installer.
Late news: BOINC Client 7.2.10 and above solve this problem for running as a service under Windows.
For GNU/Linux users the recommendation is to use the official BOINC GNU/Linux installer instead of the packaged ones for your distribution.
First of all, HAVE YOU INSTALLED VirtualBox ??
Next, check that your BOINC installation sets up the correct permissions for running VirtualBox. Recheck our information on "Installing BOINC".
If BOINC is correctly installed, the main reason for that message is that the wrapper fails to remove an old virtual machine (VM) after it has expired, and so cannot register a new VM for the next Work Unit (WU).
The best solution for cleaning your project files if you have to do it manually is:
- Abort the running WU.
- Quit BOINC (the core client should be not running).
- Open VirtualBox Manager, and remove the registered machine named "BOINC_VM" (or any VM's with names "boinc_wu_xxxx_xxx").
- Open VirtualBox Media Manager and remove the cernvm.vmdk virtual hard disk if it is registered.
- Launch BOINC again.
You can change how much CPU time is used by the Virtual Machine going into your BOINC project account and changing the Preferences for this project -> Maximum CPU % for Virtual Machine. You can specify an amount between 0 and 100% (by default 100%), then save your preferences and update the BOINC project.
If you have installed BOINC with the Protected Application Execution option enabled, then you will not be able to run the project, and all the work units will fail. The reason is that when you install BOINC with that flag enabled, BOINC is run under an unprivileged user that cannot create, start, pause, resume virtual machines at all. Thus, the wrapper will not be able to run the required virtual machine of this project.
In order to solve it, please, reinstall BOINC with that option disabled.
If you only have access to Internet via a Proxy, you may get Compute Errors in BOINC, as the Virtual Machine needs direct connection to Internet. For the moment there is no solution, but we will try to fix it.
For the moment LHC@home does not use GPUs for running the experiments. Additionally, the GPU code could not work as we are accessing the hardware via a virtual machine.
VirtualBox warns the user about how the keyboard and mouse will be captured if you click inside the window of the virtual machine. This message will pop up everytime you run a virtual machine unless you tick the "don't show this window again" option in the message box.
If you click inside the console window of the Virtual Machine and the keyboard and mouse get "grabbed" in the window, then to release them, you have to press the Host Key (Right Ctrl) or (Right Cmd in Mac OS X). You can check which is the Host Key by clicking in: File->Preferences->Input
(This is a Windows problem only).If you get that error it seems like your VirtualBox installation missed installing the vboxdrv.inf driver. Please first try to reinstall VirtualBox - if this does not solve the problem, go to C:\Program Files\Oracle\VirtualBox\Drivers\ and double click in the file vboxdrv.inf. After that, you should be able to run VirtualBox without problems.
The BOINC transfer at most network preference is not supported for the moment. If your ISP has a limitation in the bandwidth that you can use each month, bear in mind that the virtual machine will continue downloading/uploading data when needed.
You will only have to provide a user name and an e-mail, nothing else is required. The information that is sent about your machine is the hardware specifications: CPU type, RAM and disk space, OS version, etc.
We know it, and for this reason we are working together with the BOINC and VirtualBox communities to simplify the whole process to set up the software and join us. It will be interesting if you can tell us where you have difficulties, please use the forums, so we can try to fix them for the next releases.
We recommend to exit BOINC before powering off the computer, because the VBox Wrapper will capture that exit signal, and will try to save the virtual machine and avoid canceling the WU. This is not necessary when suspending or hibernating the computer.
VBoxWrapper does not support more than 1 core currently. We recommend you run multiple BOINC tasks, each with a single VM, to use multiple cores on your system.
- an interactive gallery with all the figures from the simulations of your computer:
- zoom in and out with a friendly interface,
- browse the figures (next,previous and index) using shortcuts and without going back and forward to see other image,
- swipe movement for flicking through images on touch devices,
- and some BOINC statistics.
Here you have an screenshot of the web page with a free, modern and open source web browser like Mozilla Firefox or Google Chrome (but note that Safari versions 6+ and Internet Explorer versions 10+ do support our graphics):
You can still access the raw figures and BOINC stats data and the LOGs folder as you will get a warning with links to those resources.
This project uses the following ports:
- Jabber messaging which needs XMPP (port 5222),
- Chirp (port 9094) for moving data in and out,
- HTTP (port 80) and
- HTTPS (port 443)
And if you want, you can grant access to the entire CERN network:
No other ports are used by the project.
If you have upgraded VirtualBox, you will need to also upgrade the VirtualBox Extensions Pack, otherwise you will not be able to see again the Virtual Machine Console. After upgrading the extensions, cancel the running WU and request a new one, this will allow T4T to configure the VM correctly with the new extensions.