Tue, 07/05/2011 - 10:04 — Daniel Lombraña... (Updated July 2013, BS)
*** The following advice only applies to the old wrapper ***
If after quitting BOINC, the virtual machine continues running, you can safely stop it by running the following command in your computer:
VBoxManage controlvm BOINC_VM savestate
Fri, 07/15/2011 - 10:01 — Daniel Lombraña... (Updated July 2013, BS)
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.
Thu, 08/04/2011 - 12:42 — Daniel Lombraña...
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.
Wed, 07/27/2011 - 10:33 — Daniel Lombraña... (Updated July 2013, BS)
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). This applies mainly to the older "CernVM wrapper" system, not the new "VBox Wrapper" system.
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.
Tue, 08/09/2011 - 11:41 — Daniel Lombraña...
I installed BOINC in Windows with the "Protected Application Execution" option. Could this be a problem?
Tue, 08/09/2011 - 12:01 — Daniel Lombraña...
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.