<?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>WJPatton.com &#187; CIM</title>
	<atom:link href="http://wjpatton.com/index.php/tag/cim/feed/" rel="self" type="application/rss+xml" />
	<link>http://wjpatton.com</link>
	<description></description>
	<lastBuildDate>Fri, 23 Dec 2011 17:33:20 +0000</lastBuildDate>
	<language>en</language>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
	<generator>http://wordpress.org/?v=3.2.1</generator>
		<item>
		<title>VMware KB1009607 &#8211; Pegasus CIMSERVER Memory Leak</title>
		<link>http://wjpatton.com/index.php/2009/11/vmware-kb1009607-pegasus-cimserver-memory-leak/</link>
		<comments>http://wjpatton.com/index.php/2009/11/vmware-kb1009607-pegasus-cimserver-memory-leak/#comments</comments>
		<pubDate>Fri, 06 Nov 2009 20:56:26 +0000</pubDate>
		<dc:creator>wjpatton</dc:creator>
				<category><![CDATA[Virtualization]]></category>
		<category><![CDATA[VMware]]></category>
		<category><![CDATA[CIM]]></category>
		<category><![CDATA[ESX3.5]]></category>
		<category><![CDATA[ESX4]]></category>
		<category><![CDATA[HP]]></category>
		<category><![CDATA[KB]]></category>

		<guid isPermaLink="false">http://wjpatton.com/?p=199</guid>
		<description><![CDATA[VMware has acknowledged an issue that we have been battling for some time with a Pegasus CIMSERVER memory leak.  It has been fixed under ESX 4, as it does not use Pegasus, otherwise setup a CRON job for restart Pegasus periodically. This issue has been extremely frustrating in our environment for a very long time, [...]]]></description>
			<content:encoded><![CDATA[<p>VMware has acknowledged an issue that we have been battling for some time with a Pegasus CIMSERVER memory leak.  It has been fixed under ESX 4, as it does not use Pegasus, otherwise setup a CRON job for restart Pegasus periodically.</p>
<p>This issue has been extremely frustrating in our environment for a very long time, and initially we suspected that HP SIM may be to blame, turns out we may have gotten that wrong.</p>
<p>We have worked with VMware Support many times, and this is the first time they have acknowledged this leak and that HP SIM is not the culprit.</p>
<p><a href="http://kb.vmware.com/selfservice/microsites/search.do?language=en_US&amp;cmd=displayKC&amp;externalId=1009607" target="_blank">Read the KB here.</a></p>
]]></content:encoded>
			<wfw:commentRss>http://wjpatton.com/index.php/2009/11/vmware-kb1009607-pegasus-cimserver-memory-leak/feed/</wfw:commentRss>
		<slash:comments>2</slash:comments>
		</item>
	</channel>
</rss>

