Hi all!

I recently started contributing to BOINC again and I recently have also installed VirtualBox 6.0 for a VM that I use for home automation (Home Assistant - go check it out!). Unfortunately it seems that after installing this for my own personal VM, that this has caused an issue with running the Cosmology@Home jobs that are also running in a virtual environment.

#1 - In the Tasks list under the status column for these jobs, it states "Postponed: VM job unmanageable, restarting later (4 CPUs)"

#2 - When I fire up the VM VirtualBox Manager, I can see these VMs in the list with my own VMs. Some are "Powered Off" and some are "Aborted."

Any easy (or difficult, I'll do what I need to do to get both running, if at all possible) solutions to:

#1 - Actually get these tasks past the few percent that they seem to run before erroring out?
#2 - Remove these VMs from my Manager window?

I tried searching but didn't really come across much for some reason. I thought that this might be a common problem for people who use VirtualBox for other VMs, but maybe I can't search or I'm an edge case. Or both.

-Running on Windows 10
-BOINC v7.14.2 (x64)
-Have not really tried anything to resolve this issue. I need VirtualBox installed to manage my own VM and prefer to have the latest and greatest out.
-All the Cosmology@Home tasks seem to have this issue as each application ends in vbox64_mt (e.g. camb_boinc2docker 2.05 (vbox64_mt).
-Event log message for when each of these jobs/tasks run states "Task camb_..... postponed for 86400 seconds: VM job unmanageable, restarting later."

Thanks in advance!

BOINC on!

You best ask at the Cosmo forums (http://www.cosmologyathome.org/forum_index.php) what their required/requested version of VirtualBox is, as not all VBox versions work with all BOINC projects.

---

Just wanted to update this thread in case someone else comes here searching for answers. I uninstalled VirtualBox 6.0 and installed v5.2.34 and everything seems to be working as expected.

Thanks!