16 files changed, 784 insertions, 0 deletions
diff --git a/results/classifier/108/other/117 b/results/classifier/108/other/117
new file mode 100644
index 000000000..7c6facdcd
--- /dev/null
+++ b/results/classifier/108/other/117
@@ -0,0 +1,16 @@
+device: 0.808
+network: 0.765
+files: 0.652
+vnc: 0.551
+boot: 0.512
+debug: 0.309
+graphic: 0.276
+PID: 0.253
+performance: 0.246
+semantic: 0.148
+permissions: 0.147
+other: 0.077
+socket: 0.077
+KVM: 0.046
+
+nested 9p filesystem with security_model=mapped-xattr
diff --git a/results/classifier/108/other/1170 b/results/classifier/108/other/1170
new file mode 100644
index 000000000..555d23e23
--- /dev/null
+++ b/results/classifier/108/other/1170
@@ -0,0 +1,71 @@
+other: 0.827
+debug: 0.798
+permissions: 0.784
+KVM: 0.773
+graphic: 0.754
+device: 0.752
+semantic: 0.746
+vnc: 0.733
+network: 0.730
+PID: 0.716
+performance: 0.707
+boot: 0.706
+socket: 0.702
+files: 0.691
+
+Unable to compile in Ubuntu 22.04, at compiling linux-user_arm_nwfpe_double_cpdo.c.o
+Description of problem:
+Compiling of QEMU 7.1.0-rc3 stops here for me:
+```
+[7172/9855] Compiling C object libqemu-armeb-linux-user.fa.p/linux-user_arm_nwfpe_double_cpdo.c.o
+FAILED: libqemu-armeb-linux-user.fa.p/linux-user_arm_nwfpe_double_cpdo.c.o 
+cc -m64 -mcx16 -Ilibqemu-armeb-linux-user.fa.p -I. -I.. -Itarget/arm -I../target/arm -I../common-user/host/x86_64 -I../linux-user/include/host/x86_64 -I../linux-user/include -Ilinux-user -I../linux-user -Ilinux-user/arm -I../linux-user/arm -Iqapi -Itrace -Iui -Iui/shader -I/usr/include/capstone -I/usr/include/glib-2.0 -I/usr/lib/x86_64-linux-gnu/glib-2.0/include -fdiagnostics-color=auto -Wall -Winvalid-pch -std=gnu11 -O2 -g -isystem /home/andrea/Downloads/qemu-7.1.0-rc3/linux-headers -isystem linux-headers -iquote . -iquote /home/andrea/Downloads/qemu-7.1.0-rc3 -iquote /home/andrea/Downloads/qemu-7.1.0-rc3/include -iquote /home/andrea/Downloads/qemu-7.1.0-rc3/tcg/i386 -pthread -U_FORTIFY_SOURCE -D_FORTIFY_SOURCE=2 -D_GNU_SOURCE -D_FILE_OFFSET_BITS=64 -D_LARGEFILE_SOURCE -Wstrict-prototypes -Wredundant-decls -Wundef -Wwrite-strings -Wmissing-prototypes -fno-strict-aliasing -fno-common -fwrapv -Wold-style-declaration -Wold-style-definition -Wtype-limits -Wformat-security -Wformat-y2k -Winit-self -Wignored-qualifiers -Wempty-body -Wnested-externs -Wendif-labels -Wexpansion-to-defined -Wimplicit-fallthrough=2 -Wno-missing-include-dirs -Wno-shift-negative-value -Wno-psabi -fstack-protector-strong -fPIE -isystem../linux-headers -isystemlinux-headers -DNEED_CPU_H '-DCONFIG_TARGET="armeb-linux-user-config-target.h"' '-DCONFIG_DEVICES="armeb-linux-user-config-devices.h"' -MD -MQ libqemu-armeb-linux-user.fa.p/linux-user_arm_nwfpe_double_cpdo.c.o -MF libqemu-armeb-linux-user.fa.p/linux-user_arm_nwfpe_double_cpdo.c.o.d -o libqemu-armeb-linux-user.fa.p/linux-user_arm_nwfpe_double_cpdo.c.o -c ../linux-user/arm/nwfpe/double_cpdo.c
+during RTL pass: expand
+../linux-user/arm/nwfpe/double_cpdo.c: In function ‘DoubleCPDO’:
+../linux-user/arm/nwfpe/double_cpdo.c:232:1: internal compiler error: Segmentation fault
+  232 | }
+      | ^
+0x7fe5b824251f ???
+	./signal/../sysdeps/unix/sysv/linux/x86_64/libc_sigaction.c:0
+0x7fe5b8229d8f __libc_start_call_main
+	../sysdeps/nptl/libc_start_call_main.h:58
+0x7fe5b8229e3f __libc_start_main_impl
+	../csu/libc-start.c:392
+Please submit a full bug report,
+with preprocessed source if appropriate.
+Please include the complete backtrace with any bug report.
+See <file:///usr/share/doc/gcc-11/README.Bugs> for instructions.
+ninja: build stopped: subcommand failed.
+make[1]: *** [Makefile:162: run-ninja] Error 1
+make[1]: Leaving directory '/home/andrea/Downloads/qemu-7.1.0-rc3/build'
+make: *** [GNUmakefile:11: all] Error 2
+```
+
+Configure Output:
+[Configure_Output.txt](/uploads/40055846573b79cc2817d5cb338e18c1/Configure_Output.txt)
+
+Compiles on 7.0.0.
+Steps to reproduce:
+1. Run 'sudo apt purge qemu-kvm qemu-utils libvirt-daemon-system libvirt-clients bridge-utils virt-manager ovmf'
+2. Run 'sudo apt-get install git libglib2.0-dev libfdt-dev libpixman-1-dev zlib1g-dev ninja-build' ([Wiki](https://wiki.qemu.org/Hosts/Linux))
+3. Additional Packages:
+```
+sudo apt-get install git-email
+sudo apt-get install libaio-dev libbluetooth-dev libcapstone-dev libbrlapi-dev libbz2-dev
+sudo apt-get install libcap-ng-dev libcurl4-gnutls-dev libgtk-3-dev
+sudo apt-get install libibverbs-dev libjpeg8-dev libncurses5-dev libnuma-dev
+sudo apt-get install librbd-dev librdmacm-dev
+sudo apt-get install libsasl2-dev libsdl2-dev libseccomp-dev libsnappy-dev libssh-dev
+sudo apt-get install libvde-dev libvdeplug-dev libvte-2.91-dev libxen-dev liblzo2-dev
+sudo apt-get install valgrind xfslibs-dev 
+
+sudo apt-get install libnfs-dev libiscsi-dev
+```
+4. Build instructions for QEMU:
+```
+wget https://download.qemu.org/qemu-7.1.0-rc3.tar.xz
+tar xvJf qemu-7.1.0-rc3.tar.xz
+cd qemu-7.1.0-rc3
+./configure
+make
+```
diff --git a/results/classifier/108/other/1171 b/results/classifier/108/other/1171
new file mode 100644
index 000000000..834dc1649
--- /dev/null
+++ b/results/classifier/108/other/1171
@@ -0,0 +1,18 @@
+device: 0.893
+network: 0.707
+graphic: 0.528
+boot: 0.357
+other: 0.306
+semantic: 0.293
+PID: 0.237
+debug: 0.192
+socket: 0.150
+vnc: 0.086
+files: 0.066
+performance: 0.063
+permissions: 0.051
+KVM: 0.003
+
+tulip: DMA reentrancy issue leads to stack overflow (CVE-2022-2962)
+Description of problem:
+A DMA reentrancy issue was found in the tulip emulation. When tulip reads or writes to  rx/tx descriptor ( tulip_desc_read/write ) or copies  rx/tx frame(tulip_copy_rx_bytes / tulip_copy_tx_buffers), it doesn't check whether the destination address is its own MMIO address. A malicious guest could use this flaw to crash the QEMU process on the host, resulting in a denial of service condition or, potentially, executing arbitrary code within the context of the QEMU process on the host.
diff --git a/results/classifier/108/other/1172 b/results/classifier/108/other/1172
new file mode 100644
index 000000000..88bac3c52
--- /dev/null
+++ b/results/classifier/108/other/1172
@@ -0,0 +1,74 @@
+files: 0.777
+device: 0.579
+socket: 0.569
+PID: 0.497
+semantic: 0.495
+vnc: 0.441
+graphic: 0.435
+network: 0.417
+other: 0.363
+performance: 0.351
+permissions: 0.334
+debug: 0.303
+boot: 0.269
+KVM: 0.138
+
+Make pixman an optional dependency
+Additional information:
+Only these files use pixman functions (excluding tests, of course):
+```
+meson.build
+contrib/vhost-user-gpu/vhost-user-gpu.c
+contrib/vhost-user-gpu/meson.build
+chardev/meson.build
+include/ui/spice-display.h
+include/ui/sdl2.h
+include/ui/gtk.h
+include/ui/qemu-pixman.h
+include/ui/console.h
+include/hw/display/xlnx_dp.h
+include/hw/virtio/virtio-gpu.h
+include/hw/virtio/virtio-gpu-pixman.h
+hw/display/vga.c
+hw/display/ramfb.c
+hw/display/vhost-user-gpu.c
+hw/display/virtio-gpu-gl.c
+hw/display/virtio-gpu-udmabuf.c
+hw/display/xenfb.c
+hw/display/ati_2d.c
+hw/display/meson.build
+hw/display/vmware_vga.c
+hw/display/qxl-render.c
+hw/display/xlnx_dp.c
+hw/display/bochs-display.c
+hw/display/sm501.c
+hw/display/virtio-gpu.c
+hw/vfio/display.c
+hw/s390x/meson.build
+ui/cocoa.m
+ui/console-gl.c
+ui/vnc.c
+ui/qemu-pixman.c
+ui/gtk.c
+ui/console.c
+ui/trace-events
+ui/meson.build
+ui/dbus-listener.c
+ui/vnc-enc-tight.c
+ui/vnc.h
+ui/spice-display.c
+ui/dbus-display1.xml
+ui/sdl2-2d.c
+```
+
+This code in `meson.build` always require **pixman** for building system emulators:
+```meson
+pixman = not_found
+if have_system or have_tools
+  pixman = dependency('pixman-1', required: have_system, version:'>=0.21.8',
+                      method: 'pkg-config', kwargs: static_kwargs)
+endif
+```
+https://gitlab.com/qemu-project/qemu/-/blob/master/meson.build#L520
+
+Most of the code could work without it.
diff --git a/results/classifier/108/other/1172613 b/results/classifier/108/other/1172613
new file mode 100644
index 000000000..d50afba2c
--- /dev/null
+++ b/results/classifier/108/other/1172613
@@ -0,0 +1,85 @@
+graphic: 0.867
+performance: 0.830
+other: 0.824
+PID: 0.806
+permissions: 0.806
+KVM: 0.804
+device: 0.795
+semantic: 0.790
+boot: 0.771
+files: 0.770
+vnc: 0.759
+network: 0.747
+debug: 0.735
+socket: 0.701
+
+[qemu 1.4.1] inconsistent behavior on different architecture
+
+Running with qemu 1.4.1 and eglibc 2.17 on Debian Linux 7.0 for amd64
+
+---------------- armhf ----------------
+$ arm-linux-gnueabihf-gcc hello.c
+$ qemu-arm ./a.out
+/lib/ld-linux-armhf.so.3: No such file or directory
+
+$ qemu-arm arm-linux-gnueabihf/lib/ld-2.17.so ./a.out
+./a.out: error while loading shared libraries: libc.so.6: cannot open shared object file: No such file or directory
+
+$ qemu-arm arm-linux-gnueabihf/lib/ld-2.17.so --library-path  arm-linux-gnueabihf/lib ./a.out
+Hello, world !
+
+---------------- powerpc64 ----------------
+$ powerpc64-linux-gcc hello.c
+
+$ qemu-ppc64 ./a.out
+/lib64/ld64.so.1: No such file or directory
+
+[BAD BEHAVIOR !!!]
+$ qemu-ppc64 powerpc64-linux/lib64/ld-2.17.so ./a.out
+Invalid data memory access: 0x00000041988fd008
+NIP 000000400001cb2c   LR 000000400001cc30 CTR 0000000000000000 XER 0000000000000000
+MSR 8000000002006000 HID0 0000000060000000  HF 8000000002006000 idx 0
+TB 00000000 00000000
+GPR00 0000000000000000 000000400083a220 0000004000041230 00000043309bd010
+GPR04 0000004000026f12 000000000000000b 000000000000002e 000000000000002e
+GPR08 0000000000000030 000000008803fffc 00000041988fcff4 0000000000000037
+GPR12 0000000000000000 0000000000000000 0000000000000000 0000000000000000
+GPR16 0000000000000000 000000400003a4d8 000000400083a6d0 000000400083a6d8
+GPR20 000000400003a898 000000000000000a 0000000000000000 00000043309bd010
+GPR24 0000004000037b60 00000000cfe8ced7 000000400003a430 0000000010000261
+GPR28 00000001980bfff4 0000000000000000 000000004401ffff 000000002200ffff
+CR 22242224  [ E  E  E  G  E  E  E  G  ]             RES ffffffffffffffff
+FPR00 0000000000000000 0000000000000000 0000000000000000 0000000000000000
+FPR04 0000000000000000 0000000000000000 0000000000000000 0000000000000000
+FPR08 0000000000000000 0000000000000000 0000000000000000 0000000000000000
+FPR12 0000000000000000 0000000000000000 0000000000000000 0000000000000000
+FPR16 0000000000000000 0000000000000000 0000000000000000 0000000000000000
+FPR20 0000000000000000 0000000000000000 0000000000000000 0000000000000000
+FPR24 0000000000000000 0000000000000000 0000000000000000 0000000000000000
+FPR28 0000000000000000 0000000000000000 0000000000000000 0000000000000000
+FPSCR 0000000000000000
+qemu: uncaught target signal 11 (Segmentation fault) - core dumped
+Segmentation fault
+
+$ qemu-ppc64 powerpc64-linux/lib64/ld-2.17.so --library-path powerpc64-linux/lib64 ./a.out
+Hello, world !
+
+---------------- sparc64 ----------------
+$ sparc64-linux-gcc hello.c
+
+$ qemu-sparc64 ./a.out
+/lib64/ld-linux.so.2: No such file or directory
+
+[BAD BEHAVIOR !!!]
+$ qemu-sparc64 sparc64-linux/lib64/ld-2.17.so ./a.out
+Segmentation fault
+
+$ qemu-sparc64 sparc64-linux/lib64/ld-2.17.so --library-path sparc64-linux/lib64 ./a.out
+Hello, world !
+
+This is going to be the same "glibc crashes if it sees a wrong-endianness /etc/ld.so.cache" situation also seen in lp:1701798. Personally I think it's a glibc bug, not really a QEMU bug.
+
+
+In particular, the only crashes here are the ones where --library-path isn't specified, so it isn't even a case of "QEMU should somehow support whiteouts in --library-path so you can tell it to ignore the host ld.so.cache". So I'm going to close this bug report (with 'invalid' as the closest sensible resolution).
+
+
diff --git a/results/classifier/108/other/1173 b/results/classifier/108/other/1173
new file mode 100644
index 000000000..7f4331928
--- /dev/null
+++ b/results/classifier/108/other/1173
@@ -0,0 +1,16 @@
+other: 0.855
+device: 0.683
+semantic: 0.590
+graphic: 0.572
+network: 0.563
+performance: 0.462
+files: 0.317
+debug: 0.284
+vnc: 0.231
+boot: 0.191
+permissions: 0.181
+socket: 0.137
+KVM: 0.136
+PID: 0.069
+
+is that `fsgnjn.s` will affect other bits except sign bit.
diff --git a/results/classifier/108/other/1174 b/results/classifier/108/other/1174
new file mode 100644
index 000000000..86b28cc19
--- /dev/null
+++ b/results/classifier/108/other/1174
@@ -0,0 +1,28 @@
+network: 0.855
+device: 0.851
+graphic: 0.805
+performance: 0.771
+PID: 0.594
+other: 0.586
+files: 0.578
+semantic: 0.564
+vnc: 0.518
+socket: 0.494
+permissions: 0.438
+boot: 0.306
+debug: 0.291
+KVM: 0.265
+
+aspeed: Fix first byte in I2C old register mode slave receive
+Description of problem:
+The first byte of data received through the Aspeed I2C slave controller through the old-register mode (specifically byte-buffered, not pool buffered or DMA buffered) is incorrect. It should be the 8-bit I2C slave address for the transfer, which will be the 7-bit I2C slave address of the I2C controller shifted left 1, and 1 or 0 for the lowest bit (is-slave-to-master-transfer, or is-master-to-slave-transfer).
+Steps to reproduce:
+You could use the simulated I2C slave EEPROM https://docs.kernel.org/i2c/slave-eeprom-backend.html, but you need another I2C model to send data to it.
+
+Alternatively, you can take this downstream patch and run the qtest in it. It has a test case for slave-mode rx in old-register mode:
+
+https://github.com/facebook/openbmc/blob/helium/common/recipes-devtools/qemu/qemu/0008-hw-misc-Add-byte-by-byte-i2c-network-device.patch
+Additional information:
+I already created the fix, it's pretty simple, I submitted it to the mailing list and Klaus (the author of that section of the Aspeed I2C controller) reviewed it. https://lore.kernel.org/qemu-devel/20220820225712.713209-1-peter@pjd.dev/#t
+
+This is relatively critical fix, but since slave-mode I2C is not widely used at this point, it's probably fine to ship with this bug. My team uses the master branch for everything anyways.
diff --git a/results/classifier/108/other/1175 b/results/classifier/108/other/1175
new file mode 100644
index 000000000..8ed0bd355
--- /dev/null
+++ b/results/classifier/108/other/1175
@@ -0,0 +1,23 @@
+graphic: 0.809
+device: 0.666
+other: 0.381
+files: 0.330
+network: 0.215
+vnc: 0.186
+semantic: 0.159
+boot: 0.141
+socket: 0.132
+performance: 0.130
+debug: 0.102
+PID: 0.099
+permissions: 0.066
+KVM: 0.002
+
+Crash / Assert in VVFAT.c while installaling WinXP from QEMU 7.0 running in Raspberry OS
+Description of problem:
+- Windows XP installation crashes QEMU with : 
+qemu-system-i386: ../block/vvfat.c:103: array_get: Assertion `index < array->next' failed.
+Steps to reproduce:
+Use command line above and run WindowsXP installation
+Additional information:
+Execution also leads to many "Invalid file name" being reported by QEMU
diff --git a/results/classifier/108/other/1175089 b/results/classifier/108/other/1175089
new file mode 100644
index 000000000..fa952d4c2
--- /dev/null
+++ b/results/classifier/108/other/1175089
@@ -0,0 +1,80 @@
+other: 0.804
+permissions: 0.797
+KVM: 0.777
+vnc: 0.775
+device: 0.765
+performance: 0.763
+files: 0.757
+graphic: 0.753
+network: 0.745
+boot: 0.741
+socket: 0.739
+debug: 0.739
+PID: 0.737
+semantic: 0.709
+
+Crash why dragon fly 3.4.1
+
+Hello, all is here (kernel 3.8, qemu 1.2.2-r3):
+/usr/bin/qemu-system-x86_64 -k fr -alt-grab -m 2048 -vga vmware -net nic,vlan=0,model=virtio -net user -rtc base=localtime -smp 4,cores=4,sockets=1 -boot once=d -cdrom dfly-x86_64-gui-3.4.1_REL.iso 
+KVM internal error. Suberror: 1
+emulation failure
+EAX=00000010 EBX=00009338 ECX=00000000 EDX=00000000
+ESI=000017fc EDI=000017c8 EBP=000364a0 ESP=000017b8
+EIP=00009318 EFL=00003002 [-------] CPL=0 II=0 A20=1 SMM=0 HLT=0
+ES =0010 00000000 ffffffff 00c09300
+CS =0018 00000000 0000ffff 00009b00
+SS =0010 00000000 ffffffff 00c09300
+DS =0010 00000000 ffffffff 00c09300
+FS =0033 0000a000 ffffffff 00c0f300
+GS =0033 0000a000 ffffffff 00c0f300
+LDT=0000 00000000 0000ffff 00008200
+TR =0038 00005f98 00002067 00008b00
+GDT=     00009590 0000003f
+IDT=     00005e00 00000197
+CR0=00000010 CR2=00000000 CR3=00000000 CR4=00000000
+DR0=0000000000000000 DR1=0000000000000000 DR2=0000000000000000 DR3=0000000000000000 
+DR6=00000000ffff0ff0 DR7=0000000000000400
+EFER=0000000000000000
+Code=00 a3 ea 5d 00 00 66 ea 10 93 18 00 0f 20 c0 fe c8 0f 22 c0 <ea> 1d 93 00 00 31 c0 8e d8 8e d0 0f 01 1e dc 95 66 07 66 1f 66 0f a1 66 0f a9 66 61 bc ea
+
+Same code for FreeBSD on older devices under openstack/qemu:
+LC_ALL=C PATH=/usr/local/sbin:/usr/local/bin:/usr/bin:/usr/sbin:/sbin:/bin QEMU_AUDIO_DRV=none /usr/bin/kvm -name instance-00000968 -S -machine pc-i440fx-1.5,accel=kvm,usb=off -cpu host -m 2096 -realtime mlock=off -smp 1,sockets=1,cores=1,threads=1 -uuid 387ce256-de98-4ae9-89f4-a4c26e970bf1 -smbios type=1,manufacturer=OpenStack Foundation,product=OpenStack Nova,version=2013.2.4,serial=4c4c4544-0034-5210-8058-b4c04f5a344a,uuid=387ce256-de98-4ae9-89f4-a4c26e970bf1 -no-user-config -nodefaults -chardev socket,id=charmonitor,path=/var/lib/libvirt/qemu/instance-00000968.monitor,server,nowait -mon chardev=charmonitor,id=monitor,mode=control -rtc base=utc,driftfix=slew -no-kvm-pit-reinjection -no-shutdown -device piix3-usb-uhci,id=usb,bus=pci.0,addr=0x1.0x2 -drive file=/var/lib/nova/instances/387ce256-de98-4ae9-89f4-a4c26e970bf1/disk,if=none,id=drive-virtio-disk0,format=raw,cache=none -device virtio-blk-pci,scsi=off,bus=pci.0,addr=0x4,drive=drive-virtio-disk0,id=virtio-disk0,bootindex=1 -netdev tap,fd=30,id=hostnet0,vhost=on,vhostfd=33 -device virtio-net-pci,netdev=hostnet0,id=net0,mac=fa:16:3e:0e:59:74,bus=pci.0,addr=0x3 -chardev file,id=charserial0,path=/var/lib/nova/instances/387ce256-de98-4ae9-89f4-a4c26e970bf1/console.log -device isa-serial,chardev=charserial0,id=serial0 -chardev pty,id=charserial1 -device isa-serial,chardev=charserial1,id=serial1 -device usb-tablet,id=input0 -vnc 0.0.0.0:4 -k en-us -vga cirrus -device virtio-balloon-pci,id=balloon0,bus=pci.0,addr=0x5
+
+Domain id=41 is tainted: host-cpu
+W: kvm binary is deprecated, please use qemu-system-x86_64 instead
+Warning: option deprecated, use lost_tick_policy property of kvm-pit instead.
+char device redirected to /dev/pts/5 (label charserial1)
+KVM internal error. Suberror: 1
+emulation failure
+EAX=00000010 EBX=00009336 ECX=00000000 EDX=00000000
+ESI=000017fc EDI=000017c8 EBP=0003b500 ESP=000017b8
+EIP=00009316 EFL=00003002 [-------] CPL=0 II=0 A20=1 SMM=0 HLT=0
+ES =0010 00000000 ffffffff 00c09300
+CS =0018 00000000 0000ffff 00009b00
+SS =0010 00000000 ffffffff 00c09300
+DS =0010 00000000 ffffffff 00c09300
+FS =0033 0000a000 ffffffff 00c0f300
+GS =0033 0000a000 ffffffff 00c0f300
+LDT=0000 00000000 0000ffff 00008200
+TR =0038 00005f98 00002067 00008b00
+GDT=     00009590 0000003f
+IDT=     00005e00 00000197
+CR0=00000010 CR2=00000000 CR3=00000000 CR4=00000000
+DR0=0000000000000000 DR1=0000000000000000 DR2=0000000000000000 DR3=0000000000000000
+DR6=00000000ffff0ff0 DR7=0000000000000400
+EFER=0000000000000000
+Code=00 a3 ea 5d 00 00 66 ea 0e 93 18 00 0f 20 c0 fe c8 0f 22 c0 <ea> 1b 93 00 00 31 c0 8e d8 8e d0 0f 01 1e dc 95 66 07 66 1f 66 0f a1 66 0f a9 66 61 bc ea
+qemu: terminating on signal 15 from pid 12541
+2015-01-29 14:11:08.678+0000: shutting down
+
+PowerEdge R210
+qemu: 1.5.0+dfsg-3ubuntu5.4~cloud0
+cpu flags: flags		: fpu vme de pse tsc msr pae mce cx8 apic sep mtrr pge mca cmov pat pse36 clflush dts acpi mmx fxsr sse sse2 ss ht tm pbe syscall nx rdtscp lm constant_tsc arch_perfmon pebs bts rep_good nopl xtopology nonstop_tsc aperfmperf pni dtes64 monitor ds_cpl vmx smx est tm2 ssse3 cx16 xtpr pdcm sse4_1 sse4_2 popcnt lahf_lm ida dtherm tpr_shadow vnmi flexpriority ept vpid
+
+3.8.0-44-generic x86_64
+
+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/1176 b/results/classifier/108/other/1176
new file mode 100644
index 000000000..bf5d70a73
--- /dev/null
+++ b/results/classifier/108/other/1176
@@ -0,0 +1,22 @@
+other: 0.958
+files: 0.911
+graphic: 0.863
+device: 0.839
+network: 0.690
+vnc: 0.674
+socket: 0.494
+performance: 0.482
+semantic: 0.403
+debug: 0.342
+boot: 0.293
+PID: 0.287
+permissions: 0.202
+KVM: 0.004
+
+VVFAT :rw writes from guest (ReactOS, windowsXP) not visible by host
+Description of problem:
+As described in https://jira.reactos.org/browse/CORE-18327
+While ./LMS is mounted as a :rw VVFAT drive, guest OS (ReactOS) is able to read files BUT when files are "written" from the guest, they are not visible on host side.
+QEMU execution is also massively polluted by "invalid file name" messages coming from https://git.qemu.org/?p=qemu.git;a=blob_plain;f=block/vvfat.c;hb=HEAD (but this is not specific to the use with ReactOS, as this is also observed with other guest : WXP, ...)
+
+See attached screenshot showing WXPSP3 as guest with file created in VVFAT drive while guest misses the newly created file.
diff --git a/results/classifier/108/other/1176366 b/results/classifier/108/other/1176366
new file mode 100644
index 000000000..cf4ca266c
--- /dev/null
+++ b/results/classifier/108/other/1176366
@@ -0,0 +1,44 @@
+network: 0.851
+debug: 0.708
+device: 0.568
+performance: 0.526
+graphic: 0.525
+semantic: 0.490
+PID: 0.484
+permissions: 0.400
+files: 0.378
+vnc: 0.355
+other: 0.330
+socket: 0.312
+boot: 0.296
+KVM: 0.153
+
+TCPIP not working on qemu 1.4.50 (master)
+
+whenever I try, in the guest OS, in this case it's NT 3.1, to enable TCP/IP, it crashes the whole emulator. With either the ne2000 isa, ne2000 pci or PCnet, still crashes
+
+below is attached a screenshot.
+
+
+
+On Sat, May 04, 2013 at 04:13:19PM -0000, TC1988 wrote:
+> whenever I try, in the guest OS, in this case it's NT 3.1, to enable
+> TCP/IP, it crashes the whole emulator. With either the ne2000 isa,
+> ne2000 pci or PCnet, still crashes
+> 
+> below is attached a screenshot.
+
+Please use git-bisect(1) to identify the commit that broke networking.
+
+http://git-scm.com/book/en/Git-Tools-Debugging-with-Git#Binary-Search
+https://www.kernel.org/pub/software/scm/git/docs/git-bisect.html
+
+Stefan
+
+
+looks like it also happens in 1.5.0-rc1, will check later with git bisect in the latest git release based on rc1.
+
+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/1177774 b/results/classifier/108/other/1177774
new file mode 100644
index 000000000..49d2446bf
--- /dev/null
+++ b/results/classifier/108/other/1177774
@@ -0,0 +1,84 @@
+other: 0.807
+permissions: 0.751
+performance: 0.721
+semantic: 0.718
+graphic: 0.710
+vnc: 0.675
+socket: 0.666
+device: 0.661
+PID: 0.657
+network: 0.646
+debug: 0.645
+files: 0.637
+KVM: 0.610
+boot: 0.604
+
+Gtk+ frontend fails to build
+
+The QEMU Gtk+ frontend fails to build..
+
+cc -I/home/ports/pobj/qemu-1.5.0-rc0/qemu-1.5.0-rc0/tcg -I/home/ports/pobj/qemu-1.5.0-rc0/qemu-1.5.0-rc0/tcg/i386 -I. -I/home/ports/pobj/qemu-1.5.0-rc0/qemu-1.5.0-rc0 -I/home/ports/pobj/qemu-1.5.0-rc0/qemu-1.5.0-rc0/include -Iui -Iui -fPIE -DPIE -m64 -D_GNU_SOURCE -D_FILE_OFFSET_BITS=64 -D_LARGEFILE_SOURCE -Wstrict-prototypes -Wredundant-decls -Wall -Wundef -Wwrite-strings -Wmissing-prototypes -fno-strict-aliasing -I/usr/local/include -I/usr/X11R6/include -Wno-redundant-decls -DTIME_MAX=INT_MAX  -Wendif-labels -Wmissing-include-dirs -Wnested-externs -Wformat-security -Wformat-y2k -Winit-self -Wold-style-definition -fstack-protector-all -I/usr/local/include -I/usr/local/include/p11-kit-1 -I/usr/include  -I/usr/local/include/libpng -I/usr/local/include -I/usr/include -I/usr/X11R6/include/pixman-1 -I/home/ports/pobj/qemu-1.5.0-rc0/qemu-1.5.0-rc0/dtc/libfdt -pthread -I/usr/local/include/glib-2.0 -I/usr/local/lib/glib-2.0/include -I/usr/local/include -I/home/ports/pobj/qemu-1.5.0-rc0/qemu-1.5.0-rc0/tests -I/usr/local/include/gtk-2.0 -I/usr/local/lib/gtk-2.0/include -I/usr/local/include/pango-1.0 -I/usr/local/include/gio-unix-2.0/ -I/usr/X11R6/include -I/usr/local/include/cairo -I/usr/local/include/atk-1.0 -I/usr/X11R6/include/pixman-1 -I/usr/local/include/libpng -I/usr/local/include/gdk-pixbuf-2.0 -I/usr/local/include/harfbuzz -pthread -I/usr/local/include/glib-2.0 -I/usr/local/lib/glib-2.0/include -I/usr/local/include -I/usr/X11R6/include/freetype2 -I/usr/local/include/vte-0.0 -I/usr/local/include/gtk-2.0 -I/usr/local/lib/gtk-2.0/include -I/usr/local/include/pango-1.0 -I/usr/X11R6/include -I/usr/local/include/atk-1.0 -I/usr/local/include/gdk-pixbuf-2.0 -I/usr/local/include/harfbuzz -I/usr/local/include/gio-unix-2.0/ -pthread -I/usr/local/include/cairo -I/usr/local/include/glib-2.0 -I/usr/local/lib/glib-2.0/include -I/usr/local/include -I/usr/X11R6/include/pixman-1 -I/usr/X11R6/include/freetype2 -I/usr/local/include/libpng -MMD -MP -MT ui/gtk.o -MF ui/gtk.d -O2 -pipe -c -o ui/gtk.o ui/gtk.c
+In file included from /usr/local/include/gtk-2.0/gtk/gtk.h:234,
+                 from ui/gtk.c:44:
+/usr/local/include/gtk-2.0/gtk/gtkitemfactory.h:47: warning: function declaration isn't a prototype
+ui/gtk.c:58:17: warning: pty.h: No such file or directory
+ui/gtk.c: In function 'gd_vc_init':
+ui/gtk.c:1142: error: storage size of 'tty' isn't known
+ui/gtk.c:1162: warning: implicit declaration of function 'openpty'
+ui/gtk.c:1162: warning: nested extern declaration of 'openpty'
+ui/gtk.c:1166: warning: implicit declaration of function 'tcgetattr'
+ui/gtk.c:1166: warning: nested extern declaration of 'tcgetattr'
+ui/gtk.c:1167: warning: implicit declaration of function 'cfmakeraw'
+ui/gtk.c:1167: warning: nested extern declaration of 'cfmakeraw'
+ui/gtk.c:1168: warning: implicit declaration of function 'tcsetattr'
+ui/gtk.c:1168: warning: nested extern declaration of 'tcsetattr'
+ui/gtk.c:1168: error: 'TCSAFLUSH' undeclared (first use in this function)
+ui/gtk.c:1168: error: (Each undeclared identifier is reported only once
+ui/gtk.c:1168: error: for each function it appears in.)
+ui/gtk.c:1142: warning: unused variable 'tty'
+
+With the 1.5 release so near does no one really care that the Gtk+ frontend does not build? I would think this would be a pretty important bug to fix before the release.
+
+Sending a patch soon, please reply with Tested-by if it works.
+
+For *BSD OS's you have to include termios.h..
+
+In file included from /usr/local/include/gtk-2.0/gtk/gtk.h:234,
+                 from ui/gtk.c:44:
+/usr/local/include/gtk-2.0/gtk/gtkitemfactory.h:47: warning: function declaration isn't a prototype
+ui/gtk.c: In function 'gd_vc_init':
+ui/gtk.c:1141: error: storage size of 'tty' isn't known
+ui/gtk.c:1165: warning: implicit declaration of function 'tcgetattr'
+ui/gtk.c:1165: warning: nested extern declaration of 'tcgetattr'
+ui/gtk.c:1166: warning: implicit declaration of function 'cfmakeraw'
+ui/gtk.c:1166: warning: nested extern declaration of 'cfmakeraw'
+ui/gtk.c:1167: warning: implicit declaration of function 'tcsetattr'
+ui/gtk.c:1167: warning: nested extern declaration of 'tcsetattr'
+ui/gtk.c:1167: error: 'TCSAFLUSH' undeclared (first use in this function)
+ui/gtk.c:1167: error: (Each undeclared identifier is reported only once
+ui/gtk.c:1167: error: for each function it appears in.)
+ui/gtk.c:1141: warning: unused variable 'tty'
+
+e.g.
+
+#if defined(__GLIBC__)
+# include <pty.h>
+#elif defined CONFIG_BSD
+# include <termios.h>
+# if defined(__FreeBSD__) || defined(__FreeBSD_kernel__) || defined(__DragonFly__)
+#  include <libutil.h>
+# else
+#  include <util.h>
+# endif
+#elif defined CONFIG_SOLARIS
+# include <stropts.h>
+#endif
+
+This should allow OS X to at least build. It looks like Solaris does not have openpty() and cfmakeraw()
+
+So the *BSD build has been fixed, but someone needs to look into fixing the Gtk+ backend on Solaris.
+
+Looks like this issue has been fixed by this commit here:
+http://git.qemu.org/?p=qemu.git;a=commitdiff;h=4efeabbbe8441cc327052304
+... so I think it should be OK to close this now.
+
diff --git a/results/classifier/108/other/1178 b/results/classifier/108/other/1178
new file mode 100644
index 000000000..070425eec
--- /dev/null
+++ b/results/classifier/108/other/1178
@@ -0,0 +1,16 @@
+device: 0.714
+performance: 0.588
+graphic: 0.533
+semantic: 0.478
+permissions: 0.404
+network: 0.383
+debug: 0.365
+files: 0.356
+other: 0.331
+boot: 0.278
+PID: 0.111
+vnc: 0.096
+KVM: 0.069
+socket: 0.062
+
+is that  riscv64 `feq.s` only should consider the lowest  32-bits.
diff --git a/results/classifier/108/other/1179 b/results/classifier/108/other/1179
new file mode 100644
index 000000000..30945e54c
--- /dev/null
+++ b/results/classifier/108/other/1179
@@ -0,0 +1,80 @@
+graphic: 0.700
+debug: 0.599
+device: 0.576
+other: 0.543
+vnc: 0.524
+socket: 0.505
+PID: 0.470
+files: 0.458
+performance: 0.418
+boot: 0.384
+network: 0.347
+permissions: 0.293
+semantic: 0.219
+KVM: 0.121
+
+qemu-img snapshot would break win8.1's system disk data
+Description of problem:
+`qemu-img snapshot` will cause a damage on windows 8.1 virtual machine
+Steps to reproduce:
+1.shutdown the virtual machine
+
+2.exec command
+```
+$ qemu-img snapshot -d standard /media/user/SSD_VM/disk/win8_1.qcow2
+...
+ERROR cluster 554329 refcount=0 reference=1
+ERROR cluster 554330 refcount=0 reference=1
+ERROR cluster 554331 refcount=0 reference=1
+ERROR cluster 554332 refcount=0 reference=1
+ERROR cluster 554333 refcount=0 reference=1
+ERROR cluster 554334 refcount=0 reference=1
+ERROR cluster 554335 refcount=0 reference=1
+Leaked cluster 557183 refcount=2 reference=1
+Leaked cluster 557472 refcount=2 reference=1
+Leaked cluster 564785 refcount=2 reference=1
+...
+Leaked cluster 580393 refcount=2 reference=1
+Leaked cluster 580434 refcount=2 reference=1
+Leaked cluster 580713 refcount=2 reference=1
+Leaked cluster 580718 refcount=2 reference=1
+Leaked cluster 580726 refcount=2 reference=1
+Leaked cluster 580965 refcount=2 reference=1
+Leaked cluster 581268 refcount=2 reference=1
+Leaked cluster 581280 refcount=2 reference=1
+Leaked cluster 581367 refcount=2 reference=1
+Leaked cluster 582743 refcount=2 reference=1
+Leaked cluster 582938 refcount=2 reference=1
+Leaked cluster 583026 refcount=2 reference=1
+Leaked cluster 583027 refcount=2 reference=1
+Leaked cluster 583028 refcount=2 reference=1
+Leaked cluster 583029 refcount=2 reference=1
+Rebuilding refcount structure
+Repairing cluster 547917 refcount=1 reference=0
+Repairing cluster 547936 refcount=1 reference=0
+Repairing cluster 547955 refcount=1 reference=0
+Repairing cluster 548069 refcount=1 reference=0
+Repairing cluster 548092 refcount=1 reference=0
+Repairing cluster 548115 refcount=1 reference=0
+Repairing cluster 548125 refcount=1 reference=0
+Repairing cluster 548128 refcount=1 reference=0
+Repairing cluster 548130 refcount=1 reference=0
+Repairing cluster 548144 refcount=1 reference=0
+Repairing cluster 548146 refcount=1 reference=0
+Repairing cluster 548150 refcount=1 reference=0
+Repairing cluster 548199 refcount=1 reference=0
+Repairing cluster 548201 refcount=1 reference=0
+Repairing cluster 548226 refcount=1 reference=0
+Repairing cluster 548234 refcount=1 reference=0
+Repairing cluster 548236 refcount=1 reference=0
+Repairing cluster 557073 refcount=1 reference=0
+Repairing cluster 557074 refcount=1 reference=0
+...
+
+```
+
+3.start the virtual machine , it shows blue screen error:
+`UNEXPECTED_STORE_EXCPETION`
+![Screenshot_20220828_131532](/uploads/d8c03c01deb9ae1183a4efd823850c7e/Screenshot_20220828_131532.png)
+Additional information:
+the windows virtual machine will automatically fix the damage that qemu-img caused on next restart .
diff --git a/results/classifier/108/other/1179664 b/results/classifier/108/other/1179664
new file mode 100644
index 000000000..94f8d19b9
--- /dev/null
+++ b/results/classifier/108/other/1179664
@@ -0,0 +1,66 @@
+PID: 0.669
+socket: 0.625
+device: 0.624
+semantic: 0.496
+debug: 0.449
+vnc: 0.401
+permissions: 0.356
+network: 0.352
+boot: 0.335
+other: 0.280
+performance: 0.266
+files: 0.257
+graphic: 0.178
+KVM: 0.098
+
+migration.c:293: undefined reference to  `__sync_val_compare_and_swap_4'
+
+latest git qemu error i get on compiling with mingw
+
+  LINK  i386-softmmu/qemu-system-i386w.exe
+../migration.o: In function `migrate_finish_set_state':
+C:\MinGW\msys\1.0\home\therock247uk\qemu/migration.c:293: undefined reference to
+ `__sync_val_compare_and_swap_4'
+C:\MinGW\msys\1.0\home\therock247uk\qemu/migration.c:293: undefined reference to
+ `__sync_val_compare_and_swap_4'
+C:\MinGW\msys\1.0\home\therock247uk\qemu/migration.c:293: undefined reference to
+ `__sync_val_compare_and_swap_4'
+collect2.exe: error: ld returned 1 exit status
+make[1]: *** [qemu-system-i386w.exe] Error 1
+make: *** [subdir-i386-softmmu] Error 2
+
+On Mon, May 13, 2013 at 08:46:27PM -0000, therock247uk wrote:
+> Public bug reported:
+> 
+> latest git qemu error i get on compiling with mingw
+> 
+>   LINK  i386-softmmu/qemu-system-i386w.exe
+> ../migration.o: In function `migrate_finish_set_state':
+> C:\MinGW\msys\1.0\home\therock247uk\qemu/migration.c:293: undefined reference to
+>  `__sync_val_compare_and_swap_4'
+> C:\MinGW\msys\1.0\home\therock247uk\qemu/migration.c:293: undefined reference to
+>  `__sync_val_compare_and_swap_4'
+> C:\MinGW\msys\1.0\home\therock247uk\qemu/migration.c:293: undefined reference to
+>  `__sync_val_compare_and_swap_4'
+> collect2.exe: error: ld returned 1 exit status
+> make[1]: *** [qemu-system-i386w.exe] Error 1
+> make: *** [subdir-i386-softmmu] Error 2
+
+Please post your gcc version:
+
+  $ gcc --version
+
+
+therock247uk@dell-PC ~
+$ gcc --version
+gcc.exe (GCC) 4.7.2
+Copyright (C) 2012 Free Software Foundation, Inc.
+This is free software; see the source for copying conditions.  There is NO
+warranty; not even for MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE.
+
+
+therock247uk@dell-PC ~
+$
+
+I assume this had been fixed by this commit here: http://git.qemu.org/?p=qemu.git;a=commitdiff;h=1405b6290fa2143e02dce - so I'm closing this ticket now. If you still hit the problem with the latest version of QEMU, please feel free to open this ticket again.
+
diff --git a/results/classifier/108/other/1179731 b/results/classifier/108/other/1179731
new file mode 100644
index 000000000..184935018
--- /dev/null
+++ b/results/classifier/108/other/1179731
@@ -0,0 +1,61 @@
+network: 0.890
+files: 0.847
+PID: 0.806
+KVM: 0.800
+other: 0.788
+graphic: 0.770
+device: 0.767
+performance: 0.758
+semantic: 0.750
+socket: 0.691
+permissions: 0.688
+vnc: 0.656
+debug: 0.570
+boot: 0.499
+
+is networking broken on windows hosts?
+
+just wondering as i just compiled the latest git and qemu goes into none responding mode when i try to do any networking stuff on guests (both linux and windows)
+
+On Tue, May 14, 2013 at 12:02:24AM -0000, therock247uk wrote:
+> just wondering as i just compiled the latest git and qemu goes into none
+> responding mode when i try to do any networking stuff on guests (both
+> linux and windows)
+
+Works for me on qemu.git/master on Linux:
+
+  $ git rev-parse HEAD
+  b087143b4d010451208264b7c841436aafe1cbb1
+  $ x86_64-softmmu/qemu-system-x86_64 -m 1024 -enable-kvm -cpu host \
+          -drive if=virtio,cache=none,file=test.img
+
+Please include more information, like the QEMU command-line and commit
+ID.
+
+Stefan
+
+
+latest git as of yesterday compiled under mingw using qemu-system-i386 -localtime -m 512 windows.img when ever it connects to the internet qemu hangs.
+
+trying other network adapters does not help either i tried the model=rtl8139 and the xp guest says limited or no connectivty.
+
+tried the patch did not work though still hangs/crashes has issues
+
+On 05/16/2013 10:59 AM, Paolo Bonzini wrote:
+> Il 16/05/2013 07:52, TeLeMan ha scritto:
+>> The patch is working on 134a03e0b3d34b01b68107104c525c3bff1211d4 and
+>> is not working from cbff4b342b000a7642125dbdabf61113e05eee44.
+> 
+> Thanks.
+> 
+> Fabien or Stefan, can you take a look?
+> 
+
+Unfortunately I don't have time to investigate these days.
+
+-- 
+Fabien Chouteau
+
+
+Looking at http://lists.gnu.org/archive/html/qemu-devel/2013-05/msg02268.html it seems this has been fixed with commits 8db165b36ef893ac69af045 and 3cb8c205e36531a07dff1d84 ==> setting status to "Fix released"
+