VT-x on HP 805D is unsupported

[bulavko]

Hello, everybody

I have a problem...

When trying to run a virtual machine in QEMU (ArchWSL2), while checking the capability flags inside ArchWSL, I noticed that the processor does not support VTX instructions, which are required to run virtual machines in KVM mode. At the beginning, I've think that is only problem of WSL and distro. But after checking the system by hwinfo - I've noticed that problem of the host system.

Intel ARK shows information that the processor I have in my computer supports VT-x instructions.

The chipset on motherboard also supports VT-d instructions which are necessary for VT-x.

If the hardware of the PC is support VT-x and VT-d, what can cause this problem?

HWinfo report:

hwinfo report

SystemInfo report:

BIOS version: N02 02.58 (latest available for HP 805D)

Intel Virtualization is enabled.

[BeemerBiker]

Make sure you have hypervisor enabled

[bulavko]

Thank you for reply, but  I've enabled the Hyper-V before this thread was opened.

I've found Intel Processor Identification Utility and report from this program also say that my CPU doesn't support Hyper-V

And this directly contradicts from Intel ARK information about my CPU

[BeemerBiker]

Is VT enabled in bios?  Version N02 2.07  had all those features

[bulavko]

It gets very interesting

When I disable Hypervisor, Windows Hypervisor Platform in Windows and VT-x and VT-d in UEFI - Intel Processor Identification Utility, after restart, display me that VT-x and VTd are supported. But when I enable them (firstly in UEFI, secondly - in Windows) and restart OS - this utility says, that VT-x and VTd are unsupported.

[BeemerBiker · Accepted solution]

---

@bulavko wrote:

It gets very interesting

When I disable Hypervisor, Windows Hypervisor Platform in Windows and VT-x and VT-d in UEFI - Intel Processor Identification Utility, after restart, display me that VT-x and VTd are supported. But when I enable them (firstly in UEFI, secondly - in Windows) and restart OS - this utility says, that VT-x and VTd are unsupported.

---

When  it first came out, I tried that original Microsoft subsystem for Linux on a Windows 10 system and do not remember having to to anything to Hypervisor.  I uninstalled it as I was unable to run or test CUDA applications on the GPUs.  I ended up using two Ubuntu system I built using cheap old motherboard and accessed them using VNC.  

[edit] please read this https://superuser.com/questions/1208850/why-cant-virtualbox-or-vmware-run-with-hyper-v-enabled-on-wi...

Something else I remembered is some of the BOINC applications ran under VirtualBox and that may have been the problem.  I have mod'ed BOINC and some of the BOINC app for setiathome and milkyway at home and needed the full Ubuntu desktop and that was one of the reasons that WSL was not any good. 

The above article indicates that your host system (formerly windows) is using those feature and you have to disable Hypervisor before your apps can use them.

[bulavko]

Thank you! Your message resolve my problem :).
Before reading linked message from topic at superuser I didn't know about "proxied" VM, which created by Hyper-V Windows feature.