<div dir="ltr">Thanks Keith, my question was about kernel update in centos 6.x ...<div><br></div><div>-Pablo</div></div><div class="gmail_extra"><br><br><div class="gmail_quote">On Thu, Jul 17, 2014 at 1:33 PM, Keith Keller <span dir="ltr"><<a href="mailto:kkeller@wombat.san-francisco.ca.us" target="_blank">kkeller@wombat.san-francisco.ca.us</a>></span> wrote:<br>
<blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><div class="HOEnZb"><div class="h5">On 2014-07-17, Pablo Silva <<a href="mailto:psilvao@gmail.com">psilvao@gmail.com</a>> wrote:<br>
><br>
> Dear Colleagues, I would like to know your experience using openvz, my boss<br>
> tells me that if we use openvz, when you upgrade from Centos 6.x, we lose<br>
> the openvz kernel and leave offline multiple virtual machines. Exists this<br>
> risk?, As you have faced, or is a valid opinion but that has not happened<br>
> in practice?<br>
<br>
</div></div>When you upgrade from CentOS 6.x to what? 7.x? 6.x to 6.x+1?<br>
<br>
If you update the CentOS kernel package there is a slight risk that you<br>
will mess up your grub.conf file and boot that kernel by accident. The<br>
easy solution is to exclude kernel-* in your yum configuration, so that<br>
yum will never update the package. (And FWIW I haven't seen this issue<br>
in practice.)<br>
<span class="HOEnZb"><font color="#888888"><br>
--keith<br>
<br>
--<br>
<a href="mailto:kkeller@wombat.san-francisco.ca.us">kkeller@wombat.san-francisco.ca.us</a><br>
</font></span><div class="HOEnZb"><div class="h5"><br>
<br>
_______________________________________________<br>
Users mailing list<br>
<a href="mailto:Users@openvz.org">Users@openvz.org</a><br>
<a href="https://lists.openvz.org/mailman/listinfo/users" target="_blank">https://lists.openvz.org/mailman/listinfo/users</a><br>
</div></div></blockquote></div><br></div>