Posts by Sandman192

InfoMessage
21) Message boards : Questions and problems : Can't get virtual work.
Message 113544
Posted 4 Feb 2024 by Sandman192
Can't get virtual work for Rosset or LHC. All I get is 0 New Tasks. I checked they both got task ready to send and I have both to get all work units. I suspend all other tasks just to have BOINC get Virtual work.
The hard pat is I get no message from Event Log on why I can't get Virtual work.
I got Mint to run on VirtualBox.
2/3/2024 7:34:47 PM | | Starting BOINC client version 7.24.1 for windows_x86_64
2/3/2024 7:34:48 PM | | Processor: 16 AuthenticAMD AMD Ryzen 7 7700X 8-Core Processor [Family 25 Model 97 Stepping 2]
2/3/2024 7:34:48 PM | | OS: Microsoft Windows 11: Professional x64 Edition, (10.00.22631.00)
2/3/2024 7:34:48 PM | | No WSL found.
2/3/2024 7:34:48 PM | | VirtualBox version: 7.0.6
2/3/2024 7:34:48 PM | | Config: use all coprocessors
2/3/2024 7:34:48 PM | | Config: open console window for VirtualBox applications
2/3/2024 7:34:48 PM | LHC@home | URL https://lhcathome.cern.ch/lhcathome/; Computer ID 10835631; resource share 100
2/3/2024 7:34:48 PM | Rosetta@home | URL https://boinc.bakerlab.org/rosetta/; Computer ID 6279686; resource share 1000
2/3/2024 7:36:24 PM | Rosetta@home | project resumed by user
2/3/2024 7:36:41 PM | Rosetta@home | update requested by user
2/3/2024 7:36:45 PM | Rosetta@home | Sending scheduler request: Requested by user.
2/3/2024 7:36:45 PM | Rosetta@home | Requesting new tasks for CPU
2/3/2024 7:36:46 PM | Rosetta@home | Scheduler request completed: got 0 new tasks
2/3/2024 7:36:46 PM | Rosetta@home | No tasks sent
2/3/2024 7:36:46 PM | Rosetta@home | Project requested delay of 31 seconds
2/3/2024 7:37:22 PM | Rosetta@home | Sending scheduler request: To fetch work.
2/3/2024 7:37:22 PM | Rosetta@home | Requesting new tasks for CPU
2/3/2024 7:37:23 PM | Rosetta@home | Scheduler request completed: got 0 new tasks
2/3/2024 7:37:23 PM | Rosetta@home | No tasks sent
2/3/2024 7:37:23 PM | Rosetta@home | Project requested delay of 31 seconds
2/3/2024 7:38:01 PM | LHC@home | project resumed by user
2/3/2024 7:38:05 PM | LHC@home | update requested by user
2/3/2024 7:38:09 PM | LHC@home | Sending scheduler request: Requested by user.
2/3/2024 7:38:09 PM | LHC@home | Requesting new tasks for CPU and AMD/ATI GPU
2/3/2024 7:38:19 PM | LHC@home | Scheduler request completed: got 0 new tasks
2/3/2024 7:38:19 PM | LHC@home | No tasks sent
2/3/2024 7:38:19 PM | LHC@home | Project requested delay of 6 seconds
2/3/2024 7:38:29 PM | LHC@home | Sending scheduler request: To fetch work.
2/3/2024 7:38:29 PM | LHC@home | Requesting new tasks for CPU and AMD/ATI GPU
2/3/2024 7:38:38 PM | LHC@home | Scheduler request completed: got 0 new tasks
2/3/2024 7:38:38 PM | LHC@home | No tasks sent
2/3/2024 7:38:38 PM | LHC@home | Project requested delay of 6 seconds
22) Message boards : GPUs : Not all GPUs running. 3 GPUs only 2 running.
Message 112605
Posted 30 Aug 2023 by Sandman192
I've got it.
1. I put the command in wrong location.
2. I didn't see the command that was already there.

1. Why is it not on by default.
2. It should be in the option menu or somewhere to select it.

It's running all 3 GPUS.
23) Message boards : GPUs : Not all GPUs running. 3 GPUs only 2 running.
Message 112604
Posted 30 Aug 2023 by Sandman192
<cc_config>
<log_flags>
<file_xfer>1</file_xfer>
<sched_ops>1</sched_ops>
<task>1</task>
<app_msg_receive>0</app_msg_receive>
<app_msg_send>0</app_msg_send>
<async_file_debug>0</async_file_debug>
<benchmark_debug>0</benchmark_debug>
<checkpoint_debug>0</checkpoint_debug>
<coproc_debug>0</coproc_debug>
<cpu_sched>0</cpu_sched>
<cpu_sched_debug>0</cpu_sched_debug>
<cpu_sched_status>0</cpu_sched_status>
<dcf_debug>0</dcf_debug>
<disk_usage_debug>0</disk_usage_debug>
<file_xfer_debug>0</file_xfer_debug>
<gui_rpc_debug>0</gui_rpc_debug>
<heartbeat_debug>0</heartbeat_debug>
<http_debug>0</http_debug>
<http_xfer_debug>0</http_xfer_debug>
<idle_detection_debug>0</idle_detection_debug>
<mem_usage_debug>0</mem_usage_debug>
<network_status_debug>0</network_status_debug>
<notice_debug>0</notice_debug>
<poll_debug>0</poll_debug>
<priority_debug>0</priority_debug>
<proxy_debug>0</proxy_debug>
<rr_simulation>0</rr_simulation>
<rrsim_detail>0</rrsim_detail>
<sched_op_debug>0</sched_op_debug>
<scrsave_debug>0</scrsave_debug>
<slot_debug>0</slot_debug>
<state_debug>0</state_debug>
<statefile_debug>0</statefile_debug>
<suspend_debug>0</suspend_debug>
<task_debug>0</task_debug>
<time_debug>0</time_debug>
<trickle_debug>0</trickle_debug>
<unparsed_xml>0</unparsed_xml>
<work_fetch_debug>0</work_fetch_debug>
</log_flags>
<options>
<abort_jobs_on_exit>0</abort_jobs_on_exit>
<allow_gui_rpc_get>0</allow_gui_rpc_get>
<allow_multiple_clients>0</allow_multiple_clients>
<allow_remote_gui_rpc>0</allow_remote_gui_rpc>
<disallow_attach>0</disallow_attach>
<dont_check_file_sizes>0</dont_check_file_sizes>
<dont_contact_ref_site>0</dont_contact_ref_site>
<lower_client_priority>0</lower_client_priority>
<dont_suspend_nci>0</dont_suspend_nci>
<dont_use_vbox>0</dont_use_vbox>
<dont_use_wsl>0</dont_use_wsl>
<exit_after_finish>0</exit_after_finish>
<exit_before_start>0</exit_before_start>
<exit_when_idle>0</exit_when_idle>
<fetch_minimal_work>0</fetch_minimal_work>
<fetch_on_update>0</fetch_on_update>
<force_auth>default</force_auth>
<http_1_0>0</http_1_0>
<http_transfer_timeout>300</http_transfer_timeout>
<http_transfer_timeout_bps>10</http_transfer_timeout_bps>
<max_event_log_lines>2000</max_event_log_lines>
<max_file_xfers>2</max_file_xfers>
<max_file_xfers_per_project>2</max_file_xfers_per_project>
<max_stderr_file_size>0.000000</max_stderr_file_size>
<max_stdout_file_size>0.000000</max_stdout_file_size>
<max_tasks_reported>0</max_tasks_reported>
<ncpus>-1</ncpus>
<no_alt_platform>0</no_alt_platform>
<no_gpus>0</no_gpus>
<no_info_fetch>0</no_info_fetch>
<no_opencl>0</no_opencl>
<no_priority_change>0</no_priority_change>
<no_rdp_check>0</no_rdp_check>
<os_random_only>0</os_random_only>
<process_priority>-1</process_priority>
<process_priority_special>-1</process_priority_special>
<use_all_gpus>1</use_all_gpus>
<proxy_info>
<socks_server_name></socks_server_name>
<socks_server_port>80</socks_server_port>
<http_server_name></http_server_name>
<http_server_port>80</http_server_port>
<socks5_user_name></socks5_user_name>
<socks5_user_passwd></socks5_user_passwd>
<socks5_remote_dns>0</socks5_remote_dns>
<http_user_name></http_user_name>
<http_user_passwd></http_user_passwd>
<no_proxy></no_proxy>
<no_autodetect>0</no_autodetect>
</proxy_info>
<rec_half_life_days>10.000000</rec_half_life_days>
<report_results_immediately>0</report_results_immediately>
<run_apps_manually>0</run_apps_manually>
<save_stats_days>30</save_stats_days>
<skip_cpu_benchmarks>0</skip_cpu_benchmarks>
<simple_gui_only>0</simple_gui_only>
<start_delay>0.000000</start_delay>
<stderr_head>0</stderr_head>
<suppress_net_info>0</suppress_net_info>
<unsigned_apps_ok>0</unsigned_apps_ok>
<use_all_gpus>0</use_all_gpus>
<use_certs>0</use_certs>
<use_certs_only>0</use_certs_only>
<vbox_window>0</vbox_window>
</options>
</cc_config>
24) Message boards : GPUs : Not all GPUs running. 3 GPUs only 2 running.
Message 112602
Posted 30 Aug 2023 by Sandman192
Well, it says "ignored by config". so that's the place to start looking. Double-check (proof-read) your cc_config.xml file.

  • Did you put 'use_all...' in the right section (options)
  • is there only one instance of that command (keep them in alphabetical order)
  • Did you restart BOINC after adding that command?

and so on.



I just showed you the command I put down.
<use_all_gpus>1</use_all_gpus>

I did put it in alphabetical order.
And I did restart BOINC after.
I already had the command in and it worked before on a different computer.
25) Message boards : GPUs : Not all GPUs running. 3 GPUs only 2 running.
Message 112590
Posted 30 Aug 2023 by Sandman192
I have 3 GPUs.
1 - 1080Ti, 1 - 980 and 1 - Internal GPU on a AMD 7700X
I'm only getting 2 running. The 1080Ti and AMD internal GPU. The 980 is not doing anything. Both work right out of the box.
I can get the 980 to run on 3D Mark so it is posable.
I think BOINC is confuse when have an internal GPU.
I added a command <use_all_gpus>1</use_all_gpus> and still nothing.
BOINC sees all 3 GPUs.
8/29/2023 9:42:19 PM | | Starting BOINC client version 7.22.2 for windows_x86_64
8/29/2023 9:42:19 PM | | log flags: file_xfer, sched_ops, task
8/29/2023 9:42:19 PM | | Libraries: libcurl/8.0.1-DEV Schannel zlib/1.2.13
8/29/2023 9:42:19 PM | | Data directory: E:\ProgramData\BOINC
8/29/2023 9:42:19 PM | | Running under account Sandm
8/29/2023 9:42:20 PM | | CUDA: NVIDIA GPU 0: NVIDIA GeForce GTX 1080 Ti (driver version 537.13, CUDA version 12.2, compute capability 6.1, 11264MB, 11264MB available, 12064 GFLOPS peak)
8/29/2023 9:42:20 PM | | CUDA: NVIDIA GPU 1 (not used): NVIDIA GeForce GTX 980 (driver version 537.13, CUDA version 12.2, compute capability 5.2, 4096MB, 4096MB available, 4979 GFLOPS peak)
8/29/2023 9:42:20 PM | | OpenCL: NVIDIA GPU 0: NVIDIA GeForce GTX 1080 Ti (driver version 537.13, device version OpenCL 3.0 CUDA, 11264MB, 11264MB available, 12064 GFLOPS peak)
8/29/2023 9:42:20 PM | | OpenCL: NVIDIA GPU 1 (ignored by config): NVIDIA GeForce GTX 980 (driver version 537.13, device version OpenCL 3.0 CUDA, 4096MB, 4096MB available, 4979 GFLOPS peak)
8/29/2023 9:42:20 PM | | OpenCL: AMD/ATI GPU 0: AMD Radeon(TM) Graphics (driver version 3570.0 (PAL,LC), device version OpenCL 2.0 AMD-APP (3570.0), 12269MB, 12269MB available, 563 GFLOPS peak)

Just to note, I had both 1080Ti and 980 on a different MoBo with no internal GPU and both ran fine together.
Edit: I just saw that "GPU not used" but why?
Window 11, BOICN 7.22.2[/quote]
26) Message boards : BOINC Manager : Addons that may help make things easier
Message 106827
Posted 20 Jan 2022 by Sandman192
1. Projects Tab: Add "Won't get new tasks for all projects" button. But doesn't change Status column for each project that does or doesn't have won't get new tasks. Just gray all projects when selected.
2. Project Tab: Add "Pause CPU only" button to make it so you can pause CPU work but leave GPU work alone and running.
3. Task Tab: Place "Total work units" footer to show all work units running and is stored on computer.
For all Tabs: Place "CPU" "GPU" "Net" = Networking in bottom right footer to show if either of them are paused.
Maybe like it does in WordPad with the Cap for Caps Lock and/or icon. Great to let you know if you forgot that you paused them. Of give us that option to show what we want it to show.
4. Add short cut key to pause all work even if BOINC is not focused. Great if your computer slows to a crawl. Sometimes Taskbar can be unstable at times, and you can't click on anything there or just the hole computer where you can't click on anything to respond, but computer is still running fine, and you want to get back control of the computer. 3 keys should be ok. Times it took so long to get my computer under control. Running to many virtual box work units at once will do that.
27) Message boards : Questions and problems : BOINC will only run 1 GPU when set to less than 10 days of work.
Message 106548
Posted 27 Dec 2021 by Sandman192
What DOES it say in the Event Log?

I see nothing that's related to GPU work and why it stopped using the second GPU.

I did the test again. Right now, both GPUs are running and is set for 10 days.

I did a 1-day test and not right away, but it did stop on the second GPU.
I did a 5-day test, and it ran both GPUs for a while and then stopped on the second GPU again.
I went to 7 days, and it ran both GPUs just fine.
I went to 6-day test, and it ran both GPUs again and then stopped on the second GPU stopped again.

So, no lower than 7 days of extra work or it will just stop working on the second GPU.
28) Message boards : Questions and problems : BOINC will only run 1 GPU when set to less than 10 days of work.
Message 106525
Posted 26 Dec 2021 by Sandman192
Have you set

<use_all_gpus>1</use_all_gpus>
in cc_config.xml?

Does BOINC list both GPUs in the event log at startup, without saying that the second is unused?


It is on. I told you it was running all GPUs and only stopped if I go to anything less than 10 days of work. Setting it back to 10 days starts running all GPUs. That is very odd indeed.
29) Message boards : Questions and problems : BOINC will only run 1 GPU when set to less than 10 days of work.
Message 106497
Posted 24 Dec 2021 by Sandman192
I have 2 GPUs, a 1080 and a 980 and when I set "day of work to 0.5, 1 or 2 days BOINC will only run just the 1080 only and will never run any work on the 980. And I still have at least 50 GPUs WUs waiting when it was set to 10 days but setting BOINC to 0.5, 1 or 2 days it will stop using the 980.

Assine GPU work.
Einstein
Moo Wrapper
All of Prime
Milkyway
Collatz


Windows 10, BOINC v7.16.20
30) Message boards : Questions and problems : GPU tasks skipped after scheduler overcommits CPU cores
Message 104586
Posted 17 Jun 2021 by Sandman192
If you reduce your work cache size, you will never have tasks going into EDF mode and pre-empting other projects. Then the client can work as it is supposed to and obey project resource shares.

Also the <rec_half_life_days>X</rec_half_life_days> value is a legacy from cpu only project days and doesn't compensate for gpu work.


Reducing cache size does nothing.
Still same results.
31) Message boards : Questions and problems : GPU tasks skipped after scheduler overcommits CPU cores
Message 103725
Posted 28 Mar 2021 by Sandman192
You probably pushed up the priority of the other projects by being locked into working on TN-Grid for so long by deadline pressure. It will return to normal gradually, but over a period of several days.

See the Configuration Options page of the User Manual. Try setting the line

<rec_half_life_days>X</rec_half_life_days>
A project's scheduling priority is determined by its estimated credit in the last X days. Default is 10; set it larger if you run long high-priority jobs.
to something much smaller: one day, instead of the default 10, would sort things out quicker.

If I had to edit a setting to make it work then it's a bug if that setting is by default and not working as devs intended then it's a BUG. Does that stand for 10 days of extra work? If so then changing it from the BOINC options doesn't work. I've tried. 1 day, 10 days, nothing.
It's not just TN-Grid. WCG is the same way. Just now I have it set to get more work for WCG. And as soon as the other projects are done... All I'll get is WCG and nothing else. I've done this twice already. Never had this problem until I updated BOINC. For years... Ever since BOINC came out I had 20 projects and all 20 projects were "waiting to run". Now 1 project is "waiting to run" when WGC or TN-Grid is added. 10 days or 1. Does not matter.

I'm not changing any settings. I here to report a bug. The point is if I had to change settings every time I updated BOINC then why? That's when I notice problems.

P.S. Note: I had no work at all "waiting to run". So I added Milky Way only for GPU work. And all it did is run 1 of my 2 GPUs installed. Adding another project like Moo Wrapper into it and Milky Way started on the second GPU just fine???😲 And only after I added another GPU project.
32) Message boards : Questions and problems : GPU tasks skipped after scheduler overcommits CPU cores
Message 103593
Posted 18 Mar 2021 by Sandman192
I can have 10 projects schedule but WCG or TN-Grid is all I get unless I stop WCG or TN-Grid from getting any work at all and things seem to be normal.

And again I have never had this problem before I updated my BOINC version.
And also happing on my second computer running Linux.
33) Message boards : Questions and problems : GPU tasks skipped after scheduler overcommits CPU cores
Message 103502
Posted 12 Mar 2021 by Sandman192
BOINC gets work but can't finish on time? What?
Plus, won't get **ANY** work units from project unless I stop another project. Exp: If TN-Grid is scheduled to get work then only TN-Grid will only get work. If WCG is scheduled to get work then only WCG will get work and will be more in charge and takes out TN-Grid.

This is happening on 2 of my computers. One Linux and one Windows 10.


**"Days overdue; you may not get credit for it. Consider aborting it". ???**
**"Tasks won't finish in time: BOINC runs 99.6% of the time; computation is enabled 100.0% of that". ???** Unless I stop it from getting other projects.
3/9/2021 3:57:05 AM | TN-Grid Platform | Task 181047_Hs_T154140-OXCT1_wu-277_1614546821865_1 is 3.11 days overdue; you may not get credit for it. Consider aborting it.
3/9/2021 3:57:05 AM | TN-Grid Platform | Task 181053_Hs_T002498-OPTN_wu-183_1614555068070_1 is 3.03 days overdue; you may not get credit for it. Consider aborting it.
3/9/2021 3:57:05 AM | TN-Grid Platform | Task 181055_Hs_T002502-OPTN_wu-232_1614558714182_0 is 2.99 days overdue; you may not get credit for it. Consider aborting it.
3/9/2021 3:57:05 AM | TN-Grid Platform | Task 181074_Hs_T194898-OGN_wu-176_1614588563451_1 is 2.66 days overdue; you may not get credit for it. Consider aborting it.
3/9/2021 3:57:05 AM | TN-Grid Platform | Task 181084_Hs_T116698-OBFC2A_wu-83_1614600576731_1 is 2.50 days overdue; you may not get credit for it. Consider aborting it.
3/9/2021 3:57:05 AM | TN-Grid Platform | Task 181162_Hs_T191705-NELF_wu-18_1614716635947_0 is 1.18 days overdue; you may not get credit for it. Consider aborting it.
3/9/2021 3:57:05 AM | TN-Grid Platform | Task 181166_Hs_T191709-NELF_wu-65_1614721341325_1 is 1.11 days overdue; you may not get credit for it. Consider aborting it.
3/9/2021 3:57:05 AM | TN-Grid Platform | Task 181235_Hs_T175748-MYO1G_wu-194_1614812880971_1 is 0.25 days overdue; you may not get credit for it. Consider aborting it.
3/9/2021 3:57:05 AM | TN-Grid Platform | Task 181242_Hs_T045070-MYO1E_wu-217_1614821392673_1 is 0.18 days overdue; you may not get credit for it. Consider aborting it.
3/9/2021 3:57:45 AM | SiDock@home | Tasks won't finish in time: BOINC runs 99.6% of the time; computation is enabled 100.0% of that
3/9/2021 3:57:45 AM | SiDock@home | Project requested delay of 7 seconds
3/9/2021 3:57:52 AM | Rosetta@home | Sending scheduler request: To fetch work.
3/9/2021 3:57:52 AM | Rosetta@home | Requesting new tasks for CPU
3/9/2021 3:57:53 AM | Rosetta@home | Scheduler request completed: got 0 new tasks
3/9/2021 3:57:53 AM | Rosetta@home | No tasks sent
3/9/2021 3:57:53 AM | Rosetta@home | Tasks won't finish in time: BOINC runs 99.6% of the time; computation is enabled 100.0% of that
3/9/2021 3:57:53 AM | Rosetta@home | Project requested delay of 31 seconds
3/9/2021 3:57:59 AM | GPUGRID | Sending scheduler request: To fetch work.
3/9/2021 4:44:11 AM | TN-Grid Platform | Aborting task 181258_Hs_T100042-MYH7B_wu-211_1614840590806_1; not started and deadline has passed
3/9/2021 4:44:11 AM | TN-Grid Platform | Aborting task 181259_Hs_T100043-MYH7B_wu-90_1614841440934_1; not started and deadline has passed
3/9/2021 9:20:21 AM | SiDock@home | Tasks won't finish in time: BOINC runs 99.6% of the time; computation is enabled 100.0% of that/9/2021 9:20:21 AM | SiDock@home | Project requested delay of 7 seconds
3/9/2021 10:43:19 AM | Rosetta@home | Tasks won't finish in time: BOINC runs 99.6% of the time; computation is enabled 100.0% of that
3/9/2021 10:43:19 AM | Rosetta@home | Project requested delay of 31 seconds
3/9/2021 2:23:04 PM | SiDock@home | Tasks won't finish in time: BOINC runs 99.6% of the time; computation is enabled 100.0% of that
3/9/2021 2:23:04 PM | SiDock@home | Project requested delay of 7 seconds
34) Message boards : Questions and problems : How to run multiple GPUs from BOINC
Message 99973
Posted 15 Jul 2020 by Sandman192
This is what I'm talking about... So BOINC does creat cc_config.xml in a matter of speaking. But is the new version of BOINC v7.16.7 deleting this file??? If any one out there has the cc_config file and find out it's missing then you need to report as a bug on this.
<cc_config>
<log_flags>
<file_xfer>1</file_xfer>
<sched_ops>1</sched_ops>
<task>1</task>
<android_debug>1</android_debug>
<app_msg_receive>1</app_msg_receive>
<app_msg_send>1</app_msg_send>
<async_file_debug>1</async_file_debug>
<benchmark_debug>1</benchmark_debug>
<checkpoint_debug>1</checkpoint_debug>
<coproc_debug>1</coproc_debug>
<cpu_sched>1</cpu_sched>
<cpu_sched_debug>1</cpu_sched_debug>
<cpu_sched_status>1</cpu_sched_status>
<dcf_debug>1</dcf_debug>
<disk_usage_debug>1</disk_usage_debug>
<file_xfer_debug>1</file_xfer_debug>
<gui_rpc_debug>1</gui_rpc_debug>
<heartbeat_debug>1</heartbeat_debug>
<http_debug>1</http_debug>
<http_xfer_debug>1</http_xfer_debug>
<idle_detection_debug>1</idle_detection_debug>
<mem_usage_debug>1</mem_usage_debug>
<network_status_debug>1</network_status_debug>
<notice_debug>1</notice_debug>
<poll_debug>1</poll_debug>
<priority_debug>1</priority_debug>
<proxy_debug>1</proxy_debug>
<rr_simulation>1</rr_simulation>
<rrsim_detail>1</rrsim_detail>
<sched_op_debug>1</sched_op_debug>
<scrsave_debug>1</scrsave_debug>
<slot_debug>1</slot_debug>
<state_debug>1</state_debug>
<statefile_debug>1</statefile_debug>
<suspend_debug>1</suspend_debug>
<task_debug>1</task_debug>
<time_debug>1</time_debug>
<trickle_debug>1</trickle_debug>
<unparsed_xml>1</unparsed_xml>
<work_fetch_debug>1</work_fetch_debug>
</log_flags>
<options>
<abort_jobs_on_exit>0</abort_jobs_on_exit>
<allow_multiple_clients>0</allow_multiple_clients>
<allow_remote_gui_rpc>0</allow_remote_gui_rpc>
<client_version_check_url>https://boinc.berkeley.edu/download.php?xml=1</client_version_check_url>
<client_new_version_text></client_new_version_text>
<client_download_url>https://boinc.berkeley.edu/download.php</client_download_url>
<disallow_attach>0</disallow_attach>
<dont_check_file_sizes>0</dont_check_file_sizes>
<dont_contact_ref_site>0</dont_contact_ref_site>
<lower_client_priority>0</lower_client_priority>
<dont_suspend_nci>0</dont_suspend_nci>
<dont_use_vbox>0</dont_use_vbox>
<exit_after_finish>0</exit_after_finish>
<exit_before_start>0</exit_before_start>
<exit_when_idle>0</exit_when_idle>
<fetch_minimal_work>0</fetch_minimal_work>
<fetch_on_update>0</fetch_on_update>
<force_auth>default</force_auth>
<http_1_0>0</http_1_0>
<http_transfer_timeout>300</http_transfer_timeout>
<http_transfer_timeout_bps>10</http_transfer_timeout_bps>
<max_event_log_lines>2000</max_event_log_lines>
<max_file_xfers>8</max_file_xfers>
<max_file_xfers_per_project>2</max_file_xfers_per_project>
<max_stderr_file_size>0</max_stderr_file_size>
<max_stdout_file_size>0</max_stdout_file_size>
<max_tasks_reported>0</max_tasks_reported>
<ncpus>-1</ncpus>
<network_test_url>https://www.google.com/</network_test_url>
<no_alt_platform>0</no_alt_platform>
<no_gpus>0</no_gpus>
<no_info_fetch>0</no_info_fetch>
<no_opencl>0</no_opencl>
<no_priority_change>0</no_priority_change>
<os_random_only>0</os_random_only>
<process_priority>-1</process_priority>
<process_priority_special>-1</process_priority_special>
<proxy_info>
<socks_server_name></socks_server_name>
<socks_server_port>80</socks_server_port>
<http_server_name></http_server_name>
<http_server_port>80</http_server_port>
<socks5_user_name></socks5_user_name>
<socks5_user_passwd></socks5_user_passwd>
<socks5_remote_dns>0</socks5_remote_dns>
<http_user_name></http_user_name>
<http_user_passwd></http_user_passwd>
<no_proxy></no_proxy>
<no_autodetect>0</no_autodetect>
</proxy_info>
<rec_half_life_days>10.000000</rec_half_life_days>
<report_results_immediately>0</report_results_immediately>
<run_apps_manually>0</run_apps_manually>
<save_stats_days>30</save_stats_days>
<skip_cpu_benchmarks>0</skip_cpu_benchmarks>
<simple_gui_only>0</simple_gui_only>
<start_delay>0.000000</start_delay>
<stderr_head>0</stderr_head>
<suppress_net_info>0</suppress_net_info>
<unsigned_apps_ok>0</unsigned_apps_ok>
<use_all_gpus>0</use_all_gpus>
<use_certs>0</use_certs>
<use_certs_only>0</use_certs_only>
<vbox_window>0</vbox_window>
</options>
</cc_config>
35) Message boards : Questions and problems : How to run multiple GPUs from BOINC
Message 99971
Posted 15 Jul 2020 by Sandman192
Ok, I installed Windows 10 on to a Vbox and installed BOINC 7.8.0.

No cc_config.xml

Now I know how it got there.

But I do know it was pages long.

And I do know now that I remember it saying that every time I check the logs...
7/15/2020 3:58:01 AM | | cc_config.xml not found - using defaults

But I did have the file before and for some reason, it is gone after upgrading BOINC to 7.16.7.

The point is that I figure it out and got it to run all GPUS.
Which why it's not on by default for a program that runs CPU and GPUS and has no option to change it in the client settings is be on me.

I see now and thanks.
36) Message boards : Questions and problems : How to run multiple GPUs from BOINC
Message 99968
Posted 15 Jul 2020 by Sandman192
cc_config.xml is an optional file.

BOINC does not, and as far as I'm aware, never has auto-generated a cc_config.xml file

No, it is not. It's been there from the start. I remember the cc_config.xml codes in there that took at least 3 pages of coding. And no cc_config.xml never ones showed up in "Event log" that the cc_config.xml was missing.

I certainly didn't type or copy and paste all that stuff in. Why would I? I had no need to.
37) Message boards : Questions and problems : How to run multiple GPUs from BOINC
Message 99938
Posted 14 Jul 2020 by Sandman192
Upgrading BOINC does not delete anything in the data directory, where cc_config.xml resides.

No, I'm just making things up! It did because I have seen in the BOINC logs that cc_config.xml is missing. Which I've never seen for years.
However, BOINC does not start with a default cc_config.xml file, you will always have to make one.
As explained, BOINC does by default not come with cc_config.xml; if you never had it it wasn't removed, you just never had it.

Plus, It didn't create a cc_config.xml ether. I know it's not that way in older versions.
So you don't know what you're talking about. I've seen it. I've been a BOINC user for over 8 years. Looking through logs and BOINC folders.

And your help desk and tester??? How do you think I know about cc_config.xml? It wasn't from Google.
38) Message boards : Questions and problems : How to run multiple GPUs from BOINC
Message 99911
Posted 13 Jul 2020 by Sandman192
Upgrading or doing a fresh install of BOINC v7.16.7 will delete or not creat a cc_config.xml. I see this as a major bug in this.

I search long and hard to get my computer to run more than 1 GPU on my computer. For one it's off by default, it should be in 'Computing preference' and cc_config.xml is not there anymore. It doesn't have to be this hard to get BOINC to configure to use more than one GPU.
It should be in the 'Computing preference' option to set it and not off by default.

If anyone has this problem with a new version of BOINC v7.16.7 for mutable GPUS than just add a cc_config.XML. I didn't know how to create an .XML so I copied any .XML file I found and pasted it back in the same directory and now I have 2 of the same file with one having copy added to the file. I right-clicked on the file and clicked 'edit' and 'select all' and pasted the command down below. Then I closed and saved the file. And all you have to do is rename the file with copy in it to 'cc_config and restart BOINC.
<cc_config>
<options>
<use_all_gpus>1</use_all_gpus>
</options>
</cc_config>
39) Message boards : Questions and problems : How to run multiple GPUs from BOINC
Message 99907
Posted 12 Jul 2020 by Sandman192
I added a second GPU and can't get it to run both.
7/12/2020 12:39:51 PM | | CUDA: NVIDIA GPU 1 (not used): GeForce GTX 980 (driver version 451.48, CUDA version 11.0, compute capability 5.2, 4096MB, 3378MB available, 4979 GFLOPS peak)
7/12/2020 12:39:51 PM | | OpenCL: NVIDIA GPU 1 (ignored by config): GeForce GTX 980 (driver version 451.48, device version OpenCL 1.2 CUDA, 4096MB, 3378MB available, 4979 GFLOPS peak)

Plus, why isn't multiple GPUs on by default? And I wish the setting where in the BOINC client.
40) Message boards : Questions and problems : Notices headaches.
Message 99584
Posted 2 Jul 2020 by Sandman192
I think they revert back, probably due to HTTPS issues. And BOINC@TACC did the same.

For both projects, I'll have both HTTP and HTTPS until I get a message from BOINC app that they have changed back to HTTPS.

Ya, I might report to WCG and find out what's going on.
Previous 20 · Next 20

Copyright © 2026 University of California.
Permission is granted to copy, distribute and/or modify this document under the terms of the GNU Free Documentation License, Version 1.2 or any later version published by the Free Software Foundation.