1) Forums : General Topics : VM job unmanageable, restarting later... (Message 22919)
Posted 3 days ago by Jonathan
Post:
Max # cpus = avg_ncpus

Max # Jobs = max_concurrent.

If you are already using app_config.xml, just stick with that.

Your app_config should be running three jobs using a single core in each VM from what you posted.
It may make a difference as to where your Boinc data directory is. Hard drive vs SSD vs NVMe. I haven't really played around with that too much though as I don't have much space on my NVMe. I have my data directory on a HD.
2) Forums : General Topics : VM job unmanageable, restarting later... (Message 22917)
Posted 3 days ago by Jonathan
Post:
Virtual Box version 5 seemed to work better and it was rare to see this issue. Version 6 and above we started to have more of these types of errors.
I use either project preferences and/or app_config.xml to control the Virtual Box related tasks. It take a bit of work to find the correct balance on how many task and what kind you can run from each project.

Try setting the Cosmology at home preferences for Max # jobs and Max # cpus to control this project
Max # cpus sets the number of cores assigned to each VM.

I have 8 true cores on my Ryzen 1700 and I am running two, two core Cosmology task along with one, four core LHC / Atlas task. SMT / hyperthreading is on so I am only seeing about 50% processor usage.

Try Max # job set to 1 and Max # cpus set to 1 or 2. See if it is stable running that way. You can always increase the Max # jobs for more tasks concurrently. I don't think you will be able to run two, two core VM tasks without errors even if you suspend other projects temporarily.
3) Forums : General Topics : VM job unmanageable, restarting later... (Message 22915)
Posted 3 days ago by Jonathan
Post:
The Vboxwrapper is losing communication with VM or not getting a timely response. The stuck tasks will start back up after 24 hours. Vboxwrapper runs at a lower priority than the other processes and sometimes gets starved.
I looked at a few of your completed jobs. You have it set to use 1 cpu per task. How many concurrent jobs are you running? You can try cutting down on that. Are you running other VBox projects or other boinc projects?
I find that I can't run Vbox related task with the computer using 100% processing. It also chokes when too many VBox tasks are in use, ie. starting and stopping.
4) Forums : Technical Support : MT VB units get stuck at 0.100% for 20 mins and then get aborted. CPU stayed idle. (Message 22914)
Posted 3 days ago by Jonathan
Post:
I would set Max # CPUs to 2 or 4. You could even set it to 1 if you prefer. The work units complete so quickly with 2 or 4 cores assigned, I don't see any point in assigning more as it just mean more time spent creating and destroying VM images for each task ran.
My 4 core tasks took about 5 minutes and the 2 core are claiming about 10 minutes. CPU time per task is about the same.
5) Forums : Technical Support : MT VB units get stuck at 0.100% for 20 mins and then get aborted. CPU stayed idle. (Message 22911)
Posted 4 days ago by Jonathan
Post:
Change these setting on the Cosmology@Home Preferences page. Mzx # CPUs controls how many core get assigned per VM. Each VM will use about 2Gb of RAM. You can also control this using app_config.xml method per the FAQ section. Start with Max # job set low or you might run into the Vboxwrapper losing communication problem and work units starting later (about 24 hours)

Max # jobs No limit
Max # CPUs 4
6) Forums : Technical Support : Cosmology@home tasks fail with Postponed: VM job unmanageable, restarting later if vboxsvc priority is set to idle (Message 22905)
Posted 9 days ago by Jonathan
Post:
Your newest computer isn't even running the legacy app and is getting segfault errors. Is it running any Boinc projects successfully?

Your other computers don't seem to have problems using all the cores assigned to a virtual box machine. Maybe that isn't a problem like it was in the past.
7) Forums : General Topics : Formula BOINC (Message 22904)
Posted 9 days ago by Jonathan
Post:
It looks fine going by the number of tasks in progress. The numbers are a lot bigger than normal.
Hope the project doesn't run into out of disk space errors.
8) Forums : Technical Support : Cosmology@home tasks fail with Postponed: VM job unmanageable, restarting later if vboxsvc priority is set to idle (Message 22899)
Posted 10 days ago by Jonathan
Post:
Is that computer 443084? That one is assigning 4 cpu cores to a work unit or VM. You need to get it to assign 1 to 2 cores, probably by using the app_config.xml method or set the project preferences of Max # CPUs to 1 or 2. app_config.xml is shown in the FAQ section.



Your work units aren't even starting in virtualbox.
9) Forums : Technical Support : Cosmology@home tasks fail with Postponed: VM job unmanageable, restarting later if vboxsvc priority is set to idle (Message 22847)
Posted 1 Oct 2021 by Jonathan
Post:
Try checking out the BOINC forums or LHC @ home forums. Those should be more active.
VirtualBox 6.1 is the only active and supported version per www.virtualbox.org
10) 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
11) 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>
12) 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>
13) 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
14) 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/
15) 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.
16) 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?
17) 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.
18) 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
19) 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?
20) 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.


Next 20