1) Forums : Technical Support : cannot attach Cosmology@Home with BOINC manager (Message 22728)
Posted 23 Dec 2020 by Jonathan
Post:
Was that computer a new host or were you just reattaching a previously attached one?

Host 430922 is showing
Created 27 Oct 2020, 16:29:31 UTC
2) Forums : Technical Support : 'VM job unmanageable' blocks download of new WUs (Message 22709)
Posted 1 Dec 2020 by Jonathan
Post:
You would need to cut down on the number of concurrently running virtual machines. Use the app_config.xml method to control the camb_boinc2docker application. It is explained a bit in the FAQ.

Your computer is just too busy dealing with all the virtual machines under VirtualBox and the BOINC / virtualbox wrapper isn't able to communicate in a timely manor and causes the errors.

Attached my app_config.xml below. I usually run two concurrent, four core work units. I have done three concurrent but then it runs into errors every so often.

<app_config>
    <app>
        <name>camb_boinc2docker</name>
        <max_concurrent>2</max_concurrent>
    </app>
    <app_version>
        <app_name>camb_boinc2docker</app_name>
        <plan_class>vbox64_mt</plan_class>
        <avg_ncpus>4</avg_ncpus>
    </app_version>
</app_config>
3) Forums : Technical Support : camb_boinc2docker problems (Message 22708)
Posted 1 Dec 2020 by Jonathan
Post:
Your Xeon computer is assigning 24 cores to a VM. Try setting it to eight or less cores using project preferences for Max # of cpus. You could also use the app_config.xml method to control the project and applications. It is covered in the FAQ a bit.

Pasted my current app_config.xml below. Just change the numbers to suit what you want.

<app_config>
    <app>
        <name>camb_boinc2docker</name>
        <max_concurrent>2</max_concurrent>
    </app>
    <app_version>
        <app_name>camb_boinc2docker</app_name>
        <plan_class>vbox64_mt</plan_class>
        <avg_ncpus>4</avg_ncpus>
    </app_version>
</app_config>
4) Forums : Wish list : WU Limits (Message 22703)
Posted 23 Nov 2020 by Jonathan
Post:
What do you have set for your preferences as a work cache? Preferences then Other. Running other projects?

Store at least 0.1 days of work
Store up to an additional 0.5 days of work
5) Forums : Technical Support : I have troubles creating a new team ! (Message 22700)
Posted 15 Nov 2020 by Jonathan
Post:
If it is a cross project Boinc team, that may be disabled on purpose. If it is just a team for Cosmology@home, I don't think anyone knows as it has been brought up many times in the forums.

https://boinc.berkeley.edu/teams/
6) Forums : Technical Support : immediate SIGSEGV on Ubuntu 20.04 (Message 22699)
Posted 15 Nov 2020 by Jonathan
Post:
You can try browsing through the checklist over at LHC@home.
https://lhcathome.cern.ch/lhcathome/forum_thread.php?id=4161

That forum is more active and the list may help.
7) Forums : Technical Support : VM job unmaneagable (Message 22681)
Posted 9 Nov 2020 by Jonathan
Post:
Computer appears short on RAM. What do you have set for preferences on memory usage?
You can try setting your preferences to max # of jobs = 1 and max # cpus to 2 and see if that will get one task running. You will need to set 'no new tasks' abort all current cosmology work and then change you web preferences for this project. When you allow new work, it should grab the new preferences and start up a single, two core task. Are you running any other projects?
8) Forums : Technical Support : work stops when network is disabled (Message 22680)
Posted 9 Nov 2020 by Jonathan
Post:
It looks like camb_legacy doesn't work on computer 431307. Look at the error logs on the returned tasks. camb_boinc2docker looks to be running normally.
9) Forums : Technical Support : Communication with VM Hypervisor failed (Message 22676)
Posted 3 Nov 2020 by Jonathan
Post:
Versions 5.2 and 6.0 are unsupported as of July 2020 per the virtualbox.org website.

https://www.virtualbox.org/wiki/Downloads

That error message essentially says the computer is to 'busy' to communicate with the boinc virtualbox wrapper in a timely manor. It has happened on all version of Virtual Box but the 5 version it happens a lot less. You can try the forums over at LHC at home as they have a lot more project that use virtual box and the forum is active to see if there are any fixes.
I had that problem when I would have too many VMs running at one time and the data directory was on a conventional hard disk. I use the app_config.xml method to control the number of concurrent tasks along with the number of cpus assigned to each VM. I had to go down to using only 8 cores total and skipping using up to 16 with hyperthreading/SMT on my platform. I can run two VMs of 4 cores each for Cosmology at home but if I allow 3 concurrent tasks, I sometimes see that error. I am on Virtual Box 6.1.16
10) Forums : Technical Support : Communication with VM Hypervisor failed (Message 22673)
Posted 2 Nov 2020 by Jonathan
Post:
Please post more details on your preferences, other projects and how many cpu cores are assigned to your camb_boinc2docker task when it is trying to start. Is the message "Postponed: Communication with VM Hypervisor failed" or are your tasks not starting the VM at all?
11) Forums : Technical Support : Issues with vbox when working (Message 22660)
Posted 1 Oct 2020 by Jonathan
Post:
I think you should be fine for now. I still don't see any tasks listed by your computer in the past 30 days. Are they completing okay? If you are running LHC@home VM projects, you will have to do the same thing for those. I usually only run one VM related task at a time.
12) Forums : Wish list : Hide Computers (Message 22659)
Posted 1 Oct 2020 by Jonathan
Post:
Cosmology@home preferences

Should Cosmology@Home show your computers on its web site?
13) Forums : Technical Support : Issues with vbox when working (Message 22656)
Posted 28 Sep 2020 by Jonathan
Post:
Your computer listing at Cosmology@home should be listing current assigned tasks. I want to try to get you new tasks and let you try an 'app_config.xml' set up to control the camb_boinc2docker application.

Set no new tasks for the Cosmology project in the Boinc Manager and then abort all related tasks for this project.

Open notepad and paste the following text into it and do a 'save as' using the name 'app_config.xml' and make sure to change the Save As Type drop down at the bottom of Notepad from 'Text Document' to 'All Files'. You will save it in the project data folder that may be currently hidden. Program Data is a hidden folder on Windows 10. My location is 'D:\ProgramData\BOINC\projects\www.cosmologyathome.org'. You can either choose to show hidden files in the file browser or just copy and past that location but change the drive letter to where you installed Boinc.

After doing all that, exit Boinc and all tasks, restart Boinc Manager and allow new tasks for this project. It should grab some work units and then try to run them. These should also allow your computer to show current assigned tasks. I set the configuration below to run a single camb_boinc2docker task that uses 6 cores. It should run pretty quick as I finish in 5.5 to 6 minutes on 4 cpus. You can always edit the numbers to allow more concurrent tasks or change the cpu counts but I don't think you can go higher than 6 in your case.

app_config.xml
<app_config>
    <app>
        <name>camb_boinc2docker</name>
        <max_concurrent>1</max_concurrent>
    </app>
    <app_version>
        <app_name>camb_boinc2docker</app_name>
        <plan_class>vbox64_mt</plan_class>
        <avg_ncpus>6</avg_ncpus>
    </app_version>
</app_config>
14) Forums : Technical Support : Issues with vbox when working (Message 22652)
Posted 27 Sep 2020 by Jonathan
Post:
I am just double checking that you are using Microsoft Hyper-V and have it enabled or did you mean AMD-V or SVM is enabled in your BIOS?
Try setting your preferences to run just the camb_leagacy tasks and make sure those work. If you are running any other projects, stop or suspend them temporarily. If you can complete a few tasks then you can switch to running only the camb_boinc2docker version and work out the VM problem. Set max # cpus to six or less in your case or you can use the 'app_config.xml' method to control number of concurrent tasks running or camb_boinc2docker and the number of cpus cores assigned to a single VM. Just a wild guess right now is that the VM is getting 12 cores assigned and it is messing with all your work units. You can look at the settings of the running VM in Virtual Box
15) Forums : Technical Support : Issues with vbox when working (Message 22650)
Posted 26 Sep 2020 by Jonathan
Post:
Your computer doesn't show when I use the link from your forum name. LHC@home has a checklist for VM related task by Yeti. Try working through that to see if it helps. Do you have Hyper-V enabled? That clashes with Virtualbox but there may be a work around.
I am guessing you have your computer under a different account than the one you are posting on the forums under. Please post a link to your current computer so we can look at tasks and any error messages.

Link to computers showing on your forum account.
https://www.cosmologyathome.org/hosts_user.php?sort=rpc_time&rev=0&show_all=1&userid=1569122
16) Forums : Technical Support : Issues with vbox when working (Message 22647)
Posted 24 Sep 2020 by Jonathan
Post:
Your tasks are all showing as camb_legacy and not camb_boinc2docker. If you want to run the VM versions (camb_boinc2docker) you need to select that in your cosmology@home preferences.

Max # CPUs controls how many cpu cores are assigned to a VM. I have mine set to 4 on a Ryzen 1700 that has eight true cores.
Max # of jobs controls the number of concurrent jobs, I think?

You will need to set no new tasks on the project, abort all current cosmology work units and then make your preference changes on this website. You can also check out the FAQ section. When you allow new work, you should get camb_boinc2docker work units with your new settings.
17) Forums : Technical Support : Camb_boinc2docker 2.05 jobs all stop at 18 seconds with Computation Error (Message 22600)
Posted 14 Aug 2020 by Jonathan
Post:
I just checked on that link I posted a bit more. It looks like you have to run VirtualBox VMs using the Hyper-V Paravirtualization Interface. I am not sure if you will be able to run Boinc / VirtualBox projects as the project may set that in the VM image. Good luck and please post back your results
18) Forums : Technical Support : Camb_boinc2docker 2.05 jobs all stop at 18 seconds with Computation Error (Message 22599)
Posted 14 Aug 2020 by Jonathan
Post:
If Hyper-V is enabled, that should be the problem. You can try the link below for a possible solution or just try searching the web for something like 'Hyper-V VirtualBox problems'

https://www.how2shout.com/how-to/use-virtualbox-and-hyper-v-together-on-windows-10.html
19) Forums : Technical Support : memory and disk requirements? (Message 22587)
Posted 11 Jul 2020 by Jonathan
Post:
camb_boinc2docker work units will use 2Gb of ram for each running virtual machine. You can use the project preferences to control how many run concurrently and the number of CPUs assigned to a work unit.
If you need different settings for different computers on an account you will need to use the app_config.xml method from the FAQ section. You probably want to set CPUs between 4 and 8. You may have to pare back on concurrent work units depending on if you have trouble with "Postponed: VM job unmanageable, restarting later" errors.
I am not sure what the legacy application requires as I only run the camb_boinc2docker version.
20) Forums : News : Server upgrade planned for Dec 19 (Message 22585)
Posted 9 Jul 2020 by Jonathan
Post:
Did you mean "Science United" instead of "United Science"?
Did you connect your previous computer directly to Cosmology@home?
Are you using your Cosmology@home user and password or the Science United to attempt addition?

It suggests to detach from previously running project on their website.
https://scienceunited.org/intro.php


Next 20