<?xml version="1.0" encoding="UTF-8"?><rss version="2.0"
	xmlns:content="http://purl.org/rss/1.0/modules/content/"
	xmlns:dc="http://purl.org/dc/elements/1.1/"
	xmlns:atom="http://www.w3.org/2005/Atom"
	xmlns:sy="http://purl.org/rss/1.0/modules/syndication/"
		>
<channel>
	<title>Comments on: Is Virtuozzo good for OpenVZ?</title>
	<atom:link href="http://hostingfu.com/article/is-virtuozzo-good-for-openvz/feed" rel="self" type="application/rss+xml" />
	<link>http://hostingfu.com/article/is-virtuozzo-good-for-openvz</link>
	<description>Web Hosting Blog by a Software Developer</description>
	<lastBuildDate>Fri, 02 Jul 2010 10:59:16 +0000</lastBuildDate>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
	<generator>http://wordpress.org/?v=3.0</generator>
	<item>
		<title>By: Dev</title>
		<link>http://hostingfu.com/article/is-virtuozzo-good-for-openvz/comment-page-#comment-361</link>
		<dc:creator>Dev</dc:creator>
		<pubDate>Fri, 29 Dec 2006 06:23:25 +0000</pubDate>
		<guid isPermaLink="false">http://hostingfu.com/?p=77#comment-361</guid>
		<description>&lt;p&gt;Matt, aren&#039;t you taking simlpy what Herbert tells you?
1. Have you looked at so called disk I/O QoS in Vserver?
It is not &lt;em&gt;per-VPS&lt;/em&gt;. Simply run 10 tars in one VPS and
monitor how it affects another one. You will be suprised :)
You will be suprised to know that CFQ scheduler also doesn&#039;t handle writes.
OpenVZ is going to fix all this very soon and the first step was already done -
commited disk I/O accounting patches.
2. limit for RSS? do you really think that killing an application w/o giving it a chance
to handle out-of-memory situation gracefully is a good idea?
ok, if I wanted to select the easies way, I would definetely choose the same.&lt;/p&gt;
&lt;p&gt;why don&#039;t you use vserver if it is more advanced? don&#039;t you want to do all this dirty hacks and tweaks to make it work?&lt;/p&gt;</description>
		<content:encoded><![CDATA[<p>Matt, aren&#8217;t you taking simlpy what Herbert tells you?<br />
1. Have you looked at so called disk I/O QoS in Vserver?<br />
It is not <em>per-VPS</em>. Simply run 10 tars in one VPS and<br />
monitor how it affects another one. You will be suprised :)<br />
You will be suprised to know that CFQ scheduler also doesn&#8217;t handle writes.<br />
OpenVZ is going to fix all this very soon and the first step was already done -<br />
commited disk I/O accounting patches.<br />
2. limit for RSS? do you really think that killing an application w/o giving it a chance<br />
to handle out-of-memory situation gracefully is a good idea?<br />
ok, if I wanted to select the easies way, I would definetely choose the same.</p>
<p>why don&#8217;t you use vserver if it is more advanced? don&#8217;t you want to do all this dirty hacks and tweaks to make it work?</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: scotty</title>
		<link>http://hostingfu.com/article/is-virtuozzo-good-for-openvz/comment-page-1#comment-363</link>
		<dc:creator>scotty</dc:creator>
		<pubDate>Wed, 20 Dec 2006 23:14:42 +0000</pubDate>
		<guid isPermaLink="false">http://hostingfu.com/?p=77#comment-363</guid>
		<description>&lt;p&gt;Hi Matt!&lt;/p&gt;
&lt;p&gt;&quot;Now based on all of this, why did you choose OpenVZ over VServer?&quot;&lt;/p&gt;
&lt;p&gt;Sold by the SWSoft propaganda that Virtuozzo == VPS?&lt;/p&gt;
&lt;p&gt;We actually have used OpenVZ for quite a while at work when we started getting those 4-core 2850/2950&#039;s with massive amount of RAM for development. When I did a search on &quot;VPS&quot; on Google, it looked like the most obvious choice was Virtuozzo because &quot;everyone else was using it&quot;. As OpenVZ is similar to Virtuozzo so we went ahead with it.&lt;/p&gt;
&lt;p&gt;I was aware of VServer but had an impression that quite a lot of things have not been virtualized (networking, or iptables as you have mentioned), but from the spec it does have a lot of advantages over OpenVZ. It&#039;s definitely on my to-do list, but I&#039;ll leave it to next year :)&lt;/p&gt;</description>
		<content:encoded><![CDATA[<p>Hi Matt!</p>
<p>&#8220;Now based on all of this, why did you choose OpenVZ over VServer?&#8221;</p>
<p>Sold by the SWSoft propaganda that Virtuozzo == VPS?</p>
<p>We actually have used OpenVZ for quite a while at work when we started getting those 4-core 2850/2950&#8242;s with massive amount of RAM for development. When I did a search on &#8220;VPS&#8221; on Google, it looked like the most obvious choice was Virtuozzo because &#8220;everyone else was using it&#8221;. As OpenVZ is similar to Virtuozzo so we went ahead with it.</p>
<p>I was aware of VServer but had an impression that quite a lot of things have not been virtualized (networking, or iptables as you have mentioned), but from the spec it does have a lot of advantages over OpenVZ. It&#8217;s definitely on my to-do list, but I&#8217;ll leave it to next year :)</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Matt Ayres</title>
		<link>http://hostingfu.com/article/is-virtuozzo-good-for-openvz/comment-page-1#comment-362</link>
		<dc:creator>Matt Ayres</dc:creator>
		<pubDate>Wed, 20 Dec 2006 15:53:55 +0000</pubDate>
		<guid isPermaLink="false">http://hostingfu.com/?p=77#comment-362</guid>
		<description>&lt;p&gt;Interesting to mention Linux VServer.  I know the project very well since it&#039;s beginnings and even contributed lots of testing and some code to it&#039;s earlier versions. I am actually amazed OpenVZ was adopted so rapidly by many while Linux VServer/FreeVPS projects have both existed for years before. Linux VServer is a more advanced kernel than OpenVZ&#039;s in some areas with CoW links vs overlay filesystem (VZFS), a limit for RSS (even before Virtuozzo SLM was available), and CFQ disk I/O QoS implemented per-VPS.  What OpenVZ did provide was mature tools, easy installation, and a 100+ page PDF manual.  It doesn&#039;t help that Linux VServer does not yet have iptables inside the VPS or even 2nd-level quota support (which it actually had in it&#039;s 2.4 kernel). Now based on all of this, why did you choose OpenVZ over VServer?&lt;/p&gt;</description>
		<content:encoded><![CDATA[<p>Interesting to mention Linux VServer.  I know the project very well since it&#8217;s beginnings and even contributed lots of testing and some code to it&#8217;s earlier versions. I am actually amazed OpenVZ was adopted so rapidly by many while Linux VServer/FreeVPS projects have both existed for years before. Linux VServer is a more advanced kernel than OpenVZ&#8217;s in some areas with CoW links vs overlay filesystem (VZFS), a limit for RSS (even before Virtuozzo SLM was available), and CFQ disk I/O QoS implemented per-VPS.  What OpenVZ did provide was mature tools, easy installation, and a 100+ page PDF manual.  It doesn&#8217;t help that Linux VServer does not yet have iptables inside the VPS or even 2nd-level quota support (which it actually had in it&#8217;s 2.4 kernel). Now based on all of this, why did you choose OpenVZ over VServer?</p>
]]></content:encoded>
	</item>
</channel>
</rss>
