6 files changed, 626 insertions, 0 deletions
diff --git a/results/classifier/118/user-level-i386/1363467 b/results/classifier/118/user-level-i386/1363467
new file mode 100644
index 000000000..fd7e5d65c
--- /dev/null
+++ b/results/classifier/118/user-level-i386/1363467
@@ -0,0 +1,85 @@
+i386: 0.980
+graphic: 0.880
+KVM: 0.871
+user-level: 0.851
+performance: 0.846
+semantic: 0.811
+device: 0.809
+kernel: 0.776
+network: 0.725
+permissions: 0.722
+hypervisor: 0.719
+socket: 0.714
+architecture: 0.712
+files: 0.710
+register: 0.699
+PID: 0.693
+boot: 0.693
+debug: 0.683
+VMM: 0.663
+x86: 0.652
+arm: 0.625
+risc-v: 0.621
+vnc: 0.616
+peripherals: 0.600
+virtual: 0.590
+ppc: 0.566
+mistranslation: 0.552
+TCG: 0.449
+assembly: 0.414
+--------------------
+i386: 0.999
+user-level: 0.989
+x86: 0.977
+virtual: 0.119
+debug: 0.065
+TCG: 0.022
+register: 0.021
+hypervisor: 0.021
+files: 0.018
+performance: 0.012
+network: 0.004
+risc-v: 0.004
+kernel: 0.004
+VMM: 0.003
+device: 0.003
+boot: 0.003
+semantic: 0.002
+PID: 0.002
+assembly: 0.002
+socket: 0.001
+architecture: 0.001
+peripherals: 0.001
+KVM: 0.001
+graphic: 0.001
+ppc: 0.001
+permissions: 0.001
+vnc: 0.000
+mistranslation: 0.000
+arm: 0.000
+
+qemu-system-i386 does not work
+
+I am using QEMU 2.1.0 on a Slackware 14.1 operating system (with Linux 3.15.8).
+
+I run QEMU like this:
+$ qemu-system-i386 slackware-14.1-install-dvd.iso
+I have also tested with the "-enable-kvm" and the "-m 1000" options.
+
+And QEMU is does not work.
+I mean, after 10 minutes, nothing is displayed on the screen, I am not able to see the Slackware installer.
+
+
+
+Triaging old bug tickets... can you still reproduce this issue with the latest version of QEMU? Or could we close this ticket nowadays?
+
+I have just tested with QEMU 2.10.0 on Slackware 14.2 and Slackware64 14.2.
+
+I run QEMU like this:
+$ qemu-system-i386 slackware-14.1-install-dvd.iso
+
+It works perfectly now.
+It is fixed.
+
+Thanks for checking it again!
+
diff --git a/results/classifier/118/user-level-i386/1671173 b/results/classifier/118/user-level-i386/1671173
new file mode 100644
index 000000000..d4bd1c7b9
--- /dev/null
+++ b/results/classifier/118/user-level-i386/1671173
@@ -0,0 +1,101 @@
+i386: 0.959
+x86: 0.937
+graphic: 0.914
+debug: 0.886
+kernel: 0.868
+files: 0.821
+user-level: 0.820
+architecture: 0.810
+register: 0.784
+performance: 0.767
+device: 0.760
+semantic: 0.747
+mistranslation: 0.698
+ppc: 0.678
+permissions: 0.653
+peripherals: 0.625
+PID: 0.622
+hypervisor: 0.608
+network: 0.604
+risc-v: 0.540
+socket: 0.530
+TCG: 0.521
+boot: 0.517
+vnc: 0.514
+KVM: 0.509
+VMM: 0.487
+arm: 0.454
+virtual: 0.383
+assembly: 0.383
+--------------------
+i386: 0.992
+x86: 0.941
+virtual: 0.788
+user-level: 0.652
+debug: 0.331
+hypervisor: 0.136
+kernel: 0.076
+boot: 0.063
+TCG: 0.034
+PID: 0.023
+performance: 0.012
+files: 0.012
+socket: 0.009
+semantic: 0.006
+register: 0.006
+device: 0.006
+network: 0.006
+vnc: 0.004
+architecture: 0.004
+graphic: 0.003
+assembly: 0.002
+ppc: 0.002
+risc-v: 0.002
+permissions: 0.002
+VMM: 0.001
+peripherals: 0.001
+arm: 0.001
+mistranslation: 0.001
+KVM: 0.000
+
+OS started to crash with a message: "Trying to execute code outside RAM or ROM"
+
+There is a project (https://github.com/narke/colorForth ) wich always worked with qemu up to version 2.5.1.1 but doesn't works from version 2.6 onwards. It continues to work with bochs.
+
+Downlaod: git clone https://github.com/narke/colorForth.git
+Build: make
+Test: qemu-system-i386 -drive format=raw,file=cf2012.img,index=0,if=floppy
+
+
+System information: Ubuntu LTS 16.04 x86-64
+Affected qemu versions: 2.6 to present (2.8)
+
+
+I got the message:
+
+
+WARNING: Image format was not specified for 'cf2012.img' and probing guessed raw.
+         Automatically detecting the format is dangerous for raw images, write operations on block 0 will be restricted.
+         Specify the 'raw' format explicitly to remove the restrictions.
+qemu-system-i386: Trying to execute code outside RAM or ROM at 0x8998c426
+This usually means one of the following happened:
+
+(1) You told QEMU to execute a kernel for the wrong machine type, and it crashed on startup (eg trying to run a raspberry pi kernel on a versatilepb QEMU machine)
+(2) You didn't give QEMU a kernel or BIOS filename at all, and QEMU executed a ROM full of no-op instructions until it fell off the end
+(3) Your guest kernel has a bug and crashed by jumping off into nowhere
+
+This is almost always one of the first two, so check your command line and that you are using the right type of kernel for this machine.
+If you think option (3) is likely then you can try debugging your guest with the -d debug options; in particular -d guest_errors will cause the log to include a dump of the guest register state at this point.
+
+Execution cannot continue; stopping here.
+
+
+Thank you in advance.
+
+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 all 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". 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/user-level-i386/1889421 b/results/classifier/118/user-level-i386/1889421
new file mode 100644
index 000000000..f005d9046
--- /dev/null
+++ b/results/classifier/118/user-level-i386/1889421
@@ -0,0 +1,107 @@
+i386: 0.935
+x86: 0.902
+user-level: 0.873
+files: 0.858
+graphic: 0.848
+network: 0.834
+architecture: 0.789
+permissions: 0.775
+performance: 0.758
+device: 0.740
+peripherals: 0.720
+semantic: 0.711
+vnc: 0.692
+kernel: 0.684
+ppc: 0.674
+mistranslation: 0.670
+risc-v: 0.657
+virtual: 0.656
+PID: 0.614
+hypervisor: 0.595
+boot: 0.590
+TCG: 0.574
+arm: 0.508
+register: 0.506
+socket: 0.505
+debug: 0.497
+assembly: 0.486
+KVM: 0.472
+VMM: 0.428
+--------------------
+i386: 0.996
+x86: 0.910
+virtual: 0.827
+user-level: 0.341
+TCG: 0.307
+permissions: 0.117
+debug: 0.090
+PID: 0.052
+files: 0.050
+device: 0.029
+socket: 0.026
+semantic: 0.025
+graphic: 0.022
+vnc: 0.018
+boot: 0.017
+network: 0.016
+register: 0.015
+hypervisor: 0.012
+kernel: 0.008
+risc-v: 0.008
+VMM: 0.005
+peripherals: 0.004
+performance: 0.004
+assembly: 0.003
+architecture: 0.003
+ppc: 0.002
+mistranslation: 0.001
+arm: 0.001
+KVM: 0.001
+
+VVFAT is not writable from Windows NT 3.5, 3.51 and 4.0
+
+I'm running Windows NT 3.5, 3.51 and 4.0 in QEMU 4.2.0 on Linux. I'm using a VVFAT filesystem. Command lines:
+
+$ qemu-system-i386 -L pc -cpu 486 -m 64 -vga cirrus -drive file=nt351.img,format=raw -net nic,model=pcnet -net user -soundhw sb16,pcspk -drive file=fat:rw:drived,format=raw
+
+$ qemu-system-i386 --version
+QEMU emulator version 4.2.0 (Debian 1:4.2-6)
+Copyright (c) 2003-2019 Fabrice Bellard and the QEMU Project developers
+
+Creating a new directory or file on drive D: (the VVFAT filesystem) fails on Windows NT 3.5, 3.51 and 4.0 (see screenshot). It succeeds on Windows NT 3.1.
+
+Is there a workaround, e.g. a QEMU flag or a change in the Windows NT driver settings?
+
+
+
+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" within the next 60 days (otherwise it will get
+closed as "Expired"). We will then eventually migrate the ticket auto-
+matically to the new system (but you won't be the reporter of the bug
+in the new system and thus 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/user-level-i386/1907497 b/results/classifier/118/user-level-i386/1907497
new file mode 100644
index 000000000..97d3cd35c
--- /dev/null
+++ b/results/classifier/118/user-level-i386/1907497
@@ -0,0 +1,142 @@
+user-level: 0.906
+peripherals: 0.902
+hypervisor: 0.884
+register: 0.876
+KVM: 0.860
+mistranslation: 0.849
+performance: 0.835
+device: 0.833
+architecture: 0.821
+TCG: 0.818
+permissions: 0.818
+i386: 0.816
+risc-v: 0.810
+arm: 0.804
+graphic: 0.790
+assembly: 0.790
+virtual: 0.778
+x86: 0.777
+ppc: 0.761
+vnc: 0.757
+kernel: 0.756
+boot: 0.747
+VMM: 0.744
+debug: 0.743
+socket: 0.739
+semantic: 0.731
+files: 0.730
+PID: 0.722
+network: 0.704
+--------------------
+i386: 0.999
+x86: 0.990
+debug: 0.204
+virtual: 0.183
+user-level: 0.165
+files: 0.107
+kernel: 0.065
+hypervisor: 0.057
+device: 0.046
+TCG: 0.034
+PID: 0.026
+assembly: 0.023
+semantic: 0.017
+performance: 0.015
+boot: 0.012
+register: 0.012
+architecture: 0.010
+graphic: 0.006
+permissions: 0.004
+VMM: 0.004
+KVM: 0.004
+socket: 0.004
+peripherals: 0.002
+risc-v: 0.002
+network: 0.002
+mistranslation: 0.001
+ppc: 0.001
+vnc: 0.001
+arm: 0.000
+
+[OSS-Fuzz] Issue 28435 qemu:qemu-fuzz-i386-target-generic-fuzz-intel-hda: Stack-overflow in ldl_le_dma
+
+ affects qemu
+
+=== Reproducer (build with --enable-sanitizers) ===
+
+cat << EOF | ./qemu-system-i386 -machine q35 -nodefaults \
+-device intel-hda,id=hda0 -device hda-output,bus=hda0.0 \
+-device hda-micro,bus=hda0.0 -device hda-duplex,bus=hda0.0 \
+-qtest stdio
+outl 0xcf8 0x80000804
+outw 0xcfc 0xffff
+write 0x0 0x1 0x12
+write 0x2 0x1 0x2f
+outl 0xcf8 0x80000811
+outl 0xcfc 0x5a6a4406
+write 0x6a44005a 0x1 0x11
+write 0x6a44005c 0x1 0x3f
+write 0x6a442050 0x4 0x0000446a
+write 0x6a44204a 0x1 0xf3
+write 0x6a44204c 0x1 0xff
+writeq 0x6a44005a 0x17b3f0011
+write 0x6a442050 0x4 0x0000446a
+write 0x6a44204a 0x1 0xf3
+write 0x6a44204c 0x1 0xff
+EOF
+
+=== Stack Trace ===
+==411958==ERROR: AddressSanitizer: stack-overflow on address 0x7ffcaeb8bc88 (pc 0x55c7c9dc1159 bp 0x7ffcaeb8c4d0 sp 0x7ffcaeb8bc90 T0)
+    #0 0x55c7c9dc1159 in __asan_memcpy (u-system-i386+0x2a13159)
+    #1 0x55c7cb2a457e in flatview_do_translate softmmu/physmem.c:513:12
+    #2 0x55c7cb2bdab0 in flatview_translate softmmu/physmem.c:563:15
+    #3 0x55c7cb2bdab0 in flatview_read softmmu/physmem.c:2861:10
+    #4 0x55c7cb2bdab0 in address_space_read_full softmmu/physmem.c:2875:18
+    #5 0x55c7caaec937 in dma_memory_rw_relaxed include/sysemu/dma.h:87:18
+    #6 0x55c7caaec937 in dma_memory_rw include/sysemu/dma.h:110:12
+    #7 0x55c7caaec937 in dma_memory_read include/sysemu/dma.h:116:12
+    #8 0x55c7caaec937 in ldl_le_dma include/sysemu/dma.h:179:1
+    #9 0x55c7caaec937 in ldl_le_pci_dma include/hw/pci/pci.h:816:1
+    #10 0x55c7caaec937 in intel_hda_corb_run hw/audio/intel-hda.c:338:16
+    #11 0x55c7cb2e7198 in memory_region_write_accessor softmmu/memory.c:491:5
+    #12 0x55c7cb2e6bd3 in access_with_adjusted_size softmmu/memory.c:552:18
+    #13 0x55c7cb2e646c in memory_region_dispatch_write softmmu/memory.c
+    #14 0x55c7cb2c8445 in flatview_write_continue softmmu/physmem.c:2759:23
+    #15 0x55c7cb2bdfb8 in flatview_write softmmu/physmem.c:2799:14
+    #16 0x55c7cb2bdfb8 in address_space_write softmmu/physmem.c:2891:18
+    #17 0x55c7caae2c54 in dma_memory_rw_relaxed include/sysemu/dma.h:87:18
+    #18 0x55c7caae2c54 in dma_memory_rw include/sysemu/dma.h:110:12
+    #19 0x55c7caae2c54 in dma_memory_write include/sysemu/dma.h:122:12
+    #20 0x55c7caae2c54 in stl_le_dma include/sysemu/dma.h:179:1
+    #21 0x55c7caae2c54 in stl_le_pci_dma include/hw/pci/pci.h:816:1
+    #22 0x55c7caae2c54 in intel_hda_response hw/audio/intel-hda.c:370:5
+    #23 0x55c7caaeca00 in intel_hda_corb_run hw/audio/intel-hda.c:342:9
+    #24 0x55c7cb2e7198 in memory_region_write_accessor softmmu/memory.c:491:5
+...
+
+OSS-Fuzz Report: https://bugs.chromium.org/p/oss-fuzz/issues/detail?id=28435
+
+
+
+I think this [0] commit actually fixes this bug, can someone please confirm it?
+
+[0] https://github.com/qemu/qemu/commit/1bf8b88f144bee747e386c88d45d772e066bbb36
+
+No, I can still reproduce this issue with current version from the git repo (commit 8f521741e1280f0957ac1) ... when I compile QEMU with Clang and --enable-sanitizers, the reproducer still crashes with "ERROR: AddressSanitizer: stack-overflow"
+
+Just FYI, this issue was assigned CVE-2021-3611 by Red Hat.
+
+@Thomas, could you try by compiling qemu with a commit close to the timeframe mentioned here [0]?
+
+[0] https://bugs.chromium.org/p/oss-fuzz/issues/detail?id=28435#c2
+
+@Gianluca: The problem still reproduces with the current master branch (commit 13d5f87cc3b94bfccc5), so the problem is definitely not fixed yet. So no, I certainly won't waste my time trying it on older versions.
+
+I moved this report over to QEMU's new bug tracker on gitlab.com.
+Please continue with the discussion here:
+
+https://gitlab.com/qemu-project/qemu/-/issues/542
+
+Thanks for moving it over! ... let's close this one here on Launchpad now.
+
+
diff --git a/results/classifier/118/user-level-i386/1914294 b/results/classifier/118/user-level-i386/1914294
new file mode 100644
index 000000000..eaa1eedc0
--- /dev/null
+++ b/results/classifier/118/user-level-i386/1914294
@@ -0,0 +1,115 @@
+i386: 0.928
+user-level: 0.868
+graphic: 0.808
+performance: 0.780
+x86: 0.773
+architecture: 0.769
+hypervisor: 0.755
+device: 0.718
+PID: 0.709
+mistranslation: 0.697
+files: 0.692
+VMM: 0.658
+arm: 0.648
+ppc: 0.644
+kernel: 0.643
+peripherals: 0.630
+permissions: 0.630
+register: 0.628
+semantic: 0.615
+debug: 0.605
+TCG: 0.587
+network: 0.583
+vnc: 0.570
+risc-v: 0.559
+socket: 0.537
+KVM: 0.534
+assembly: 0.529
+boot: 0.501
+virtual: 0.434
+--------------------
+i386: 0.992
+x86: 0.981
+user-level: 0.275
+virtual: 0.274
+TCG: 0.091
+hypervisor: 0.082
+debug: 0.050
+files: 0.034
+performance: 0.023
+PID: 0.015
+socket: 0.009
+semantic: 0.008
+network: 0.008
+graphic: 0.005
+device: 0.004
+risc-v: 0.003
+kernel: 0.003
+vnc: 0.002
+register: 0.002
+assembly: 0.002
+boot: 0.002
+VMM: 0.001
+architecture: 0.001
+permissions: 0.001
+peripherals: 0.001
+ppc: 0.001
+arm: 0.001
+mistranslation: 0.000
+KVM: 0.000
+
+Windows XP displays black screen when smp option is used
+
+When I use Windows XP with the -smp option, the screen goes black. The only thing I can see is a cursor. I have tried -smp 2, -smp cores=4, and -smp cores=2.
+
+My info:
+
+Host:
+M1 Mac
+Mac OS 11.1
+QEMU 5.2 at cf7ca7d5b9faca13f1f8e3ea92cfb2f741eb0c0e.
+
+Guest:
+32-bit Windows XP SP3 build 2600.
+
+Command line to reproduce this issue: 
+qemu-system-i386 -m 700 -hda <Windows XP HD image file> -smp 2
+
+Last commit tested with this problem: 1214d55d1c41fbab3a9973a05085b8760647e411
+
+I restarted QEMU without the '-smp 2' option and Windows XP started working again. The only problem is the host CPU usage will stay at 100% even with the guest CPU load being close to 0%. The only way to fix this problem that I know currently is to reinstall Windows XP. 
+
+To fix this problem open Windows XP's System Restore and restore from a point before using the smp option.
+
+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/user-level-i386/788701 b/results/classifier/118/user-level-i386/788701
new file mode 100644
index 000000000..346214c3d
--- /dev/null
+++ b/results/classifier/118/user-level-i386/788701
@@ -0,0 +1,76 @@
+i386: 0.949
+x86: 0.926
+graphic: 0.903
+user-level: 0.857
+architecture: 0.797
+device: 0.795
+network: 0.688
+performance: 0.686
+register: 0.618
+semantic: 0.600
+PID: 0.584
+socket: 0.569
+boot: 0.534
+vnc: 0.504
+files: 0.489
+permissions: 0.487
+ppc: 0.461
+peripherals: 0.452
+debug: 0.431
+mistranslation: 0.410
+arm: 0.381
+risc-v: 0.356
+TCG: 0.319
+kernel: 0.309
+VMM: 0.304
+KVM: 0.136
+virtual: 0.123
+hypervisor: 0.094
+assembly: 0.080
+--------------------
+user-level: 0.941
+x86: 0.852
+hypervisor: 0.652
+virtual: 0.456
+i386: 0.053
+debug: 0.053
+TCG: 0.039
+register: 0.028
+files: 0.025
+network: 0.007
+performance: 0.006
+kernel: 0.005
+PID: 0.003
+device: 0.002
+semantic: 0.002
+assembly: 0.002
+VMM: 0.001
+socket: 0.001
+architecture: 0.001
+risc-v: 0.001
+peripherals: 0.001
+ppc: 0.001
+boot: 0.001
+KVM: 0.000
+permissions: 0.000
+graphic: 0.000
+vnc: 0.000
+mistranslation: 0.000
+arm: 0.000
+
+qemu-user fails to run rpcgen (i386, x86_64)
+
+Confirmed on qemu current development tree (git commit aa29141). While trying to run eglibc's rpcgen from native system by qemu-user, I get an error:
+
+qemu-x86_64 /usr/bin/rpcgen -c /dev/null 
+fork: Invalid argument
+
+I am running a Debian Wheezy system and rpcgen comes from libc-dev-bin. Just in case I am attaching my rpcgen binaries from i386 and x86_64 systems.
+
+Very similar problem was mentioned on the QEMU forum on February 2007, so I guess it might be a known issue. Nevertheless, I was unable to find any information about bug reports, fixes nor workarounds for it so I'm reporting it here.
+
+
+
+This should be fixed in QEMU 1.6.
+
+