Many machines won't have those enabled by default. What can we do about it? Well, here are the things that I know of that are required to run Vbox tasks:ġ) VirtualBox requires virtualisation extensions to be enabled in the BIOS. Or potentially create a work-around to allow BOINC to run under a dedicated user-account prior to login?ī) virtualisation isn't enabled in the BIOS It doesn't give much information about whether VirtualBox tasks are likely to work on the machine.Ī) you're running BOINC as a service, and so VirtualBox isn't available. I would guess significantly less than half of machines.ģ) #2 is made worse, because BOINC is not well set up for telling users whether it can run VirtualBox tasks or not. We have seen a huge amount of wasted traffic over the last few days because a batch of work has been released that has a 2GB download with a bad hash, causing it to fail every time.Ģ) VirtualBox tasks can't run on all BOINC systems.
Why is that an issue for VirtualBox tasks? Because they don't run like "normal" BOINC tasks do - e.g. But I have no doubt the project could be much bigger with a little bit of input, news and feedback.
Personally, I can forgive the project for that to some extent because of the work that they are doing. Things are definitely worst since Mod.Sense hasn't been around.
I think it's probably the worst-run major BOINC project. There are a few issues with running VirtualBox tasks as I see it:ġ) has been run very "light-touch" in terms of news and feedback over the last few years.
0 kommentar(er)
