Hi Greg,<br><br>I ran into this problem when building my own ovz kernel, and have since noted some distro's stock kernels have this issue as well. This seems to be a symptom of a known bug tied to the kernel scheduling. <br>
<pre class="bz_comment_text"><span class="quote"><a href="http://forum.openvz.org/index.php?t=msg&goto=27142&">http://forum.openvz.org/index.php?t=msg&goto=27142&</a></span><br></pre>To fix this issue, recompile your kernel with this option commented out:<br>
<br><span class="MsgBodyText"><pre><span class="MsgBodyText"><pre><span class="quote">#CONFIG_FAIR_USER_SCHED</span></pre></span><br><span class="quote">#CONFIG_FAIR_GROUP_SCHED</span></pre></span><br>GMSI - Gemini Microsystems<br>
John Knight | Systems Engineer<br><a href="mailto:jknight@geminimicro.com">jknight@geminimicro.com</a> | (706) 255-9203<br><br><br><br><div class="gmail_quote">On Tue, May 26, 2009 at 6:47 PM, Gregor at HostGIS <span dir="ltr"><<a href="mailto:gregor@hostgis.com">gregor@hostgis.com</a>></span> wrote:<br>
<blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;">I am having a problem creating and starting a new VE.<br>
vzctl start gives me: mounted, container start failed, unmounting.<br>
<br>
<br>
dmesg shows only this:<br>
CT: 30: stopped<br>
CT: 30: failed to start with err=-12<br>
<br>
The verbose log (level 10) is no more useful to me:<br>
<br>
Starting container ...<br>
Running: /usr/sbin/vzquota show 30<br>
Running: /usr/sbin/vzquota on 30 -r 0 -b 104857700 -B 104857700 -i 20000100 -I 20000100 -e 0 -n 0 -s 0<br>
Mounting root: /vz/root/30 /vz/private/30<br>
Container is mounted<br>
Set iptables mask 0x000017bf<br>
Set features mask 0000000000000000/0000000000000000<br>
Container start failed<br>
Running: /usr/sbin/vzquota stat 30 -f<br>
Running: vzquota setlimit 30 -b 104857600 -B 104857600 -i 20000000 -I 20000000 -e 0 -n 0<br>
Running: /usr/sbin/vzquota stat 30 -f<br>
Running: /usr/sbin/vzquota off 30<br>
Container is unmounted<br>
<br>
<br>
It can't possibly be a RAM shortage. This hardware has 24 GB physical, and only 9 is allocated amongst the other VEs. There are presently 8 VEs, and this would make 9 if it would start.<br>
<br>
Any thoughts on how I can debug this?<br><font color="#888888">
<br>
-- <br>
HostGIS, Open Source solutions for the global GIS community<br>
Greg Allensworth - SysAdmin, Programmer, GIS Person, Security<br>
Network+ Server+ A+ Security+<br>
_______________________________________________<br>
Users mailing list<br>
<a href="mailto:Users@openvz.org" target="_blank">Users@openvz.org</a><br>
<a href="https://openvz.org/mailman/listinfo/users" target="_blank">https://openvz.org/mailman/listinfo/users</a><br>
</font></blockquote></div><br>