<?xml version='1.0' encoding='utf-8' ?>
<!--  If you are running a bot please visit this policy page outlining rules you must respect. https://www.livejournal.com/bots/  -->
<rss version='2.0'  xmlns:lj='http://www.livejournal.org/rss/lj/1.0/' xmlns:media='http://search.yahoo.com/mrss/' xmlns:atom10='http://www.w3.org/2005/Atom'>
<channel>
  <title>OpenVZ</title>
  <link>https://openvz.livejournal.com/</link>
  <description>OpenVZ - LiveJournal.com</description>
  <lastBuildDate>Sat, 13 Nov 2010 17:43:28 GMT</lastBuildDate>
  <generator>LiveJournal / LiveJournal.com</generator>
  <lj:journal>openvz</lj:journal>
  <lj:journalid>9392309</lj:journalid>
  <lj:journaltype>community</lj:journaltype>
  <image>
    <url>https://l-userpic.livejournal.com/128680075/9392309</url>
    <title>OpenVZ</title>
    <link>https://openvz.livejournal.com/</link>
    <width>100</width>
    <height>100</height>
  </image>

  <item>
  <guid isPermaLink='true'>https://openvz.livejournal.com/33832.html</guid>
  <pubDate>Sat, 13 Nov 2010 17:43:28 GMT</pubDate>
  <title>On RHEL5 kernel releases</title>
  <author>k001</author>
  <link>https://openvz.livejournal.com/33832.html</link>
  <description>&lt;p&gt;You might have noticed that we have announced a new kernel branch
named rhel5-testing a while ago (&lt;a href=&quot;http://openvz.org/pipermail/announce/2010-July/000138.html&quot; target=&quot;_blank&quot; rel=&quot;nofollow&quot;&gt;back in July&lt;/a&gt;,
to be more specific). The idea is pretty simple: at the same time as giving the new
kernel to our internal QA we are releasing it to &lt;a href=&quot;http://wiki.openvz.org/Download/kernel/rhel5-testing&quot; target=&quot;_blank&quot; rel=&quot;nofollow&quot;&gt;rhel5-testing&lt;/a&gt;.&lt;/p&gt;

&lt;p&gt;Although this change imposes some more work on me (more kernels
to release, scripts to run, changelogs to prepare), I&apos;m pleased
to say that this model works very well. First, vendors who use
our kernels as a base for theirs (for example, &lt;a href=&quot;http://www.openwall.com/Owl/&quot; target=&quot;_blank&quot; rel=&quot;nofollow&quot;&gt;OWL&lt;/a&gt;) now enjoy
earlier access to the sources. Second, new kernels get more
testing coverage due to OpenVZ users who choose to use this
branch. Finally, it works as a “technology preview”.&lt;/p&gt;

&lt;p&gt;Now, let me explain why we have so strange version numbers
in the recent rhel5-testing kernels — kernels 028stab07x
are intermixed with 028stab070.y. The thing is, we still keep
updating 028stab070.y with new fixes and upstream (RHEL) updates,
while 028stab07x is a newer “sub-branch” which adds a few new
features:&lt;ul&gt;
&lt;li&gt;live migration of containers with NFS and AutoFS mounts&lt;/li&gt;
&lt;li&gt;iotop working in containers and the host system&lt;/li&gt;
&lt;/ul&gt;&lt;/p&gt;

&lt;p&gt;Because of these new features, these kernels haven&apos;t reached the
stability yet so we keep releasing those in rhel5-testing.
Hopefully soon it will end up being stable enough and we
will abandon 028stab070.y in favor of 028stab078 (or so).&lt;/p&gt;

&lt;p&gt;&lt;b&gt;Update:&lt;/b&gt; this post was mostly written yesterday. Today we have just released
&lt;a href=&quot;http://wiki.openvz.org/Download/kernel/rhel5-testing/028stab078.1&quot; target=&quot;_blank&quot; rel=&quot;nofollow&quot;&gt;028stab078.1&lt;/a&gt; kernel.&lt;/p&gt;

&lt;p&gt;&lt;b&gt;Update&lt;/b&gt; 7 Oct 2012: comments disabled due to spam&lt;/p&gt;</description>
  <category>testing</category>
  <category>kernel</category>
  <category>openvz</category>
  <category>rhel5</category>
  <lj:security>public</lj:security>
  <lj:poster>k001</lj:poster>
  <lj:posterid>990679</lj:posterid>
  <lj:reply-count>4</lj:reply-count>
  </item>
</channel>
</rss>
