diff options
Diffstat (limited to 'results/classifier/zero-shot/108/other/1541643')
| -rw-r--r-- | results/classifier/zero-shot/108/other/1541643 | 28 |
1 files changed, 28 insertions, 0 deletions
diff --git a/results/classifier/zero-shot/108/other/1541643 b/results/classifier/zero-shot/108/other/1541643 new file mode 100644 index 000000000..52dfe769c --- /dev/null +++ b/results/classifier/zero-shot/108/other/1541643 @@ -0,0 +1,28 @@ +device: 0.765 +graphic: 0.586 +semantic: 0.577 +network: 0.569 +other: 0.559 +vnc: 0.533 +KVM: 0.499 +permissions: 0.479 +socket: 0.470 +performance: 0.463 +boot: 0.441 +debug: 0.330 +PID: 0.313 +files: 0.310 + +IA32_FEATURE_CONTROL MSR unset for nested virtualization + +I enabled nested virtualization for the kvm_intel module, and passed -enable-kvm and -cpu host to qemu. However, the qemu BIOS did not set IA32_FEATURE_CONTROL MSR (index 0x3a) to a non-zero value allow VMXON. According to the Intel manual Section 23.7 ENABLING AND ENTERING VMX OPERATION: "To enable VMX support in a platform, BIOS must set bit 1, bit 2, or both (see below), as well as the lock bit." + +I noticed an old mailing list thread on this (https://lists.nongnu.org/archive/html/qemu-devel/2015-01/msg01372.html), but I wanted to point out that the Intel manual (and all the physical hardware I've tested) specifically contradicts this response. + +Tested on kernel 4.3.3 and qemu 2.4.1. + +Looking through old bug tickets... can you still reproduce this issue with the latest version of QEMU? Or could we close this ticket nowadays? + + +[Expired for QEMU because there has been no activity for 60 days.] + |