summary refs log tree commit diff stats
path: root/results/classifier/zero-shot/105/KVM/2325
diff options
context:
space:
mode:
Diffstat (limited to 'results/classifier/zero-shot/105/KVM/2325')
-rw-r--r--results/classifier/zero-shot/105/KVM/232524
1 files changed, 24 insertions, 0 deletions
diff --git a/results/classifier/zero-shot/105/KVM/2325 b/results/classifier/zero-shot/105/KVM/2325
new file mode 100644
index 000000000..b42801115
--- /dev/null
+++ b/results/classifier/zero-shot/105/KVM/2325
@@ -0,0 +1,24 @@
+KVM: 0.964
+device: 0.837
+graphic: 0.830
+semantic: 0.625
+instruction: 0.618
+other: 0.470
+vnc: 0.397
+socket: 0.397
+mistranslation: 0.306
+boot: 0.255
+network: 0.168
+assembly: 0.066
+
+[Performance Regression] Constant freezes on Alder lake and Raptor lake CPUs.
+Description of problem:
+Strangely, no logs are recorded. The guest just freezes. It can however be rescued by a simple pause and unpause.
+
+This issue only happens when using the KVM hypervisor. Other hypervisors are fine.
+
+This issue does NOT happen when I tested my Intel Core i7 8700K.
+Steps to reproduce:
+1. Create a basic virtual machine for Windows 11 (Or 10).
+2. Run it for about 5 - 30 minutes (Sometimes it happens in 20 seconds or even less).
+3. The problem should occur.