VMware Communities
fynniboy123456
Contributor
Contributor
‎07-06-2023 07:09 AM
Jump to solution

XSAVE error

Hello Guys,

I need a 32 bit Win7 VM. I set it up but everytime I try to start it, it throws the XSAVE error at me "the processor doesn't support XSAVE. This virtual machine can not be powered on". I am rocking two Xeon x5620 in a HP Z800. It ran fine with workstation 15.x player a few months ago, tho it had a Win10 host, now it runs Win11. I also had a different GPU. My current version of VMware is 17.0.0 

I have googled the issue and disabled all the given stuff I found (Hyper V, WSL2, Sandbox, ect) but it doesn't work. I also checked the bios but all the virtualization stuff is turned on.  

What could the issue be? Do I need an older version of VMware? Am I missing a driver or something like that?  

Sorry if it's been discussed before but I couldn't find anything. Please don't be too harsh on me, I am new to all this stuff.

Thanks for your help!

Reply
0 Kudos
1 Solution

Accepted Solutions
Technogeezer
Immortal
Immortal
‎07-06-2023 11:32 AM
Jump to solution

Did you check the Workstation 17 CPU requirements here:

https://docs.vmware.com/en/VMware-Workstation-Pro/17/com.vmware.ws.using.doc/GUID-BBD199AA-C346-4334...

The CPU requirements have changed between Workstation 15 and 17. Workstation 15 and 16 indicate that the Westmere architecture CPUs are supported (the Xeon you have is a Westmere architecture CPU released in 2010). However, Workstation 17 no longer lists Westmere CPUs as supported - it only says that Intel CPUs released in 2011 and later are supported.

The XSAVE instruction was introduced in Sandy Bridge architecture, which followed Westmere. I'm wondering if VMware dropped support for Westmere CPUs because of the lack of the XSAVE instruction.

The other thing to check is that you've completely disabled Hyper-V. If the vmware.log of the VM has the monitor mode set to ULM, then you haven't disabled Hyper-V entirely. Windows 11 starts using things in Hyper-V so that simply uninstalling Hyper-V components doesn't do the job. (using the bcdedit command to set hypervisorlaunchtype to off is the piece that has to be done to completely disable hyper-v). 

 

 

- Paul (Technogeezer)
Editor of the Unofficial Fusion Companion Guides

View solution in original post

Reply
0 Kudos
2 Replies
Technogeezer
Immortal
Immortal
‎07-06-2023 11:32 AM
Jump to solution

Did you check the Workstation 17 CPU requirements here:

https://docs.vmware.com/en/VMware-Workstation-Pro/17/com.vmware.ws.using.doc/GUID-BBD199AA-C346-4334...

The CPU requirements have changed between Workstation 15 and 17. Workstation 15 and 16 indicate that the Westmere architecture CPUs are supported (the Xeon you have is a Westmere architecture CPU released in 2010). However, Workstation 17 no longer lists Westmere CPUs as supported - it only says that Intel CPUs released in 2011 and later are supported.

The XSAVE instruction was introduced in Sandy Bridge architecture, which followed Westmere. I'm wondering if VMware dropped support for Westmere CPUs because of the lack of the XSAVE instruction.

The other thing to check is that you've completely disabled Hyper-V. If the vmware.log of the VM has the monitor mode set to ULM, then you haven't disabled Hyper-V entirely. Windows 11 starts using things in Hyper-V so that simply uninstalling Hyper-V components doesn't do the job. (using the bcdedit command to set hypervisorlaunchtype to off is the piece that has to be done to completely disable hyper-v). 

 

 

- Paul (Technogeezer)
Editor of the Unofficial Fusion Companion Guides
Reply
0 Kudos
fynniboy123456
Contributor
Contributor
‎07-06-2023 01:29 PM
Jump to solution

Thanks for the info. That's obviously the issue. I will try my luck with workstation 16 player since I don't want to spend money on this project.

Reply
0 Kudos