So, there can be several boinc-client instances running on the same host, provided each instance has its own data directory and its own remote GUI control port. (And some more requirements.)
Here are projects which are not compatible with such a setup:
Here are projects which are not compatible with such a setup:
- GPUGrid collapses all the instances into a single host. As soon as tasks are fetched in instance 2, the tasks in instance 1 are marked as "abandoned".
- There are one or more other projects which behave like GPUGrid. Maybe you know some that I don't recall right now. You can detect this kind of project this way: When you add another client instance to the project, you don't see another host added to your hosts list at the project's web site.
Cosmology@Home's vboxwrapper based camb_boinc2docker tasks get stuck in "postponed: VM Hypervisor failed to enter an online state in a timely fashion" if there is another boinc-client instance on the same host starting jobs in whatever other project. (Seen when trying to run Cosmo in instance 1 and MindModeling in instance 2.)
If memory doesn't deceive me, LHC@Home's vboxwrapper based applications are similarly wonky.
Edit: camb_boinc2docker also fails if MindModeling runs in the same client instance. I have not yet tried to reproduce the multi-client problem with other projects. Maybe there was no multiple-instance problem with vboxwrapper after all.
Last edited: