<?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>VMware Communities: Message List - ESX 3.5 Update 1 - PSOD (Crash)</title>
    <link>http://communities.vmware.com/community/vmtn/vi/esx3.5?view=discussions</link>
    <description>Most recent forum messages</description>
    <language>en</language>
    <pubDate>Sat, 19 Jul 2008 21:59:27 GMT</pubDate>
    <generator>Clearspace 1.10.12 (http://jivesoftware.com/products/clearspace/)</generator>
    <dc:date>2008-07-19T21:59:27Z</dc:date>
    <dc:language>en</dc:language>
    <item>
      <title>Re: ESX 3.5 Update 1 - PSOD (Crash)</title>
      <link>http://communities.vmware.com/message/997866?tstart=0#997866</link>
      <description>Both exceptions were page faults with the vm.  Have you checked the console memory?  Are you seeing memory utilization as high?  &lt;br /&gt;
&lt;br /&gt;
-KjB</description>
      <pubDate>Sat, 19 Jul 2008 21:59:27 GMT</pubDate>
      <author>kjb007</author>
      <guid>http://communities.vmware.com/message/997866?tstart=0#997866</guid>
      <dc:date>2008-07-19T21:59:27Z</dc:date>
      <clearspace:dateToText>1 year, 4 months ago</clearspace:dateToText>
    </item>
    <item>
      <title>Re: ESX 3.5 Update 1 - PSOD (Crash)</title>
      <link>http://communities.vmware.com/message/997008?tstart=0#997008</link>
      <description>Hello,&lt;br /&gt;
&lt;br /&gt;
As mcowger states, VMware ESX stresses systems more than any OS out there. I would do the following:&lt;br /&gt;
&lt;br /&gt;
Ensure the BIOS is updated to the latest (per Dell Instructions) for system and PCI cards, etc.&lt;br /&gt;
Ensure that all components within the box are on the HCL (specifically RAID and other PCI/PCIe/PCI-X cards)&lt;br /&gt;
Ensure the BIOS is configured for ESX per Dell instrcutions.&lt;br /&gt;
Run Hardware DIags from Dell for at least 24-48 hours&lt;br /&gt;
Run memtest86 for at least 24-48 hours&lt;br /&gt;
&lt;br /&gt;
Generally I see these issues when the BIOS has not been updated.&lt;br /&gt;
&lt;br /&gt;
&lt;br&gt;Best regards,&lt;br /&gt;
Edward L. Haletky&lt;br /&gt;
VMware Communities User Moderator&lt;br /&gt;
====&lt;br /&gt;
Author of the book 'VMWare ESX Server in the Enterprise: Planning and Securing Virtualization Servers', Copyright 2008 Pearson Education. &lt;br /&gt;
CIO Virtualization Blog: &lt;a class="jive-link-external" href="http://www.cio.com/blog/index/topic/168354"&gt;http://www.cio.com/blog/index/topic/168354&lt;/a&gt;&lt;br /&gt;
As well as the Virtualization Wiki at &lt;a class="jive-link-external" href="http://www.astroarch.com/wiki/index.php/Virtualization"&gt;http://www.astroarch.com/wiki/index.php/Virtualization&lt;/a&gt;</description>
      <pubDate>Fri, 18 Jul 2008 12:39:30 GMT</pubDate>
      <author>Texiwill</author>
      <guid>http://communities.vmware.com/message/997008?tstart=0#997008</guid>
      <dc:date>2008-07-18T12:39:30Z</dc:date>
      <clearspace:dateToText>1 year, 4 months ago</clearspace:dateToText>
    </item>
    <item>
      <title>Re: ESX 3.5 Update 1 - PSOD (Crash)</title>
      <link>http://communities.vmware.com/message/996791?tstart=0#996791</link>
      <description>ESX stresses machines very diffirently, and a PSOD is almost always a hardware issue.&lt;br /&gt;
&lt;br /&gt;
Makre sure you have updated the BIOS on that 1850, as well as the BMC and SAS backplane firmwares.&lt;br /&gt;
&lt;p /&gt;
--Matt</description>
      <pubDate>Fri, 18 Jul 2008 04:35:49 GMT</pubDate>
      <author>mcowger</author>
      <guid>http://communities.vmware.com/message/996791?tstart=0#996791</guid>
      <dc:date>2008-07-18T04:35:49Z</dc:date>
      <clearspace:dateToText>1 year, 4 months ago</clearspace:dateToText>
      <clearspace:replyCount>1</clearspace:replyCount>
    </item>
    <item>
      <title>Re: ESX 3.5 Update 1 - PSOD (Crash)</title>
      <link>http://communities.vmware.com/message/995960?tstart=0#995960</link>
      <description>&lt;br /&gt;
Update:&lt;br /&gt;
&lt;p /&gt;
 System has passed a full memtest using memtest86 3.4a.  The server is in the list of officially supported hardware.&lt;br /&gt;
&lt;p /&gt;
I tried copying the same iso file from the OpenSUSE 10.3 guest to the Windows XP guest, again with WinSCP, and again got the purple screen of death.  I will attach this crash dump as well for comparison.&lt;br /&gt;
&lt;p /&gt;
&lt;br /&gt;</description>
      <pubDate>Thu, 17 Jul 2008 10:12:26 GMT</pubDate>
      <author>dbvuetec</author>
      <guid>http://communities.vmware.com/message/995960?tstart=0#995960</guid>
      <dc:date>2008-07-17T10:12:26Z</dc:date>
      <clearspace:dateToText>1 year, 4 months ago</clearspace:dateToText>
      <clearspace:replyCount>1</clearspace:replyCount>
    </item>
    <item>
      <title>Re: ESX 3.5 Update 1 - PSOD (Crash)</title>
      <link>http://communities.vmware.com/message/995903?tstart=0#995903</link>
      <description>bumping for sheer fascination</description>
      <pubDate>Thu, 17 Jul 2008 08:36:37 GMT</pubDate>
      <author>RussellCorey</author>
      <guid>http://communities.vmware.com/message/995903?tstart=0#995903</guid>
      <dc:date>2008-07-17T08:36:37Z</dc:date>
      <clearspace:dateToText>1 year, 4 months ago</clearspace:dateToText>
    </item>
    <item>
      <title>ESX 3.5 Update 1 - PSOD (Crash)</title>
      <link>http://communities.vmware.com/message/995849?tstart=0#995849</link>
      <description>&lt;br /&gt;
Hi guys, I'm just in the process of evaluating ESX 3.5 Update 1, on a Dell 1850 server.  This server has been running OpenSUSE in a production environment for a number of years now without any lockups or crashes.  I have 3 vms installed on it (local storage SCSI raid), openSUSE 10.3, 11.0 and a novelty Windows XP which is used primarily for accessing the VI client, and the DRAC etc.&lt;br /&gt;
&lt;p /&gt;
At the time of the crash, I was using WinSCP on the Windows XP guest, to copy a couple of ISO images off the 10.3 guest.&lt;br /&gt;
&lt;p /&gt;
 I might add this crash is quite disturbing, and although it could be a hardware problem (memory or chipset issue), it probably isn't, given that it has never crashed before up until this point.&lt;br /&gt;
&lt;p /&gt;
&lt;br /&gt;</description>
      <pubDate>Thu, 17 Jul 2008 05:24:22 GMT</pubDate>
      <author>dbvuetec</author>
      <guid>http://communities.vmware.com/message/995849?tstart=0#995849</guid>
      <dc:date>2008-07-17T05:24:22Z</dc:date>
      <clearspace:dateToText>1 year, 4 months ago</clearspace:dateToText>
      <clearspace:replyCount>5</clearspace:replyCount>
    </item>
  </channel>
</rss>

