1 files changed, 53 insertions, 0 deletions
diff --git a/results/classifier/118/virtual/1795148 b/results/classifier/118/virtual/1795148
new file mode 100644
index 000000000..cf057ce4c
--- /dev/null
+++ b/results/classifier/118/virtual/1795148
@@ -0,0 +1,53 @@
+x86: 0.988
+virtual: 0.978
+architecture: 0.950
+graphic: 0.891
+performance: 0.869
+device: 0.848
+semantic: 0.829
+register: 0.825
+hypervisor: 0.813
+files: 0.804
+network: 0.793
+arm: 0.792
+ppc: 0.773
+PID: 0.770
+VMM: 0.746
+user-level: 0.741
+mistranslation: 0.737
+i386: 0.706
+socket: 0.692
+vnc: 0.687
+peripherals: 0.661
+risc-v: 0.660
+kernel: 0.645
+debug: 0.642
+boot: 0.630
+permissions: 0.623
+TCG: 0.598
+assembly: 0.587
+KVM: 0.446
+
+address_space_stw_le_cached: Assertion `addr < cache->len && 2 <= cache ->len - addr' failed
+
+When running OpenBSD-current as a guest, the following assertion is hit after a few seconds, resulting in the virtual machine to crash:
+
+```
+qemu-system-x86_64: /build/qemu/src/qemu-3.0.0/include/exec/memory_ldst_cached.inc.h:85: address_space_stw_le_cached: Assertion `addr < cache->len && 2 <= cache->len - addr' failed.
+```
+
+Host is Arch Linux stable, running on x86_64.
+
+Qemu version is 3.0.0, installed via the standard Arch Linux package.
+
+Version 2.12.1 didn't exhibit this behavior.
+
+Do you know how to use "git bisect"? If so, could you maybe try to bisect which commit between v2.12.0 and v3.0.0 introduced this problem?
+
+I suspect this is a known bug, fixed in master in commit db812c4073c77. You could test that by cherry-picking it to 3.0 or just testing against master.
+
+
+
+In the absence of further information from the submitter, it seems reasonable to assume that this is indeed the bug fixed by commit db812c4073c77 (which resulted in this assertion when running OpenBSD guests). That commit is in 3.1, which was released in December.
+
+