Posts by fazel

Info	Message
1) Message boards : API : Example_app compile error in windows: boinc_win.h not found... Message 55020 Posted 24 Jul 2014 by fazel	Hello all, I am trying to compile example_app with mingw but it gives me the error: boinc_win.h not found what should I do? TNX.
2) Message boards : API : How to use DaCapo benchmarks in Vboxwrapper? Message 54784 Posted 7 Jul 2014 by fazel	Hello all, I want to use DaCapo benchmarks in Vboxwrapper, I want to know how it is possible to use it as a Boinc job? Regards, Fazel.
3) Message boards : API : The order of functions that called during the result ready and upload to server Message 49686 Posted 23 Jun 2013 by fazel	Hi every body, Can any body know the order of functions that involve in uploading result from host to server? I want to know when boinc knows the result is ready and how? and then which functions are involved in uploading the result?
4) Message boards : API : modification of slots directory Message 49520 Posted 7 Jun 2013 by fazel	Hi all, If I want to change the original boinc architecture about moving projects files from project directory to slots directory, where should I change the source code? I just want to move some part of project's files into a slots directory instead of slot number directory(ex 1,2,3,...). Regards.
5) Message boards : API : limitation number of jobs per physical CPU Message 49481 Posted 3 Jun 2013 by fazel	Use the <ncpus>N</ncpus> option in cc_config.xml This emulates that you have more cores than you actually have. A value of <ncpus>4</ncpus> will run 4 tasks at a time, even on a 2 core CPU. See http://boinc.berkeley.edu/wiki/Client_configuration for more information about the cc_config.xml file and its options and flags. thanks, and I have read somewhere that there is a configuration that how much each task can used CPU time as I think,Is that true? for example if I want to adjust that each job utilize only 50% of each CPU time how can I do that? And one more thing, Is it possible to set the ncpu at the run time?
6) Message boards : API : limitation number of jobs per physical CPU Message 49473 Posted 2 Jun 2013 by fazel	Hello all, If I want to modify the limitation of jobs per PCPUs in the source code, where should I do this? Regards. You can set it in config.xml <max_wus_to_send> x </max_wus_to_send> Thanks my friend,but I want to fetch more jobs per PCPUs now I have two Cores and the boinc has fetched only two WUs simultaneously.
7) Message boards : API : limitation number of jobs per physical CPU Message 49451 Posted 1 Jun 2013 by fazel	Hello all, If I want to modify the limitation of jobs per PCPUs in the source code, where should I do this? Regards.
8) Message boards : API : how to deploy vboxwrapper? Message 48999 Posted 6 May 2013 by fazel	please forgive me I was so busy during previous week,I am now here and ready to solve the problem. Regards.
9) Message boards : API : how to deploy vboxwrapper? Message 48854 Posted 29 Apr 2013 by fazel	yes, my version file content: <version> <file> <physical_name>vboxwrapper_26012_i686-pc-linux-gnu</physical_name> <main_program/> <copy_file/> </file> <file> <physical_name>uppercase</physical_name> <copy_file/> <logical_name>shared/uppercase</logical_name> </file> <file> <physical_name>vm_image86.vdi</physical_name> <copy_file/> <logical_name>vm_image.vdi</logical_name> </file> <file> <physical_name>vbox_job_9.0.xml</physical_name> <logical_name>vbox_job.xml</logical_name> </file> </version> my input template file: <file_info> <number>0</number> </file_info> <workunit> <file_ref> <file_number>0</file_number> <open_name>shared/in</open_name> <copy_file/> </file_ref> <min_quorum>1</min_quorum> <target_nresults>1</target_nresults> </workunit> my output template: <file_info> <name><OUTFILE_0/></name> <generated_locally/> <upload_when_present/> <max_nbytes>10000</max_nbytes> <url><UPLOAD_URL/></url> </file_info> <result> <file_ref> <file_name><OUTFILE_0/></file_name> <copy_file>1</copy_file> <open_name>shared/out</open_name> </file_ref> </result>
10) Message boards : API : how to deploy vboxwrapper? Message 48844 Posted 29 Apr 2013 by fazel	Thanks, But now I see this error: Mon 29 Apr 2013 10:44:54 AM MYT uppercase [error] Can't copy projects/127.0.0.1_uppercase/uppercase to slots/0/shared/uppercase: fopen() failed what is wrong?
11) Message boards : API : how to deploy vboxwrapper? Message 48801 Posted 24 Apr 2013 by fazel	when I run the boinc I face with these problems: Wed 24 Apr 2013 07:32:31 PM MYT uppercase Starting VVV_0 Wed 24 Apr 2013 07:32:31 PM MYT uppercase [error] Can't create link file slots/0/shared/uppercase Wed 24 Apr 2013 07:33:06 PM MYT uppercase Computation for task VVV_0 finished Wed 24 Apr 2013 07:33:06 PM MYT uppercase Output file VVV_0_0 for task VVV_0 absent I already tried to set up the access permissions for the slot and other folders, but that still doesn't work. why am I getting these error?
12) Message boards : API : how to deploy vboxwrapper? Message 48800 Posted 24 Apr 2013 by fazel	The input and output files don't go into version.xml. So how I mention logical name to input file? "Creating jobs for VM apps The input and output files of a VM app must Have logical names starting with shared/. Have the copy_file attribute. This causes the BOINC client to copy them to and from the slot/x/shared/ directory."
13) Message boards : API : how to deploy vboxwrapper? Message 48781 Posted 23 Apr 2013 by fazel	this is my version.xml content: <version> <file> <physical_name>vboxwrapper_26012_i686-pc-linux-gnu</physical_name> <main_program/> <copy_file/> </file> <file> <physical_name>uppercase</physical_name> <logical_name>shared/UP</logical_name> </file> <file> <physical_name>vm_image86.vdi</physical_name> <copy_file/> <logical_name>vm_image.vdi</logical_name> </file> <file> <physical_name>vbox_job_3.0.xml</physical_name> <logical_name>vbox_job.xml</logical_name> </file> <file> <physical_name>input.txt</physical_name> <copy_file/> <logical_name>shared/IN</logical_name> </file> <file> <physical_name>output.txt</physical_name> <copy_file/> <logical_name>shared/OUT</logical_name> </file> <file_prefix>shared</file_prefix> </version>
14) Message boards : API : how to deploy vboxwrapper? Message 48780 Posted 23 Apr 2013 by fazel	but after downloading all of the files,noting was happened. why?
15) Message boards : API : how to deploy vboxwrapper? Message 48779 Posted 23 Apr 2013 by fazel	[quote] I have done every things that needed but when I run the boinc I face with this error: Temporary failed download of vm_image86.vdi:http error I solved this error:user rights!
16) Message boards : API : how to deploy vboxwrapper? Message 48778 Posted 23 Apr 2013 by fazel	Bascally you have to make sure: Input files have logical names starting with shared/ and have the copy_file attribute. That should be it. So we have to define input file in the version file? I have done every things that needed but when I run the boinc I face with this error: Temporary failed download of vm_image86.vdi:http error Thanks.
17) Message boards : API : how to deploy vboxwrapper? Message 48775 Posted 23 Apr 2013 by fazel	ok Thanks, what about workunits? how should we create them?
18) Message boards : API : how to deploy vboxwrapper? Message 48745 Posted 21 Apr 2013 by fazel	Really thanks for your help, this is very helpful. So as I understand we should not create shared directory this is just logical name? How does VBOX_USER_HOME set? I read some where that we have to change this one to the vbox directory under the slot directory. Thanks.
19) Message boards : API : how to deploy vboxwrapper? Message 48716 Posted 20 Apr 2013 by fazel	Thanks for your information, actually I know all of them but for example how does boinc client work with vboxwrapper? I mean what should we do to enable vboxwrapper and virtualization? and also where should I put the vboxwrapper and other files? Regards.
20) Message boards : API : how to deploy vboxwrapper? Message 48713 Posted 20 Apr 2013 by fazel	thanks

Copyright © 2025 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.