Upgraded WorkstationPro to 17.5.0 build-22583795 and all VMs now unstartable with XSAVE error

[EvilEmt]

Windows 10 guest, several Linux distro guest VMs functional under 17.0 prior to upgrade to 17.5.0 build-22583795.  After upgrade and reboot of host OS, all VMs unable to start.  Throwing "The processor does not support XSAVE. This virtual machine can not be powered on." error dialog.

Uninstalling 17.5 and reinstalling 17.0 resolves the error.

Pertinent HOST OS INFO

OS Name Microsoft Windows 10 Pro
Version 10.0.19045 Build 19045
System Manufacturer Dell Inc.
System Model Precision WorkStation T3500
System Type x64-based PC
Processor Intel(R) Xeon(R) CPU X5650 @ 2.67GHz, 2661 Mhz, 6 Core(s), 6 Logical Processor(s)
BIOS Version/Date Dell Inc. A17, 5/28/2013
SMBIOS Version 2.5
Embedded Controller Version 255.255
BIOS Mode Legacy
BaseBoard Manufacturer Dell Inc.
BaseBoard Product 09KPNV
BaseBoard Version A00
Platform Role SOHO Server
Secure Boot State Unsupported
PCR7 Configuration Binding Not Possible
Hardware Abstraction Layer Version = "10.0.19041.3570"
Installed Physical Memory (RAM) 24.0 GB
Total Physical Memory 24.0 GB
Available Physical Memory 19.2 GB
Total Virtual Memory 28.7 GB
Available Virtual Memory 22.5 GB
Page File Space 4.75 GB
Kernel DMA Protection Off
Virtualization-based security Not enabled
Device Encryption Support Reasons for failed automatic device encryption: TPM is not usable, PCR7 binding is not supported, Hardware Security Test Interface failed and device is not Modern Standby, Un-allowed DMA capable bus/device(s) detected, TPM is not usable
Hyper-V - VM Monitor Mode Extensions Yes
Hyper-V - Second Level Address Translation Extensions Yes
Hyper-V - Virtualization Enabled in Firmware Yes
Hyper-V - Data Execution Protection Yes

[Technogeezer]

VMware's hardware requirements for Workstation 17 per https://docs.vmware.com/en/VMware-Workstation-Pro/17/com.vmware.ws.using.doc/GUID-BBD199AA-C346-4334... 

are:

• A compatible 64-bit x86/AMD64 CPU launched in 2011 or later.

What isn't clear is that there seems to be a dependency on the XSAVE instruction. The requirements should more specifically read:

• An Intel Sandy Bridge or AMD Bulldozer family CPU or later.

as the XSAVE instruction was introduced in those family CPUs (which appears to coincide with the 2011 date). 

The Xeon X5650 is a Westmere family CPU, the generation immediately preceding Sandy Bridge. 

I wonder if VMware is now more strictly enforcing the processor requirement. I had a laptop with an older Intel chipset that worked fine under Workstation 17.0 and the VMware hypervisor (not Hyper-V). The Workstation Tech Preview would not run on that system as it is missing XSAVE . 

[Danny58]

I'm having the same problem. I have an Intel Xeon E5620. I don't like that VMware is changing hardware requirements without a warning!!

[Technogeezer]

---

@Danny58 wrote:

I'm having the same problem. I have an Intel Xeon E5620. I don't like that VMware is changing hardware requirements without a warning!!

---

I don't think VMware officially changed their processor requirement. It's just that it's being enforced. The hardware requirements have been in the release notes all along. 

[Danny58]

I guess it depends on where you look.

At this link: Windows VM | Workstation Pro | VMware:

• A compatible 64-bit x86/AMD64 CPU launched in 2011 or later *

If you look for the * towards the bottom of the page it shows that Xeon 5600 are supported:

* With exception, the following CPUs are not supported:

• Intel Atom processors based on the 2011 “Bonnell” micro-architecture (e.g. Atom Z670/Z650; Atom N570)
• Systems using Intel Atom processors based on the 2012 “Saltwell” micro-architecture (e.g. Atom S1200, Atom D2700/D2500, Atom N2800/N2600.
• Systems using AMD processors based on the “Llano” and “Bobcat” micro-architectures (e.g. code-named “Hondo”, “Ontario”, “Zacate”, “Llano”)

In addition, the following CPUs are supported:

• Intel processors based on the 2010 “Westmere” micro-architecture (e.g. Xeon 5600, Xeon
  3600, Core i7-970, Core i7-980, Core i7-990)

[dwknoble]

I'm having the same problem.  My i7-900 processor was purchased in 2011, but does not support XSAVE.  I now have an expensive Vmware Workstation 17 which is absolutely useless to me.  No more VMware for me.  I am now a former customer.

[RDPetruska]

---

@dwknoble wrote:

I'm having the same problem.  My i7-900 processor was purchased in 2011, but does not support XSAVE.  I now have an expensive Vmware Workstation 17 which is absolutely useless to me.  No more VMware for me.  I am now a former customer.

---

Well, you can still run 17.0.2 - so it's not expensive and absolutely useless...

[DhairyaT]

@EvilEmt Unable to reproduce this issue. Requesting you to again reproduce this issue and share the VM Support Bundle using below steps-

Help->Support->Collect Support Data

[dwknoble]

Since I've reverted to VMWare 15 (as opposed to my copious versions back to 5.5), I'm simply too busy at this point to reinstall 17, find the errors, then reinstall 15 so it works.  I can tell you that my processor is this:

Name Windows 10 Pro x64, version 22H2
Product Name Windows 10 Pro
Version 22H2 (OS Build 19045.3570)

System Start Options NOEXECUTE=OPTIN HYPERVISORLAUNCHTYPE=OFF
Kernel Version 10.0.19041.3570
KernelBase Version 10.0.19041.3570
Build Branch vb_release
Build Lab 19041.vb_release.191206-1406
Build Lab Ex 19041.1.amd64fre.vb_release.191206-1406

PROCESSOR_IDENTIFIER Intel64 Family 6 Model 44 Stepping 2, GenuineIntel
PROCESSOR_LEVEL 6
PROCESSOR_REVISION 2c02

This is from SIW.  The processor is listed in other programs is an i7-900.  It is a 6 core, 12 thread processor, in an HP Pavilion purchased in 2011.  (Yea, I've been hoping to get more current machine, but economics has delayed that.)

VMWare does not work with this processor (XSAVE error), which surprised me, as every version I've had in the past works well.

Thanks for your reply.

[dstrr]

Same issue. Intel Xeon X5675.

[DhairyaT]

Ticket has been raised. Relevant team will look into the same and revert.