Christian has updated RNA World's vbox wrapper such that you may now use the latest Virtual Box versions for all systems supported by our project.
In case you encounter trouble, please inform us in our discussion forum.

Christian hat den Vbox-Wrapper aktualisiert, so dass ihr nun auch die neusten Versionen von Virtual Box für alle von RNA World unterstützten Systeme einsetzen könnt.
Solltet ihr Probleme entdecken, meldet euch bitte in unserem Diskussionsforum.

Michael.

---

Rechenkraft.net e.V. - Verein zur Foerderung von Bildung, Forschung und Wissenschaft durch Einsatz vernetzter Computer.

Does this update handle the previous VM problem that kept BOINC from ever checking for VM support again on computers where such a check had previously failed?

Does this update handle the previous VM problem that kept BOINC from ever checking for VM support again on computers where such a check had previously failed?

No it does not. The problem you describe is in the BOINC Client. One has to manually remove a certain XML tag from client_state.xml I think but I'm not sure. This needs to be fixed in the Client or Manager and there is a proposal but nobody implemented it yet.

Will the VBox wrapper update itself during trickle-up for my WU from before the change, or do I have to let this WU run its course before installing the new version of BOINC with VM?

Does this update handle the previous VM problem that kept BOINC from ever checking for VM support again on computers where such a check had previously failed?

No it does not. The problem you describe is in the BOINC Client. One has to manually remove a certain XML tag from client_state.xml I think but I'm not sure. This needs to be fixed in the Client or Manager and there is a proposal but nobody implemented it yet.

Then you might get more users actually running your VM workunits by giving a detailed description of how to remove that XML tag manually, preferably mentioning saving a copy of the file before it is changed.

@ robertmiles

I think I saw instructions for doing that on the BOINC site. It was a while back and I was looking for something else, so I don't remember where it was located. You might be able to search it up, though.

@ robertmiles

I think I saw instructions for doing that on the BOINC site. It was a while back and I was looking for something else, so I don't remember where it was located. You might be able to search it up, though.

@Silverdrake

I tried such a search; it found 61200 items. I looked at the first 50 of them; none appear to say anything relevant to this problem.

Is this what you're looking for?
http://github.com/BOINC/boinc/issues/1460

Is this what you're looking for?
http://github.com/BOINC/boinc/issues/1460

Probably. I'll try it tomorrow.

Is this what you're looking for?
http://github.com/BOINC/boinc/issues/1460

Probably. I'll try it tomorrow.

I tried to do it, and found no sign that either of my computers running BOINC appear to have any file named client_config.xml .

What directory should this file be in if it even exists?

Hmm... I'm thinking the correct file name is actually "client_state.xml" in your BOINC data directory.

So.. with BOINC closed, find "client_state.xml", and see if you have a "p_vm_extensions_disabled" entry that could be deleted. Take special care when editing this file -- if you get it wrong, you could trash your BOINC projects/tasks.

Let us know what you find!

For those tracking this thread...

Christian mentioned that he updated the application to v1.17, which includes an updated VBoxWrapper, and a new vbox.job file that should allow progress to report correctly in the UI, instead of constantly reporting 0.1% progress. Prior versions are still valid for getting work done, though, so DON'T abort your 1.14/1.15/1.16 tasks!

Note: If progress appears to get stuck at 98.765%, it actually is still progressing, DON'T abort it - the estimate was just way too low, but your work is still valid, so don't abort it! You can make sure it is progressing because the progress.txt file's modified date should be getting updated, even if the value inside stays at 0.98765. If you want to know an even crazier way to verify progress, you can PM me and I'll explain a riskier technical way.

Thanks,
Jacob