LHC@home

Here is a list of the common VM applications errors (exit status codes), causes and solutions. For all other errors first try a project reset. If there is still a problem, post a message with a link to the failed task.

* EXIT_ABORTED_BY_CLIENT (194)
This exit status is caused when the VM heartbeat is not detected. This mainly occurs when the VM fails to boot. First try a project reset and the try re-installing a recent version of VirtualBox. It can also occur when hardware virtualization is not enabled in the BIOS.
* STATUS_ACCESS_VIOLATION (-1073741819)
This occurs when using an old VirtualBox version with Windows 10. Upgrade VirtualBox to a more recent version.
* EXIT_INIT_FAILURE (206)
This error happens when the application is starting. There are three main reasons that are reported in the stderr_out log as the VM Completion Message:


* Could not ping HTCondor
This is typically a network related issue
* The x509 proxy creation failed
This is typically a network related issue
* Condor exited after 107582s without running a job
This usually occurs when the VM was stopped (not suspended) before the first job finished and was restarted after 18 hours. The subsequent task should run fine.


* ERR_NO_NETWORK_CONNECTION (-203)
This occurs when the VM does not have a network connection. As there is a task, it suggests that the host machines does have a connection. Check the BOINC preferences relating to the use of the network.
* -152 ERR_NETOPEN
This occurs when port 3125 or 9618 is closed to outgoing network traffic. Check your firewall setting.

This one is missing:
EXIT_INIT_FAILURE (206) usually occurs when the task queue is empty.

(I sent you a pm)

BUT you have to remember we all are not living in western Europe and we all do not have the fastest DSL on the planet and that is just the way it goes......we have no choice and I pay $100 per month for mine but many times (the only Invalids I ever get) are because of the DSL and NOT my computers or the versions of VB or Boinc.

I have been running thousands of these since March 1st 2011 and the DSL speed at any given time is my only problem and since I don't own Centurylink there is nothing that can be done.

It should be EXIT_NO_SUB_TASKS (207) when there are no jobs. Will investigate ...

This one is missing:
EXIT_INIT_FAILURE (206) usually occurs when the task queue is empty.

It should be EXIT_NO_SUB_TASKS (207) when there are no jobs. Will investigate ...

Here, it is also EXIT_INIT_FAILURE (206) whenever no tasks are available. Occurs after about 10 minutes.

5CPU WU couldn't be calculated because the application exced the memory space and I have 8 GB memory space and this is not enough
A lot of work unit write Hypervisor Failed
Since the begining of Formula Boinc the 22/06/2017

Guy PFLIEGER
Masevaux-Niederbruck

The last 5 CPU task couldn't run longer as 1:27 Forward the t5cPU tasks could run only 0:06 to 0:08. It is a little better but not enough to run completly the 5CPU tasks
I hope the Hypervisor could sleep this night because he must today solve the problems.
I Have 8 GB memory space. I don't know how much need the minimal memory space to run the 5cpu WU
Drink a lot and when the wetter is warm then slow down your processors with the tool box of the boinc manager to protect your computers and for having a better cooling of the system. Use, if you have it, the AEGIS 2 thermomether to Survey the cooling of the processors

Guy PFLIEGER
Masevaux-Niederbruck

In short words: Your computer is overstrained with 5-core-WUs.

You may limit the #cores per WU to 2 via the project's website (your personal preferency page) and use an app_config.xml that includes the following RAM setting:
<cmdline>--memory_size_mb 4600</cmdline>

when the VM suspends because of processor usage then the vm will not run next time in the same user session !

in addition on reboot progress has to start from the beginning !

This sounds a lot like a problem that a previous version of VboxWrapper had. Please, could you confirm you are using the latest version (by detaching and reattaching to the project)? Also, what application have you selected ? If something different than Theory, please try selecting it and see if you complete a task without problems.

Thank you for your support.

when the VM suspends because of processor usage then the vm will not run next time in the same user session !

in addition on reboot progress has to start from the beginning !

You should look into my Checklist, especially Nr. 2 regarding Win10

---

Supporting BOINC, a great concept !

how to convert VM's and use hyper V

https://www.virtualbox.org/manual/ch10.html - virualize

https://docs.microsoft.com/en-us/virtualization/hyper-v-on-windows/quick-start/enable-hyper-v

https://www.groovypost.com/howto/migrate-virtual-box-vms-windows-10-hyper-v/

https://docs.microsoft.com/en-us/virtualization/hyper-v-on-windows/user-guide/nested-virtualization

https://superuser.com/questions/1144405/enable-virtualization-for-windows-10-pro-running-inside-virtualbox

https://www.vmware.com/try-vmware.html - free products at the bottom these also run linux physics images

Nesting Virtualbox

https://hyperv.veeam.com/blog/nested-vitualization-hyperv/


from :

http://bit.ly/HPC-Dev

http://bit.ly/tRNG-Dev

what about >

https://cernvm.cern.ch

https://cernvm.cern.ch/portal/vbinstallation

I would like very much to know while all LHC tasks fail except ATLAS and SixTrack. This happens both on a Windows `10 PC with 22 GB RAM and on a Linux box with 8 GB RAM running SuSE Leap 42.2. Then it does not depend on a badly configured PC. VirtualBox is 5.2.2 on all PCs.
Tullio

I would like very much to know while all LHC tasks fail except ATLAS and SixTrack. This happens both on a Windows `10 PC with 22 GB RAM and on a Linux box with 8 GB RAM running SuSE Leap 42.2. Then it does not depend on a badly configured PC. VirtualBox is 5.2.2 on all PCs.
Tullio

Your tasks seem to be unable to collect jobs from the Condor servers, and eventually time out. Unfortunately I'm not expert enough to say why that might be. You seem to contact the servers OK -- it's suspiciously like a firewall problem of some sort.

---

Tullio,
when you use the same Computer with the same preferences:
1. Atlas is running with two CPU's and finished successful. Saw this in a task.
2. Theory, CMS and LHCb can therefore not run with the same preferences, because they are using only ONE CPU.
In LHC-dev is multicore possible for Theory, CMS or LHCb!

I am using 2 CPUs on Atlas tasks on Windows 10 PC, because the CPU has 4 cores, or 4 logical processors according to the Task Manager. I am using only one CPU on the Linux boxen and, again, all LHC tasks fail except Atlas and SixTrack. I have a new 30 Mbit connection via fiber on my modem, but it goes up to 40 Mbit in download and 10 Mbit in upload. The Windows PC has 22 GB RAM, mostly unused, the two Linux boxen 8 GB RAM All other BOINC projects run happily both on CPUs and GPUs (SETI, SETI Beta, Einstein, Climateprediction.net).
Tullio

---