Posts by Jonathan

1) Message boards : Number crunching : Problems and Technical Issues with Rosetta@home (Message 103886)
Posted 23 Dec 2021 by Jonathan
Post:
Check the details tab of your individual computer(s) on this website and see if "VirtualBox VM jobs" is showing Skip. If you want VM / Python jobs, that has to say Allow
2) Questions and Answers : Windows : "rosetta python projects needs more disk space" (Message 103880)
Posted 23 Dec 2021 by Jonathan
Post:
No computers listed under your username. What applications are you running and any other projects? 10Gb is very small for a resource.
You need to provide more details on your setup.
3) Message boards : Number crunching : Problems and Technical Issues with Rosetta@home (Message 103830)
Posted 15 Dec 2021 by Jonathan
Post:
Those task have hung or the processing inside the VM crashed. Just abort the work unit(s).
If you don't want to run the VM tasks here, and just legacy tasks, you go to your individual computer details and look at the bottom where it says "VirtualBox VM jobs" Just turn off the option. The button is only visible if you have Virtual Box installed and the project was allowing you those tasks.
4) Message boards : Number crunching : Increase deadline on rosetta python projects 1.03 (vbox64) (Message 103774)
Posted 8 Dec 2021 by Jonathan
Post:
You shouldn't run Virtual Box on a machine with only 4Gb of RAM. Stick to conventional Boinc projects with low memory requirements.
The Python VMs are created with 6Gb of RAM and seem to use at least 7Gb per the properties in Boinc Manager.

If you wish to keep Virtual Box and just not run the Python VM tasks here, do the following. Go to your computers info on this webpage, hit Details and scroll to the bottom. You should see a button next to VirtualBox VM jobs. Just click on Skip and that will mark your computer so it doesn't receive the Python VM jobs. The button is only visible if the project thinks you can run the VMs and have Virtual Box set up.
5) Message boards : Number crunching : Problems and Technical Issues with Rosetta@home (Message 103737)
Posted 5 Dec 2021 by Jonathan
Post:
I notice the same thing with the wrapper for Atlas tasks.
Logs for my completed tasks there show "Detected: vboxwrapper 26197". File is "vboxwrapper_26198ab7_windows_x86_64"
6) Message boards : Number crunching : Problems and Technical Issues with Rosetta@home (Message 103735)
Posted 5 Dec 2021 by Jonathan
Post:
I am showing a date modified of 12/3/2021 for the wrapper.
It is odd. The properties of the file and the messages return 26202 but it is named 26203
They didn't change the file properties and version from BOINC? I just downloaded the linked zip from that post and checked it also.

I have it running Cosmology VMs and it is more stable on my old computer. Running 4 work units of 2 cores each on an Intel i7 920. It's running at 100% and not complaining.
7) Message boards : Number crunching : Problems and Technical Issues with Rosetta@home (Message 103732)
Posted 5 Dec 2021 by Jonathan
Post:
Rosetta is already using that wrapper version, vboxwrapper_26203_windows_x86_64.exe on windows.
8) Message boards : Number crunching : Problems and Technical Issues with Rosetta@home (Message 103710)
Posted 4 Dec 2021 by Jonathan
Post:
The current VM work is using about 3Gb for the work units starting with 'aa'. The 'boinc_cages_IL' is running about 6Gb. You should be able to run camb_boinc2docker VMs from Cosmology at home as those only use 2Gb. You just need to set your preferences to 1 or 2 for Max # CPUs so it only assigns one or two cores to each work unit and VM.
It's probably best if you just stick to conventional Boinc work units as they behave better and share resources as they run at a lower priority. Virtual Box task run at a normal priority.
9) Message boards : Number crunching : Problems and Technical Issues with Rosetta@home (Message 103708)
Posted 4 Dec 2021 by Jonathan
Post:
trevG, if your computer has only 4Gb of RAM, you don't have enough to run the VM tasks.
10) Message boards : Number crunching : Problems and Technical Issues with Rosetta@home (Message 103707)
Posted 4 Dec 2021 by Jonathan
Post:
You got Blacklisted
11) Message boards : Number crunching : Problems and Technical Issues with Rosetta@home (Message 103698)
Posted 4 Dec 2021 by Jonathan
Post:
I aborted all the newer python jobs that started with 'aa'. I got a single 'boinc_cages_IL' job so I kept that one. That one runs fine. I set the computer to not receive VM jobs from Rosetta.
12) Message boards : Number crunching : Problems and Technical Issues with Rosetta@home (Message 103688)
Posted 3 Dec 2021 by Jonathan
Post:
It's using Rosetta preferences
RAM set to %75 in use and not in use. So can use 9 out of 12Gb. That seems correct as It has 3 tasks. It doesn't keep non running tasks in memory. that box is unchecked.

I think it is something inside the VM. I kind of got spoiled with the LCH Atlas tasks and being able to see the second and third terminals. One for tasks and one showing TOP
13) Message boards : Number crunching : Problems and Technical Issues with Rosetta@home (Message 103686)
Posted 3 Dec 2021 by Jonathan
Post:
Are you thinking of a different project that shows Virtual Box on the computer details page? I don't see it on either of the computer details for mine, nor on the two I check listed under you.
Virtual Box is working on both my computers but I have been sticking to 6.1 since it is supported by Virtualbox. Support was dropped for the earlier versions. I just don't load up my computers to 100 percent processor usage nor juggle too many concurrent VM tasks. These Python / Rosettas are brutal with creating almost 8 Gb images.

I just can't figure out why the one computer is having problems now as it was working with the previous python related tasks.
14) Message boards : Number crunching : Problems and Technical Issues with Rosetta@home (Message 103683)
Posted 3 Dec 2021 by Jonathan
Post:
Python tasks failing
Error posted inside VM is "Intel MKL FATAL ERROR: Error on loading function mkl_lapack_ps_mc3_dsytrf_l_small."
Stops right after it gives workunit name.

Computer is an old Intel I7-920. I get no cpu usage after hang.
I have removed and reattached project from a December 1 when this first started. I thought maybe it was bad files.

https://boinc.bakerlab.org/rosetta/results.php?hostid=6157362
15) Questions and Answers : Windows : Boinc demands VirtualBox (Message 103678)
Posted 3 Dec 2021 by Jonathan
Post:
Do you have Hyper-V turned on on the machine?
16) Questions and Answers : Windows : Boinc demands VirtualBox (Message 103658)
Posted 2 Dec 2021 by Jonathan
Post:
Where is boinc installed and complaining? Windows 10 or inside the running Virtual Box VM?

Instructions called VT-x orAMD-v
17) Message boards : Number crunching : Problems and Technical Issues with Rosetta@home (Message 103641)
Posted 1 Dec 2021 by Jonathan
Post:
What Boinc reports and what the VM is created with is two different things. I get about the same results as you looking at the Boinc task properties.
All the successful tasks were the previous Python versions. Started with "boinc_cages_IL_"

I haven't got a single, newer one to run yet. they all hang and when I call up the VM's screen the last line is
"Intel MKL FATAL ERROR: Error on loading function mkl_lapack_ps_mc3_dsytrf_l_small."

If you call up Virtual box and look at a VM, is you last line like that on the monitor? You just go to Machine - Detach GUI to close it afterwards.
18) Message boards : Number crunching : Problems and Technical Issues with Rosetta@home (Message 103639)
Posted 1 Dec 2021 by Jonathan
Post:
The created VMs still have the same Hard Disk and RAM set up as before. 8Gb HD and 6Gb RAM.
All tasks I had running had to be aborted. They weren't using any cpu cycles.

Is anyone successfully completing one?
19) Message boards : Number crunching : Why only one task running at the same time with Rosetta Python project 1.03 VBOX64 ? (Message 103607)
Posted 30 Nov 2021 by Jonathan
Post:
I checked the RAM setting in the running VM and it was set at 6144Mb. (6Gb). There may be different sizes of VMs by the project.
We really don't know what Rosetta@home has planned to fit inside the Python / VirtualBox tasks. They may have ran some VM images elsewhere and 6 - 8 Gb may have been needed.

Added link to completed work unit showing RAM assigned to VM
https://boinc.bakerlab.org/rosetta/result.php?resultid=1452114781
20) Message boards : Number crunching : Why only one task running at the same time with Rosetta Python project 1.03 VBOX64 ? (Message 103604)
Posted 30 Nov 2021 by Jonathan
Post:
The two computers listed under your name have 16Gb of RAM. The Virtual Box version of the app is using about 6Gb of RAM for the virtual machine, one cpu.
If you don't need Virtual Box for any other Boinc projects, you can uninstall it and run just regular Boinc projects fine.


Next 20



©2022 University of Washington
https://www.bakerlab.org