OK, so that is the issue, I understand.
Thanks a million for the feedback.
Time to add more memory!

Lets see now
Python ram calculator says 12 cpu`s times 8 gig each [allowing a bit] seems you need to fit about 100GB to be safe to run full on
And that`s no joke
well the way RPP tasks hog ram its a sad joke the project needs to do some thing about
and this is only the hundredth {or so} post to `hint` at it
OK folks I`le go back to banging my head on the wall . . . .

I just encountered an issue. My BOINC client cannot recieve any Rosetta@Home projects.
The log says:

22/11/2021 20:40:55 | Rosetta@home | Sending scheduler request: To fetch work.
22/11/2021 20:40:55 | Rosetta@home | Requesting new tasks for CPU
22/11/2021 20:40:57 | Rosetta@home | Scheduler request completed: got 0 new tasks
22/11/2021 20:40:57 | Rosetta@home | No tasks sent
22/11/2021 20:40:57 | Rosetta@home | Message from server: VirtualBox is not installed
22/11/2021 20:40:57 | Rosetta@home | Project requested delay of 31 seconds

After that I installed VBox but it still outputs this error.
I also tried to reset the project but it doesn't make any difference.

What can I do now?

I just encountered an issue. My BOINC client cannot recieve any Rosetta@Home projects.
The log says:

22/11/2021 20:40:55 | Rosetta@home | Sending scheduler request: To fetch work.
22/11/2021 20:40:55 | Rosetta@home | Requesting new tasks for CPU
22/11/2021 20:40:57 | Rosetta@home | Scheduler request completed: got 0 new tasks
22/11/2021 20:40:57 | Rosetta@home | No tasks sent
22/11/2021 20:40:57 | Rosetta@home | Message from server: VirtualBox is not installed
22/11/2021 20:40:57 | Rosetta@home | Project requested delay of 31 seconds

After that I installed VBox but it still outputs this error.
I also tried to reset the project but it doesn't make any difference.

What can I do now?

What version of Vbox? A version recent enough to include vbox64 is required for the Python tasks.

How much memory does your computer have? 12 GB is about the least that will run Python tasks, and then only if you have enabled virtualization in the BIOS settings,

Under Options, then computer preferences, you may have to tell BOINC that it is allowed to use higher fractions of the memory and the disk space.

There's an occasional task with much smaller requirements, but people try to download them much more often than they become available.

Also, you may have to restart or reboot your operating system (probably Windows or Linux) before such changes will take effect.

Did you restart Windows? If not, did you restart BOINC?
It will likely be fixed if you restart Windows.

---

Python ram calculator says 12 cpu`s times 8 gig each [allowing a bit] seems you need to fit about 100GB to be safe to run full on
And that`s no joke
well the way RPP tasks hog ram its a sad joke the project needs to do some thing about
and this is only the hundredth {or so} post to `hint` at it

Never has so much been asked to do so little for so few.

---

I just encountered an issue. My BOINC client cannot recieve any Rosetta@Home projects.
The log says:

22/11/2021 20:40:55 | Rosetta@home | Sending scheduler request: To fetch work.
22/11/2021 20:40:55 | Rosetta@home | Requesting new tasks for CPU
22/11/2021 20:40:57 | Rosetta@home | Scheduler request completed: got 0 new tasks
22/11/2021 20:40:57 | Rosetta@home | No tasks sent
22/11/2021 20:40:57 | Rosetta@home | Message from server: VirtualBox is not installed
22/11/2021 20:40:57 | Rosetta@home | Project requested delay of 31 seconds

After that I installed VBox but it still outputs this error.
I also tried to reset the project but it doesn't make any difference.

What can I do now?

VirtualBox, is not compatible and does not work in Windows if Microsoft Hyper-V is enabled.
First of all, uninstall any component of Hypr-V from your system.



Windows it will restart, then try again.
If again, BOIN Manager, should give you the same warning, you will have to open 'Windows PowerShell' (with administrator rights) and type (copy-paste):

bcdedit /set hypervisorlaunchtype off and press [OK]
Subsequently 'exit' ...

Restart Windows and now BOINC, should be able to download the wus

I am starting to get some server aborts (202) on the regular Rosettas, so they must have some bad ones.
Also I see some pythons eliminated that way too, which is good. Hopefully they are finding and getting rid of the "0 CPU" tasks.

I still get "Vm job unmanageable" suspensions on the pythons, but that may be beyond their power to easily correct for a while.
My automatic reboot cron job (as posted previously) takes care of it by rebooting daily.

---

I have an EPYC 7742 with 128 gig ram. When I added virtualbox (now required I guess) now I only get 16 tasks, the machine is almost idle. What needs to be done to fix this ?

Running cinnamon mint 19 (ubuntu Linux)

---

I have an EPYC 7742 with 128 gig ram. When I added virtualbox (now required I guess) now I only get 16 tasks, the machine is almost idle. What needs to be gone to fix this ?

Running cinnamon mint 19 (ubuntu Linux)

Each of the Python tasks reserves 7.45GB of memory. The amount it actually uses is closer to 100 MB, but that is less important.

To get more tasks, you'll have to either add a lot more memory, or wait for tasks that don't reserve so much memory.

You may have to also tell BOINC that it can use a bigger fraction of the disk space.

I have an EPYC 7742 with 128 gig ram. When I added virtualbox (now required I guess) now I only get 16 tasks, the machine is almost idle. What needs to be done to fix this ?
Running cinnamon mint 19 (ubuntu Linux)

Ooops,
Back to to Python ram calculator again ;) . so 128 cpu/threads X 7.45GB Hmm that's a cool 953.6 giblets of rambo
If you want to keep all of its 128 cpu/threads busy you will have to fit an entire TERABYTE of ram, utterly nuts . . . . .
{nice system :}
there is another AMD EPYC 7742 at `top hosts` position 106 that does have a terrible bite of RAM,
But its still stuffed for running full on coz its got 256 cpu/threads to play with . . . . .
That would help keep the house warm
Don't fancy the lecky bill though :}

I have an EPYC 7742 with 128 gig ram. When I added virtualbox (now required I guess) now I only get 16 tasks, the machine is almost idle. What needs to be done to fix this ?
Running cinnamon mint 19 (ubuntu Linux)

Ooops,
Back to to Python ram calculator again ;) . so 128 cpu/threads X 7.45GB Hmm that's a cool 953.6 giblets of rambo
If you want to keep all of its 128 cpu/threads busy you will have to fit an entire TERABYTE of ram, utterly nuts . . . . .
{nice system :}
there is another AMD EPYC 7742 at `top hosts` position 106 that does have a terrible bite of RAM,
But its still stuffed for running full on coz its got 256 cpu/threads to play with . . . . .
That would help keep the house warm
Don't fancy the lecky bill though :}

Well, I WAS number 29 in this project worldwide. If they are now only allowing 8 gig ram per task, I think I will quit, and run WCG. I can't have my 1100 threads of EPYC going idle. I have a dual 7601 EPYC system and for some reason, it only has 5 tasks for 256 gig ram. I have a contributor on my team with a dual 7742, so 256 threads, and 256 gig ram. He is only getting 30 tasks, and both of use are almost idle.

Whatever they did the require virtualbox was a mistake. All of Anandtech may quit this project because of this.

---

Whatever they did the require virtualbox was a mistake. All of Anandtech may quit this project because of this.

It may be required for the science, even though they are not using much of it now. But maybe they are planning bigger payloads later?
However, you are right in wanting to keep your machine busy. If you can find better work for it, go to it.

But I just increased the memory on my Ryzen 3950X to 128 GB, so that I could run 16 full cores on the pythons. That is full enough.
I am willing to do without the benefit of virtualization for now.

---

Whatever they did the require virtualbox was a mistake. All of Anandtech may quit this project because of this.

It may be required for the science, even though they are not using much of it now. But maybe they are planning bigger payloads later?
However, you are right in wanting to keep your machine busy. If you can find better work for it, go to it.

But I just increased the memory on my Ryzen 3950X to 128 GB, so that I could run 16 full cores on the pythons. That is full enough.
I am willing to do without the benefit of virtualization for now.

That should work if the tasks are not written to require virtualization. However, I believe that they do require virtualization, at least under Windows.

That should work if the tasks are not written to require virtualization. However, I believe that they do require virtualization, at least under Windows.

I probably should have said that I am not using virtual cores. Virtual cores just makes more efficient use of a full core by running two threads on it at once. However, each work unit on a virtual core still requires the full (8 GB) amount of memory.

I have been running 12 work units on a Ryzen 3900X for almost a week on 50% of the (virtual) cores, so each work unit effectively gets a full core.
So I am willing to use only the full cores and lose the benefits of the virtual cores when I say that I am willing to give up the benefits of virtualization, in order to save on memory.

The use of virtual cores is not the VirtualBox type of virtualization, which it requires even on Linux.

---

Whatever they did the require virtualbox was a mistake. All of Anandtech may quit this project because of this.

It may be required for the science

No, it's not.
Python is just a language, although unlike the various forms of C & others, it's an interpreted language, not compiled.

I'm guessing they're using it as it's meant to be a lot easier to use than most other high level languages- so it'd be good for non-programmers to develop applications with (eg scientists), and the use of VirtualBox to run it is just the easiest way of getting it to run on multiple Operating Systems without having to code for Python on each different OS and the resulting quirks that would require debugging due to the different behaviour of the code on different OSes (even though the same conde on any given Python interpreter should give exactly the same result on the OS it's running under, different OSes would have different ways of doing things, so that's not how things would actually work- eg Rosetta 4.xx applications are each written for the OS (Android, Windows, Linux, OSX/OSX on M1 etc) as while the underlying procedures, algorithms etc would be the same, getting them all to work as intended requires the programme to be written for each OS specifically).

Ideally they would just produce Python applications for each OS like they do for the present Rosetta 4.20 applications- but it would still require people to manually install Python on their Windows systems (and some Linux distros don't include it as standard either) in order for them to be able process Python tasks.

---

Grant
Darwin NT

That is a nice explanation, but any use of VirtualBox might be done with a native implementation, whether using python or otherwise.
So it is required for us in order to do their science, rather than in less convenient ways.

---

I have an EPYC 7742 with 128 gig ram. When I added virtualbox (now required I guess) now I only get 16 tasks, the machine is almost idle. What needs to be done to fix this ?

Running cinnamon mint 19 (ubuntu Linux)

There *IS* a way to make this work, but it's complicated. Two ways, actually.

As others have said, the tasks are set up such that BOINC must provide 7.5 GB of memory for each task. They don't actually need that much, and don't actually use that much. If, for example, you recompiled BOINC and turned off that restriction (which is something you CAN do), the tasks would all run just fine.

If you're not a programmer and don't want to change the BOINC software, what you can do is Google the instructions for running multiple BOINC instances on the same computer. Instead of running the normal single BOINC instance, run 8 instances. Each instance will think it's running on a computer with 128 GB. Each of the 8 instances will therefore be able to run 16 tasks. Set the memory limits in the preferences to 100%.

It's a nuisance to do. You have to change cc_config.xml to enable multiple BOINC clients. You have to explicitly start each BOINC instance on a different port number. You have to control each instance individually, again using that unique port number. Finally, if you use WUProp, you need to tell it about the port number with app_config.xml. You should probably also set each instance to use 12.5% of the CPU in case regular tasks are available. (6.125% if the CPU is hyperthreaded and has 256 threads).

EDIT: It would, of course, just be much easier if the project lowered the memory limit. It's just a single setting in the work generator and won't affect how the tasks actually run. I'm not privy to the thought process of the admins, nor am I aware of all the facts, but I'd guess the odds are 50/50 that they lower the memory requirements to something more reasonable at some point. 500 MB seems reasonable to me, based on what I've seen.

---

Want to find one of the largest known primes? Try PrimeGrid. Or help cure disease at WCG.

I have an EPYC 7742 with 128 gig ram. When I added virtualbox (now required I guess) now I only get 16 tasks, the machine is almost idle. What needs to be done to fix this ?

Running cinnamon mint 19 (ubuntu Linux)

There *IS* a way to make this work, but it's complicated. Two ways, actually.

As others have said, the tasks are set up such that BOINC must provide 7.5 GB of memory for each task. They don't actually need that much, and don't actually use that much. If, for example, you recompiled BOINC and turned off that restriction (which is something you CAN do), the tasks would all run just fine.

If you're not a programmer and don't want to change the BOINC software, what you can do is Google the instructions for running multiple BOINC instances on the same computer. Instead of running the normal single BOINC instance, run 8 instances. Each instance will think it's running on a computer with 128 GB. Each of the 8 instances will therefore be able to run 16 tasks. Set the memory limits in the preferences to 100%.

It's a nuisance to do. You have to change cc_config.xml to enable multiple BOINC clients. You have to explicitly start each BOINC instance on a different port number. You have to control each instance individually, again using that unique port number. Finally, if you use WUProp, you need to tell it about the port number with app_config.xml. You should probably also set each instance to use 12.5% of the CPU in case regular tasks are available. (6.125% if the CPU is hyperthreaded and has 256 threads).

EDIT: It would, of course, just be much easier if the project lowered the memory limit. It's just a single setting in the work generator and won't affect how the tasks actually run. I'm not privy to the thought process of the admins, nor am I aware of all the facts, but I'd guess the odds are 50/50 that they lower the memory requirements to something more reasonable at some point. 500 MB seems reasonable to me, based on what I've seen.

Either is too much for me. I have had bladder cancer and lost. I am still going to the hospital weekly or more, and having surgeries bi-annually. I don't have time to mess with all that. I have 1100 cores, and 8 EPYC boxes, 3 of them are 64 core 7742's. They used to do Rosetta a lot (I am number 29 worldwide), but now all of that will be put on WCG. If Rosetta wants my computers, they need to make it easy to use, like all other BOINC projects.

Edit: as to memory, they should let BOINC do it, and also, NO virtualbox. It worked fine for years before, not now.

---

Sorry to hear about your cancer.
I wish you nothing but the best.

---

How can I limit the number of simultaneous R@H tasks? I have 64GB installed, and R@H is consuming the lot, making other projects wait for memory..10 R@H jobs are running just now, and using all the memory. I'd prefer to limit them to, say, 4, but unlike other projects I can't see a way to influence this.

---