9 files changed, 819 insertions, 0 deletions
diff --git a/results/classifier/118/mistranslation-x86/1502934 b/results/classifier/118/mistranslation-x86/1502934
new file mode 100644
index 000000000..bc881373b
--- /dev/null
+++ b/results/classifier/118/mistranslation-x86/1502934
@@ -0,0 +1,89 @@
+x86: 0.924
+KVM: 0.913
+mistranslation: 0.817
+architecture: 0.798
+device: 0.782
+debug: 0.782
+graphic: 0.743
+ppc: 0.728
+semantic: 0.716
+permissions: 0.659
+performance: 0.621
+virtual: 0.539
+boot: 0.529
+user-level: 0.502
+register: 0.493
+kernel: 0.458
+PID: 0.452
+hypervisor: 0.433
+arm: 0.429
+network: 0.378
+vnc: 0.371
+files: 0.357
+peripherals: 0.314
+socket: 0.307
+risc-v: 0.281
+assembly: 0.262
+TCG: 0.204
+VMM: 0.163
+i386: 0.121
+--------------------
+x86: 0.956
+KVM: 0.939
+user-level: 0.785
+hypervisor: 0.746
+debug: 0.576
+virtual: 0.569
+kernel: 0.110
+PID: 0.026
+boot: 0.025
+VMM: 0.016
+performance: 0.010
+files: 0.010
+semantic: 0.009
+network: 0.006
+register: 0.005
+TCG: 0.004
+architecture: 0.004
+socket: 0.004
+device: 0.003
+vnc: 0.001
+permissions: 0.001
+mistranslation: 0.001
+graphic: 0.001
+assembly: 0.001
+peripherals: 0.001
+risc-v: 0.001
+ppc: 0.000
+i386: 0.000
+arm: 0.000
+
+QEMU does not start when kvm enabled (SMM issue?)
+
+Hi!
+
+QEMU stopped working after "[355023f2010c4df619d88a0dd7012b4b9c74c12c] pc: add SMM property" on my server. It says "Guest has not initialized the display (yet)." and nothing happens. But only if I use -enable-kvm.
+
+However, the problem gone after I hardcoded pc_machine_is_smm_enabled() to always return false (but I have little to no understanding of what SMM really is).
+
+CMD line that reproduces the issue: qemu-system-x86_64 -enable-kvm -display curses . It doesn't work the server, but works perfectly on my laptop :(.
+
+I'm using Arch Linux with all updates.
+Some info:
+Linux machine 4.2.2-1-ARCH #1 SMP PREEMPT Tue Sep 29 22:21:33 CEST 2015 x86_64 GNU/Linux
+Qemu-2.4.0 (tried HEAD as well)
+CPU: Intel(R) Core(TM) i7 CPU         950  @ 3.07GHz
+Some messages from dmesg, just in case:
+[    6.996297] kvm: VM_EXIT_LOAD_IA32_PERF_GLOBAL_CTRL does not work properly. Using workaround
+[ 6381.722990] kvm: zapping shadow pages for mmio generation wraparound
+
+
+I'm more than happy to provide additional  information if needed.
+
+Cheers,
+Alex
+
+This is a KVM bug, not a QEMU bug. It only happens with ept=1 and unrestricted_guest=0. A workaround is to disable SMM in QEMU (-machine smm=off) or to set kvm_intel's ept parameter to 0.
+
+I'm closing the bug here because it is the wrong tracker (also I know about it, can reproduce, and hope to provide a fix later this week).
+
diff --git a/results/classifier/118/mistranslation-x86/1773743 b/results/classifier/118/mistranslation-x86/1773743
new file mode 100644
index 000000000..42ef80534
--- /dev/null
+++ b/results/classifier/118/mistranslation-x86/1773743
@@ -0,0 +1,90 @@
+mistranslation: 0.990
+user-level: 0.938
+x86: 0.910
+performance: 0.750
+device: 0.740
+semantic: 0.739
+graphic: 0.724
+vnc: 0.657
+debug: 0.634
+architecture: 0.613
+ppc: 0.601
+peripherals: 0.581
+network: 0.520
+permissions: 0.507
+socket: 0.506
+PID: 0.476
+VMM: 0.449
+register: 0.433
+hypervisor: 0.432
+risc-v: 0.423
+files: 0.422
+kernel: 0.419
+i386: 0.414
+TCG: 0.413
+virtual: 0.330
+boot: 0.277
+arm: 0.238
+KVM: 0.215
+assembly: 0.158
+--------------------
+debug: 0.965
+x86: 0.947
+user-level: 0.885
+hypervisor: 0.569
+virtual: 0.264
+TCG: 0.122
+files: 0.036
+PID: 0.023
+performance: 0.023
+network: 0.018
+semantic: 0.015
+register: 0.011
+kernel: 0.009
+device: 0.007
+assembly: 0.005
+socket: 0.005
+ppc: 0.004
+architecture: 0.004
+VMM: 0.004
+KVM: 0.003
+peripherals: 0.003
+graphic: 0.002
+boot: 0.002
+permissions: 0.002
+vnc: 0.001
+i386: 0.001
+risc-v: 0.001
+mistranslation: 0.001
+arm: 0.000
+
+qemu-user -g xxx -E LD_PROFILE=xxx segfault
+
+Here is two simple steps to reproduce the bug:
+
+$ qemu-x86_64 -E LD_PROFILE=libc.so.6 -E LD_PROFILE_OUTPUT=. -g 12345 -L / /bin/ls
+
+(libc.so and /bin/ls might change on your system, in this case we just need a binary with a profilable needed library)
+
+In a other window launch:
+
+$ gdb
+(gdb) target remote :12345
+(gdb) c
+
+At this point qemu will segfault.
+
+It seems this problem is appends when sigprof passed to gdb.
+One way I have found to bypass this:
+patch gdbstub.c gdb_handlesig and ignore sig if
+sig == TARGET_SIGPROF
+(which means now I can't catch sigprof on gdb anymore)
+
+We were mis-parsing the 'vCont' packet in the gdb protocol, so when gdb told us "send a SIGPROF (0x1b)" we skipped the first digit in the hex signal number and interpreted it as "send an 0xb", which happens to be SIGSEGV.
+
+Should be fixed by this:
+https://<email address hidden>/
+
+
+https://gitlab.com/qemu-project/qemu/-/commit/3ddd9036389f5f577e09
+
diff --git a/results/classifier/118/mistranslation-x86/1832914 b/results/classifier/118/mistranslation-x86/1832914
new file mode 100644
index 000000000..b420f1091
--- /dev/null
+++ b/results/classifier/118/mistranslation-x86/1832914
@@ -0,0 +1,75 @@
+mistranslation: 0.973
+architecture: 0.962
+x86: 0.931
+device: 0.874
+semantic: 0.783
+arm: 0.742
+user-level: 0.733
+files: 0.733
+graphic: 0.731
+ppc: 0.664
+PID: 0.603
+network: 0.566
+performance: 0.563
+kernel: 0.546
+debug: 0.545
+i386: 0.540
+permissions: 0.536
+boot: 0.523
+VMM: 0.431
+peripherals: 0.421
+socket: 0.420
+risc-v: 0.417
+register: 0.402
+hypervisor: 0.400
+TCG: 0.381
+virtual: 0.365
+vnc: 0.347
+KVM: 0.267
+assembly: 0.098
+--------------------
+x86: 0.980
+user-level: 0.930
+debug: 0.692
+hypervisor: 0.589
+files: 0.165
+virtual: 0.150
+register: 0.077
+TCG: 0.049
+device: 0.047
+semantic: 0.015
+kernel: 0.011
+architecture: 0.009
+PID: 0.007
+permissions: 0.007
+boot: 0.006
+assembly: 0.003
+network: 0.003
+VMM: 0.003
+peripherals: 0.002
+socket: 0.002
+KVM: 0.002
+performance: 0.002
+graphic: 0.002
+ppc: 0.002
+mistranslation: 0.001
+risc-v: 0.001
+vnc: 0.001
+i386: 0.000
+arm: 0.000
+
+Wrong error log when drive is specified qcow but qcow2 image file used.
+
+On archlinux qemu version 4.0.0 when I type:
+
+$ qemu-system-x86_64 -drive format=qcow,file=image.qcow2 ...
+
+I get this output in stderr 
+
+qemu-system-x86_64 -drive format=qcow,file=image.qcow2 ...: Unsupported qcow version 3
+
+image.qcow2 is a qcow2 image created by qemu-img. error states that problem is with lack support with qcow3 format but real problem is that foramt=qcow is wrong option.
+
+Fix has been included here:
+https://git.qemu.org/?p=qemu.git;a=commitdiff;h=197bfa7da7c8eeb39aa5
+
diff --git a/results/classifier/118/mistranslation-x86/1850751 b/results/classifier/118/mistranslation-x86/1850751
new file mode 100644
index 000000000..f35d27bfc
--- /dev/null
+++ b/results/classifier/118/mistranslation-x86/1850751
@@ -0,0 +1,84 @@
+x86: 0.970
+KVM: 0.844
+mistranslation: 0.843
+graphic: 0.813
+hypervisor: 0.812
+architecture: 0.790
+device: 0.788
+semantic: 0.737
+i386: 0.704
+performance: 0.694
+permissions: 0.646
+kernel: 0.619
+files: 0.607
+network: 0.598
+ppc: 0.589
+register: 0.582
+risc-v: 0.567
+virtual: 0.566
+debug: 0.531
+user-level: 0.530
+vnc: 0.520
+PID: 0.514
+socket: 0.485
+VMM: 0.475
+peripherals: 0.466
+boot: 0.458
+arm: 0.421
+TCG: 0.417
+assembly: 0.370
+--------------------
+x86: 0.976
+KVM: 0.765
+hypervisor: 0.642
+user-level: 0.617
+TCG: 0.088
+virtual: 0.080
+debug: 0.046
+architecture: 0.028
+semantic: 0.013
+files: 0.013
+kernel: 0.013
+PID: 0.012
+socket: 0.006
+boot: 0.006
+device: 0.006
+network: 0.006
+performance: 0.006
+i386: 0.006
+risc-v: 0.005
+register: 0.005
+permissions: 0.004
+assembly: 0.003
+ppc: 0.003
+peripherals: 0.002
+vnc: 0.001
+graphic: 0.001
+VMM: 0.001
+arm: 0.001
+mistranslation: 0.000
+
+kvm flag is not exposed by default
+
+Hi I found that the kvm flags is not exposed by default, but according to the source code, it should be exposed by default when the CPU Model is a X86CPU.
+
+we have to specifically add "kvm=on" in QEMU custom cpu args like this:
+<qemu:arg value='host,kvm=on,+invtsc,+hypervisor'/>
+
+Also the libvirt can't expose kvm because this (libvirt assumes the kvm flag is exposed by default, only "kvm hidden = 'true'" can be used.
+
+The QEMU project is currently considering to move its bug tracking to
+another system. For this we need to know which bugs are still valid
+and which could be closed already. Thus we are setting older bugs to
+"Incomplete" now.
+
+If you still think this bug report here is valid, then please switch
+the state back to "New" within the next 60 days, otherwise this report
+will be marked as "Expired". Or please mark it as "Fix Released" if
+the problem has been solved with a newer version of QEMU already.
+
+Thank you and sorry for the inconvenience.
+
+
+[Expired for QEMU because there has been no activity for 60 days.]
+
diff --git a/results/classifier/118/mistranslation-x86/1878641 b/results/classifier/118/mistranslation-x86/1878641
new file mode 100644
index 000000000..611d6b762
--- /dev/null
+++ b/results/classifier/118/mistranslation-x86/1878641
@@ -0,0 +1,121 @@
+mistranslation: 0.814
+x86: 0.809
+peripherals: 0.802
+risc-v: 0.764
+i386: 0.753
+user-level: 0.751
+KVM: 0.745
+VMM: 0.737
+TCG: 0.735
+vnc: 0.733
+hypervisor: 0.717
+ppc: 0.711
+graphic: 0.700
+virtual: 0.690
+performance: 0.684
+register: 0.675
+semantic: 0.658
+arm: 0.622
+device: 0.620
+debug: 0.615
+architecture: 0.608
+permissions: 0.601
+assembly: 0.599
+socket: 0.573
+PID: 0.568
+boot: 0.564
+kernel: 0.531
+files: 0.530
+network: 0.495
+--------------------
+debug: 0.947
+x86: 0.865
+kernel: 0.805
+hypervisor: 0.734
+TCG: 0.238
+register: 0.234
+i386: 0.214
+user-level: 0.183
+assembly: 0.170
+device: 0.151
+files: 0.147
+VMM: 0.130
+performance: 0.109
+virtual: 0.099
+KVM: 0.082
+semantic: 0.064
+PID: 0.055
+architecture: 0.045
+ppc: 0.033
+socket: 0.024
+risc-v: 0.023
+peripherals: 0.018
+permissions: 0.012
+boot: 0.009
+network: 0.007
+arm: 0.006
+vnc: 0.003
+graphic: 0.002
+mistranslation: 0.000
+
+Abort() in mch_update_pciexbar
+
+Hello,
+I found an input which triggers an abort() in mch_update_pciexbar:
+
+#0  0x00007ffff686d761 in __GI_raise (sig=sig@entry=0x6) at ../sysdeps/unix/sysv/linux/raise.c:50
+#1  0x00007ffff685755b in __GI_abort () at abort.c:79
+#2  0x000055555705c7ae in mch_update_pciexbar (mch=0x629000005920) at /home/alxndr/Development/qemu/hw/pci-host/q35.c:324
+#3  0x000055555705bb6a in mch_write_config (d=0x629000005920, address=0x60, val=0x8400056e, len=0x4) at /home/alxndr/Development/qemu/hw/pci-host/q35.c:480
+#4  0x00005555570954fb in pci_host_config_write_common (pci_dev=0x629000005920, addr=0x60, limit=0x100, val=0x8400056e, len=0x4) at /home/alxndr/Development/qemu/hw/pci/pci_host.c:81
+#5  0x000055555709606e in pci_data_write (s=0x61d000096080, addr=0xf2000060, val=0x8400056e, len=0x4) at /home/alxndr/Development/qemu/hw/pci/pci_host.c:118
+#6  0x00005555570967d0 in pci_host_data_write (opaque=0x629000005200, addr=0x0, val=0x8400056e, len=0x4) at /home/alxndr/Development/qemu/hw/pci/pci_host.c:165
+#7  0x00005555564938b5 in memory_region_write_accessor (mr=0x629000005610, addr=0x0, value=0x7fffffff9c70, size=0x4, shift=0x0, mask=0xffffffff, attrs=...) at /home/alxndr/Development/qemu/memory.c:483
+#8  0x000055555649328a in access_with_adjusted_size (addr=0x0, value=0x7fffffff9c70, size=0x4, access_size_min=0x1, access_size_max=0x4, access_fn=0x555556493360 <memory_region_write_accessor>, mr=0x629000005610, attrs=...) at /home/alxndr/Development/qemu/memory.c:544
+#9  0x0000555556491df6 in memory_region_dispatch_write (mr=0x629000005610, addr=0x0, data=0x8400056e, op=MO_32, attrs=...) at /home/alxndr/Development/qemu/memory.c:1476
+#10 0x00005555562cbbf4 in flatview_write_continue (fv=0x606000033b00, addr=0xcfc, attrs=..., ptr=0x7fffffffa4e0, len=0x4, addr1=0x0, l=0x4, mr=0x629000005610) at /home/alxndr/Development/qemu/exec.c:3137
+#11 0x00005555562bbad9 in flatview_write (fv=0x606000033b00, addr=0xcfc, attrs=..., buf=0x7fffffffa4e0, len=0x4) at /home/alxndr/Development/qemu/exec.c:3177
+#12 0x00005555562bb609 in address_space_write (as=0x55555968f940 <address_space_io>, addr=0xcfc, attrs=..., buf=0x7fffffffa4e0, len=0x4) at /home/alxndr/Development/qemu/exec.c:3268
+#13 0x0000555556478c0a in cpu_outl (addr=0xcfc, val=0x8400056e) at /home/alxndr/Development/qemu/ioport.c:80
+#14 0x000055555648166f in qtest_process_command (chr=0x555559691d00 <qtest_chr>, words=0x60300009ebf0) at /home/alxndr/Development/qemu/qtest.c:396
+#15 0x000055555647f187 in qtest_process_inbuf (chr=0x555559691d00 <qtest_chr>, inbuf=0x61900000f680) at /home/alxndr/Development/qemu/qtest.c:710
+#16 0x000055555647e8b4 in qtest_read (opaque=0x555559691d00 <qtest_chr>, buf=0x7fffffffca40 "outl 0xcf8 0xf2000060\noutl 0xcfc 0x8400056e\n-M pc-q35-5.0 -device intel-hda,id=hda0 -device hda-output,bus=hda0.0 -device hda-micro,bus=hda0.0 -device hda-duplex,bus=hda0.0 -display none -nodefaults -nographic\n\377\377\377\177", size=0xd2) at /home/alxndr/Development/qemu/qtest.c:722
+#17 0x00005555579c260c in qemu_chr_be_write_impl (s=0x60f000001f30, buf=0x7fffffffca40 "outl 0xcf8 0xf2000060\noutl 0xcfc 0x8400056e\n-M pc-q35-5.0 -device intel-hda,id=hda0 -device hda-output,bus=hda0.0 -device hda-micro,bus=hda0.0 -device hda-duplex,bus=hda0.0 -display none -nodefaults -nographic\n\377\377\377\177", len=0xd2) at /home/alxndr/Development/qemu/chardev/char.c:183
+#18 0x00005555579c275b in qemu_chr_be_write (s=0x60f000001f30, buf=0x7fffffffca40 "outl 0xcf8 0xf2000060\noutl 0xcfc 0x8400056e\n-M pc-q35-5.0 -device intel-hda,id=hda0 -device hda-output,bus=hda0.0 -device hda-micro,bus=hda0.0 -device hda-duplex,bus=hda0.0 -display none -nodefaults -nographic\n\377\377\377\177", len=0xd2) at /home/alxndr/Development/qemu/chardev/char.c:195
+#19 0x00005555579cb97a in fd_chr_read (chan=0x6080000026a0, cond=G_IO_IN, opaque=0x60f000001f30) at /home/alxndr/Development/qemu/chardev/char-fd.c:68
+#20 0x0000555557a530ea in qio_channel_fd_source_dispatch (source=0x60c00002ef00, callback=0x5555579cb540 <fd_chr_read>, user_data=0x60f000001f30) at /home/alxndr/Development/qemu/io/channel-watch.c:84
+#21 0x00007ffff7ca8898 in g_main_context_dispatch () at /usr/lib/x86_64-linux-gnu/libglib-2.0.so.0
+#22 0x0000555557c10b85 in glib_pollfds_poll () at /home/alxndr/Development/qemu/util/main-loop.c:219
+#23 0x0000555557c0f57e in os_host_main_loop_wait (timeout=0x0) at /home/alxndr/Development/qemu/util/main-loop.c:242
+#24 0x0000555557c0f177 in main_loop_wait (nonblocking=0x0) at /home/alxndr/Development/qemu/util/main-loop.c:518
+#25 0x000055555689fd1e in qemu_main_loop () at /home/alxndr/Development/qemu/softmmu/vl.c:1664
+#26 0x0000555557a6a29d in main (argc=0x17, argv=0x7fffffffe148, envp=0x7fffffffe208) at /home/alxndr/Development/qemu/softmmu/main.c:49
+
+
+I can reproduce this in qemu 5.0 built using these qtest commands:
+
+cat << EOF | ./qemu-system-i386 \
+-qtest stdio -nographic -monitor none -serial none \
+-M pc-q35-5.0
+outl 0xcf8 0xf2000060
+outl 0xcfc 0x8400056e
+EOF
+
+Please let me know if I can provide any further info.
+-Alex
+
+Proposed fix:
+https://lists.gnu.org/archive/html/qemu-devel/2020-07/msg05612.html
+
+Confirmed, this is not fixed yet. Philippe, what happened to your patch?
+
+On 5/26/21 1:06 PM, Thomas Huth wrote:
+> Confirmed, this is not fixed yet. Philippe, what happened to your patch?
+
+I was waiting someone suggest me how to propagate error from
+PCIConfigWriteFunc. Probably not very important.
+
+
+Fix has been included here:
+https://gitlab.com/qemu-project/qemu/-/commit/9b0ca75e0196a725232
+
diff --git a/results/classifier/118/mistranslation-x86/1898954 b/results/classifier/118/mistranslation-x86/1898954
new file mode 100644
index 000000000..607230401
--- /dev/null
+++ b/results/classifier/118/mistranslation-x86/1898954
@@ -0,0 +1,120 @@
+x86: 0.916
+i386: 0.915
+mistranslation: 0.880
+architecture: 0.876
+user-level: 0.872
+boot: 0.854
+graphic: 0.850
+performance: 0.819
+virtual: 0.809
+KVM: 0.778
+permissions: 0.765
+device: 0.762
+semantic: 0.752
+files: 0.732
+debug: 0.692
+hypervisor: 0.677
+PID: 0.677
+ppc: 0.676
+risc-v: 0.670
+socket: 0.648
+kernel: 0.626
+network: 0.624
+VMM: 0.610
+register: 0.593
+assembly: 0.575
+arm: 0.574
+peripherals: 0.569
+vnc: 0.567
+TCG: 0.557
+--------------------
+x86: 0.970
+user-level: 0.844
+assembly: 0.580
+i386: 0.265
+virtual: 0.187
+debug: 0.140
+TCG: 0.052
+files: 0.031
+boot: 0.021
+hypervisor: 0.019
+PID: 0.015
+semantic: 0.010
+socket: 0.008
+risc-v: 0.007
+network: 0.006
+register: 0.005
+vnc: 0.005
+VMM: 0.004
+device: 0.003
+kernel: 0.003
+performance: 0.003
+graphic: 0.002
+architecture: 0.001
+ppc: 0.001
+permissions: 0.001
+mistranslation: 0.001
+peripherals: 0.001
+KVM: 0.000
+arm: 0.000
+
+x86 f1 opcode hangs qemu
+
+I have qemu installed and running in linux and windows
+in linux i execute the following simple code in real mode of cpu in my vm
+90 nop
+90 nop
+90 nop
+f1         ;this should conjure up my interrupt handler from ivt int 1
+--------- end of code ----
+it works properly in vbox,qemu linux,and even in my boot loder
+on a real platform
+   it doeas not work fine in windows 10 (32 bit efi) based qemu
+---
+all of the below was retyped there may be typo
+so onwards to the flawed software 
+********** for qemu-system-x86_64.exe **********
+info version 
+4.2.0v4.2.0.11797-g2890edc853-dirty
+********** for qemu-system-i386.exe **********
+info version 
+4.2.0v4.2.0.11797-g2890edc853-dirty
+***********************************************
+my startup code is
+"d:\programs\qemu\qemu-system-x86_64.exe" -m 16M -boot a -fda "d:\floppy.img" -cpu Nehalem -machine pc
+---
+also same flaw if i change above section to
+"d:\programs\qemu\qemu-system-i386.exe"
+
+The QEMU project is currently moving its bug tracking to another system.
+For this we need to know which bugs are still valid and which could be
+closed already. Thus we are setting the bug state to "Incomplete" now.
+
+If the bug has already been fixed in the latest upstream version of QEMU,
+then please close this ticket as "Fix released".
+
+If it is not fixed yet and you think that this bug report here is still
+valid, then you have two options:
+
+1) If you already have an account on gitlab.com, please open a new ticket
+for this problem in our new tracker here:
+
+    https://gitlab.com/qemu-project/qemu/-/issues
+
+and then close this ticket here on Launchpad (or let it expire auto-
+matically after 60 days). Please mention the URL of this bug ticket on
+Launchpad in the new ticket on GitLab.
+
+2) If you don't have an account on gitlab.com and don't intend to get
+one, but still would like to keep this ticket opened, then please switch
+the state back to "New" or "Confirmed" within the next 60 days (other-
+wise it will get closed as "Expired"). We will then eventually migrate
+the ticket automatically to the new system (but you won't be the reporter
+of the bug in the new system and thus you won't get notified on changes
+anymore).
+
+Thank you and sorry for the inconvenience.
+
+
+[Expired for QEMU because there has been no activity for 60 days.]
+
diff --git a/results/classifier/118/mistranslation-x86/1900919 b/results/classifier/118/mistranslation-x86/1900919
new file mode 100644
index 000000000..90859c252
--- /dev/null
+++ b/results/classifier/118/mistranslation-x86/1900919
@@ -0,0 +1,107 @@
+mistranslation: 0.906
+user-level: 0.886
+x86: 0.886
+peripherals: 0.885
+graphic: 0.874
+architecture: 0.871
+device: 0.853
+semantic: 0.843
+PID: 0.811
+permissions: 0.801
+ppc: 0.801
+performance: 0.783
+debug: 0.753
+network: 0.729
+hypervisor: 0.705
+assembly: 0.674
+register: 0.659
+files: 0.635
+kernel: 0.597
+socket: 0.541
+vnc: 0.536
+i386: 0.532
+arm: 0.511
+virtual: 0.504
+TCG: 0.472
+boot: 0.447
+risc-v: 0.430
+KVM: 0.408
+VMM: 0.406
+--------------------
+x86: 0.896
+debug: 0.212
+files: 0.059
+virtual: 0.036
+device: 0.035
+PID: 0.034
+TCG: 0.028
+hypervisor: 0.024
+semantic: 0.012
+ppc: 0.011
+user-level: 0.009
+boot: 0.009
+VMM: 0.006
+risc-v: 0.005
+peripherals: 0.005
+register: 0.005
+socket: 0.005
+vnc: 0.005
+performance: 0.004
+architecture: 0.004
+network: 0.004
+kernel: 0.003
+permissions: 0.003
+i386: 0.003
+assembly: 0.002
+arm: 0.002
+graphic: 0.002
+mistranslation: 0.001
+KVM: 0.000
+
+PXB selected as root bus incorrectly
+
+release: 4c41341af76cfc85b5a6c0f87de4838672ab9f89
+
+qdev_device_add() will search for the "closest" bus possible, and bail out early if that bus is a root bus. pxb devices are considered root buses and so if you either
+1. Add a PCI device on the QEMU command line *after* a pxb device, or
+2. Add an integrated PCI device (like a watchdog)
+
+#1: -device pxb-pcie,id=cxl.0,bus=pcie.0,bus_nr=52 -device ahci,id=sata0,addr=0x8
+#2: -watchdog i6300esb -device pxb-pcie,id=cxl.0,bus=pcie.0,bus_nr=52
+
+The PXB will get selected as the bus (instead of the real root bus) and this will cause an assertion failure with the message like "qemu-system-x86_64: -device ahci,id=sata0,addr=0x8: PCI: Only PCI/PCIe bridges can be plugged into pxb-pcie"
+
+I think this is relatively solvable in the code base by determining if a bus is an expander, and skipping it if so. However, I wonder if it makes more sense to just allow expanders to have endpoint devices.
+
+The QEMU project is currently moving its bug tracking to another system.
+For this we need to know which bugs are still valid and which could be
+closed already. Thus we are setting the bug state to "Incomplete" now.
+
+If the bug has already been fixed in the latest upstream version of QEMU,
+then please close this ticket as "Fix released".
+
+If it is not fixed yet and you think that this bug report here is still
+valid, then you have two options:
+
+1) If you already have an account on gitlab.com, please open a new ticket
+for this problem in our new tracker here:
+
+    https://gitlab.com/qemu-project/qemu/-/issues
+
+and then close this ticket here on Launchpad (or let it expire auto-
+matically after 60 days). Please mention the URL of this bug ticket on
+Launchpad in the new ticket on GitLab.
+
+2) If you don't have an account on gitlab.com and don't intend to get
+one, but still would like to keep this ticket opened, then please switch
+the state back to "New" or "Confirmed" within the next 60 days (other-
+wise it will get closed as "Expired"). We will then eventually migrate
+the ticket automatically to the new system (but you won't be the reporter
+of the bug in the new system and thus you won't get notified on changes
+anymore).
+
+Thank you and sorry for the inconvenience.
+
+
+[Expired for QEMU because there has been no activity for 60 days.]
+
diff --git a/results/classifier/118/mistranslation-x86/1907953 b/results/classifier/118/mistranslation-x86/1907953
new file mode 100644
index 000000000..b28825e54
--- /dev/null
+++ b/results/classifier/118/mistranslation-x86/1907953
@@ -0,0 +1,66 @@
+mistranslation: 0.999
+x86: 0.985
+vnc: 0.737
+device: 0.724
+semantic: 0.713
+architecture: 0.607
+arm: 0.585
+risc-v: 0.478
+performance: 0.477
+graphic: 0.439
+user-level: 0.438
+debug: 0.414
+files: 0.383
+register: 0.341
+network: 0.315
+assembly: 0.277
+boot: 0.263
+ppc: 0.262
+VMM: 0.241
+TCG: 0.228
+permissions: 0.220
+peripherals: 0.179
+hypervisor: 0.145
+socket: 0.139
+virtual: 0.127
+PID: 0.123
+kernel: 0.077
+i386: 0.037
+KVM: 0.029
+--------------------
+user-level: 0.958
+virtual: 0.812
+hypervisor: 0.775
+x86: 0.324
+debug: 0.246
+ppc: 0.070
+boot: 0.030
+TCG: 0.025
+performance: 0.022
+files: 0.021
+semantic: 0.009
+device: 0.006
+mistranslation: 0.003
+risc-v: 0.003
+kernel: 0.002
+PID: 0.002
+assembly: 0.002
+KVM: 0.002
+graphic: 0.001
+VMM: 0.001
+network: 0.001
+arm: 0.001
+socket: 0.001
+register: 0.001
+peripherals: 0.001
+architecture: 0.000
+vnc: 0.000
+i386: 0.000
+permissions: 0.000
+
+pkg install qemu-system-x86_64  não funciona qemu 5.2.0
+
+A qemu funcionava mais quando atualizei para 5.2.0 não iniciar o Windows só fica tela preta quero voltar para anterior mais não consigo
+
+Sorry, please write bug reports in proper English.
+
diff --git a/results/classifier/118/mistranslation-x86/1914 b/results/classifier/118/mistranslation-x86/1914
new file mode 100644
index 000000000..5c5c268ae
--- /dev/null
+++ b/results/classifier/118/mistranslation-x86/1914
@@ -0,0 +1,67 @@
+x86: 0.996
+i386: 0.972
+device: 0.895
+graphic: 0.859
+mistranslation: 0.852
+architecture: 0.709
+semantic: 0.675
+PID: 0.651
+files: 0.642
+register: 0.596
+TCG: 0.524
+vnc: 0.516
+VMM: 0.504
+network: 0.495
+debug: 0.485
+ppc: 0.485
+permissions: 0.442
+user-level: 0.436
+risc-v: 0.425
+boot: 0.372
+socket: 0.300
+virtual: 0.271
+performance: 0.243
+arm: 0.208
+kernel: 0.178
+assembly: 0.093
+peripherals: 0.072
+hypervisor: 0.043
+KVM: 0.029
+--------------------
+x86: 1.000
+i386: 0.394
+files: 0.246
+architecture: 0.158
+virtual: 0.108
+kernel: 0.061
+hypervisor: 0.033
+TCG: 0.025
+semantic: 0.025
+KVM: 0.019
+register: 0.014
+debug: 0.011
+device: 0.006
+assembly: 0.005
+VMM: 0.005
+boot: 0.004
+user-level: 0.003
+PID: 0.002
+network: 0.001
+graphic: 0.001
+permissions: 0.001
+performance: 0.001
+socket: 0.000
+mistranslation: 0.000
+vnc: 0.000
+peripherals: 0.000
+ppc: 0.000
+arm: 0.000
+risc-v: 0.000
+
+x86 q35 machine type documentation is missing
+Description of problem:
+The x86 machine type of q35 was added in 2012 by commit
+df2d8b3ed4d2 ("q35: Introduce q35 pc based chipset emulator")
+but no documentation was added to docs/master/system/target-i386.html
+Additional information:
+There was development documentation at https://wiki.qemu.org/Features/Q35