<?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: The processor does not support XSAVE. This virtual machine cannot be powered on. Docker caused i in VMware Workstation Pro Discussions</title>
    <link>https://communities.vmware.com/t5/VMware-Workstation-Pro/The-processor-does-not-support-XSAVE-This-virtual-machine-cannot/m-p/2839615#M169465</link>
    <description>&lt;P&gt;Thank you it worked.&lt;/P&gt;&lt;P&gt;Hypervisor was set to auto, just disabled it with the instructions and everything worked fine.&lt;/P&gt;</description>
    <pubDate>Fri, 02 Apr 2021 23:07:54 GMT</pubDate>
    <dc:creator>SherJaan</dc:creator>
    <dc:date>2021-04-02T23:07:54Z</dc:date>
    <item>
      <title>The processor does not support XSAVE. This virtual machine cannot be powered on. Docker caused issue</title>
      <link>https://communities.vmware.com/t5/VMware-Workstation-Pro/The-processor-does-not-support-XSAVE-This-virtual-machine-cannot/m-p/2839604#M169462</link>
      <description>&lt;P&gt;Hi,&lt;/P&gt;&lt;P&gt;Error:&amp;nbsp;&lt;STRONG&gt;The processor does not support XSAVE. This virtual machine cannot be powered on.&lt;/STRONG&gt;&lt;/P&gt;&lt;P&gt;I am in a trouble. Everything was working fine for years, but then last week I installed the &lt;STRONG&gt;Docker for Desktop&lt;/STRONG&gt; and I started getting the following error whenever I try to turn ON any of the VM Machine.&lt;/P&gt;&lt;P&gt;First I get the "side channel mitigation" issue, then "XSAVE" issue start upon disabling the side channel mitigation from the VM Machine Settings ---&amp;gt; .&lt;/P&gt;&lt;P&gt;Even though I uninstalled the Docker, but things are same.&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;&lt;STRONG&gt;Host Details:&lt;/STRONG&gt;&lt;BR /&gt;Processor: Intel(R) Xeon(R) CPU X5650 @ 2.67GHz 2.66 GHz (2 processors)&lt;BR /&gt;Installed RAM: 16.0 GB&lt;BR /&gt;System type 64-bit operating system, x64-based processor&lt;/P&gt;&lt;P&gt;Edition: Windows 10 Pro&lt;BR /&gt;Version: 20H2&lt;BR /&gt;Installed on: ‎1/‎29/‎2021&lt;BR /&gt;OS build: 19042.868&lt;BR /&gt;Experience Windows Feature Experience Pack 120.2212.551.0&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;&lt;STRONG&gt;Guest Details (Multiple Guests, but same problem with all):&lt;/STRONG&gt;&lt;/P&gt;&lt;P&gt;Windows 7&lt;/P&gt;&lt;P&gt;Windows 10&lt;/P&gt;&lt;P&gt;Ubuntu 20.04&lt;/P&gt;&lt;P&gt;&lt;span class="lia-inline-image-display-wrapper lia-image-align-center" image-alt="VM4.jpg" style="width: 400px;"&gt;&lt;img src="https://communities.vmware.com/t5/image/serverpage/image-id/87965i61746AC4E3A862BB/image-size/medium/is-moderation-mode/true?v=v2&amp;amp;px=400" role="button" title="VM4.jpg" alt="VM4.jpg" /&gt;&lt;/span&gt;&lt;/P&gt;&lt;P&gt; &lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;&lt;span class="lia-inline-image-display-wrapper lia-image-align-center" image-alt="VM2.jpg" style="width: 400px;"&gt;&lt;img src="https://communities.vmware.com/t5/image/serverpage/image-id/87962i11D7F0BE549FB2EB/image-size/medium/is-moderation-mode/true?v=v2&amp;amp;px=400" role="button" title="VM2.jpg" alt="VM2.jpg" /&gt;&lt;/span&gt;&lt;/P&gt;&lt;P&gt;&lt;span class="lia-inline-image-display-wrapper lia-image-align-center" image-alt="VM3.jpg" style="width: 999px;"&gt;&lt;img src="https://communities.vmware.com/t5/image/serverpage/image-id/87964i3A6AE10BB3304ADB/image-size/large/is-moderation-mode/true?v=v2&amp;amp;px=999" role="button" title="VM3.jpg" alt="VM3.jpg" /&gt;&lt;/span&gt;&lt;/P&gt;&lt;P&gt; &lt;/P&gt;&lt;P&gt; &lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;&lt;span class="lia-inline-image-display-wrapper lia-image-align-center" image-alt="VM.jpg" style="width: 400px;"&gt;&lt;img src="https://communities.vmware.com/t5/image/serverpage/image-id/87963i07E04A15394FFD1D/image-size/medium/is-moderation-mode/true?v=v2&amp;amp;px=400" role="button" title="VM.jpg" alt="VM.jpg" /&gt;&lt;/span&gt;&lt;/P&gt;&lt;P&gt; &lt;/P&gt;</description>
      <pubDate>Fri, 02 Apr 2021 21:23:33 GMT</pubDate>
      <guid>https://communities.vmware.com/t5/VMware-Workstation-Pro/The-processor-does-not-support-XSAVE-This-virtual-machine-cannot/m-p/2839604#M169462</guid>
      <dc:creator>SherJaan</dc:creator>
      <dc:date>2021-04-02T21:23:33Z</dc:date>
    </item>
    <item>
      <title>Re: The processor does not support XSAVE. This virtual machine cannot be powered on. Docker caused i</title>
      <link>https://communities.vmware.com/t5/VMware-Workstation-Pro/The-processor-does-not-support-XSAVE-This-virtual-machine-cannot/m-p/2839610#M169464</link>
      <description>&lt;P&gt;&lt;BR /&gt;When Hyper-V is enabled on the Windows host (such is the result of installing Docker on a Windows host), the Microsoft Hypervisor API is used instead of the ring 0 VMM. The minimum CPU requirement becomes Sandy Bridge as well.&lt;/P&gt;&lt;P&gt;&lt;A href="https://docs.vmware.com/en/VMware-Workstation-Pro/16.0/com.vmware.ws.using.doc/GUID-177F1E77-BFFD-485F-90BB-2E45B6B88678.html" target="_blank"&gt;https://docs.vmware.com/en/VMware-Workstation-Pro/16.0/com.vmware.ws.using.doc/GUID-177F1E77-BFFD-485F-90BB-2E45B6B88678.html&lt;/A&gt;&lt;/P&gt;&lt;P&gt;X5650 CPU is from Westmere generation (one behind Sandy Bridge). The XSAVE instruction was introduced in the Sandy Bridge generation of Intel CPUs.&lt;/P&gt;&lt;P&gt;After removing Docker, the Hyper-V components are likely still active. Refer to this KB on steps to remove it.&lt;BR /&gt;&lt;A href="https://kb.vmware.com/s/article/2146361" target="_blank"&gt;https://kb.vmware.com/s/article/2146361&lt;/A&gt;&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;</description>
      <pubDate>Fri, 02 Apr 2021 22:38:55 GMT</pubDate>
      <guid>https://communities.vmware.com/t5/VMware-Workstation-Pro/The-processor-does-not-support-XSAVE-This-virtual-machine-cannot/m-p/2839610#M169464</guid>
      <dc:creator>bluefirestorm</dc:creator>
      <dc:date>2021-04-02T22:38:55Z</dc:date>
    </item>
    <item>
      <title>Re: The processor does not support XSAVE. This virtual machine cannot be powered on. Docker caused i</title>
      <link>https://communities.vmware.com/t5/VMware-Workstation-Pro/The-processor-does-not-support-XSAVE-This-virtual-machine-cannot/m-p/2839615#M169465</link>
      <description>&lt;P&gt;Thank you it worked.&lt;/P&gt;&lt;P&gt;Hypervisor was set to auto, just disabled it with the instructions and everything worked fine.&lt;/P&gt;</description>
      <pubDate>Fri, 02 Apr 2021 23:07:54 GMT</pubDate>
      <guid>https://communities.vmware.com/t5/VMware-Workstation-Pro/The-processor-does-not-support-XSAVE-This-virtual-machine-cannot/m-p/2839615#M169465</guid>
      <dc:creator>SherJaan</dc:creator>
      <dc:date>2021-04-02T23:07:54Z</dc:date>
    </item>
    <item>
      <title>Re: The processor does not support XSAVE. This virtual machine cannot be powered on. Docker caused i</title>
      <link>https://communities.vmware.com/t5/VMware-Workstation-Pro/The-processor-does-not-support-XSAVE-This-virtual-machine-cannot/m-p/2927617#M177428</link>
      <description>&lt;P&gt;So, how do I fix this on a Mac OS X host?&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;</description>
      <pubDate>Wed, 07 Sep 2022 06:04:22 GMT</pubDate>
      <guid>https://communities.vmware.com/t5/VMware-Workstation-Pro/The-processor-does-not-support-XSAVE-This-virtual-machine-cannot/m-p/2927617#M177428</guid>
      <dc:creator>Fred_4</dc:creator>
      <dc:date>2022-09-07T06:04:22Z</dc:date>
    </item>
    <item>
      <title>Re: The processor does not support XSAVE. This virtual machine cannot be powered on. Docker caused i</title>
      <link>https://communities.vmware.com/t5/VMware-Workstation-Pro/The-processor-does-not-support-XSAVE-This-virtual-machine-cannot/m-p/2927653#M177430</link>
      <description>&lt;BLOCKQUOTE&gt;&lt;HR /&gt;&lt;a href="https://communities.vmware.com/t5/user/viewprofilepage/user-id/5575778"&gt;@Fred_4&lt;/a&gt;&amp;nbsp;wrote:&lt;BR /&gt;
&lt;P&gt;So, how do I fix this on a Mac OS X host?&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;HR /&gt;&lt;/BLOCKQUOTE&gt;
&lt;P&gt;Totally different problem, and different product.&amp;nbsp; Search the Fusion forum for posts regarding no longer supported hardware by Apple and VMware, etc.&amp;nbsp; Short answer = you can't.&lt;/P&gt;</description>
      <pubDate>Wed, 07 Sep 2022 11:41:06 GMT</pubDate>
      <guid>https://communities.vmware.com/t5/VMware-Workstation-Pro/The-processor-does-not-support-XSAVE-This-virtual-machine-cannot/m-p/2927653#M177430</guid>
      <dc:creator>RDPetruska</dc:creator>
      <dc:date>2022-09-07T11:41:06Z</dc:date>
    </item>
  </channel>
</rss>

