-
Notifications
You must be signed in to change notification settings - Fork 884
HAXM does not enable XSAVE yet AVX is supported and cannot be enabled #465
Comments
Another thing : Enabling virtualization only activates XSAVE on other VMs (Without HAXM). Which provides activation possibility and usage for the AVX instruction set. |
Haxm does not support XSAVE and OSXSAVE emulation, thus returns these as disabled from cpuid emulation handlers. The feature set supported by haxm corresponds to very old CPU models - very similar to Nehalem.
Nearly impossible, haxm didnt add features for a long time, see closed pull request list. There is no active development of the project. |
Is there a way to do it ? or I just emulate with VBox or VMWare to test these extensions ? |
To do it with haxm, one has to implement these features in haxm code. |
where are HAXM developers ? |
After a long trip fixing my LEGACY BIOS bootloader to run on QEMU with HAXM enabled, the bootloader successfully do its job and jumps to the kernel, the first thing the kernel does is to enable CPU features. However, when HAXM is enabled, the kernel detects AVX support but xsetbv triggers a vCPU Shutdown. I figured out that XSAVE and OSXSAVE are disabled in CPUID,EAX=1. I tried to check for them by creating a windows program and they seem to be both enabled on the host CPU.
The goal of enabling HAXM was mainly to test and use AVX, PCID, AES, TSC_DEADLINE support and lot of other features present on my CPU, rather than just rebooting my PC each time which takes minutes !
How to enable OSXSAVE, XSAVE on an HAXM host ? How to use AVX and other CPU features ?
Please, I need to fix this soon.
However enabling these extensions on real hardware (the host CPU) seems to work normally.
I'll appreciate it too much if you provide these features, I don't want to reboot my PC each time to try them. AVX is only 86 Instructions though
The text was updated successfully, but these errors were encountered: