Weird

I think I just posted the long version of what you're getting in the "There's a max WU of 8 with Virtualbox" thread.
In short: yes, me too, exactly the same but on a 1Tb drive

1TB and YOU got an error?
I got into it with computer whats his name...so what did you and him figure out?
And you said 8 tasks..but 8 python or 8 in total?

Sidock: ok
TN-Grid: I got there and looked around a bit, but I didn't really understand what was going on tbh.
If you repeat what they say, I'm not sure I'll understand it any better. I know my limitations.
I'll persist here[/quote]

I had a look there as well. It's over my head...but I think its just a larger cellular form of this.
We are researching on the micro micro scale. They research on the gene level, quite a few steps up from this.
But at first glance it really didn't look that exciting.

I had a look there as well. It's over my head...but I think its just a larger cellular form of this.
We are researching on the micro micro scale. They research on the gene level, quite a few steps up from this.
But at first glance it really didn't look that exciting.

The tn-grid project is managed by the University of Trento, Helmut Mach Foundation and CNR (Italian National Research Council)
Here a description of the project.
They worked, in the past, with some model organism, with Vitis VInifera, and now with human genome, in project like, for example, colorectan cancer characterization
Here, for example, a publication from the project about drug repositioning.

Plus:
- no virtual machine
- optimized app for cpu (SSE-AVX)
- android app
- admins on forums

---

Looks like sidock is working again
https://www.sidock.si/sidock/forum_thread.php?id=189

Thanks to all for the responses about VirtualBox.

I installed and run BOINC from a mechanical hard disk that is separate from the SSD from which the Windows OS, specifically to reduce the constant writes I expected BOINC to be doing. So getting VirtualBox running on that same drive should not be a problem for the SSD.

At this point, the still don't understand is how to get the VM up and running in VirtualBox to begin with.

VirtualBox was installed at the same time as BOINC, using the combined BOINC + VB installer, so the two program versions should be the approved/compatible pairing. I can start VirtualBox separately, and it looks to be running OK, it just doesn't have any VMs loaded. From the BOINC Event Log, it knows that VirtualBox is available.

2/17/2022 10:44:30 AM | | Host name: DELL-XPS8930
2/17/2022 10:44:30 AM | | Processor: 16 GenuineIntel Intel(R) Core(TM) i9-9900K CPU @ 3.60GHz [Family 6 Model 158 Stepping 12]
2/17/2022 10:44:30 AM | | Processor features: fpu vme de pse tsc msr pae mce cx8 apic sep mtrr pge mca cmov pat pse36 clflush dts acpi mmx fxsr sse sse2 ss htt tm pni ssse3 fma cx16 sse4_1 sse4_2 movebe popcnt aes f16c rdrandsyscall nx lm avx avx2 vmx smx tm2 pbe fsgsbase bmi1 hle smep bmi2
2/17/2022 10:44:30 AM | | OS: Microsoft Windows 10: Professional x64 Edition, (10.00.22000.00)
2/17/2022 10:44:30 AM | | Memory: 31.81 GB physical, 40.31 GB virtual
2/17/2022 10:44:30 AM | | Disk: 931.39 GB total, 751.12 GB free
2/17/2022 10:44:30 AM | | Local time is UTC -5 hours
2/17/2022 10:44:30 AM | | No WSL found.
2/17/2022 10:44:30 AM | | VirtualBox version: 6.1.12


Is Rosetta@home supposed to downloaded and start a VM automatically? Or do I have to manually kick off the VM installation somehow? After reading countless forum posts for a few hours, I have seen lots of discussion about trying to get stuff to run correctly, and a few mentions of an image checksum being wrong so the VM apparently won't install, but haven't seen an explanation about how how the initial VM installation is supposed to work.

On my system the original tasks will download and run when they are available, but nothing seems to be happening as it relates to VirtualBox.

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.

---

Rosetta 4.2 work is back. Assuming the increase in the queue is 100% due to 4.2 work, it's a sizeable batch with over almost 3 million tasks.
Then again, we'll probably plough through it in an instant or it will get pulled by the devs since it has a 100% error rate so far on my laptop.

Edit: Ok, got some tasks that are all numbers on the name and those are running well so far.
100% error rate on the movingstub ones.

---

Movingstubs crash on my pc too.

My movingstub tasks fail also.

Sorted tasks by name, then suspended the non-movingstub ones. That forced all of the movingstubs to fail immediately, report back as failed (not canceled) and then download more good tasks.

I had to update project several times to get working tasks.
Rosetta gave me four good tasks and four bad tasks.

The Pcr work units are getting up me nose
Error at startup 20 seconds
17/02/2022 22:13:33 | Rosetta@home | Output file PcrV11AA_PcrV_111136_000009_extract_A_SAVE_ALL_OUT_2906118_477_1_r1856145221_0 for task PcrV11AA_PcrV_111136_000009_extract_A_SAVE_ALL_OUT_2906118_477_1 absent
Anyone else having problems with them ?
edit - had a look back up the thread , its not just me.

Anyone else having problems with them ?
edit - had a look back up the thread , its not just me.

I don't know if they are the same on Windows as Linux, but I have had my share.
https://boinc.bakerlab.org/rosetta/results.php?hostid=6176524&offset=0&show_names=0&state=6&appid=

I really want only the pythons, but they don't allow you to select them.

---

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 with "Computational error" after 15 seconds. So it doesn't look like Python will be running smoothly on my system anytime soon. :(

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.