https://sourceforge.net/p/xval/wiki/Troubleshooting/Recent changes to TroubleshootingenFri, 12 May 2017 14:15:00 -0000https://sourceforge.net/p/xval/wiki/Troubleshooting/<div class="markdown_content"><pre>--- v1 +++ v2 @@ -1,3 +1,4 @@ +[TOC] #Virtual Machine issues# ##Virtual machine does not start## Make sure you have installed the Extension Pack correctly </pre> </div>Nick CrabtreeFri, 12 May 2017 14:15:00 -0000https://sourceforge.netdf2fa1a6b7487ce6d00c2eea57c75e1d3ee5e373https://sourceforge.net/p/xval/wiki/Troubleshooting/<div class="markdown_content"><h1 id="virtual-machine-issues">Virtual Machine issues</h1> <h2 id="virtual-machine-does-not-start">Virtual machine does not start</h2> <p>Make sure you have installed the Extension Pack correctly</p> <h2 id="virtual-machine-is-slow">Virtual machine is slow</h2> <p>Reconfigure the virtual machine to use as many of the host CPUs and as much of the host memory as possible. <em>Explanation: The virtual machine image is deliberately distributed with a 'minimum' configuration. An update to this configuration is strongly recommended</em></p> <h1 id="problems-running-jobs">Problems running jobs</h1> <h2 id="jobs-appear-to-hang">Jobs appear to hang</h2> <p>In general, if jobs appear to hang then:<br/> 1. Check 'top' in another terminal to see if it the process still running<br/> 2. Check the output file size to see if it is growing<br/> 3. Kill the job and re-run using a higher verboseness (--verbose=10 for example - a bit of trial-and-error is needed to get the right verboseness which tells you what is happening but doesn't swamp you).</p> <p>Note there is extensive use of 'lock' files which need to be cleaned up manually if you kill the job.</p></div>Nick CrabtreeFri, 12 May 2017 14:14:24 -0000https://sourceforge.net4b8716a89c215b72f31c25ace771b63ac44a1c67