<?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 Virtual machine crashes after login with &amp;quot;Unexpected signal: 11&amp;quot; error in VMware vSphere™ Discussions</title>
    <link>https://communities.vmware.com/t5/VMware-vSphere-Discussions/Virtual-machine-crashes-after-login-with-quot-Unexpected-signal/m-p/520026#M9390</link>
    <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Hello everybody,&lt;/P&gt;&lt;P&gt;since yesterday I have a problem in vSphere Client (not web interface, the old one) with a VM (Windows 7 64bit) where a custom application is installed. It uses a lot the video driver.&lt;/P&gt;&lt;P&gt;The VM runs on ESXi 6.0.0 build 3620759 (you can see the log file in attachment) together with two Windows Server 2008R2 machines (DC + generic server): only this machine is affected.&lt;/P&gt;&lt;P&gt;The VM has 128MB Total Video Memory, 3D Graphic Support enabled, VMware Tools 10.0 installed and it is part of a domain.&lt;/P&gt;&lt;P&gt;Now the problem is that immediately after the login the VM crashes and power off itself.&lt;/P&gt;&lt;P&gt;If you have a look to the log file there are lines like these:&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;2020-04-28T13:46:15Z[+4.315]| mks| I120: Msg_Post: Error&lt;/P&gt;&lt;P&gt;2020-04-28T13:46:15Z[+4.315]| mks| I120: [msg.log.error.unrecoverable] VMware ESX unrecoverable error: (mks)&lt;/P&gt;&lt;P&gt;2020-04-28T13:46:15Z[+4.315]| mks| I120+ Unexpected signal: 11.&lt;/P&gt;&lt;P&gt;2020-04-28T13:46:15Z[+4.315]| mks| I120: [msg.panic.haveLog] A log file is available in "/vmfs/volumes/5a312c66-c050cc36-4b19-90e2bae584d4/WSM01XXXXXX/vmware.log".&amp;nbsp; &lt;/P&gt;&lt;P&gt;2020-04-28T13:46:15Z[+4.315]| mks| I120: [msg.panic.requestSupport.withoutLog] You can request support.&amp;nbsp; &lt;/P&gt;&lt;P&gt;2020-04-28T13:46:15Z[+4.315]| mks| I120: [msg.panic.requestSupport.vmSupport.vmx86] &lt;/P&gt;&lt;P&gt;2020-04-28T13:46:15Z[+4.315]| mks| I120+ To collect data to submit to VMware technical support, run "vm-support".&lt;/P&gt;&lt;P&gt;2020-04-28T13:46:15Z[+4.315]| mks| I120: [msg.panic.response] We will respond on the basis of your support entitlement.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Has somebody already experienced in vSphere Client a problem like this and has a solution that can help? I have seen something similar related to VMware Player.&lt;/P&gt;&lt;P&gt;Thanks a lot.&lt;/P&gt;&lt;P&gt;Rodo&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
    <pubDate>Wed, 29 Apr 2020 09:49:53 GMT</pubDate>
    <dc:creator>rudycapp</dc:creator>
    <dc:date>2020-04-29T09:49:53Z</dc:date>
    <item>
      <title>Virtual machine crashes after login with "Unexpected signal: 11" error</title>
      <link>https://communities.vmware.com/t5/VMware-vSphere-Discussions/Virtual-machine-crashes-after-login-with-quot-Unexpected-signal/m-p/520026#M9390</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Hello everybody,&lt;/P&gt;&lt;P&gt;since yesterday I have a problem in vSphere Client (not web interface, the old one) with a VM (Windows 7 64bit) where a custom application is installed. It uses a lot the video driver.&lt;/P&gt;&lt;P&gt;The VM runs on ESXi 6.0.0 build 3620759 (you can see the log file in attachment) together with two Windows Server 2008R2 machines (DC + generic server): only this machine is affected.&lt;/P&gt;&lt;P&gt;The VM has 128MB Total Video Memory, 3D Graphic Support enabled, VMware Tools 10.0 installed and it is part of a domain.&lt;/P&gt;&lt;P&gt;Now the problem is that immediately after the login the VM crashes and power off itself.&lt;/P&gt;&lt;P&gt;If you have a look to the log file there are lines like these:&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;2020-04-28T13:46:15Z[+4.315]| mks| I120: Msg_Post: Error&lt;/P&gt;&lt;P&gt;2020-04-28T13:46:15Z[+4.315]| mks| I120: [msg.log.error.unrecoverable] VMware ESX unrecoverable error: (mks)&lt;/P&gt;&lt;P&gt;2020-04-28T13:46:15Z[+4.315]| mks| I120+ Unexpected signal: 11.&lt;/P&gt;&lt;P&gt;2020-04-28T13:46:15Z[+4.315]| mks| I120: [msg.panic.haveLog] A log file is available in "/vmfs/volumes/5a312c66-c050cc36-4b19-90e2bae584d4/WSM01XXXXXX/vmware.log".&amp;nbsp; &lt;/P&gt;&lt;P&gt;2020-04-28T13:46:15Z[+4.315]| mks| I120: [msg.panic.requestSupport.withoutLog] You can request support.&amp;nbsp; &lt;/P&gt;&lt;P&gt;2020-04-28T13:46:15Z[+4.315]| mks| I120: [msg.panic.requestSupport.vmSupport.vmx86] &lt;/P&gt;&lt;P&gt;2020-04-28T13:46:15Z[+4.315]| mks| I120+ To collect data to submit to VMware technical support, run "vm-support".&lt;/P&gt;&lt;P&gt;2020-04-28T13:46:15Z[+4.315]| mks| I120: [msg.panic.response] We will respond on the basis of your support entitlement.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Has somebody already experienced in vSphere Client a problem like this and has a solution that can help? I have seen something similar related to VMware Player.&lt;/P&gt;&lt;P&gt;Thanks a lot.&lt;/P&gt;&lt;P&gt;Rodo&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Wed, 29 Apr 2020 09:49:53 GMT</pubDate>
      <guid>https://communities.vmware.com/t5/VMware-vSphere-Discussions/Virtual-machine-crashes-after-login-with-quot-Unexpected-signal/m-p/520026#M9390</guid>
      <dc:creator>rudycapp</dc:creator>
      <dc:date>2020-04-29T09:49:53Z</dc:date>
    </item>
    <item>
      <title>Re: Virtual machine crashes after login with "Unexpected signal: 11" error</title>
      <link>https://communities.vmware.com/t5/VMware-vSphere-Discussions/Virtual-machine-crashes-after-login-with-quot-Unexpected-signal/m-p/520027#M9391</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;Sounds a lot like the issue described here: &lt;A href="https://kb.vmware.com/s/article/50862" title="https://kb.vmware.com/s/article/50862"&gt;VMware Knowledge Base&lt;/A&gt;&amp;nbsp; &lt;/P&gt;&lt;P&gt;Updating to ESXi to 6.0 P07 (build 9239799) should fix it... &lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;/Rubeck&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Wed, 29 Apr 2020 10:37:35 GMT</pubDate>
      <guid>https://communities.vmware.com/t5/VMware-vSphere-Discussions/Virtual-machine-crashes-after-login-with-quot-Unexpected-signal/m-p/520027#M9391</guid>
      <dc:creator>Rubeck</dc:creator>
      <dc:date>2020-04-29T10:37:35Z</dc:date>
    </item>
    <item>
      <title>Re: Virtual machine crashes after login with "Unexpected signal: 11" error</title>
      <link>https://communities.vmware.com/t5/VMware-vSphere-Discussions/Virtual-machine-crashes-after-login-with-quot-Unexpected-signal/m-p/520028#M9392</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Hello Rubeck,&lt;/P&gt;&lt;P&gt;thanks for your answer. I have already seen this issue in Knowledge Base.&lt;/P&gt;&lt;P&gt;The problem is that we cannot update the systems until the next approved general "upgrade", however in the meantime the people should work with this PC, that's why I'm looking for a temporary solution...waiting for the upgrade that can be in 3-4 months.&lt;/P&gt;&lt;P&gt;Thanks anyway for your time&lt;/P&gt;&lt;P&gt;Rodolfo&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Wed, 29 Apr 2020 12:45:34 GMT</pubDate>
      <guid>https://communities.vmware.com/t5/VMware-vSphere-Discussions/Virtual-machine-crashes-after-login-with-quot-Unexpected-signal/m-p/520028#M9392</guid>
      <dc:creator>rudycapp</dc:creator>
      <dc:date>2020-04-29T12:45:34Z</dc:date>
    </item>
    <item>
      <title>Re: Virtual machine crashes after login with "Unexpected signal: 11" error</title>
      <link>https://communities.vmware.com/t5/VMware-vSphere-Discussions/Virtual-machine-crashes-after-login-with-quot-Unexpected-signal/m-p/520029#M9393</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Shame, as there's lots of unsupported elements there - ESXi 6.0, Windows 7, Windows Server 2008.&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Wed, 29 Apr 2020 13:00:46 GMT</pubDate>
      <guid>https://communities.vmware.com/t5/VMware-vSphere-Discussions/Virtual-machine-crashes-after-login-with-quot-Unexpected-signal/m-p/520029#M9393</guid>
      <dc:creator>scott28tt</dc:creator>
      <dc:date>2020-04-29T13:00:46Z</dc:date>
    </item>
    <item>
      <title>Re: Virtual machine crashes after login with "Unexpected signal: 11" error</title>
      <link>https://communities.vmware.com/t5/VMware-vSphere-Discussions/Virtual-machine-crashes-after-login-with-quot-Unexpected-signal/m-p/520030#M9394</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Yes, it is. &lt;/P&gt;&lt;P&gt;What I can tell you is that only the windows 7 VM is affected, and I have seen that disabling the "3D graphic support" the VM doesn't crash...but this function is unfortunately needed to run our application.&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Wed, 29 Apr 2020 14:14:38 GMT</pubDate>
      <guid>https://communities.vmware.com/t5/VMware-vSphere-Discussions/Virtual-machine-crashes-after-login-with-quot-Unexpected-signal/m-p/520030#M9394</guid>
      <dc:creator>rudycapp</dc:creator>
      <dc:date>2020-04-29T14:14:38Z</dc:date>
    </item>
  </channel>
</rss>

