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.
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.
I installed BOINC in Windows with the "Protected Application Execution" option. Could this be a problem?
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.
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
VirtualBox shows me the following runtime error message: "cannot access the kernel driver!" What can I do?
(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.