Skip to content
This repository was archived by the owner on Jan 28, 2023. It is now read-only.
This repository was archived by the owner on Jan 28, 2023. It is now read-only.

HAXM does not enable XSAVE yet AVX is supported and cannot be enabled #465

Open
@NXTdevosc1

Description

@NXTdevosc1

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

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions