<?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: VMware ESX Memory Over Commit Technology Explained</title>
	<atom:link href="http://vmetc.com/2009/01/30/vmware-esx-memory-over-commit-technology-explained/feed/" rel="self" type="application/rss+xml" />
	<link>http://vmetc.com/2009/01/30/vmware-esx-memory-over-commit-technology-explained/</link>
	<description>Go Green with Virtualization. Go UGLY Green with vmetc.com.</description>
	<lastBuildDate>Wed, 25 Jan 2012 13:41:00 +0000</lastBuildDate>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
	<generator>http://wordpress.org/?v=3.3.1</generator>
	<item>
		<title>By: Windows Server 2008 R2 Question - Overclock.net - Overclocking.net</title>
		<link>http://vmetc.com/2009/01/30/vmware-esx-memory-over-commit-technology-explained/comment-page-1/#comment-3922</link>
		<dc:creator>Windows Server 2008 R2 Question - Overclock.net - Overclocking.net</dc:creator>
		<pubDate>Sun, 03 Jan 2010 20:29:58 +0000</pubDate>
		<guid isPermaLink="false">http://vmetc.com/?p=3039#comment-3922</guid>
		<description>[...] with 1GB each without a problem, especially if they&#039;re all running the same OS.  Reference this: http://vmetc.com/2009/01/30/vmware-e...ogy-explained/  For a brief explanation about memory over-committing on ESX.   [...]</description>
		<content:encoded><![CDATA[<p>[...] with 1GB each without a problem, especially if they&#39;re all running the same OS.  Reference this: <a href="http://vmetc.com/2009/01/30/vmware-e...ogy-explained/" rel="nofollow">http://vmetc.com/2009/01/30/vmware-e&#8230;ogy-explained/</a>  For a brief explanation about memory over-committing on ESX.   [...]</p>
]]></content:encoded>
	</item>
</channel>
</rss>

