I keep getting this error.
I run LHC ATLAS on Vbox and I am trying to run this project as well.
But if I run 2 tasks from this project (with or without ATLAS) I get this error message.

I have searched all of the web for information on this and I can find nothing that explains a solution to this error or what is causing it. Lots of generic answers, but nothing specific.

I just set my project settings to 1/1 to try and get some stable work done.
2/2 does not work very well. 3/3 forget it.

You can usually solve it by going back to VirtualBox 5.2.44, at least on most projects.
https://www.virtualbox.org/wiki/Download_Old_Builds_5_2

You will still get a lot of invalids, but that is just the nature of the scientific work and not a VBox problem.

I am using VBox 6.1.28 on three projects, this one, rosetta python and LHC@home. When I get the "unmanageable" error I simply exit BOINC and restart it. My BOINC is 7.16.20.
Tullio

---

I am using VBox 6.1.28 on three projects, this one, rosetta python and LHC@home. When I get the "unmanageable" error I simply exit BOINC and restart it. My BOINC is 7.16.20.
Tullio

That's what I have been doing. But its annoying.
I am trying to find out where this projects sweet spot is with my machine other than a 1/1.

You can usually solve it by going back to VirtualBox 5.2.44, at least on most projects.
https://www.virtualbox.org/wiki/Download_Old_Builds_5_2

You will still get a lot of invalids, but that is just the nature of the scientific work and not a VBox problem.

Not really sure about going that far back. But I went back two flavors in 6.1 to .24
What's the point of building Vbox jobs if they go into unmanageable all the time?
I don't have all day to sit here and restart BOINC everytime.
I thought this project was a little more advanced.

If you don't listen to what I say, you are on your own.

If you don't listen to what I say, you are on your own.

Well being that doesn't work..i guess i'll roll back to 5.
Nothing to lose.

If you don't listen to what I say, you are on your own.

Well being that doesn't work..i guess i'll roll back to 5.
Nothing to lose.

5.2.44 installed. Stable at 40+ minutes.
But now off to work.

How do you get BOINC to report the tasks immediately and download a new one?

Neither LHC@home nor rosetta python.which requests 6144 MB of RAM, ever signal an "unmanageable VM job". Only QuChem does and I kill and restart BOINC.
Tullio

---

Neither LHC@home nor rosetta python.which requests 6144 MB of RAM, ever signal an "unmanageable VM job". Only QuChem does and I kill and restart BOINC.
Tullio

I think Master Jim is right (as usual) about rolling back to 5.2.xx
Things are running smoothly now with each task taking just a hair over 2 hrs to run.
LHC and WCG are working just fine as well.

I quit RAH...you probably saw my posts.
My system got blacklisted by the python scheduler, part of the slash and burn to solve problems.
Then 4.2 doesn't have any work or very little on and off, so I bailed after 15 years.

My RAC is now 2955 yet I am out of the credits list. My last position was 40.
Tullio

---

Still absent, with 2 tasks running and 13 ready to run, none "unmanageable".
Tullio

---

My RAC is now 2955 yet I am out of the credits list. My last position was 40.
Tullio

Oh....I see your problem.
Your running 6.1.28.
This project does not like that.
Jim already pointed that out.
You need to roll back to 5.2.44

"You can usually solve it by going back to VirtualBox 5.2.44, at least on most projects.
https://www.virtualbox.org/wiki/Download_Old_Builds_5_2" - Jim1348

Once I rolled back everything runs fine. Even LHC ATLAS does not mind it.[/url]

Now I am back in position 36. I am running also LHC@home and Rosetta python on the same VBox version. On "Nature" I've read tha Rosetta is RoseTTA and makes use of AI, following AlphaFold2 by Deep Mind (Google).:
Tullio

---