1 files changed, 107 insertions, 0 deletions
diff --git a/results/classifier/118/review/1902777 b/results/classifier/118/review/1902777
new file mode 100644
index 00000000..b7d06c7f
--- /dev/null
+++ b/results/classifier/118/review/1902777
@@ -0,0 +1,107 @@
+x86: 0.889
+hypervisor: 0.884
+user-level: 0.878
+graphic: 0.866
+performance: 0.865
+files: 0.838
+architecture: 0.825
+device: 0.785
+mistranslation: 0.783
+virtual: 0.772
+permissions: 0.736
+peripherals: 0.722
+debug: 0.705
+PID: 0.687
+network: 0.661
+semantic: 0.651
+VMM: 0.625
+kernel: 0.617
+TCG: 0.608
+ppc: 0.607
+i386: 0.550
+register: 0.550
+arm: 0.541
+KVM: 0.523
+risc-v: 0.493
+socket: 0.480
+vnc: 0.468
+assembly: 0.462
+boot: 0.416
+--------------------
+x86: 0.407
+user-level: 0.101
+virtual: 0.068
+debug: 0.025
+hypervisor: 0.015
+files: 0.012
+TCG: 0.009
+semantic: 0.007
+PID: 0.006
+socket: 0.004
+performance: 0.003
+network: 0.003
+device: 0.002
+register: 0.002
+boot: 0.002
+assembly: 0.002
+architecture: 0.001
+permissions: 0.001
+risc-v: 0.001
+graphic: 0.001
+kernel: 0.001
+vnc: 0.001
+VMM: 0.001
+peripherals: 0.001
+ppc: 0.001
+mistranslation: 0.001
+arm: 0.000
+KVM: 0.000
+i386: 0.000
+
+qemu with whpx acceleration crashes with vmx=on
+
+Under Windows 10, qemu crashes when using whpx acceleration and the vmx=on option.  The reported error is
+  qemu-system-x86_64.exe: WHPX: Unexpected VP exit code 4
+Before the error, it reports
+  Windows Hypervisor Platform accelerator is operational
+
+The command line is the following:
+  "C:\Program Files\qemu\qemu-system-x86_64.exe" -accel whpx -cpu qemu64,vmx=on
+It crashes with any model of CPU as long as the "vmx=on" option is added.  Without this option it runs fine (but no nested virtualization).
+
+My processor is an Intel i7-10510U, and I am running Windows 10 2004 (build 19041.572).
+
+Forgot to say: qemu version 5.1.0
+
+The QEMU project is currently moving its bug tracking to another system.
+For this we need to know which bugs are still valid and which could be
+closed already. Thus we are setting the bug state to "Incomplete" now.
+
+If the bug has already been fixed in the latest upstream version of QEMU,
+then please close this ticket as "Fix released".
+
+If it is not fixed yet and you think that this bug report here is still
+valid, then you have two options:
+
+1) If you already have an account on gitlab.com, please open a new ticket
+for this problem in our new tracker here:
+
+    https://gitlab.com/qemu-project/qemu/-/issues
+
+and then close this ticket here on Launchpad (or let it expire auto-
+matically after 60 days). Please mention the URL of this bug ticket on
+Launchpad in the new ticket on GitLab.
+
+2) If you don't have an account on gitlab.com and don't intend to get
+one, but still would like to keep this ticket opened, then please switch
+the state back to "New" or "Confirmed" within the next 60 days (other-
+wise it will get closed as "Expired"). We will then eventually migrate
+the ticket automatically to the new system (but you won't be the reporter
+of the bug in the new system and thus you won't get notified on changes
+anymore).
+
+Thank you and sorry for the inconvenience.
+
+
+[Expired for QEMU because there has been no activity for 60 days.]
+