15 files changed, 685 insertions, 0 deletions
diff --git a/results/classifier/108/other/143 b/results/classifier/108/other/143
new file mode 100644
index 000000000..cacf1d1ae
--- /dev/null
+++ b/results/classifier/108/other/143
@@ -0,0 +1,16 @@
+device: 0.813
+performance: 0.794
+graphic: 0.497
+debug: 0.490
+permissions: 0.389
+network: 0.328
+boot: 0.321
+semantic: 0.237
+other: 0.112
+vnc: 0.087
+files: 0.033
+PID: 0.031
+socket: 0.026
+KVM: 0.023
+
+xhci HCIVERSION register read emulation incorrectly handled
diff --git a/results/classifier/108/other/1431 b/results/classifier/108/other/1431
new file mode 100644
index 000000000..9e49c6a4e
--- /dev/null
+++ b/results/classifier/108/other/1431
@@ -0,0 +1,65 @@
+graphic: 0.796
+device: 0.622
+KVM: 0.470
+files: 0.389
+socket: 0.356
+PID: 0.355
+debug: 0.353
+semantic: 0.338
+permissions: 0.305
+vnc: 0.251
+other: 0.208
+boot: 0.171
+performance: 0.161
+network: 0.121
+
+qemu spice support opengl
+Steps to reproduce:
+I wan to use spice support opengl, but my qemu seems not support,what can i do to support opengl for spice?
+
+qemu configure:
+```
+./configure --target-list=x86_64-softmmu --enable-kvm --enable-debug --enable-spice --enable-numa --enable-libusb --enable-curl --enable-usb-redir --enable-libiscsi  --enable-virglrenderer --enable-opengl  --enable-gtk --prefix="/usr"
+```
+
+xml:
+```xml
+<domain type='kvm'>
+    <name>test</name>
+    <memory>1048576</memory>
+    <currentMemory>1048576</currentMemory>
+    <vcpu>1</vcpu>
+    <os>
+      <type arch='x86_64' machine='pc'>hvm</type>
+    </os>
+   <cpu mode='custom' match='exact' check='full'>
+    <topology sockets='1' dies='1' cores='1' threads='1'/>
+  </cpu>
+   <features>
+     <acpi/>
+     <apic/>
+     <pae/>
+   </features>
+   <clock offset='localtime'/>
+   <on_poweroff>destroy</on_poweroff>
+   <on_reboot>restart</on_reboot>
+   <on_crash>destroy</on_crash>
+   <devices>
+     <emulator>/usr/bin/qemu-system-x86_64</emulator>
+     <disk type='file' device='disk'>
+      <driver name='qemu' type='qcow2'/>
+       <source file='/root/kk.img'/>
+       <target dev='hda' bus='ide'/>
+     </disk>
+    <input type='mouse' bus='ps2'/>
+    <graphics type='spice'>
+      <listen type='none'/>
+      <gl enable='yes' rendernode='/dev/dri/renderD128'/>
+    </graphics>
+   </devices>
+</domain>
+```
+
+error report:
+
+![image](/uploads/74ecd52966d71bbbd2921f4c292002a9/image.png)
diff --git a/results/classifier/108/other/1431084 b/results/classifier/108/other/1431084
new file mode 100644
index 000000000..87dd7d5de
--- /dev/null
+++ b/results/classifier/108/other/1431084
@@ -0,0 +1,30 @@
+graphic: 0.895
+other: 0.887
+semantic: 0.879
+device: 0.877
+vnc: 0.714
+PID: 0.690
+network: 0.690
+files: 0.689
+boot: 0.638
+performance: 0.619
+debug: 0.597
+socket: 0.545
+KVM: 0.475
+permissions: 0.458
+
+improve configure error message "ERROR: User requested feature nptl"
+
+Running `./configure` on Ubuntu 14.10 amd64 with Linux 3.19.1 causes the error 
+
+    ERROR: User requested feature nptl
+           configure was not able to find it.
+           Install glibc and linux kernel headers.
+
+Both linux kernel headers and `libglib2.0-dev` are installed in my case, so the error message definitely misses a point and is at least confusing and should either omit the hint if the recommended dependencies are already installed or - better - give one that fixes the issue.
+
+experienced with git commit d598911b6f5e7bf7bafb63b8e1d074729e94aca7
+
+You say "Both linux kernel headers and `libglib2.0-dev` are installed", but the error message says "Install glibc and linux kernel headers". "glibc" is not "libglib". I suspect you didn't have what on Ubuntu is the "libc6-dev" package. Unfortunately it's difficult to be specific in these error messages, because different distros call their dev packages by different names.
+
+
diff --git a/results/classifier/108/other/1432 b/results/classifier/108/other/1432
new file mode 100644
index 000000000..7062f9976
--- /dev/null
+++ b/results/classifier/108/other/1432
@@ -0,0 +1,39 @@
+device: 0.911
+graphic: 0.872
+debug: 0.871
+PID: 0.845
+semantic: 0.841
+vnc: 0.803
+files: 0.782
+network: 0.751
+performance: 0.751
+socket: 0.728
+permissions: 0.677
+KVM: 0.602
+boot: 0.563
+other: 0.136
+
+meson prints "Unknown TAP version. The first line MUST be `TAP version <int>`. Assuming version 12." for every test
+Description of problem:
+Run 'make check V=1' and observe that every test causes an warning message about an unknown TAP version
+
+```
+>>> G_TEST_SRCDIR=/home/berrange/src/virt/qemu/tests/unit MALLOC_PERTURB_=61 G_TEST_BUILDDIR=/home/berrange/src/virt/qemu/build/tests/unit /home/berrange/src/virt/qemu/build/tests/unit/test-shift128 --tap -k
+▶ 22/44 /host-utils/test_lshift                       OK            
+▶ 22/44 /host-utils/test_rshift                       OK            
+22/44 qemu:unit / test-shift128                       OK              0.01s   2 subtests passed
+
+Unknown TAP version. The first line MUST be `TAP version <int>`. Assuming version 12.
+
+```
+
+This message comes from inside meson
+
+```
+$ rpm -ql meson | xargs grep 'Unknown TAP version' 2>/dev/null
+/usr/lib/python3.11/site-packages/mesonbuild/mtest.py:            self.warnings.append('Unknown TAP version. The first line MUST be `TAP version <int>`. Assuming version 12.')
+```
+
+This is with meson-1.0.0-1.fc38.noarch
+Steps to reproduce:
+1. make check V=1
diff --git a/results/classifier/108/other/1432103 b/results/classifier/108/other/1432103
new file mode 100644
index 000000000..8537ec113
--- /dev/null
+++ b/results/classifier/108/other/1432103
@@ -0,0 +1,23 @@
+permissions: 0.884
+device: 0.653
+network: 0.468
+socket: 0.399
+graphic: 0.364
+performance: 0.310
+vnc: 0.301
+other: 0.301
+boot: 0.272
+files: 0.262
+debug: 0.242
+semantic: 0.211
+PID: 0.176
+KVM: 0.143
+
+error in x86 executable segment permission check
+
+When the code segment register (%cs) selects an executable segment with no read permission, mov instructions that read from the segment via %cs prefix can still succeed without causing a general protection error.
+
+Triaging old bug tickets... can you still reproduce this issue with the latest version of QEMU? Or could we close this ticket nowadays? Can you provide a binary to reproduce this issue?
+
+[Expired for QEMU because there has been no activity for 60 days.]
+
diff --git a/results/classifier/108/other/1433 b/results/classifier/108/other/1433
new file mode 100644
index 000000000..4f3dfdf0b
--- /dev/null
+++ b/results/classifier/108/other/1433
@@ -0,0 +1,172 @@
+other: 0.822
+graphic: 0.811
+vnc: 0.806
+semantic: 0.799
+debug: 0.793
+permissions: 0.783
+performance: 0.782
+PID: 0.774
+socket: 0.774
+device: 0.767
+boot: 0.763
+files: 0.749
+KVM: 0.737
+network: 0.711
+
+Abort in lan9118_16bit_mode_[read|write]()
+Description of problem:
+[read|write][w|l] are allowed but [read|write]b are not allowed when mode_16bit is enabled.
+Steps to reproduce:
+```
+export QEMU=/path/to/qemu-system-arm
+
+cat << EOF | $QEMU \
+-machine smdkc210 -monitor none -serial none \
+-display none -qtest stdio
+readb 0x5000070
+EOF
+```
+Additional information:
+```
+==1940==WARNING: ASan doesn't fully support makecontext/swapcontext functions and may produce false positives in some cases!
+INFO: found LLVMFuzzerCustomMutator (0x5654b8eede90). Disabling -len_control by default.
+INFO: Running with entropic power schedule (0xFF, 100).
+INFO: Seed: 3248453476
+INFO: Loaded 1 modules   (601357 inline 8-bit counters): 601357 [0x5654bbdd8000, 0x5654bbe6ad0d), 
+INFO: Loaded 1 PC tables (601357 PCs): 601357 [0x5654bb4aa340,0x5654bbdd7410), 
+./qemu-videzzo-arm-target-videzzo-fuzz-lan9118: Running 1 inputs 1 time(s) each.
+INFO: Reading pre_seed_input if any ...
+INFO: Executing pre_seed_input if any ...
+INFO: -max_len is not provided; libFuzzer will not generate inputs larger than 4096 bytes
+Matching objects by name , *lan9118-mmio*
+This process will fuzz the following MemoryRegions:
+  * lan9118-mmio[0] (size 100)
+This process will fuzz through the following interfaces:
+  * clock_step, EVENT_TYPE_CLOCK_STEP, 0xffffffff +0xffffffff, 255,255
+  * lan9118-mmio, EVENT_TYPE_MMIO_READ, 0x5000000 +0x100, 1,4
+  * lan9118-mmio, EVENT_TYPE_MMIO_WRITE, 0x5000000 +0x100, 1,4
+INFO: A corpus is not provided, starting from an empty corpus
+#2      INITED cov: 3 ft: 4 corp: 1/1b exec/s: 0 rss: 221Mb
+Running: ./crash-663e5408ee573b1e9d073c796ffbaaae9bd583cb
+qemu: hardware error: lan9118_read: Bad size 0x1
+
+CPU #0:
+R00=00000000 R01=00000000 R02=00000000 R03=00000000
+R04=00000000 R05=00000000 R06=00000000 R07=00000000
+R08=00000000 R09=00000000 R10=00000000 R11=00000000
+R12=00000000 R13=00000000 R14=00000000 R15=00000000
+PSR=400001d3 -Z-- A svc32
+s00=00000000 s01=00000000 d00=0000000000000000
+s02=00000000 s03=00000000 d01=0000000000000000
+s04=00000000 s05=00000000 d02=0000000000000000
+s06=00000000 s07=00000000 d03=0000000000000000
+s08=00000000 s09=00000000 d04=0000000000000000
+s10=00000000 s11=00000000 d05=0000000000000000
+s12=00000000 s13=00000000 d06=0000000000000000
+s14=00000000 s15=00000000 d07=0000000000000000
+s16=00000000 s17=00000000 d08=0000000000000000
+s18=00000000 s19=00000000 d09=0000000000000000
+s20=00000000 s21=00000000 d10=0000000000000000
+s22=00000000 s23=00000000 d11=0000000000000000
+s24=00000000 s25=00000000 d12=0000000000000000
+s26=00000000 s27=00000000 d13=0000000000000000
+s28=00000000 s29=00000000 d14=0000000000000000
+s30=00000000 s31=00000000 d15=0000000000000000
+s32=00000000 s33=00000000 d16=0000000000000000
+s34=00000000 s35=00000000 d17=0000000000000000
+s36=00000000 s37=00000000 d18=0000000000000000
+s38=00000000 s39=00000000 d19=0000000000000000
+s40=00000000 s41=00000000 d20=0000000000000000
+s42=00000000 s43=00000000 d21=0000000000000000
+s44=00000000 s45=00000000 d22=0000000000000000
+s46=00000000 s47=00000000 d23=0000000000000000
+s48=00000000 s49=00000000 d24=0000000000000000
+s50=00000000 s51=00000000 d25=0000000000000000
+s52=00000000 s53=00000000 d26=0000000000000000
+s54=00000000 s55=00000000 d27=0000000000000000
+s56=00000000 s57=00000000 d28=0000000000000000
+s58=00000000 s59=00000000 d29=0000000000000000
+s60=00000000 s61=00000000 d30=0000000000000000
+s62=00000000 s63=00000000 d31=0000000000000000
+FPSCR: 00000000
+CPU #1:
+R00=00000000 R01=00000000 R02=00000000 R03=00000000
+R04=00000000 R05=00000000 R06=00000000 R07=00000000
+R08=00000000 R09=00000000 R10=00000000 R11=00000000
+R12=00000000 R13=00000000 R14=00000000 R15=00000000
+PSR=400001d3 -Z-- A svc32
+s00=00000000 s01=00000000 d00=0000000000000000
+s02=00000000 s03=00000000 d01=0000000000000000
+s04=00000000 s05=00000000 d02=0000000000000000
+s06=00000000 s07=00000000 d03=0000000000000000
+s08=00000000 s09=00000000 d04=0000000000000000
+s10=00000000 s11=00000000 d05=0000000000000000
+s12=00000000 s13=00000000 d06=0000000000000000
+s14=00000000 s15=00000000 d07=0000000000000000
+s16=00000000 s17=00000000 d08=0000000000000000
+s18=00000000 s19=00000000 d09=0000000000000000
+s20=00000000 s21=00000000 d10=0000000000000000
+s22=00000000 s23=00000000 d11=0000000000000000
+s24=00000000 s25=00000000 d12=0000000000000000
+s26=00000000 s27=00000000 d13=0000000000000000
+s28=00000000 s29=00000000 d14=0000000000000000
+s30=00000000 s31=00000000 d15=0000000000000000
+s32=00000000 s33=00000000 d16=0000000000000000
+s34=00000000 s35=00000000 d17=0000000000000000
+s36=00000000 s37=00000000 d18=0000000000000000
+s38=00000000 s39=00000000 d19=0000000000000000
+s40=00000000 s41=00000000 d20=0000000000000000
+s42=00000000 s43=00000000 d21=0000000000000000
+s44=00000000 s45=00000000 d22=0000000000000000
+s46=00000000 s47=00000000 d23=0000000000000000
+s48=00000000 s49=00000000 d24=0000000000000000
+s50=00000000 s51=00000000 d25=0000000000000000
+s52=00000000 s53=00000000 d26=0000000000000000
+s54=00000000 s55=00000000 d27=0000000000000000
+s56=00000000 s57=00000000 d28=0000000000000000
+s58=00000000 s59=00000000 d29=0000000000000000
+s60=00000000 s61=00000000 d30=0000000000000000
+s62=00000000 s63=00000000 d31=0000000000000000
+FPSCR: 00000000
+==1940== ERROR: libFuzzer: deadly signal
+    #0 0x5654b48090fe in __sanitizer_print_stack_trace /root/llvm-project/compiler-rt/lib/asan/asan_stack.cpp:86:3
+    #1 0x5654b4757d71 in fuzzer::PrintStackTrace() /root/llvm-project/compiler-rt/lib/fuzzer/FuzzerUtil.cpp:210:38
+    #2 0x5654b4730ca6 in fuzzer::Fuzzer::CrashCallback() (.part.0) /root/llvm-project/compiler-rt/lib/fuzzer/FuzzerLoop.cpp:236:18
+    #3 0x5654b4730d72 in fuzzer::Fuzzer::CrashCallback() /root/llvm-project/compiler-rt/lib/fuzzer/FuzzerLoop.cpp:208:1
+    #4 0x5654b4730d72 in fuzzer::Fuzzer::StaticCrashSignalCallback() /root/llvm-project/compiler-rt/lib/fuzzer/FuzzerLoop.cpp:207:19
+    #5 0x7fb6db17941f  (/lib/x86_64-linux-gnu/libpthread.so.0+0x1441f)
+    #6 0x7fb6daf8b00a in __libc_signal_restore_set /build/glibc-SzIz7B/glibc-2.31/signal/../sysdeps/unix/sysv/linux/internal-signals.h:86:3
+    #7 0x7fb6daf8b00a in raise /build/glibc-SzIz7B/glibc-2.31/signal/../sysdeps/unix/sysv/linux/raise.c:48:3
+    #8 0x7fb6daf6a858 in abort /build/glibc-SzIz7B/glibc-2.31/stdlib/abort.c:79:7
+    #9 0x5654b483964a in __wrap_abort /root/videzzo/videzzo_qemu/qemu/build-san-6/../tests/qtest/videzzo/less_crashes_wrappers.c:24:12
+    #10 0x5654b6a64d84 in hw_error /root/videzzo/videzzo_qemu/qemu/build-san-6/../softmmu/cpus.c:128:5
+    #11 0x5654b5ac50c7 in lan9118_16bit_mode_read /root/videzzo/videzzo_qemu/qemu/build-san-6/../hw/net/lan9118.c:1319:5
+    #12 0x5654b7ee045b in memory_region_read_accessor /root/videzzo/videzzo_qemu/qemu/build-san-6/../softmmu/memory.c:440:11
+    #13 0x5654b7ea0761 in access_with_adjusted_size /root/videzzo/videzzo_qemu/qemu/build-san-6/../softmmu/memory.c:554:18
+    #14 0x5654b7e9db2c in memory_region_dispatch_read1 /root/videzzo/videzzo_qemu/qemu/build-san-6/../softmmu/memory.c:1424:16
+    #15 0x5654b7e9d268 in memory_region_dispatch_read /root/videzzo/videzzo_qemu/qemu/build-san-6/../softmmu/memory.c:1457:9
+    #16 0x5654b7f1946d in flatview_read_continue /root/videzzo/videzzo_qemu/qemu/build-san-6/../softmmu/physmem.c:2892:23
+    #17 0x5654b7f1aa78 in flatview_read /root/videzzo/videzzo_qemu/qemu/build-san-6/../softmmu/physmem.c:2934:12
+    #18 0x5654b7f1a538 in address_space_read_full /root/videzzo/videzzo_qemu/qemu/build-san-6/../softmmu/physmem.c:2947:18
+    #19 0x5654b483a7ea in address_space_read /root/videzzo/videzzo_qemu/qemu/include/exec/memory.h:2869:18
+    #20 0x5654b483a7ea in qemu_readb /root/videzzo/videzzo_qemu/qemu/build-san-6/../tests/qtest/videzzo/videzzo_qemu.c:1010:5
+    #21 0x5654b483997e in dispatch_mmio_read /root/videzzo/videzzo_qemu/qemu/build-san-6/../tests/qtest/videzzo/videzzo_qemu.c:1034:35
+    #22 0x5654b8ee984f in videzzo_dispatch_event /root/videzzo/videzzo.c:1122:5
+    #23 0x5654b8ee0bcb in __videzzo_execute_one_input /root/videzzo/videzzo.c:272:9
+    #24 0x5654b8ee0aa0 in videzzo_execute_one_input /root/videzzo/videzzo.c:313:9
+    #25 0x5654b48500fc in videzzo_qemu /root/videzzo/videzzo_qemu/qemu/build-san-6/../tests/qtest/videzzo/videzzo_qemu.c:1497:12
+    #26 0x5654b8eee132 in LLVMFuzzerTestOneInput /root/videzzo/videzzo.c:1891:18
+    #27 0x5654b4731816 in fuzzer::Fuzzer::ExecuteCallback(unsigned char*, unsigned long) /root/llvm-project/compiler-rt/lib/fuzzer/FuzzerLoop.cpp:594:17
+    #28 0x5654b4714444 in fuzzer::RunOneTest(fuzzer::Fuzzer*, char const*, unsigned long) /root/llvm-project/compiler-rt/lib/fuzzer/FuzzerDriver.cpp:323:21
+    #29 0x5654b471f3ee in fuzzer::FuzzerDriver(int*, char***, int (*)(unsigned char*, unsigned long)) /root/llvm-project/compiler-rt/lib/fuzzer/FuzzerDriver.cpp:885:19
+    #30 0x5654b470b9d6 in main /root/llvm-project/compiler-rt/lib/fuzzer/FuzzerMain.cpp:20:30
+    #31 0x7fb6daf6c082 in __libc_start_main /build/glibc-SzIz7B/glibc-2.31/csu/../csu/libc-start.c:308:16
+    #32 0x5654b470ba2d in _start (/root/videzzo/videzzo_qemu/out-san/qemu-videzzo-arm-target-videzzo-fuzz-lan9118+0x300da2d)
+
+NOTE: libFuzzer has rudimentary signal handlers.
+      Combine libFuzzer with AddressSanitizer or similar for better crash reports.
+SUMMARY: libFuzzer: deadly signal
+MS: 0 ; base unit: 0000000000000000000000000000000000000000
+0x4,0x2,0x29,0x92,0xa,0x0,0x0,0x0,0x0,0x0,0x0,0x8,0x70,0x0,0x0,0x5,0x0,0x0,0x0,0x0,0x1,0x0,0x0,0x0,0x1,0x9,0x48,0x0,0x0,0x5,0x0,0x0,0x0,0x0,0x4,0x0,0x0,0x0,0x29,0x1f,0x8e,0x23,0x0,0x0,0x0,0x0,
+\x04\x02)\x92\x0a\x00\x00\x00\x00\x00\x00\x08p\x00\x00\x05\x00\x00\x00\x00\x01\x00\x00\x00\x01\x09H\x00\x00\x05\x00\x00\x00\x00\x04\x00\x00\x00)\x1f\x8e#\x00\x00\x00\x00
+```
diff --git a/results/classifier/108/other/1434 b/results/classifier/108/other/1434
new file mode 100644
index 000000000..e78ce3fa3
--- /dev/null
+++ b/results/classifier/108/other/1434
@@ -0,0 +1,18 @@
+device: 0.692
+other: 0.534
+network: 0.461
+boot: 0.366
+performance: 0.211
+socket: 0.209
+semantic: 0.209
+permissions: 0.197
+graphic: 0.194
+PID: 0.169
+debug: 0.143
+vnc: 0.102
+files: 0.098
+KVM: 0.013
+
+Windows on ARM64 host support
+Additional information:
+
diff --git a/results/classifier/108/other/1435101 b/results/classifier/108/other/1435101
new file mode 100644
index 000000000..4995f547e
--- /dev/null
+++ b/results/classifier/108/other/1435101
@@ -0,0 +1,25 @@
+graphic: 0.857
+device: 0.814
+boot: 0.810
+performance: 0.729
+other: 0.728
+semantic: 0.560
+files: 0.554
+permissions: 0.549
+vnc: 0.495
+PID: 0.444
+socket: 0.439
+debug: 0.357
+network: 0.181
+KVM: 0.014
+
+Windows, QEMU 2.2.50 fails to boot XP CD
+
+Running XP Pro SP3 host 32bit.  When I launch qemu booting from CD, it fails to complete load, getting stuck at "Setup is starting Windows". It does not proceed past. I tried to disable floppy but still no go. Download older version 1.5.1-win32, 0.9.1, same problem. 
+qemu-system-i386w.exe -cdrom "d:\XP.ISO" -hda d:\xp.img -boot d 
+with -global isa-fdc.driveA=c or -no-fd-bootchk switches but no go. I see others have run into this problem as well but no real solutions. Some folks says turning off floppy works and I tried.
+
+Triaging old bug tickets... can you still reproduce this issue with the latest version of QEMU? Or could we close this ticket nowadays?
+
+[Expired for QEMU because there has been no activity for 60 days.]
+
diff --git a/results/classifier/108/other/1435359 b/results/classifier/108/other/1435359
new file mode 100644
index 000000000..f067d142f
--- /dev/null
+++ b/results/classifier/108/other/1435359
@@ -0,0 +1,63 @@
+KVM: 0.602
+permissions: 0.582
+other: 0.547
+files: 0.529
+device: 0.513
+boot: 0.472
+network: 0.449
+socket: 0.426
+graphic: 0.421
+vnc: 0.420
+debug: 0.404
+performance: 0.391
+semantic: 0.379
+PID: 0.356
+
+Booting kernel 3.19.2 fails most of the time
+
+Host system: openSuSE 13.2 + kernel 4.0.0-rc4 + qemu 2.2.1.
+
+When I try to boot a virtual machine with Ubuntu 14.10 and kernel 3.13.0 every boot succeeds. However, with kernel 3.19.2 booting fails most of the time. The following appears in /var/log/libvirt/qemu/ubuntu-vm.log when I try to boot that VM with kernel 3.19.2:
+
+2015-03-23 02:44:18.801+0000: starting up
+LC_ALL=C PATH=/usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/sbin:/bin QEMU_AUDIO_DRV=spice /usr/bin/qemu-system-x86_64 -name ubuntu-vm -S -machine pc-i440fx-2.1,accel=kvm,usb=off -cpu Haswell -m 2048 -realtime mlock=off -smp 4,sockets=4,cores=1,threads=1 -uuid 395110dc-9fbe-4542-8fce-4ef958f24b2c -no-user-config -nodefaults -chardev socket,id=charmonitor,path=/var/lib/libvirt/qemu/ubuntu-vm.monitor,server,nowait -mon chardev=charmonitor,id=monitor,mode=control -rtc base=utc,driftfix=slew -global kvm-pit.lost_tick_policy=discard -no-hpet -no-shutdown -global PIIX4_PM.disable_s3=1 -global PIIX4_PM.disable_s4=1 -boot strict=on -device ich9-usb-ehci1,id=usb,bus=pci.0,addr=0x5.0x7 -device ich9-usb-uhci1,masterbus=usb.0,firstport=0,bus=pci.0,multifunction=on,addr=0x5 -device ich9-usb-uhci2,masterbus=usb.0,firstport=2,bus=pci.0,addr=0x5.0x1 -device ich9-usb-uhci3,masterbus=usb.0,firstport=4,bus=pci.0,addr=0x5.0x2 -device virtio-serial-pci,id=virtio-serial0,bus=pci.0,addr=0x4 -drive file=/var/lib/libvirt/images/ubuntusaucy.qcow2,if=none,id=drive-virtio-disk0,format=qcow2 -device virtio-blk-pci,scsi=off,bus=pci.0,addr=0x7,drive=drive-virtio-disk0,id=virtio-disk0,bootindex=1 -drive file=/var/lib/libvirt/images/ubuntu-14.04-mini.iso,if=none,id=drive-ide0-0-0,readonly=on,format=raw -device ide-cd,bus=ide.0,unit=0,drive=drive-ide0-0-0,id=ide0-0-0,bootindex=2 -netdev tap,fd=22,id=hostnet0,vhost=on,vhostfd=23 -device virtio-net-pci,netdev=hostnet0,id=net0,mac=52:54:00:5e:71:5e,bus=pci.0,addr=0x3 -chardev spicevmc,id=charchannel0,name=vdagent -device virtserialport,bus=virtio-serial0.0,nr=1,chardev=charchannel0,id=channel0,name=com.redhat.spice.0 -spice port=5900,addr=127.0.0.1,disable-ticketing,seamless-migration=on -device qxl-vga,id=video0,ram_size=67108864,vram_size=67108864,bus=pci.0,addr=0x2 -chardev spicevmc,id=charredir0,name=usbredir -device usb-redir,chardev=charredir0,id=redir0 -chardev spicevmc,id=charredir1,name=usbredir -device usb-redir,chardev=charredir1,id=redir1 -chardev spicevmc,id=charredir2,name=usbredir -device usb-redir,chardev=charredir2,id=redir2 -chardev spicevmc,id=charredir3,name=usbredir -device usb-redir,chardev=charredir3,id=redir3 -device virtio-balloon-pci,id=balloon0,bus=pci.0,addr=0x8 -object rng-random,id=rng0,filename=/dev/random -device virtio-rng-pci,rng=rng0,bus=pci.0,addr=0x9 -msg timestamp=on
+main_channel_link: add main channel client
+main_channel_handle_parsed: net test: latency 0.229000 ms, bitrate 28444444444 bps (27126.736111 Mbps)
+red_dispatcher_set_cursor_peer: 
+inputs_connect: inputs channel client create
+((null):30728): SpiceWorker-ERROR **: red_worker.c:8337:red_marshall_qxl_drawable: invalid type
+KVM: injection failed, MSI lost (Input/output error)
+qemu-system-x86_64: /home/bart/software/qemu-2.2.1/hw/net/vhost_net.c:264: vhost_net_stop_one: Assertion `r >= 0' failed.
+2015-03-23 02:44:44.952+0000: shutting down
+
+That message is similar to the message reported by the older qemu version provided by openSuse (qemu 2.1.0 + qemu-kvm 2.1.0):
+
+2015-03-21 13:51:00.724+0000: starting up
+LC_ALL=C PATH=/usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/sbin:/bin QEMU_AUDIO_DRV=spice /usr/bin/qemu-system-x86_64 -name ubuntu-vm -S -machine pc-i440fx-2.1,accel=kvm,usb=off -cpu Haswell -m 1024 -realtime mlock=off -smp 4,sockets=4,cores=1,threads=1 -uuid 395110dc-9fbe-4542-8fce-4ef958f24b2c -no-user-config -nodefaults -chardev socket,id=charmonitor,path=/var/lib/libvirt/qemu/ubuntu-vm.monitor,server,nowait -mon chardev=charmonitor,id=monitor,mode=control -rtc base=utc,driftfix=slew -global kvm-pit.lost_tick_policy=discard -no-hpet -no-shutdown -global PIIX4_PM.disable_s3=1 -global PIIX4_PM.disable_s4=1 -boot strict=on -device ich9-usb-ehci1,id=usb,bus=pci.0,addr=0x5.0x7 -device ich9-usb-uhci1,masterbus=usb.0,firstport=0,bus=pci.0,multifunction=on,addr
+=0x5 -device ich9-usb-uhci2,masterbus=usb.0,firstport=2,bus=pci.0,addr=0x5.0x1 -device ich9-usb-uhci3,masterbus=usb.0,firstport=4,bus=pci.0,addr=0x5.0x2 -device virtio-serial-pci,id=virtio-serial0,bus=pci.0,addr=0x6 -drive file=/var/lib/libvirt/images/ubuntusaucy.qcow2,if=none,id=drive-virtio-disk0,format=qcow2 -device virtio-blk-pci,scsi=off,bus=pci.0,addr=0x7,drive=drive-virtio-disk0,id=virtio-disk0,bootindex=1 -drive file=/var/lib/libvirt/images/ubuntu-14.04-mini.iso,if=none,id=drive-ide0-0-0,readonly=on,format=raw -device ide-cd,bus=ide.0,unit=0,drive=drive-ide0-0-0,id
+=ide0-0-0,bootindex=2 -netdev tap,fd=22,id=hostnet0,vhost=on,vhostfd=23 -device virtio-net-pci,netdev=hostnet0,id=net0,mac=52:54:00:5e:71:5e,bus=pci.0,addr=0x3 -chardev pty,id=charserial0 -device isa-serial,chardev=charserial0,id=serial0 -chardev spicevmc,id=charchannel0,name=vdagent -device virtserialport,bus=virtio-serial0.0,nr=1,chardev=charchannel0,id=channel0,name=com.redhat.spice.0 -spice port=5900,addr=127.0.0.1,disable-ticketing,seamless-migration=on -device qxl-vga,id=video0,ram_size=67108864,vram_size=67108864,bus=pci.0,addr=0x2 -device intel-hda,id=sound0,bus=pci.0,addr=0x4 -device hda-duplex,id=sound0-codec0,bus=sound0.0,cad=0 -chardev spicevmc,id=charredir0,name=usbredir -device usb-redir,chardev=charredir0,id=redir0 -chardev spicevmc,id=charredir1,
+name=usbredir -device usb-redir,chardev=charredir1,id=redir1 -chardev spicevmc,id=charredir2,name=usbredir -device usb-redir,chardev=charredir2,id=redir2 -chardev spicevmc,id=charredir3,name=usbredir -device usb-redir,chardev=charredir3,id=redir3 -device virtio-balloon-pci,id=balloon0,bus=pci.0,addr=0x8 -object rng-random,id=rng0,filename=/dev/random -device virtio-rng-pci,rng=rng0,bus=pci.0,addr=0x9 -msg timestamp=on
+char device redirected to /dev/pts/0 (label charserial0)
+main_channel_link: add main channel client
+main_channel_handle_parsed: net test: latency 0.233000 ms, bitrate 17964912280 bps (17132.675438 Mbps)
+red_dispatcher_set_cursor_peer: 
+inputs_connect: inputs channel client create
+((null):5798): SpiceWorker-ERROR **: red_worker.c:8337:red_marshall_qxl_drawable: invalid type
+red_channel_client_disconnect: 0x7f90397ec0c0 (channel 0x7f903812a090 type 5 id 0)
+((null):8349): Spice-Warning **: red_channel.c:1661:red_channel_remove_client: channel type 5 id 0 - channel->thread_id (0x7f90362cba80) != pthread_self (0x7f9011fff700).If one of the threads is != io-thread && != vcpu-thread, this might be a BUG
+snd_channel_put: sound channel freed
+red_channel_client_disconnect: 0x7f903a04c4c0 (channel 0x7f903812a230 type 6 id 0)
+((null):8349): Spice-Warning **: red_channel.c:1661:red_channel_remove_client: channel type 6 id 0 - channel->thread_id (0x7f90362cba80) != pthread_self (0x7f9011fff700).If one of the threads is != io-thread && != vcpu-thread, this might be a BUG
+snd_channel_put: sound channel freed
+KVM: injection failed, MSI lost (Input/output error)
+qemu-system-x86_64: /home/abuild/rpmbuild/BUILD/qemu-2.1.0/hw/virtio/vhost.c:1003: vhost_virtqueue_mask: Assertion `r >= 0' failed.
+2015-03-21 15:30:10.148+0000: shutting down
+
+The following patch might  fix this (I have not yet tested this patch myself): https://lkml.org/lkml/2015/7/5/217
+
+Triaging old bug tickets... can you still reproduce this issue with the latest version of QEMU? Or could we close this ticket nowadays?
+
+I haven't seen this for a long time so please proceed with closing this ticket.
+
+Ok, thanks, so I'm closing this now.
+
diff --git a/results/classifier/108/other/1436 b/results/classifier/108/other/1436
new file mode 100644
index 000000000..7fec8f792
--- /dev/null
+++ b/results/classifier/108/other/1436
@@ -0,0 +1,76 @@
+other: 0.856
+graphic: 0.745
+KVM: 0.695
+vnc: 0.662
+device: 0.644
+semantic: 0.621
+permissions: 0.594
+performance: 0.551
+debug: 0.548
+PID: 0.497
+network: 0.487
+files: 0.455
+socket: 0.396
+boot: 0.379
+
+Out of memory in hw/omap-dss for ARM
+Description of problem:
+In omap-dss, g_realloc() can allocate a large buffer using out of the memory.
+
+- [1] set pixels to any value
+- [2] double pixels
+- [3] allocate a large buffer
+
+```
+static void omap_rfbi_write(...) {
+   switch (addr) {
+     case 0x44: /* RFBI_PIXELCNT */
+        s->rfbi.pixels = value; // ------------------------------------> [1]
+        break;
+
+static void omap_rfbi_transfer_start(struct omap_dss_s *s) {
+    len = s->rfbi.pixels * 2;  // -------------------------------------> [2]
+    if (!data) {
+        if (len > bounce_len) {
+            bounce_buffer = g_realloc(bounce_buffer, len); // ---------> [3]
+        }
+```
+Steps to reproduce:
+```
+export QEMU=/path/to/qemu-system-arm
+
+cat << EOF | $QEMU \
+-machine n810,accel=qtest -m 128M -qtest stdio -monitor none -serial none \
+-display none -nodefaults -qtest stdio
+writel 0x48050440 0x74a57907
+writel 0x48050858 0x34982d63
+writel 0x48050840 0x65a61a51
+EOF
+```
+Additional information:
+```
+
+=================================================================
+==1029323==ERROR: AddressSanitizer: requested allocation size 0xfffffffffffffffe (0x800 after adjustments for alignment, red zones etc.) exceeds maximum supported size of 0x10000000000 (thread T0)
+    #0 0x7f4650b4ec3e in __interceptor_realloc ../../../../src/libsanitizer/asan/asan_malloc_linux.cc:163
+    #1 0x7f464fa27f3f in g_realloc (/lib/x86_64-linux-gnu/libglib-2.0.so.0+0x57f3f)
+    #2 0x55cf6212c85b in omap_rfbi_write ../hw/display/omap_dss.c:761
+    #3 0x55cf636b9c9b in memory_region_write_accessor ../softmmu/memory.c:493
+    #4 0x55cf636ba132 in access_with_adjusted_size ../softmmu/memory.c:555
+    #5 0x55cf636c76f8 in memory_region_dispatch_write ../softmmu/memory.c:1515
+    #6 0x55cf637049b9 in flatview_write_continue ../softmmu/physmem.c:2825
+    #7 0x55cf63704ddc in flatview_write ../softmmu/physmem.c:2867
+    #8 0x55cf637057c4 in address_space_write ../softmmu/physmem.c:2963
+    #9 0x55cf63716261 in qtest_process_command ../softmmu/qtest.c:533
+    #10 0x55cf6371ac52 in qtest_process_inbuf ../softmmu/qtest.c:802
+    #11 0x55cf6371ad43 in qtest_read ../softmmu/qtest.c:814
+    #12 0x55cf63d4d5e5 in qemu_chr_be_write_impl ../chardev/char.c:201
+    #13 0x55cf63d4d68c in qemu_chr_be_write ../chardev/char.c:213
+    #14 0x55cf63d544c9 in fd_chr_read ../chardev/char-fd.c:72
+    #15 0x55cf63938b9b in qio_channel_fd_source_dispatch ../io/channel-watch.c:84
+    #16 0x7f464fa2204d in g_main_context_dispatch (/lib/x86_64-linux-gnu/libglib-2.0.so.0+0x5204d)
+
+==1029323==HINT: if you don't care about these errors you may set allocator_may_return_null=1
+SUMMARY: AddressSanitizer: allocation-size-too-big ../../../../src/libsanitizer/asan/asan_malloc_linux.cc:163 in __interceptor_realloc
+==1029323==ABORTING
+```
diff --git a/results/classifier/108/other/1437367 b/results/classifier/108/other/1437367
new file mode 100644
index 000000000..108947421
--- /dev/null
+++ b/results/classifier/108/other/1437367
@@ -0,0 +1,52 @@
+files: 0.775
+device: 0.703
+other: 0.686
+semantic: 0.676
+graphic: 0.656
+performance: 0.645
+vnc: 0.508
+permissions: 0.508
+debug: 0.488
+PID: 0.466
+socket: 0.405
+network: 0.399
+boot: 0.378
+KVM: 0.273
+
+Qemu guest fails to write files with raw disk (like \\.\PhysicalDrive1) on Windows host.
+
+Qemu guest fails to write files with specifing raw disk like \\.\PhysicalDrive1
+full command line is below.
+qemu-sysytem-i386.exe -kernel bzImage -drive file=rootfs.ext2,index=0,if=scsi -append root=/dev/sda -drive file=\\.\PhysicalDrive1,index=1,if=scsi
+
+I found the reason is below aio_worker returns -EIO when flush operation.
+
+https://github.com/qemu/qemu/blob/master/block/raw-win32.c#L95
+
+static int aio_worker(void *arg)
+...
+    case QEMU_AIO_FLUSH:
+        if (!FlushFileBuffers(aiocb->hfile)) {
+            return -EIO;
+        }
+
+FlushFileBuffers always fails with GetLastError() == ERROR_INVALID_FUNCTION
+I think this function doesn't support raw device.
+For flushing, you might have to issue scsi/ata command or use another way.
+Trying to just ignoring this error, writing function seems to be fine for me.
+
+Thanks
+hiroaki
+
+The documentation of FlushFileBuffers() only mentions that consoles cannot be flushed. It doesn't specifically mention physical drives, but it does explicitly mention that whole volumes can be flushed this way:
+
+https://msdn.microsoft.com/en-us/library/windows/desktop/aa364439%28v=vs.85%29.aspx
+
+Of course, I'm not really a Windows expert, so my reading of this may be wrong. If anyone knows how physical drives are supposed to be flushed other than with FlushFileBuffers(), we can certainly implement that in qemu.
+
+In any case, just disabling the flush is not advisable as it may harm data integrity in case of crashes/power failure. If you really want to disable it, the cache=unsafe option should avoid the calls.
+
+Is there still anything left to do here, or could we close this ticket nowadays?
+
+[Expired for QEMU because there has been no activity for 60 days.]
+
diff --git a/results/classifier/108/other/1437811 b/results/classifier/108/other/1437811
new file mode 100644
index 000000000..6663ce8f9
--- /dev/null
+++ b/results/classifier/108/other/1437811
@@ -0,0 +1,26 @@
+graphic: 0.729
+device: 0.712
+socket: 0.694
+files: 0.688
+network: 0.511
+performance: 0.399
+debug: 0.378
+vnc: 0.348
+semantic: 0.330
+boot: 0.301
+PID: 0.265
+KVM: 0.144
+other: 0.134
+permissions: 0.085
+
+target-tricore/op_helper.c:2576: bad if statement 
+
+[qemu/target-tricore/op_helper.c:2576]: (style) Expression '(X & 0x400000) == 0x1' is always false.
+
+    if ((env->PCXI & MASK_PCXI_UL) == 1) {
+        /* CTYP trap */
+    }
+
+This problem has been fixed here:
+http://git.qemu.org/?p=qemu.git;a=commitdiff;h=7b4b0b5795e934a9b7efb
+
diff --git a/results/classifier/108/other/1438 b/results/classifier/108/other/1438
new file mode 100644
index 000000000..8d50e0c04
--- /dev/null
+++ b/results/classifier/108/other/1438
@@ -0,0 +1,22 @@
+device: 0.697
+other: 0.565
+network: 0.278
+socket: 0.220
+graphic: 0.205
+semantic: 0.192
+performance: 0.056
+boot: 0.054
+PID: 0.050
+files: 0.039
+debug: 0.038
+vnc: 0.032
+permissions: 0.021
+KVM: 0.006
+
+Allow to use QEMU sockets as a CAN bus backend
+Additional information:
+Good possible example how it can be done is via UDP multicast in `python-can` library:
+- https://python-can.readthedocs.io/en/master/interfaces/udp_multicast.html
+
+Another option, with less features is using a simple serial/character device like in:
+- https://python-can.readthedocs.io/en/master/interfaces/serial.html
diff --git a/results/classifier/108/other/1438144 b/results/classifier/108/other/1438144
new file mode 100644
index 000000000..a8d3e539a
--- /dev/null
+++ b/results/classifier/108/other/1438144
@@ -0,0 +1,32 @@
+device: 0.760
+semantic: 0.744
+performance: 0.653
+network: 0.649
+graphic: 0.623
+other: 0.565
+permissions: 0.563
+socket: 0.557
+files: 0.550
+vnc: 0.471
+debug: 0.393
+boot: 0.351
+PID: 0.235
+KVM: 0.220
+
+Page sizes are not interpreted correctly for E500/E500MC
+
+http://cache.freescale.com/files/32bit/doc/ref_manual/E500CORERM.pdf - see 2.12.5.2 MAS Register 1 (MAS1), p. 2-41
+http://cache.freescale.com/files/32bit/doc/ref_manual/E500MCRM.pdf - see 2.16.6.2 MAS Register 1 (MAS1), p. 2-54
+
+According to these documents, variable page size for TLB1 is computed as 4K ** TSIZE.
+
+However, QEMU always treats it as if it was 1K << TSIZE, even if options like "-cpu e500mc" are supplied to qemu.
+
+This is not a bug.  MMU v2 (implemented in e6500) extended the TSIZE field so that 1K <<
+TSIZE is correct.  The extension was on the LSB side so that it works
+fine as long as the low bit of the new TSIZE (which is reserved on
+e500v2/mc) is zero.
+
+
+You're absolutely right. Sorry for bothering. 
+
diff --git a/results/classifier/108/other/1439 b/results/classifier/108/other/1439
new file mode 100644
index 000000000..66346b57f
--- /dev/null
+++ b/results/classifier/108/other/1439
@@ -0,0 +1,26 @@
+graphic: 0.886
+device: 0.842
+KVM: 0.775
+files: 0.736
+network: 0.692
+performance: 0.598
+socket: 0.542
+semantic: 0.533
+vnc: 0.458
+boot: 0.444
+other: 0.299
+debug: 0.284
+PID: 0.231
+permissions: 0.109
+
+QEMU crashes when there is an "[accel]" section in the config file
+Description of problem:
+QEMU crashes with a segmentation fault if there is a "[accel]" section in the config file with a type="kvm" entry. It would be maybe still be OK if there was an error message instead, but it should certainly not crash.
+Steps to reproduce:
+```
+$ cat > /tmp/config <<EOF
+[accel]
+type = "kvm"
+EOF
+$ qemu-system-x86_64 -readconfig /tmp/config
+```