<?xml version="1.0" encoding="UTF-8"?>
<rss xmlns:content="http://purl.org/rss/1.0/modules/content/" xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:rdf="http://www.w3.org/1999/02/22-rdf-syntax-ns#" xmlns:taxo="http://purl.org/rss/1.0/modules/taxonomy/" version="2.0">
  <channel>
    <title>topic Re: VMware ESXi kernel panic in ESXi Discussions</title>
    <link>https://communities.vmware.com/t5/ESXi-Discussions/VMware-ESXi-kernel-panic/m-p/2709401#M265970</link>
    <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Hi,&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;I upgraded the to the latest bios version last friday. During the next scheduled maintenance I will try to reproduce the kernel panic.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Regards,&lt;/P&gt;&lt;P&gt;Steven&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
    <pubDate>Mon, 11 Jan 2016 11:35:26 GMT</pubDate>
    <dc:creator>nakrul</dc:creator>
    <dc:date>2016-01-11T11:35:26Z</dc:date>
    <item>
      <title>VMware ESXi kernel panic</title>
      <link>https://communities.vmware.com/t5/ESXi-Discussions/VMware-ESXi-kernel-panic/m-p/2709395#M265964</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Hello,&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;while copying data on a virtual machine with a Windows os from one hdd to another, the server started the configured automatic backup with veeam and ended in a kernel panic. Can you help me with the problem.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Thanks,&lt;/P&gt;&lt;P&gt;Steven&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Tue, 05 Jan 2016 13:15:38 GMT</pubDate>
      <guid>https://communities.vmware.com/t5/ESXi-Discussions/VMware-ESXi-kernel-panic/m-p/2709395#M265964</guid>
      <dc:creator>nakrul</dc:creator>
      <dc:date>2016-01-05T13:15:38Z</dc:date>
    </item>
    <item>
      <title>Re: VMware ESXi kernel panic</title>
      <link>https://communities.vmware.com/t5/ESXi-Discussions/VMware-ESXi-kernel-panic/m-p/2709396#M265965</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Hi&amp;nbsp; Steven,&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;The copy process and the Veeam Backup are completed successfully when run separately?&lt;/P&gt;&lt;P&gt;Can you reproduce the error? &lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;I can imagine that backup fails when copying an amount of data during the snapshotting proces, but I am not sure why that would cause a PSOD.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Regards,&lt;/P&gt;&lt;P&gt;Bart&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Wed, 06 Jan 2016 15:17:17 GMT</pubDate>
      <guid>https://communities.vmware.com/t5/ESXi-Discussions/VMware-ESXi-kernel-panic/m-p/2709396#M265965</guid>
      <dc:creator>bdonders</dc:creator>
      <dc:date>2016-01-06T15:17:17Z</dc:date>
    </item>
    <item>
      <title>Re: VMware ESXi kernel panic</title>
      <link>https://communities.vmware.com/t5/ESXi-Discussions/VMware-ESXi-kernel-panic/m-p/2709397#M265966</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;‌Hi Bart,&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;when run separately the copy process and the Veeam backup work like a charm. I will try to reproduce the PSOD on friday afternoon, I have scheduled a server maintenance then.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Regards,&lt;/P&gt;&lt;P&gt;Steven&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Wed, 06 Jan 2016 16:29:16 GMT</pubDate>
      <guid>https://communities.vmware.com/t5/ESXi-Discussions/VMware-ESXi-kernel-panic/m-p/2709397#M265966</guid>
      <dc:creator>nakrul</dc:creator>
      <dc:date>2016-01-06T16:29:16Z</dc:date>
    </item>
    <item>
      <title>Re: VMware ESXi kernel panic</title>
      <link>https://communities.vmware.com/t5/ESXi-Discussions/VMware-ESXi-kernel-panic/m-p/2709398#M265967</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Possibly related to &lt;A href="http://kb.vmware.com/kb/2135956"&gt;http://kb.vmware.com/kb/2135956&lt;/A&gt;?&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Wed, 06 Jan 2016 17:15:11 GMT</pubDate>
      <guid>https://communities.vmware.com/t5/ESXi-Discussions/VMware-ESXi-kernel-panic/m-p/2709398#M265967</guid>
      <dc:creator>admin</dc:creator>
      <dc:date>2016-01-06T17:15:11Z</dc:date>
    </item>
    <item>
      <title>Re: VMware ESXi kernel panic</title>
      <link>https://communities.vmware.com/t5/ESXi-Discussions/VMware-ESXi-kernel-panic/m-p/2709399#M265968</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Hi,&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;thanks for the hint to the knowledge base article. I have a single esxi host with vmware vsphere essentials. I have no distributed virtual switches or port groups defined that could cause the problem.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Regards,&lt;/P&gt;&lt;P&gt;Steven&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Thu, 07 Jan 2016 08:20:23 GMT</pubDate>
      <guid>https://communities.vmware.com/t5/ESXi-Discussions/VMware-ESXi-kernel-panic/m-p/2709399#M265968</guid>
      <dc:creator>nakrul</dc:creator>
      <dc:date>2016-01-07T08:20:23Z</dc:date>
    </item>
    <item>
      <title>Re: VMware ESXi kernel panic</title>
      <link>https://communities.vmware.com/t5/ESXi-Discussions/VMware-ESXi-kernel-panic/m-p/2709400#M265969</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Hi,&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;it seems very simmilar to the following backtrace:&lt;/P&gt;&lt;P&gt;(see the lines starting from &amp;lt;YYYY-MM_DD&amp;gt;&amp;lt;Time&amp;gt; cpu26:9842)@BlueScreen: PANIC bora/vmkernel/main/dlmalloc.c:4827 - Usage error in dlmalloc:)&lt;/P&gt;&lt;P&gt;&lt;A href="http://kb.vmware.com/selfservice/microsites/search.do?cmd=displayKC&amp;amp;docType=kc&amp;amp;externalId=2088300&amp;amp;sliceId=1&amp;amp;docTypeID=DT_KB_1_1&amp;amp;dialogID=911790501&amp;amp;stateId=0" title="http://kb.vmware.com/selfservice/microsites/search.do?cmd=displayKC&amp;amp;docType=kc&amp;amp;externalId=2088300&amp;amp;sliceId=1&amp;amp;docTypeID=DT_KB_1_1&amp;amp;dialogID=911790501&amp;amp;stateId=0"&gt;VMware KB: VMware ESXi 5.1.x host fails with a purple diagnostic screen and reports the error: PANIC bora/vmkernel/m…&lt;/A&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;H4 class="docheading Cause"&gt;Cause&lt;/H4&gt;&lt;DIV class="doccontent cc_Cause"&gt;This issue occurs if there is an issue with CPU hardware.&amp;nbsp; &lt;/DIV&gt;&lt;H4 class="docheading Resolution"&gt;Resolution&lt;/H4&gt;&lt;DIV class="doccontent cc_Resolution"&gt;&lt;DIV&gt;&lt;DIV&gt;&lt;SPAN style="color: #333333; text-indent: 0px; font-style: normal; font-weight: normal;"&gt;To resolve this issue, contact your hardware vendor for assistance&lt;/SPAN&gt;&lt;SPAN style="color: #333333; text-indent: 0px; font-style: normal; font-weight: normal;"&gt;. Also, consider a BIOS upgrade, if available.&lt;/SPAN&gt;&lt;/DIV&gt;&lt;/DIV&gt;&lt;/DIV&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Thu, 07 Jan 2016 09:49:32 GMT</pubDate>
      <guid>https://communities.vmware.com/t5/ESXi-Discussions/VMware-ESXi-kernel-panic/m-p/2709400#M265969</guid>
      <dc:creator>vNEX</dc:creator>
      <dc:date>2016-01-07T09:49:32Z</dc:date>
    </item>
    <item>
      <title>Re: VMware ESXi kernel panic</title>
      <link>https://communities.vmware.com/t5/ESXi-Discussions/VMware-ESXi-kernel-panic/m-p/2709401#M265970</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Hi,&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;I upgraded the to the latest bios version last friday. During the next scheduled maintenance I will try to reproduce the kernel panic.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Regards,&lt;/P&gt;&lt;P&gt;Steven&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Mon, 11 Jan 2016 11:35:26 GMT</pubDate>
      <guid>https://communities.vmware.com/t5/ESXi-Discussions/VMware-ESXi-kernel-panic/m-p/2709401#M265970</guid>
      <dc:creator>nakrul</dc:creator>
      <dc:date>2016-01-11T11:35:26Z</dc:date>
    </item>
  </channel>
</rss>

