Alsao make sure hyperv is disabled with
bcdedit /set hypervisorlaunchtype off

One of your Vbox tasks shows this error in the log: Failed to create the VirtualBox object!

2022-02-17 17:27:44 (8792): Detected: VirtualBox VboxManage Interface (Version: 6.1.12)
2022-02-17 17:27:51 (8792): Error in host info for VM: -2147024891
Command:
VBoxManage -q list hostinfo
Output:
VBoxManage.exe: error: Failed to create the VirtualBox object!
VBoxManage.exe: error: The object is not ready
VBoxManage.exe: error: Details: code E_ACCESSDENIED (0x80070005), component VirtualBoxClientWrap, interface IVirtualBoxClient

2022-02-17 17:27:51 (8792): WARNING: Communication with VM Hypervisor failed.
2022-02-17 17:27:51 (8792): ERROR: VBoxManage list hostinfo failed

Maybe someone else can help him with this?

It might be related to #3 here:

https://boinc.bakerlab.org/rosetta/forum_thread.php?id=14904&postid=104693

I can't get Rosetta VBox tasks working on some machines regardless of OS or settings, whilst other project's VBox tasks run fine. The things they seem to have in common are Intel CPUs and DDR3 (actually all run DDR3L), but that might be coincidence.

---

If you aren't receiving Python work, go to your Rosetta account, list of computers, click on details on whatever computer you wish to run the Pythons on, scroll down and click allow where it says "allow VirtualBox jobs". Then try again.

Thanks! That was the missing step I needed to get a VM to download.

Of the three initial "rosetta python" tasks downloaded, all three failed with "Computational error" after 15 seconds. So it doesn't look like Python will be running smoothly on my system anytime soon. :(

You need to set virtualisation to "on" in your BIOS

Also, this is relevant, though I haven't got it set up on my Intel, only on my AMD PC and I think they do it differently.
Someone will be along in a minute to say what it is on a 9900K (which I'm hoping to upgrade my 8350K to shortly, or to a 9700K, so it'll be useful for me too)

Also make sure hyperv is disabled with
bcdedit /set hypervisorlaunchtype off

---

My movingstub tasks fail also.

Still movingstub errors.
No one is watching the queue or the forum
And movingstub, obviously, was not tested on Ralph

---

My movingstub tasks fail also.

Still movingstub errors.
No one is watching the queue or the forum
And movingstub, obviously, was not tested on Ralph

I don't think they were even tested at all by whoever came up with them- 100% failure rate so far.

---

Grant
Darwin NT

Someone has to speak up for the innocent movingstubs!

I have 2 movingstub_gzm1_minimize_ tasks underway, both on Linux. One for 8 minutes, the other for 5 hours.

Hope they're not saving the fail until the end of processing. If something is going to fail, I *generally* prefer it to happen early on in the proceedings.

Someone has to speak up for the innocent movingstubs!

I have 2 movingstub_gzm1_minimize_ tasks underway, both on Linux. One for 8 minutes, the other for 5 hours.

Hope they're not saving the fail until the end of processing. If something is going to fail, I *generally* prefer it to happen early on in the proceedings.

That’s 2 Linux systems processing ok, I have 20 success with 0 fail but mine only run for 3 hours before completing.

Maybe you have set Target CPU run time to 2 hours?

That’s 2 Linux systems processing ok, I have 20 success with 0 fail but mine only run for 3 hours before completing.

Yep, looks like they instantly crash and burn only on Windows systems.
Quite a few of the last batches have only run for 3 hours or so.

---

Grant
Darwin NT

I only run on one Linux and one Windows 7 atm and all the Windows error out within 20 seconds. All the Ubuntu ones were good until now. The 14 movingstubs units ran the requested 8 hours on my 3900X. I can see that a new team member successfully completed his on Linux, but all were 3 hours. W3670. CPU and OS related?

Empty by mistake. Can’t delete it….

Empty by mistake. Can’t delete it….

Next time just go back and click edit, delete the contents and double space blanks and post. The post will self erase.

Forgot who told us this awhile back, but very useful to know.

Everything was running great until yesterday afternoon. Then every task I downloaded from Rosseta stated "Computation Error." Nothing changed on my computer. All other projects are running fine.
What happened?

---

All movingstub tasks crash on windows
you can sort by name and terminate all of them and update until you get other task family

All movingstub tasks crash on windows
you can sort by name and terminate all of them and update until you get other task family

+1
I've done on my Win11 machines

---

I have had a number of failures on the Rosetta 4.20 in the last couple of days, but all of the "movingstub" ones have worked.
It is probably because I am on Linux (Ubuntu).
https://boinc.bakerlab.org/rosetta/results.php?userid=52455&offset=0&show_names=0&state=4&appid=

---

Maybe you have set Target CPU run time to 2 hours?

No, my target run time is, and always has been, set to default.

First Rosie thinks it needs more space, now SiDock does as well.
You think there is a bug in BOINC maybe created by Vbox type tasks?
131 used and 334 available out of a 465 partition on a 500 GB drive.

Maybe there is a bug with boinc disk space measurements?
Open an issue at https://github.com/BOINC/boinc/issues