(Moving this to an actual Issue...)

Incorrect detection of hypervisor for L1TF VMM for KVM VMs and host systems. KVM Host systems are all RHEL 7. I've tested this on RHEL 7 and Ubuntu 18.04 VMs running on KVM hosts.

See #277 (comment) and #277 (comment) (and also #277 (comment)) for all the details.

I don't know if the "Booting paravirtualized kernel on bare hardware" dmesg check issue (described in #277 (comment)) is specific to KVM or RHEL 7 (or both). But it certainly shows up ONLY on physical/bare hardware systems where virtualization is enabled in the BIOS for the (physical) system. So, I'm not sure why it's existence is used to determine that a system is NOT running a hypervisor.

And then there's the two checks that will indicate false-positive hypervisor detection within KVM VMs (via #277 (comment) and #277 (comment)).

Also, the hypervisor CPU flag is set in KVM VMs, which again will cause another false-positive hypervisor detection within KVM VMs. It is NOT set on KVM host systems (at least not for RHEL 7).

Commit 906f54c via PR #259 added this detection (with a typo fix via commit d7d2e69).

Happy to provide any other details as needed!