How can I make it stop? I have been a long time supporter of RH, but will disconnect from the project if it keeps wasting my bandwidth with 2GB failed downloads.

Temporarily STOP REQUESTING NEW WORK FOR THE PROJET by settling NO NEW WORK for Rosetta on your PC(S) in BOINC until the project fixes the problem.

That means you will get no work at all, even though there are just under 13 million Rosetta 4.20 Tasks available.

---

Grant
Darwin NT

I received an odd message today:

Rosetta@home: Notice from server
VirtualBox is not installed
9/19/2021 6:01:50 PM

It is correct that I do not have VirtualBox installed, and I have not used VirtualBox to run BOINC programs.

That was sorted out yesterday.
It started on the 18th & when it did, it stopped those without VirtualBox from getting any Rosetta work- even that which doesn't need VirtualBox. Once they fixed it, there were no more notices about a lack of VirtualBox in Event logs, and work started flowing again- as can be seen in the Graph below.
In particular, the big dip on the 18th.

---

Grant
Darwin NT

There is a researcher in the group that has submitted a large batch of VM jobs that requires Virtual Box. More information is provided at https://boinc.berkeley.edu/wiki/VirtualBox.

This is the first large batch of "rosetta_python_projects" VM jobs but we hope to have more in the future. Since this is our first attempt at using BOINC's VM option, we will undoubtedly run into issues as we scale up. Please be patient as we try to resolve these issues. Our standard rosetta application is still being used but the number of available jobs can fluctuate as it has before depending on the computing demand from our researchers.

The VM app feature allows researchers much more flexibility to run scientific software that otherwise would not be possible on R@h. For example, the "rosetta_python_projects" app allows researchers to run deep learning based structure prediction pipelines including RoseTTAFold and AlphaFold2, and other python based sofware packages like AIMNet which is being used in the current batch of VM jobs to minimize potential microcycle therapeutics.

---

This is the first large batch of "rosetta_python_projects" VM jobs but we hope to have more in the future.

Very good. I have several machines with lots of memory waiting to do them.

BUT: You need to make them selectable from the regular Rosettas.
A simple checkbox would do, but even better would be the ability to select the number downloaded (or running) at at time.
See LHC, or Cosmology, or WCG for examples.

---

It is just an informational message, hoping that you will install VBox to crunch more tasks. Thanks.

There is a researcher in the group that has submitted a large batch of VM jobs that requires Virtual Box. More information is provided at https://boinc.berkeley.edu/wiki/VirtualBox

Virtualization and BOINC
BOINC uses virtualization to allow scientists to develop applications on their preferred operating system (usually Linux) and then run them on volunteered Windows and Mac computers. We call these VM apps.

BOINC's virtualization support uses a system called VirtualBox, which is open-source software maintained and distributed by Oracle. For more information about VirtualBox, please see their web site at https://www.virtualbox.org/

To run VM apps, your computer must have VirtualBox installed. Starting with BOINC version 7.2.28, the recommended BOINC installer for Windows includes VirtualBox as well. You can also install VirtualBox separately.

We recommend the VirtualBox version that is included in the recommended BOINC Windows installer, since newer VirtualBox versions do not work correctly for all projects.

If you are running Windows, it is essential that you install a version of BOINC that matches your version of Windows - use 64-bit BOINC on 64-bit versions of Windows, 32-bit BOINC on 32-bit versions of Windows. Otherwise, BOINC will not be able to detect the presence of VirtualBox.

Oh! So it's that thing I've been ignoring for several years... #Doh

Download BOINC + VirtualBox

---

aaaf-IDC_pp-FPR_pp-mNHM_pp-NMBEN3_pp_0_1737815_2_1

<core_client_version>7.16.11</core_client_version>
<![CDATA[
<message>
WU download error: couldn't get input files:
<file_xfer_error>
  <file_name>AIMNet_vm_v2.vdi</file_name>
  <error_code>-119 (md5 checksum failed for file)</error_code>
  <error_message>MD5 check failed</error_message>
</file_xfer_error>
</message>
]]>

There goes another one. I have yet to encounter a Python task that doesn't error out. Is it something wrong with my setup, or is there a problem with these tasks? I've tried the version bundled with BOINC and the latest version, still 100% error rate.

I feel like I am missing out on some new information or something. Do these new "rosetta_python_projects" run native on Linux? Virtualbox is only needed on Windows and Mac, correct? I was under the impression that all Windows BOINC installations were already containers or VMs on Windows or Macs.

I feel like I am missing out on some new information or something. Do these new "rosetta_python_projects" run native on Linux? Virtualbox is only needed on Windows and Mac, correct? I was under the impression that all Windows BOINC installations were already containers or VMs on Windows or Macs.

The applications page says:

Linux running on an AMD x86_64 or Intel EM64T CPU 1.03 (vbox64)

Same as Windows and MacOS. No mention of a native app.

---

I'm pretty sure it uses VBox regardless of the host OS. I guess that way it can ship with the correct dependancies etc.

---

Interesting. I took a look at the applications page https://boinc.bakerlab.org/rosetta/apps.php and the VirtualBox page https://boinc.berkeley.edu/wiki/VirtualBox but I don't see anything that would indicate a definitive answer. My Linux systems do not have VirtualBox installed. The apps page does indicate they are running on Linux systems but they don't indicate if VirtualBox is or needs to be installed. The same goes for Windows in the apps page.

It was my understanding that Rosetta tasks were already written for Linux environments and so it was just easier to containerize Linux on Windows than re-write everything for Windows or Macs.

I haven't seen anything in my logs about downloading AIMNet_vm_v2.vdi and when I check out my boinc directory, I see minirosetta and 4.20 executables but I don't see anything about vbox64 or python.

I have 671 tasks in progress and I am showing 0 rosetta python tasks. I was just curious if there is anything I need to do to keep my systems up to date so that they can maximize processing capability for Rosetta.

If Virtualbox isn't installed, your system won't download any work units or executables related to the vbox app.

This "1.03 (vbox64)" indicates the need of the pyrosetta app for virtualbox.

---

Hello,

Why could I receive the message "Communication with VM Hipervisor failed"? In the VBox register appears the error
«Failed to create the VirtualBox object!
NS_ERROR_SOCKET_FAIL (0xC1F30200) IPC Daemon socket error.»

I have the Boinc version 7.16.16 and the VirtualBox 6.1.26 r145957 running on Debian GNU/Linux 11 (bullseye) [5.10.0-8-amd64|libc 2.31 (Debian GLIBC 2.31-13)].
The boinc user is added to the vboxusers, vboxguests and libvirt groups.

Any clue about what could be happening? I have no experience with VirtualBox, I installed it just as a Rosetta@home requirement.

I got this when I tried to open Oracle VM VirtualBox:

You could try this app:
http://leomoon.com/downloads/application/leomoon-cpu-v/

And there are other tests listed here too:
https://lhcathome.cern.ch/lhcathome/forum_thread.php?id=4161

---

Interesting. I took a look at the applications page https://boinc.bakerlab.org/rosetta/apps.php and the VirtualBox page https://boinc.berkeley.edu/wiki/VirtualBox but I don't see anything that would indicate a definitive answer. My Linux systems do not have VirtualBox installed. The apps page does indicate they are running on Linux systems but they don't indicate if VirtualBox is or needs to be installed. The same goes for Windows in the apps page.

It was my understanding that Rosetta tasks were already written for Linux environments and so it was just easier to containerize Linux on Windows than re-write everything for Windows or Macs.

You need VirtualBox for Linux too. There are different versions of Linux, with different libraries. It can cause problems on any project.

Even LHC uses VirtualBox on Linux for Theory and ATLAS, though they also have "native" apps for them. But the native apps need a "container" such as singularity, which is even more complicated to set up than just installing VirtualBox. Though it would be nice to have native versions for Rosetta too if they can manage it, since it runs a little more efficiently, and probably needs less memory.

---

DEK/ADMIN/dcdc

What the heck is going on with your scheduler?
Or is there a bug in BOINC?

I have now 998 (What the *!&*#?) tasks sitting in my queue.
I lost 11 python tasks because something clogged my system with over 600 4.20 tasks
I am going to abort 900 tasks because there is no way hell I can plow through that many.
That's 332 days of crunching. That just beyond belief!!!

Plus that clogs up my system because your project is limited to a certain number of cpu's while I share the rest with several other projects and all your tasks have 8 hour run times. If I drop that to 4 that would be still over 5 months of work. And all these tasks were due on the 24th?

Explain this to me.....

BOINC bug or your system bug?

----
Sent back 880 or so tasks...geees...i better go find a limiting command

What the heck is going on with your scheduler?
Or is there a bug in BOINC?

I have now 998 (What the *!&*#?) tasks sitting in my queue.

I have not had that problem since getting rid of the "max concurrent" in the app_config.xml, as we discussed earlier.

---

What the heck is going on with your scheduler?
Or is there a bug in BOINC?

I have now 998 (What the *!&*#?) tasks sitting in my queue.

I have not had that problem since getting rid of the "max concurrent" in the app_config.xml, as we discussed earlier.

I have to have max concurrent in order to limit the number of cpu's RAH uses, otherwise my idea of splitting up my system so every project has its own group of cores is out the door and then I run into problem of every project dominating my system and some get all the work for days on end and others don't.

If RAH would do like LHC and allow ME to pick how many cores to give it, then I would not have to do max concurrent.

I need to find a command to limit the number of files downloaded.

OR would project_max_concurrent be any better than max_concurrent?
How about ncpus and take out max_concurrent?

OR would project_max_concurrent be any better than max_concurrent?
How about ncpus and take out max_concurrent?

Unfortunately, project_max_concurrent won't work either.
https://lhcathome.cern.ch/lhcathome/forum_thread.php?id=5720&postid=45323#45323

You could try ncpus, but I think that is mainly for multi-threaded apps.

What I do is just create separate BOINC instances for each type of work unit when I need to limit them.
Then you can just set "use at most % of the processors" to limit it to what you want.

It is a bit of a pain, but actually simple enough once you do it the first time.
This more or less gives you all you need.
https://www.overclock.net/threads/guide-setting-up-multiple-boinc-instances.1628924/

I think that on Windows, they neglect to tell you how to start it up automatically, though you can do it manually easily enough.
I used Task Scheduler to start the BOINC client automatically, but don't have the details since I usually use Ubuntu, where it is a bit simpler.
I think you have to start up BOINC Manager separately in the "Programs/Startup" folder, but that was on Win7 and I am now on Win10.

---