<?xml version="1.0" encoding="UTF-8"?>
<rss version="2.0"
	xmlns:content="http://purl.org/rss/1.0/modules/content/"
	xmlns:wfw="http://wellformedweb.org/CommentAPI/"
	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/"
	xmlns:slash="http://purl.org/rss/1.0/modules/slash/"
	>

<channel>
	<title>Malaysia VMware Communities &#187; 64GB</title>
	<atom:link href="http://malaysiavm.com/blog/tag/64gb/feed/" rel="self" type="application/rss+xml" />
	<link>http://malaysiavm.com/blog</link>
	<description></description>
	<lastBuildDate>Thu, 26 Apr 2012 15:54:26 +0000</lastBuildDate>
	<language>en</language>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
	<generator>http://wordpress.org/?v=3.3.1</generator>
		<item>
		<title>How to enable ESX host memory to utilize more than 64GB physical Memory</title>
		<link>http://malaysiavm.com/blog/esxwithmorethan64gbmem/</link>
		<comments>http://malaysiavm.com/blog/esxwithmorethan64gbmem/#comments</comments>
		<pubDate>Tue, 26 Aug 2008 16:40:16 +0000</pubDate>
		<dc:creator>craig</dc:creator>
				<category><![CDATA[Tips]]></category>
		<category><![CDATA[Virtualization]]></category>
		<category><![CDATA[64GB]]></category>
		<category><![CDATA[ESX]]></category>
		<category><![CDATA[Memory]]></category>
		<category><![CDATA[VM]]></category>
		<category><![CDATA[VMware]]></category>

		<guid isPermaLink="false">http://malaysiavm.com/blog/?p=185</guid>
		<description><![CDATA[Many of you may had experience difficult time to figure out what had been went wrong when you had ESX host which have more than 64GB physical memory. When I 1st reported this to VMware nearly a year ago, I had to wait for 3 days before VMware support team come back to me about [...]]]></description>
			<content:encoded><![CDATA[<p><script type="text/javascript"><!--
google_ad_client = "pub-7430566020196385";
/* MVM Index Link Code 468x15, created 1/3/10 */
google_ad_slot = "5937837755";
google_ad_width = 468;
google_ad_height = 15;
//-->
</script>
<script type="text/javascript"
src="http://pagead2.googlesyndication.com/pagead/show_ads.js">
</script></p><p>Many of you may had experience difficult time to figure out what had been went wrong when you had ESX host which have more than 64GB physical memory. When I 1st reported this to <a href="http://www.malaysiavm.com/blog/tag/vmware">VMware</a> nearly a year ago, I had to wait for 3 days before <a href="http://www.malaysiavm.com/blog/tag/vmware">VMware</a> support team come back to me about the solution below.</p>
<p>You may need to change the setting in 1 of the vmkernel setting from your virtual center to the specify <a href="http://www.malaysiavm.com/blog/tag/vmware">ESX</a> host.<br />
<span id="more-185"></span><br />
Look for VMkernel.Boot.force36BitMTRRMask, and uncheck the box. Follow by a reboot of the <a href="http://www.malaysiavm.com/blog/tag/esx">ESX</a> host, your <a href="http://www.malaysiavm.com/blog/tag/esx">ESX</a> should back to normal. Remember to do this before you start to provision any VM on it.</p>
]]></content:encoded>
			<wfw:commentRss>http://malaysiavm.com/blog/esxwithmorethan64gbmem/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
	</channel>
</rss>

<!-- Dynamic Page Served (once) in 0.340 seconds -->

