21) 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
22) Forums : Technical Support : Won't fetch camb_boinc2docker tasks (Message 22581)
Posted 7 Jul 2020 by Jonathan
Post:
FYI, VirtualBox 6.0 and 5.2 versions are only supported until July 2020 per the Virtual Box website. It will still work afterwards but no more updates.
If you need to limit the number of cores over computers that aren't similar in number of true cores, use the app_config.xml method you linked. Set no new tasks. cancel pending tasks or let them finish. Create or edit your app_config.xml and then restart Boinc Manager. Allow new tasks. Any download tasks should now use the configuration along with the correct number of cores set. If you have computers with identical core counts, you can just set the cosmology at home preferences concerning number of tasks and max # CPUs.

Link to VirtualBox website page showing EOL of support
https://www.virtualbox.org/wiki/Downloads
23) Forums : Technical Support : Unmanageable restart (Message 22578)
Posted 7 Jul 2020 by Jonathan
Post:
I looked at a few of your returned and valid results. You are assigning eight cores to a work unit. These problems happen with the newer Virtual Box versions for some reason. The computer is too busy and the virtual box wrapper can't communicate with the virtual machine in a timely manor and it causes this error. The wrapper runs at a lower priority than the VM.
You can try setting your cosmology at home project preferences to use less cores. (Max # CPUs). I have mine set to run two workunits of 4 cpus each and I still run into the error every so often.
24) Forums : Technical Support : Won't fetch camb_boinc2docker tasks (Message 22576)
Posted 2 Jul 2020 by Jonathan
Post:
Hyper-v and Virtual Box don't get along. You have to disable Hyper-V to run this project. Stick to non Virtual Box Boinc projects if you require Hyper-V on your machine.
25) Forums : Technical Support : What happened to the points. Lower the last 3 days. (Message 22550)
Posted 5 Jun 2020 by Jonathan
Post:
I just have been getting the postponed VMs every so often so my machine quits crunching for a bit until I restart Boinc Manager or let it go for over 24 hours. Our applications haven't changed for years. No idea why it changed.
26) Forums : Technical Support : What happened to the points. Lower the last 3 days. (Message 22544)
Posted 3 Jun 2020 by Jonathan
Post:
Your average credits or per work units credits? Mine seems normal on both. Shorter run and cpu time shows less credits per work unit.
27) Forums : Technical Support : WU CPU maxed out (Message 22538)
Posted 1 Jun 2020 by Jonathan
Post:
It's a problem in counting real cores versus SMT/hyperthreading. You can fix it by setting the project preferences to eight or less cores per workunit or you can use the app_config.xml method to see if you can get a 12 core or more work unit to complete.
I don't know of any of the Virtual Box projects that do what you want.
28) Forums : Technical Support : WU CPU maxed out (Message 22536)
Posted 1 Jun 2020 by Jonathan
Post:
All you had to do was change the values in the provided app_config.xml
29) Forums : Technical Support : WU CPU maxed out (Message 22533)
Posted 29 May 2020 by Jonathan
Post:
camb_boinc2docker workunits set to use 4cpus run between 6 - 7 minutes on my Ryzen 2700. I really doubt you would want any higher than eight cpus. I don't know if the work units will even scale higher than eight. Attaching my app_config.xml if you wish to play around. Set to run 3 concurrent work units with 4cpu cores each.

<app_config>
    <app>
        <name>camb_boinc2docker</name>
        <max_concurrent>3</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>
30) Forums : Technical Support : Postponed (Message 22530)
Posted 28 May 2020 by Jonathan
Post:
Grindylow, thanks for showing your computer and tasks.
The three tasks you returned and that got validated were using 2 cpus in the VM. I can tell by looking at the task details run time vs the cpu time listed. You just haven't had a single cpu VM run and complete yet. I also think you are getting hit by a Boinc logging issue as it looks like part of your logs aren't reported on the completed task.

In Boinc Manager, go to Options, then Event Log Options. Make note of the default items that are selected. Check or uncheck an item, hit Apply and then you can uncheck or check the item again and hit apply. I hope this causes your log to populate more of the info for the tasks. My logs start with the section I am posting below. It shows the number of cpus assigned to the VM, the RAM, etc. It is helpful in seeing how you have your settings for the tasks.

Your computer is quite low on RAM and each of the camb_boinc2docker tasks use 2 Gb, no matter how many cpus are assigned to a VM. I don't think you will ever be able to run more than one at a time and you may not be able to run other projects concurrently due to memory.

My logs start like this for a task.
<core_client_version>7.16.5</core_client_version>
<![CDATA[
<stderr_txt>
2020-05-27 18:49:19 (14908): vboxwrapper (7.9.26200): starting
2020-05-27 18:49:19 (14908): Feature: Checkpoint interval offset (292 seconds)
2020-05-27 18:49:19 (14908): Detected: VirtualBox VboxManage Interface (Version: 6.1.6)
2020-05-27 18:49:19 (14908): Detected: Minimum checkpoint interval (600.000000 seconds)
2020-05-27 18:49:20 (14908): Create VM. (boinc_19c258507036a2ec, slot#2)
2020-05-27 18:49:20 (14908): Updating drive controller type and model for desired configuration.
2020-05-27 18:49:20 (14908): Setting Memory Size for VM. (2048MB)
2020-05-27 18:49:21 (14908): Setting CPU Count for VM. (4)
2020-05-27 18:49:21 (14908): Setting Chipset Options for VM.
2020-05-27 18:49:21 (14908): Setting Boot Options for VM.
2020-05-27 18:49:21 (14908): Setting Network Configuration for NAT.
2020-05-27 18:49:22 (14908): Enabling VM Network Access.
2020-05-27 18:49:22 (14908): Disabling USB Support for VM.
2020-05-27 18:49:22 (14908): Disabling COM Port Support for VM.
2020-05-27 18:49:23 (14908): Disabling LPT Port Support for VM.
2020-05-27 18:49:23 (14908): Disabling Audio Support for VM.
2020-05-27 18:49:23 (14908): Disabling Clipboard Support for VM.
2020-05-27 18:49:23 (14908): Disabling Drag and Drop Support for VM.
2020-05-27 18:49:24 (14908): Adding storage controller(s) to VM.
2020-05-27 18:49:24 (14908): Adding virtual ISO 9660 disk drive to VM. (vm_isocontext.iso)
2020-05-27 18:49:24 (14908): Adding VirtualBox Guest Additions to VM.
2020-05-27 18:49:24 (14908): Adding network bandwidth throttle group to VM. (Defaulting to 1024GB)
2020-05-27 18:49:25 (14908): Enabling shared directory for VM.
2020-05-27 18:49:25 (14908): Starting VM using VboxManage interface. (boinc_19c258507036a2ec, slot#2)
2020-05-27 18:49:29 (14908): Successfully started VM. (PID = '15372')
2020-05-27 18:49:29 (14908): Reporting VM Process ID to BOINC.
2020-05-27 18:49:34 (14908): Guest Log: BIOS: VirtualBox 6.1.6
31) Forums : Technical Support : Postponed (Message 22529)
Posted 26 May 2020 by Jonathan
Post:
The use 50% of cpus setting is for all projects under Boinc. If you have two cores, Boinc would only run on one of them. Setting the Cosmology project preferences to use one max cpu and max one task is setting it to run a task that uses one cpu in the virtual machine and only runs a single task concurrently. It will still download multiple tasks but only one should run at one time. This can also be controlled by using the 'app_config.xml' method explained in the FAQ section.

When you set 'no new tasks' and abort all Cosmology at home tasks you have you were clearing out the ones that were set to use two cpus per virtual machine. You have your computers hidden so I can't look at your computer details and I can't look at the logs for returned tasks.

You can run other projects at the same time and you don't have to abort any work units or tasks manually.

The camb_boinc2docker task needs to run to completion as it doesn't checkpoint. This isn't a problem as they run so quickly. If you exit Boinc Manager and tell it to exit all tasks, when it starts up again you will notice the camb_boinc2docker task, that was postponed, will have to start computing at the beginning again.

I was hoping to get your Cosmology task running using a single cpu in a single task and then try adding the other projects back into the mix. Are your other projects regular Boinc or do they use Virtual Box also? I don't think you will be able to run more than one VM related project at a time due to your computer and Virtual Box and the Boinc virtual box wrapper being fickle.

I just set my AMD computer back to run camb_boinc2docker tasks here. You should be able to click my name in the forum and browse my computers and the tasks to see what info is shared when they aren't hidden.
32) Forums : Technical Support : Use of Virtual Box (Message 22527)
Posted 26 May 2020 by Jonathan
Post:
I am not sure what you are talking about on transfers and tasks but, Computer 420741 seems to be running fine and returning tasks. It also has a normal amount of errors, around 1-2%. Your other listed computer also shows valid tasks.

https://www.cosmologyathome.org/results.php?hostid=420741
33) Forums : Technical Support : Postponed (Message 22526)
Posted 26 May 2020 by Jonathan
Post:
Set no new tasks and then abort any tasks you have from here.
Easiest way to change to single cpu tasks is change your Cosmology@home preferences for this project.
Set Max # jobs to 1 and Max # CPUs to 1. You should get the new preferences when you allow new tasks and request and update on the project.
You could also use the app_config.xml method listed in the FAQ section.

Your postponed jobs will start back up on their own after about 24 hours but, most likely, will get stuck again. You probably can run one, single cpu VM task and a regular BOINC task. Your tasks starting and stopping is due to your general preferences on ram or cpu usage.
34) Forums : Technical Support : 8 computation errors, after running 7+ hours per task? (Message 22521)
Posted 23 May 2020 by Jonathan
Post:
camb_legacy is a regular Boinc task. camb_boinc2docker requires Virtual Box to run.
35) Forums : Technical Support : WU CPU maxed out (Message 22520)
Posted 23 May 2020 by Jonathan
Post:
That number is the max per work unit. Set it to eight and each task will use eight cpus. You will want to set no new tasks for the project and abort any tasks you have. I usually exit Boinc Manager and all running tasks and then open it back up again after making changes to make sure they get read. Once you allow new tasks, it should read the preferences and get tasks.
36) Forums : Technical Support : Postponed (Message 22517)
Posted 21 May 2020 by Jonathan
Post:
Suspend your other projects and see if it Cosmology runs to completion. I think your computer is just too 'busy'. The VM tasks run at a higher priority than the normal Boinc tasks. The Virtual Box wrapper used by the projects runs at a lower priority and can't communicate with Boinc quickly enough and causes that error. I am not sure if running on an SSD or NVMe would help because they are faster with communications. You could also try setting processor usage to 75% but then you would only use 3 out of 4 cores for Boinc projects.
37) Forums : Technical Support : Postponed (Message 22512)
Posted 17 May 2020 by Jonathan
Post:
372173 is currently showing VM extensions disabled and is failing all camb_boinc2docker work units. Check that it is on in the Bios. My AMD gets disabled with every Bios update. If it is enabled in Bios, check the FAQ section for a flag that may be set and still causing the error.

You can set and individual computer to run single cpu work units using the app_config.xml method. Explained in the FAQ section a little bit. I am attaching the code below if you wish to try it. Set for a single, concurrent work unit and a single cpu. It is written to only control the camb_boinc2docker task.
Set no news tasks for Cosmology on that computer. Abort and/or return all work units then exit Boinc Manager and all running work units. You can create the app_config.xml file per the FAQ and place in the correct directory. It should grab new work units once you start Boinc and allow new tasks.

<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>1</avg_ncpus>
    </app_version>
</app_config>
38) Forums : Technical Support : Postponed (Message 22510)
Posted 16 May 2020 by Jonathan
Post:
Melvin, you can try to set the same project preferences as above to get one work unit running. You might only be able to run single cpu work units on that computer, 420649. If the single cpu work units works, you could increase the Max # of jobs later.
39) Forums : Technical Support : Postponed (Message 22509)
Posted 16 May 2020 by Jonathan
Post:
Ardis, set no new tasks for Cosmology, abort all your Cosmology tasks then go to your Cosmology project preferences and set Max # of jobs to 1 and max # of cpus to 1. You can either exit Boinc and all tasks or just try updating the Cosmology project from the Boinc manager.
I am hoping you can get one VM task to run to verify your VirtualBox is working.
40) Forums : Technical Support : calculation errors (Message 22505)
Posted 8 May 2020 by Jonathan
Post:
If you update the bios, make sure to double check the processor virtualization. Mine defaults to off every time I update.


Previous 20 · Next 20