<?xml version="1.0" encoding="UTF-8"?>
<rss xmlns:content="http://purl.org/rss/1.0/modules/content/" xmlns:clearspace="http://www.jivesoftware.com/xmlns/clearspace/rss" xmlns:rdf="http://www.w3.org/1999/02/22-rdf-syntax-ns#" xmlns:wfw="http://wellformedweb.org/CommentAPI/" xmlns:opensearch="http://a9.com/-/spec/opensearch/1.1/" xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:taxo="http://purl.org/rss/1.0/modules/taxonomy/" version="2.0">
  <channel>
    <title>V-IT, I AM GOING THROUGH IT</title>
    <link>http://communities.vmware.com/blogs/eagleh</link>
    <description>VIRTUALIZING IS REVOLUTIONARY! I AM GOING THROUGH IT....</description>
    <pubDate>Wed, 28 May 2008 15:20:42 GMT</pubDate>
    <generator>Clearspace 1.10.12 (http://jivesoftware.com/products/clearspace/)</generator>
    <dc:date>2008-05-28T15:20:42Z</dc:date>
    <item>
      <title>System CPU usage spikes to 100%</title>
      <link>http://communities.vmware.com/blogs/eagleh/2008/05/28/system-cpu-usage-spikes-to-100</link>
      <description>This is an ongoing issue that bothers me from time to time since our VMware Infrastructure in production. There could be quiet a few reasons cause this problem. Everytime it spikes, the whole machine is rendered useless. I have done:&lt;br /&gt;
&lt;br /&gt;
1&amp;gt; Applied ESX3.5 Update 1 and VirtualCenter 2.5 Update 1 (This CPU problem has been fixed for a while, however, it came back recently.) &lt;br /&gt;
2&amp;gt; I am holding off the April-30-2008 patch because people are saying it brought back the CPU problem which Update 1 had fixed.&lt;br /&gt;
3&amp;gt; I switch DRS from Partially Automatic to Manually. So there should not be any Vmotion happened until next patch for this CPU issue. I have observed that Vmotion could be one reason to trigger this High CPU issue.&lt;br /&gt;
4&amp;gt; However, yesterday, it happened right at 5PM (without any Vmotion). So I guess it has to be something scheduled to run at 5PM. Eventually I realized MS System Center Essential Agent was installed on this VM. uhha! It was a left-over. Uninstalled it and hopefully that was it.&lt;br /&gt;
&lt;p /&gt;
This issue has been driving me NUTS!</description>
      <category domain="http://communities.vmware.com/blogs/eagleh/tags">system</category>
      <category domain="http://communities.vmware.com/blogs/eagleh/tags">cpu</category>
      <category domain="http://communities.vmware.com/blogs/eagleh/tags">usage</category>
      <category domain="http://communities.vmware.com/blogs/eagleh/tags">spikes</category>
      <pubDate>Wed, 28 May 2008 15:31:00 GMT</pubDate>
      <author>eagleh</author>
      <guid>http://communities.vmware.com/blogs/eagleh/2008/05/28/system-cpu-usage-spikes-to-100</guid>
      <dc:date>2008-05-28T15:31:00Z</dc:date>
      <clearspace:dateToText>1 year, 9 months ago</clearspace:dateToText>
      <clearspace:replyCount>2</clearspace:replyCount>
      <wfw:comment>http://communities.vmware.com/blogs/eagleh/comment/system-cpu-usage-spikes-to-100</wfw:comment>
      <wfw:commentRss>http://communities.vmware.com/blogs/eagleh/feeds/comments?blogPostID=1793</wfw:commentRss>
    </item>
  </channel>
</rss>

