![]() Energy, Climate Action & Sustainability.APEX Cloud Platform for Red Hat OpenShift.APEX Cloud Platform for Microsoft Azure.APEX Data Storage Services Backup Target.VMWare does not work with this processor (XSAVE error), which surprised me, as every version I've had in the past works well. (Yea, I've been hoping to get more current machine, but economics has delayed that.) It is a 6 core, 12 thread processor, in an HP Pavilion purchased in 2011. The processor is listed in other programs is an i7-900. ![]() PROCESSOR_IDENTIFIER Intel64 Family 6 Model 44 Stepping 2, GenuineIntel System Start Options NOEXECUTE=OPTIN HYPERVISORLAUNCHTYPE=OFFÄ«uild Lab Ex 19041.1.amd64fre.vb_release.191206-1406 I can tell you that my processor is this: 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. Hyper-V - Virtualization Enabled in Firmware Yes Hyper-V - Second Level Address Translation Extensions Yes Virtualization-based security Not enabledÄevice 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 Hardware Abstraction Layer Version = "1.3570" Processor Intel(R) Xeon(R) CPU X5650 2.67GHz, 2661 Mhz, 6 Core(s), 6 Logical Processor(s) Uninstalling 17.5 and reinstalling 17.0 resolves the error. This virtual machine can not be powered on." error dialog. Throwing "The processor does not support XSAVE. After upgrade and reboot of host OS, all VMs unable to start. ![]() ![]() Windows 10 guest, several Linux distro guest VMs functional under 17.0 prior to upgrade to 17.5.0 build-22583795. ![]()
0 Comments
Leave a Reply. |
Details
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |