<div>Hi Pavel,<br></div><div><br></div><div>2.6.18 (EL5) and 2.6.9 (EL4) are considered as stable branches of OpenVZ kernel</div><div>2.6.32 is development.</div><div><br></div><div>I used 2.6.32 for tests (RHEL6) - such problems were not met.</div>
<br><div class="gmail_quote">2011/3/10 Pavel Shevaev <span dir="ltr"><<a href="mailto:pacha.shevaev@gmail.com">pacha.shevaev@gmail.com</a>></span><br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex;">
Folks,<br>
<br>
I tried using OpenVZ(2.6.32-5-openvz-amd64) on a Debian Squeeze host<br>
and I faced _crazy_ IO utilization numbers(99-101%) for a VE which has<br>
unlimited resources.<br>
<br>
The VE is running Percona Server(a patched version of MySQL). I've<br>
never had such issues with it on the same load on the "real" hardware<br>
node.<br>
<br>
And the worst part - I've faced several INNODB data corruptions in VE.<br>
After that I moved Percona onto the hardware node and now all IO<br>
problems are gone(at least running 6 hours without a glitch as of this<br>
writing)....<br>
<br>
Maybe it's not a good idea to use OpenVZ 2.6.32 kernel on production<br>
yet? If yes, what is the best version of OpenVZ kernel to be used on<br>
production?<br>
<font color="#888888"><br>
--<br>
Best regards, Pavel<br>
_______________________________________________<br>
Users mailing list<br>
<a href="mailto:Users@openvz.org">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><br clear="all"><br>-- <br><div><font face="courier new,monospace">----------------</font></div><div><font face="courier new,monospace">Best regards,</font><font face="courier new,monospace"><br>
</font></div><font face="courier new,monospace">Valentine Gostev</font><br>