1 files changed, 38 insertions, 0 deletions
diff --git a/results/classifier/zero-shot/118/performance/2365 b/results/classifier/zero-shot/118/performance/2365
new file mode 100644
index 000000000..9a604cbff
--- /dev/null
+++ b/results/classifier/zero-shot/118/performance/2365
@@ -0,0 +1,38 @@
+performance: 0.963
+graphic: 0.946
+boot: 0.873
+kernel: 0.855
+VMM: 0.833
+device: 0.804
+risc-v: 0.787
+debug: 0.683
+architecture: 0.669
+vnc: 0.642
+semantic: 0.612
+hypervisor: 0.592
+PID: 0.567
+ppc: 0.539
+virtual: 0.455
+arm: 0.414
+mistranslation: 0.413
+socket: 0.380
+TCG: 0.380
+user-level: 0.370
+KVM: 0.338
+x86: 0.336
+network: 0.278
+i386: 0.259
+register: 0.256
+files: 0.249
+peripherals: 0.119
+permissions: 0.100
+assembly: 0.098
+
+[Regression v8.2/v9.0+] stuck at SeaBIOS for >30s with 100% CPU (1T)
+Description of problem:
+starting our Linux direct-kernel-boot VMs with same args on different hosts/hardware will get stuck at SeaBIOS for 30-60s with 100% 1T CPU load starting with v8.2 and also in v9.0. v9.0.0 and v8.2.3 - v8.1.5 is OK. To be clear, everything seems to be fine after that, though I did not do any benchmarks to compare performance. It just delays (re)booting by almost 1 minute, which is a shame, because before that update/regression it was instant and our VMs only take 4s to boot, which is now more like 60s.
+Downgrading to v8.1 instantly fixes it, upgrading to v8.2/v9.0 instantly breaks it.
+Steps to reproduce:
+1. start VM with same args on different versions
+
+somehow if I save this bug with `/label ~"kind::Bug"` it disappears, so I'm unable to add/keep the label