Why CPUID hypervisor flag is set? (Miscellaneous)
> > Windows itself runs in a VM nowadays.
>
> Really Windows itself as VM client?
Ever since Hyper-V came out.
> Older Win10 (that I have at work - frozen 2 years ago without updates)
> doesn't have HyperV yet so I guess it shouldn't run virtualized. I use
> Virtualbox for virtualization there and it had some conflict with old
> HyperV but it's probably solved. Current Win10 may use HyperV by default
> for WSL and other stuff, so if someone tell more detailed...
I think, Hyper-V now provides some additional security features for Windows itself, not just runs other VMs.
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
- Why CPUID hypervisor flag is set? - RayeR, 16.08.2021, 03:29
- Why CPUID hypervisor flag is set? - alexfru, 16.08.2021, 03:15
- Why CPUID hypervisor flag is set? - RayeR, 14.08.2021, 15:38
- Why CPUID hypervisor flag is set? - tkchia, 11.08.2021, 18:29