T4T already runs a Virtual Box wrapper application, but even though they are a Beta project they do not want to go test all the adjustments and bug fixes that the BOINC developers added to the Vboxwrapper app (which begs the question why they run as a beta project then, but heck ;-)), to Virtual Box (in coop with Oracle devs) and to the BOINC client. Hence the CERNVM/Vboxwrapper Test Project set up and administrated by the BOINC developers, where we test all that.

There's no validator running over there, so there's no credits even though we do real work through the hypervisor. The project will be deleted when we're done testing.

Eventually, when we're done testing the crap out of all that, hopefully T4T will take over the vboxwrapper app and run it at their project.

---

Jord.

BOINC FAQ Service

They say most of your brain shuts down in cryo-sleep. All but the primitive side, the animal side. No wonder I'm still awake.

T4T already runs a Virtual Box wrapper application, but even though they are a Beta project they do not want to go test all the adjustments and bug fixes that the BOINC developers added to the Vboxwrapper app (which begs the question why they run as a beta project then, but heck ;-)), to Virtual Box (in coop with Oracle devs) and to the BOINC client. Hence the CERNVM/Vboxwrapper Test Project set up and administrated by the BOINC developers, where we test all that.

There's no validator running over there, so there's no credits even though we do real work through the hypervisor. The project will be deleted when we're done testing.

Eventually, when we're done testing the crap out of all that, hopefully T4T will take over the vboxwrapper app and run it at their project.

Thank you for your answer.

The VirtualBox thing is a bit different software tech then used by boinc earliar.
Maybe more projects will use that tech once you guys completing devolop/addept it for boinc.

---