<?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>Wed, 01 Jul 2015 17:02:51 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/50178.html</guid>
  <pubDate>Wed, 01 Jul 2015 17:02:51 GMT</pubDate>
  <title>Publishing of Virtuozzo builds</title>
  <author>estetus</author>
  <link>https://openvz.livejournal.com/50178.html</link>
  <description>&lt;pre style=&quot;white-space: pre-wrap; color: rgb(0, 0, 0); line-height: normal;&quot;&gt;


We are ready to announce &lt;a href=&quot;https://download.openvz.org/virtuozzo/releases/7.0-beta1/x86_64/&quot; target=&quot;_blank&quot; rel=&quot;nofollow&quot;&gt;publishing of binaries&lt;/a&gt; compiled from &lt;a href=&quot;https://src.openvz.org/projects/OVZ&quot; target=&quot;_blank&quot; rel=&quot;nofollow&quot;&gt;open components&lt;/a&gt;:
&lt;/pre&gt;&lt;br /&gt;&lt;ul&gt;&lt;br /&gt;&lt;li&gt;Virtuozzo installation ISO image&lt;/li&gt;&lt;br /&gt;&lt;li&gt;RPM packages (kernel and userspace)&lt;/li&gt;&lt;br /&gt;&lt;li&gt;Source RPM packages (kernel and userspace)&lt;/li&gt;&lt;br /&gt;&lt;li&gt;Debug RPM packages (kernel and userspace)&lt;/li&gt;&lt;br /&gt;&lt;li&gt;EZ templates (CentOS 7 x86_64, CentOS 6 x86_64 etc)&lt;/li&gt;&lt;br /&gt;&lt;/ul&gt;All installation paths &lt;a href=&quot;https://openvz.org/Quick_installation&quot; target=&quot;_blank&quot; rel=&quot;nofollow&quot;&gt;described in OpenVZ wiki&lt;/a&gt;.&lt;br /&gt;&lt;br /&gt;&lt;span style=&quot;font-size:1.4em;&quot;&gt;FAQ (Frequently Asked Questions)&lt;/span&gt;&lt;br /&gt;&lt;br /&gt;&lt;b&gt;Q: Can we use binaries or Virtuozzo distribution in production?&lt;/b&gt;&lt;br /&gt;A: No. Virtuozzo 7 is in pre-Beta stage and we strongly recommend to avoid any production use. We continue to develop new features and Virtuozzo 7 may contain serious bugs.&lt;br /&gt;&lt;br /&gt;&lt;b&gt;Q: Would it be possible to upgrade from Beta 1 to Beta 2?&lt;/b&gt;&lt;br /&gt;A: Upgrade will be supported only for OpenVZ installed on Cloud Linux (i.e. using Virtuozzo installation image of OpenVZ installed using yum on Cloud Linux).&lt;br /&gt;&lt;br /&gt;&lt;b&gt;Q: How often you will update Virtuozzo 7 files?&lt;/b&gt;&lt;br /&gt;A: RPM package (and yum repository) - nightly, ISO image - weekly.&lt;br /&gt;&lt;br /&gt;&lt;b&gt;Q: I don&amp;#39;t want to use your custom kernel or distribution. How to use OpenVZ on my own Linux distribution? &lt;/b&gt; A: We plan to make available OpenVZ for vanilla kernels and we are working on it. If you want it - please help us with testing and contribute patches [2]. Pay attention that using OpenVZ with vanilla kernel will have some limitations because some required kernel changes are not in upstream yet.</description>
  <comments>https://openvz.livejournal.com/50178.html?view=comments#comments</comments>
  <category>openvz</category>
  <category>beta</category>
  <category>virtuozzo core</category>
  <media:title type="plain">Avril Lavigne - What the Hell | Powered by Last.fm</media:title>
  <lj:music>Avril Lavigne - What the Hell | Powered by Last.fm</lj:music>
  <lj:security>public</lj:security>
  <lj:poster>estetus</lj:poster>
  <lj:posterid>12957684</lj:posterid>
  <lj:reply-count>0</lj:reply-count>
  </item>
  <item>
  <guid isPermaLink='true'>https://openvz.livejournal.com/43876.html</guid>
  <pubDate>Mon, 29 Apr 2013 18:52:48 GMT</pubDate>
  <title>vzstats in beta</title>
  <author>k001</author>
  <link>https://openvz.livejournal.com/43876.html</link>
  <description>For the last two weeks or so we&apos;ve been working on vzstats -- a way to get some statistics about OpenVZ usage. The system consists of a server, deployed to &lt;a target=&apos;_blank&apos; href=&apos;http://stats.openvz.org/&apos; rel=&apos;nofollow&apos;&gt;http://stats.openvz.org/&lt;/a&gt;, and clients installed onto OpenVZ machines (hardware nodes). This is currently in beta testing, with 71 servers participating at the moment. If you want to participate, read &lt;a target=&apos;_blank&apos; href=&apos;http://openvz.org/vzstats&apos; rel=&apos;nofollow&apos;&gt;http://openvz.org/vzstats&lt;/a&gt; and run &lt;code&gt;yum install vzstats&lt;/code&gt; on your OpenVZ boxes.&lt;br /&gt;&lt;br /&gt;So far we have some interesting results. We are not sure how representative they are -- probably they aren&apos;t, much more servers are needed to participate-- but nevertheless they are interested. Let&apos;s share a few preliminary findings.&lt;br /&gt;&lt;br /&gt;First, it looks like almost no one is using 32-bits on the host system anymore. This is reasonable and expected. Indeed, who needs system limited to 4GB of RAM nowdays?&lt;br /&gt;&lt;br /&gt;Second, many hosts stay on latest stable RHEL6-based OpenVZ kernel. This is pretty good and above our expectations.&lt;br /&gt;&lt;br /&gt;Third, very few run ploop-based containers. We don&apos;t understand why. Maybe we should write more about features you get from ploop, such as instant snapshots and improved live migration.</description>
  <comments>https://openvz.livejournal.com/43876.html?view=comments#comments</comments>
  <category>openvz</category>
  <category>beta</category>
  <category>vzstats</category>
  <lj:security>public</lj:security>
  <lj:poster>k001</lj:poster>
  <lj:posterid>990679</lj:posterid>
  <lj:reply-count>27</lj:reply-count>
  </item>
</channel>
</rss>
