Hi,
Error: The processor does not support XSAVE. This virtual machine cannot be powered on.
I am in a trouble. Everything was working fine for years, but then last week I installed the Docker for Desktop and I started getting the following error whenever I try to turn ON any of the VM Machine.
First I get the "side channel mitigation" issue, then "XSAVE" issue start upon disabling the side channel mitigation from the VM Machine Settings ---> .
Even though I uninstalled the Docker, but things are same.
Host Details:
Processor: Intel(R) Xeon(R) CPU X5650 @ 2.67GHz 2.66 GHz (2 processors)
Installed RAM: 16.0 GB
System type 64-bit operating system, x64-based processor
Edition: Windows 10 Pro
Version: 20H2
Installed on: 1/29/2021
OS build: 19042.868
Experience Windows Feature Experience Pack 120.2212.551.0
Guest Details (Multiple Guests, but same problem with all):
Windows 7
Windows 10
Ubuntu 20.04
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.
X5650 CPU is from Westmere generation (one behind Sandy Bridge). The XSAVE instruction was introduced in the Sandy Bridge generation of Intel CPUs.
After removing Docker, the Hyper-V components are likely still active. Refer to this KB on steps to remove it.
https://kb.vmware.com/s/article/2146361
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.
X5650 CPU is from Westmere generation (one behind Sandy Bridge). The XSAVE instruction was introduced in the Sandy Bridge generation of Intel CPUs.
After removing Docker, the Hyper-V components are likely still active. Refer to this KB on steps to remove it.
https://kb.vmware.com/s/article/2146361
Thank you it worked.
Hypervisor was set to auto, just disabled it with the instructions and everything worked fine.
So, how do I fix this on a Mac OS X host?
@Fred_4 wrote:
So, how do I fix this on a Mac OS X host?
Totally different problem, and different product. Search the Fusion forum for posts regarding no longer supported hardware by Apple and VMware, etc. Short answer = you can't.