1 files changed, 54 insertions, 0 deletions
diff --git a/results/classifier/zero-shot/118/KVM/1914748 b/results/classifier/zero-shot/118/KVM/1914748
new file mode 100644
index 00000000..3de69363
--- /dev/null
+++ b/results/classifier/zero-shot/118/KVM/1914748
@@ -0,0 +1,54 @@
+KVM: 0.970
+architecture: 0.935
+graphic: 0.801
+device: 0.781
+vnc: 0.699
+performance: 0.672
+mistranslation: 0.646
+semantic: 0.623
+kernel: 0.595
+virtual: 0.538
+ppc: 0.531
+network: 0.530
+x86: 0.485
+permissions: 0.458
+hypervisor: 0.436
+arm: 0.413
+register: 0.413
+boot: 0.400
+socket: 0.345
+VMM: 0.344
+files: 0.338
+i386: 0.314
+debug: 0.309
+PID: 0.287
+peripherals: 0.280
+risc-v: 0.241
+TCG: 0.223
+user-level: 0.146
+assembly: 0.137
+
+Confuse error message when KVM can not start requested CPU
+
+As of commit 1ba089f2255, on Cavium CN8890 (ThunderX cores):
+
+$ qemu-system-aarch64 -display none -accel kvm -M virt,gic-version=3 -accel kvm -cpu cortex-a57 --trace \*kvm_vcpu\*      
+kvm_vcpu_ioctl cpu_index 0, type 0x4020aeae, arg 0xffff9b7f9b18 
+qemu-system-aarch64: kvm_init_vcpu: kvm_arch_init_vcpu failed (0): Invalid argument
+
+(same using "-cpu cortex-a53" or cortex-a72).
+
+Explanation from Peter Maydell on IRC:
+> using a specific cpu type will only work with KVM if the host CPU really is that
+> exact CPU type, otherwise, use "-cpu host" or "-cpu max"
+
+Having a better error description would help to understand the reason.
+
+
+This is an automated cleanup. This bug report has been moved to QEMU's
+new bug tracker on gitlab.com and thus gets marked as 'invalid' now.
+Please continue with the discussion here:
+
+ https://gitlab.com/qemu-project/qemu/-/issues/239
+
+