DOS ain't dead

Why CPUID hypervisor flag is set? (Miscellaneous)

posted by Rugxulo , Usono, 11.08.2021, 22:31

> > Does anyone know why the processor returns
> > CPUID.00000001h.ECX = 0xFE9AE383 and the flag set
> > (Bit 31: Running on a hypervisor) on a real CPU?
> > (Windows OS, CPU = Intel Xeon ES-2680, family 6, model 62, stepping 4).
>
> No idea. Perhaps some hypervisor is indeed installed by the Windows
> setup?

Is Hyper-V installed? Even WSL2 (Windows Subsystem for Linux) uses VT-X nowadays, last I heard. (But I've never used Windows 10.)

I actually think that causes (or used to cause) conflicts with other hypervisor software. And VirtualBox dropped support for cpus without hardware VT-X extensions sometime last year, IIRC. So, more or less, everyone is expected to have it available these days. (EDIT: Even this Chromebook [Celeron] has VT-X.)

Complete thread:

• Why CPUID hypervisor flag is set? - CandyMan, 11.08.2021, 17:31 (Miscellaneous)
  • Why CPUID hypervisor flag is set? - tkchia, 11.08.2021, 18:29
    • Why CPUID hypervisor flag is set? - Rugxulo, 11.08.2021, 22:31
  • Why CPUID hypervisor flag is set? - alexfru, 12.08.2021, 09:35
    • Why CPUID hypervisor flag is set? - RayeR, 14.08.2021, 15:38
      • Why CPUID hypervisor flag is set? - alexfru, 16.08.2021, 03:15
        • Why CPUID hypervisor flag is set? - RayeR, 16.08.2021, 03:29
          • Why CPUID hypervisor flag is set? - alexfru, 16.08.2021, 07:20