11 files changed, 485 insertions, 0 deletions
diff --git a/results/classifier/108/other/61 b/results/classifier/108/other/61
new file mode 100644
index 000000000..415da51af
--- /dev/null
+++ b/results/classifier/108/other/61
@@ -0,0 +1,16 @@
+device: 0.916
+performance: 0.791
+network: 0.641
+graphic: 0.549
+debug: 0.532
+semantic: 0.276
+vnc: 0.194
+boot: 0.176
+other: 0.129
+socket: 0.095
+files: 0.043
+permissions: 0.032
+PID: 0.023
+KVM: 0.007
+
+qemu-system-arm segfaults while servicing SYS_HEAPINFO
diff --git a/results/classifier/108/other/612 b/results/classifier/108/other/612
new file mode 100644
index 000000000..2ab7578b2
--- /dev/null
+++ b/results/classifier/108/other/612
@@ -0,0 +1,16 @@
+graphic: 0.743
+device: 0.553
+performance: 0.510
+network: 0.278
+permissions: 0.258
+files: 0.250
+debug: 0.177
+semantic: 0.077
+other: 0.053
+PID: 0.053
+socket: 0.034
+vnc: 0.032
+boot: 0.026
+KVM: 0.008
+
+Much larger traces with qemu-6.1 than qemu-6.0
diff --git a/results/classifier/108/other/612297 b/results/classifier/108/other/612297
new file mode 100644
index 000000000..ef3d701fc
--- /dev/null
+++ b/results/classifier/108/other/612297
@@ -0,0 +1,33 @@
+KVM: 0.879
+device: 0.766
+graphic: 0.763
+network: 0.712
+semantic: 0.707
+other: 0.706
+boot: 0.684
+performance: 0.584
+socket: 0.494
+permissions: 0.397
+PID: 0.362
+vnc: 0.308
+files: 0.258
+debug: 0.249
+
+qemu-kvm fails to detect mouse while Windows 95 setup
+
+CPU: AMD Phenom II X4 945
+KVM-Version: qemu-kvm-0.12.4+dfsg (Debian package)
+Kernel: linux-2.6.26.8-rt16
+arch: x86_64
+Guest: Windows 95 B
+
+I'm trying to install Windows 95 B on qemu-kvm with this options:
+
+kvm /var/mmn/vm/Win95/Win95.img -name "Windows 95" -M pc-0.12 -m 512M -rtc base=localtime -k de -soundhw sb16 -vga cirrus -net user,hostname=w95vm -net nic,model=ne2k_pci -boot a -fda /var/mmn/vm/floppy/win95B_Drive-D-boot.img -cdrom /var/mmn/vm/CD/win95-setup.iso -no-acpi -no-kvm -usb
+
+I've also tried some other option, but always the same: no ps/2 mouse detection. And usb mouse is not supported by Windows 95 B while setup process. This is only possible later by installing the extension usbsupp.exe after the system setup.
+
+Seems like you were using the QEMU from your Linux distribution. If you want to have support for that version, you should use the bug tracker from your distro instead. Otherwise, can you please try again with the latest version from http://wiki.qemu-project.org/Download to see whether the bug is already fixed there? Thanks!
+
+[Expired for QEMU because there has been no activity for 60 days.]
+
diff --git a/results/classifier/108/other/612452 b/results/classifier/108/other/612452
new file mode 100644
index 000000000..5b3bcb919
--- /dev/null
+++ b/results/classifier/108/other/612452
@@ -0,0 +1,142 @@
+KVM: 0.861
+permissions: 0.744
+vnc: 0.724
+other: 0.695
+device: 0.690
+debug: 0.667
+semantic: 0.650
+PID: 0.648
+boot: 0.645
+performance: 0.624
+files: 0.622
+socket: 0.600
+graphic: 0.586
+network: 0.445
+
+Problems with the number of serial ports for more than two
+
+qemu --version
+QEMU emulator version 0.13.50, Copyright (c) 2003-2008 Fabrice Bellard
+
+Command line:
+
+qemu -serial null -serial null -serial file:test1 hd.img
+
+Error:
+
+isa irq 4 already assigned
+
+echo $?
+1
+
+This bug seems to be solved and closed here: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=574051
+
+Is it solved in 0.12.5 or 0.13.0rc1 yet? 
+
+
+> This bug seems to be solved and closed here: http://bugs.debian.org/cgi-
+> bin/bugreport.cgi?bug=574051
+>
+> Is it solved in 0.12.5 or 0.13.0rc1 yet?
+>
+> ** Bug watch added: Debian Bug tracker #574051
+>    http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=574051
+>   
+#cd qemu-snapshot
+#date
+Fri Sep 17 09:29:01 MSD 2010
+#cat .git/config
+...
+[remote "origin"]
+    url = git://git.savannah.nongnu.org/qemu.git
+    fetch = +refs/heads/*:refs/remotes/origin/*
+[branch "master"]
+    remote = origin
+    merge = refs/heads/master
+
+#git pull
+...
+#./configure --disable-xen --audio-drv-list=alsa,sdl
+#make && make install
+...
+install -m 755 qemu "/usr/local/bin"
+...
+#ls -l /usr/local/bin/qemu
+#-rwxr-xr-x 1 root root 1960900 2010-09-17 09:45 /usr/local/bin/qemu
+#/usr/local/bin/qemu --version
+QEMU emulator version 0.13.50, Copyright (c) 2003-2008 Fabrice Bellard
+#cd /path/to/hd/image
+#/usr/local/bin/qemu -serial file:file1 -serial file:file2 -serial none 
+-serial none hd.img
+
+In VM
+
+#echo test1 >/dev/ttyS0
+#echo test2 >/dev/ttyS1
+#echo test3 >/dev/ttyS2
+... error...
+#echo test4 >/dev/ttyS3
+... error...
+
+It is right
+
+#halt
+
+
+In host
+
+#ls -l file*
+-rw-r--r-- 1 root root 7 2010-09-17 10:13 file1
+-rw-r--r-- 1 root root  7 2010-09-17 10:12 file2
+
+
+Excellent. Try next.
+
+#rm -f file*
+#/usr/local/bin/qemu -serial file:file1 -serial file:file2 -serial 
+file:file3 -serial none hd.img
+isa irq 4 already assigned
+
+Misfire. Try next.
+
+#/usr/local/bin/qemu -serial none -serial none -serial file:file3 
+-serial file:file4 hd.img
+
+In VM
+
+#echo test1 >/dev/ttyS0
+#echo test2 >/dev/ttyS1
+#echo test3 >/dev/ttyS2
+... error...
+#echo test4 >/dev/ttyS3
+... error...
+
+OOPS! Surprise.
+
+#halt
+
+
+In host
+
+#ls -l file*
+-rw-r--r-- 1 root root 7 2010-09-17 10:40 file3
+-rw-r--r-- 1 root root  7 2010-09-17 10:40 file4
+
+In this case expected.
+
+
+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/108/other/613 b/results/classifier/108/other/613
new file mode 100644
index 000000000..626766faa
--- /dev/null
+++ b/results/classifier/108/other/613
@@ -0,0 +1,16 @@
+device: 0.892
+performance: 0.766
+permissions: 0.638
+graphic: 0.550
+boot: 0.406
+network: 0.197
+semantic: 0.191
+debug: 0.157
+other: 0.127
+vnc: 0.069
+socket: 0.044
+files: 0.023
+PID: 0.015
+KVM: 0.001
+
+ARM cortex-m55 LOB instructions make QEMU crash
diff --git a/results/classifier/108/other/613529 b/results/classifier/108/other/613529
new file mode 100644
index 000000000..5757e2b1a
--- /dev/null
+++ b/results/classifier/108/other/613529
@@ -0,0 +1,41 @@
+device: 0.786
+boot: 0.712
+performance: 0.666
+semantic: 0.661
+graphic: 0.647
+files: 0.646
+PID: 0.640
+other: 0.600
+socket: 0.585
+permissions: 0.562
+vnc: 0.557
+network: 0.460
+KVM: 0.307
+debug: 0.141
+
+qemu does not accept regular disk geometry
+
+Hi, 
+
+I am currently hunting a strange bug in qemu/kvm:
+
+I am using an lvm logical volume as a virtual hard disk for a virtual machine. 
+
+I use fdisk or parted to create a partition table and partitions, kpartx to generate the device entries for the partitions, then install linux on ext3/ext4 with grub or msdos filesystem with syslinux. 
+
+But then, in most cases even the boot process fails or behaves strangely, sometimes even mounting the file system in the virtual machine fails. It seems as if there is a problem with the virtual disk geometry. The problem does not seem to occur if I reboot the host system after creating the partition table on the logical volume. I guess the linux kernel needs to learn the disk geometry by reboot. A blkdev --rereadpt does not work on lvm volumes. 
+
+The first approach to test/fix the problem would be to pass the disk geometry to qemu/lvm with the -drive option. Unfortunately, qemu/kvm does not accept the default geometry with 255 heads and 63 sectors. Seems to limit the number of heads to 16, thus limiting the disk size.
+
+Seems to be the same issue as in 
+http://qemu-forum.ipi.fi/viewtopic.php?f=4&t=5218
+
+has been (orally) confirmed by other users. 
+
+It is effectively impossible to reliably install a system on an lvm logical device and run it under kvm/qemu
+
+
+Which version of QEMU have you been using for your tests? Can you still reproduce this problem with the latest version of QEMU?
+
+[Expired for QEMU because there has been no activity for 60 days.]
+
diff --git a/results/classifier/108/other/614 b/results/classifier/108/other/614
new file mode 100644
index 000000000..ba21b481f
--- /dev/null
+++ b/results/classifier/108/other/614
@@ -0,0 +1,16 @@
+device: 0.677
+permissions: 0.609
+vnc: 0.592
+socket: 0.570
+PID: 0.543
+network: 0.504
+debug: 0.449
+files: 0.447
+boot: 0.370
+performance: 0.364
+graphic: 0.311
+semantic: 0.223
+KVM: 0.202
+other: 0.088
+
+Newly introduced dependency on GCC 7.5.0 should allow any version of GCC 7
diff --git a/results/classifier/108/other/615 b/results/classifier/108/other/615
new file mode 100644
index 000000000..338fa8bce
--- /dev/null
+++ b/results/classifier/108/other/615
@@ -0,0 +1,25 @@
+device: 0.885
+graphic: 0.665
+semantic: 0.434
+performance: 0.422
+other: 0.409
+PID: 0.373
+network: 0.349
+vnc: 0.347
+debug: 0.320
+boot: 0.209
+socket: 0.152
+permissions: 0.085
+files: 0.070
+KVM: 0.001
+
+Not sure if this is a qemu issue but SD card is not correctly read. blk_update_request: I/O error on Manjaro libvirt OS.
+Description of problem:
+
+Steps to reproduce:
+1. Run vagrant command line 
+2. Start console in virt-manager
+3. Add USB SD card reader device with SD card.
+4. Go back to console
+Additional information:
+I've bought a new SD card reader and SD card, tried it on other ports and the problem persists.
diff --git a/results/classifier/108/other/616769 b/results/classifier/108/other/616769
new file mode 100644
index 000000000..c5a47f43d
--- /dev/null
+++ b/results/classifier/108/other/616769
@@ -0,0 +1,54 @@
+graphic: 0.711
+performance: 0.691
+semantic: 0.660
+device: 0.634
+debug: 0.567
+PID: 0.533
+permissions: 0.524
+network: 0.524
+other: 0.502
+boot: 0.456
+socket: 0.453
+vnc: 0.424
+KVM: 0.299
+files: 0.287
+
+interrupt problem x86_64
+
+Hello.
+I'm studing the x86_64 arch to port colinux to this new architecture.
+
+For who does not know, colinux is a port of linux that runs on windows NATIVELY. Colinux is
+1) a small windows driver
+2) a kernel patched
+3) some windows user-space application that talk with linux kernel (network, console, ...)
+
+I have written the more internal part of colinux, that is the code that switch between windows and linux.
+This is done saving and restore the machine state :
+1) CR3
+2) IDT
+3) registers
+
+The problem I see is that after the switch I see the reboot of my virtual machine.
+I would say that the new IDT and/or CR3 is not flushed.
+My code is written in asm/C so I can follow the code step by step.
+I can say exactly the instruction that is broken.
+
+All my code runs nicely on bochs.
+I don't have an x86_64 real PC.
+
+If someone wants to repair this bug .... I'm here.
+
+Paolo Minazzi
+
+Which version of QEMU did you use when you encountered this problem? Can you still reproduce this issue with the latest version of QEMU?
+
+Hello Thomas,
+it happens some years ago and now I'm not able to reproduce it.
+I'm sorry,
+thanks again,
+Paolo
+
+
+OK, thanks a lot for your response ... so let's close this bug now.
+
diff --git a/results/classifier/108/other/618 b/results/classifier/108/other/618
new file mode 100644
index 000000000..385e14733
--- /dev/null
+++ b/results/classifier/108/other/618
@@ -0,0 +1,110 @@
+graphic: 0.894
+performance: 0.888
+other: 0.888
+device: 0.888
+debug: 0.888
+vnc: 0.886
+semantic: 0.874
+KVM: 0.870
+files: 0.868
+PID: 0.865
+permissions: 0.861
+socket: 0.855
+boot: 0.824
+network: 0.777
+
+overflow condition code determined incorrectly after subtraction on s390x
+Description of problem:
+Paul Eggert found this bug, just by taking a look at the file `qemu/target/s390x/tcg/cc_helper.c`.
+
+The following program
+[foo.c](/uploads/c1f425684fd661c4437950d7d8ddf31d/foo.c)
+```
+#include <stdio.h>
+
+int overflow_32 (int x, int y)
+{
+  int sum;
+  return __builtin_sub_overflow (x, y, &sum);
+}
+
+int overflow_64 (long long x, long long y)
+{
+  long sum;
+  return __builtin_sub_overflow (x, y, &sum);
+}
+
+int a1 = 0;
+int b1 = -2147483648;
+long long a2 = 0L;
+long long b2 = -9223372036854775808L;
+
+int main ()
+{
+  {
+    int a = a1;
+    int b = b1;
+    printf ("a = 0x%x, b = 0x%x\n", a, b);
+    printf ("no_overflow = %d\n", ! overflow_32 (a, b));
+  }
+  {
+    long long a = a2;
+    long long b = b2;
+    printf ("a = 0x%llx, b = 0x%llx\n", a, b);
+    printf ("no_overflow = %d\n", ! overflow_64 (a, b));
+  }
+}
+```
+should print
+```
+a = 0x0, b = 0x80000000
+no_overflow = 0
+a = 0x0, b = 0x8000000000000000
+no_overflow = 0
+```
+However, when compiled as an s390x program and executed through qemu 6.1.0 (Linux user-mode), it prints 'no_overflow = 1' twice.
+```
+$ s390x-linux-gnu-gcc-10 --version
+s390x-linux-gnu-gcc-10 (Ubuntu 10.3.0-1ubuntu1~20.04) 10.3.0
+```
+
+```
+$ s390x-linux-gnu-gcc-10 -static foo.c
+$ ~/inst-qemu/6.1.0/bin/qemu-s390x a.out
+a = 0x0, b = 0x80000000
+no_overflow = 1
+a = 0x0, b = 0x8000000000000000
+no_overflow = 1
+```
+
+```
+$ s390x-linux-gnu-gcc-10 -O2 -static foo.c
+$ ~/inst-qemu/6.1.0/bin/qemu-s390x a.out
+a = 0x0, b = 0x80000000
+no_overflow = 1
+a = 0x0, b = 0x8000000000000000
+no_overflow = 1
+```
+
+The code generated by 's390x-linux-gnu-gcc-10 -O2' makes use of the 'o' (overflow / ones) condition code:
+```
+overflow_64:
+        lgr     %r1,%r2    ;; copy a into %r1
+        lghi    %r2,0
+        sgr     %r1,%r3    ;; subtract b from a
+        bnor    %r14       ;; if no overflow, return %r2 = 0
+        lghi    %r2,1
+        br      %r14       ;; otherwise, return %r2 = 1
+```
+
+The condition code and the overflow bit are defined in the z/Architecture Principles of Operation (POP) http://publibfi.boulder.ibm.com/epubs/pdf/dz9zr011.pdf page 7-5 / 7-6 / 7-388 : "In mathematical terms, signed addition and subtraction produce a fixed-point overflow when the result is outside the range of representation for signed binary integers."
+
+I conclude that the bug is in QEMU: QEMU does not set the overflow condition code correctly.
+Steps to reproduce:
+[foo.static.s390x](/uploads/e4b79b019db590f3a4b13cac41e57ba6/foo.static.s390x)
+(the result of "s390x-linux-gnu-gcc-10 -static -O2 foo.c -o foo.static.s390x")
+
+1. `qemu-s390x foo.static.s390x`
+Additional information:
+The attached patch fixes it.
+[0002-s390x-Fix-determination-of-overflow-condition-code-a.patch](/uploads/8d414f84fe0ed36bf07bd28f5e7836ab/0002-s390x-Fix-determination-of-overflow-condition-code-a.patch)
diff --git a/results/classifier/108/other/619 b/results/classifier/108/other/619
new file mode 100644
index 000000000..80493d83d
--- /dev/null
+++ b/results/classifier/108/other/619
@@ -0,0 +1,16 @@
+performance: 0.701
+device: 0.342
+graphic: 0.308
+semantic: 0.223
+files: 0.198
+KVM: 0.094
+debug: 0.085
+boot: 0.084
+other: 0.063
+vnc: 0.060
+network: 0.056
+PID: 0.037
+permissions: 0.023
+socket: 0.019
+
+Move TCGCPUOps::fake_user_exception() to linux-user/i386/cpu_loop.c