9 files changed, 417 insertions, 0 deletions
diff --git a/results/classifier/108/other/281 b/results/classifier/108/other/281
new file mode 100644
index 000000000..2870f1655
--- /dev/null
+++ b/results/classifier/108/other/281
@@ -0,0 +1,16 @@
+device: 0.749
+network: 0.645
+other: 0.610
+socket: 0.378
+performance: 0.363
+boot: 0.342
+PID: 0.263
+debug: 0.258
+permissions: 0.257
+graphic: 0.245
+vnc: 0.244
+semantic: 0.199
+KVM: 0.113
+files: 0.023
+
+External modules retreval using Go1.15 on s390x appears to have checksum and ECDSA verification issues
diff --git a/results/classifier/108/other/2810 b/results/classifier/108/other/2810
new file mode 100644
index 000000000..2cc7a627b
--- /dev/null
+++ b/results/classifier/108/other/2810
@@ -0,0 +1,16 @@
+boot: 0.801
+device: 0.789
+graphic: 0.407
+performance: 0.333
+permissions: 0.234
+semantic: 0.172
+files: 0.083
+network: 0.075
+PID: 0.069
+debug: 0.049
+socket: 0.015
+vnc: 0.013
+other: 0.004
+KVM: 0.004
+
+Boot zboot images on riscv64 and loogarch64
diff --git a/results/classifier/108/other/2811 b/results/classifier/108/other/2811
new file mode 100644
index 000000000..b0222673e
--- /dev/null
+++ b/results/classifier/108/other/2811
@@ -0,0 +1,109 @@
+permissions: 0.748
+KVM: 0.730
+graphic: 0.724
+other: 0.713
+PID: 0.659
+vnc: 0.658
+device: 0.652
+socket: 0.642
+performance: 0.624
+semantic: 0.616
+boot: 0.609
+files: 0.563
+debug: 0.557
+network: 0.539
+
+The release artifact for 9.2.1 can not be authenticated with the accompanying OpenPGP signature
+Description of problem:
+Hi! :wave: 
+
+I package this project for Arch Linux.
+This ticket is to inform you that the release artifact for 9.2.1 can not be validated using the accompanying OpenPGP signature.
+The signature has been created by the OpenPGP key with the fingerprint `CEACC9E15534EBABB82D3FA03353C9CEF108B584` (held by @mdroth).
+However, I am not able to validate the downloaded archive with the provided signature.
+
+Please make sure that the archive has not been tampered with and ideally do a full re-release and re-sign cycle.
+Steps to reproduce:
+Download sources and create checksum:
+
+```bash
+curl -O https://download.qemu.org/qemu-9.2.1.tar.xz 
+curl -O https://download.qemu.org/qemu-9.2.1.tar.xz.sig
+b2sum qemu-9.2.1.tar.xz
+062b2ef336dbc488bfd9e6c6a21cd95464ab76a98ce8f66bb314101d25a5dc72815ae4eb28028507c85ddade8a28e00cf8897302645ad6ddd2c093bde1cfba9a  qemu-9.2.1.tar.xz
+```
+
+Get latest version of certificate that can be used to verify the signature:
+
+```bash
+gpg --recv-keys CEACC9E15534EBABB82D3FA03353C9CEF108B584
+gpg: key 3353C9CEF108B584: "Michael Roth <michael.roth@amd.com>" not changed
+gpg: Total number processed: 1
+gpg:              unchanged: 1
+```
+
+Export certificate to file:
+
+```bash
+gpg --export CEACC9E15534EBABB82D3FA03353C9CEF108B584 > mdroth.pgp
+```
+
+Show info about the certificate:
+
+```
+gpg --list-sigs CEACC9E15534EBABB82D3FA03353C9CEF108B584
+pub   rsa2048 2013-10-18 [SC] [expires: 2026-05-11]
+      CEACC9E15534EBABB82D3FA03353C9CEF108B584
+      Keygrip = D85EA26924D8B15B55C659659E2864C375F1547D
+uid           [ unknown] Michael Roth <michael.roth@amd.com>
+sig 3        3353C9CEF108B584 2020-10-27  [self-signature]
+sig 3        3353C9CEF108B584 2024-05-11  [self-signature]
+uid           [ unknown] Michael Roth <flukshun@gmail.com>
+sig 3        3353C9CEF108B584 2013-10-18  [self-signature]
+uid           [ unknown] Michael Roth <mdroth@utexas.edu>
+sig 3        3353C9CEF108B584 2013-10-18  [self-signature]
+sub   rsa2048 2013-10-18 [E]
+      Keygrip = 9561B09210E2442DEE64237DBA17A9E9D7A58B04
+sig          3353C9CEF108B584 2013-10-18  [self-signature]
+```
+
+Try verifying the tarball using gpg:
+
+```bash
+gpg --verify qemu-9.2.1.tar.xz.sig
+gpg: assuming signed data in 'qemu-9.2.1.tar.xz'
+gpg: Signature made 2025-02-12T03:22:55 CET
+gpg:                using RSA key CEACC9E15534EBABB82D3FA03353C9CEF108B584
+gpg: BAD signature from "Michael Roth <michael.roth@amd.com>" [unknown]
+```
+
+Try verifying the tarball using the SOP implementation rsop:
+
+```bash
+rsop verify qemu-9.2.1.tar.xz.sig mdroth.pgp < qemu-9.2.1.tar.xz
+           No acceptable signatures found
+```
+
+Try verifying the tarball using sq:
+
+```bash
+sq cert import mdroth.pgp
+ - ┌ CEACC9E15534EBABB82D3FA03353C9CEF108B584
+   └ Michael Roth <michael.roth@amd.com> (UNAUTHENTICATED)
+   - imported
+
+
+Imported 0 new certificates, updated 0 certificates, 1 certificate unchanged, 0 errors.
+
+sq verify --signature-file qemu-9.2.1.tar.xz.sig qemu-9.2.1.tar.xz
+Error verifying signature made by CEACC9E15534EBABB82D3FA03353C9CEF108B584:
+
+  Error: Message has been manipulated
+0 authenticated signatures, 1 bad signature.
+
+  Error: Verification failed: could not authenticate any signatures
+```
+Additional information:
+On Arch Linux we use the provided release tarball and verify it using the detached signature.
+For validation we rely on the OpenPGP certificate with the fingerprint `CEACC9E15534EBABB82D3FA03353C9CEF108B584`.
+The fingerprint is locked in our [build script](https://gitlab.archlinux.org/archlinux/packaging/packages/qemu/-/blob/7cddf5aa82542d6ba511a22aeaa8eca6d6e7d949/PKGBUILD#L158).
diff --git a/results/classifier/108/other/2813 b/results/classifier/108/other/2813
new file mode 100644
index 000000000..e52451b46
--- /dev/null
+++ b/results/classifier/108/other/2813
@@ -0,0 +1,24 @@
+device: 0.798
+graphic: 0.743
+socket: 0.414
+network: 0.365
+vnc: 0.305
+permissions: 0.286
+semantic: 0.268
+debug: 0.260
+other: 0.223
+boot: 0.222
+performance: 0.217
+files: 0.204
+PID: 0.161
+KVM: 0.105
+
+Cannot emulate Windows 95 / 98
+Description of problem:
+If install Windows 95 / 98 on that configuration, Windows 95 / 98 crashed on "While initializing device NDIS: Windows protection error." message, or QEMU crashed. With this command line Windows 95 / 98 can worked on previous QEMU 7.<br>And please don't allow IME input on CJK (Chinese / Japanese / Korean) host system (that relied IME to input some text). Such input process is done by the IME in CJK operating system guest.
+Steps to reproduce:
+1.
+2.
+3.
+Additional information:
+
diff --git a/results/classifier/108/other/2814 b/results/classifier/108/other/2814
new file mode 100644
index 000000000..1a2a0afac
--- /dev/null
+++ b/results/classifier/108/other/2814
@@ -0,0 +1,16 @@
+network: 0.622
+files: 0.597
+device: 0.565
+performance: 0.446
+permissions: 0.410
+vnc: 0.334
+debug: 0.330
+semantic: 0.283
+graphic: 0.207
+boot: 0.168
+socket: 0.141
+PID: 0.098
+other: 0.065
+KVM: 0.028
+
+Convert gdb_core_xml_file to function for https://linaro.atlassian.net/browse/QEMU-487
diff --git a/results/classifier/108/other/2815 b/results/classifier/108/other/2815
new file mode 100644
index 000000000..f2faa1a76
--- /dev/null
+++ b/results/classifier/108/other/2815
@@ -0,0 +1,16 @@
+device: 0.865
+network: 0.806
+performance: 0.765
+files: 0.621
+socket: 0.556
+debug: 0.524
+semantic: 0.518
+permissions: 0.465
+boot: 0.395
+vnc: 0.391
+graphic: 0.373
+other: 0.202
+PID: 0.186
+KVM: 0.021
+
+clang 17 and newer -fsanitize=function causes QEMU user-mode to SEGV when calling TCG prologue
diff --git a/results/classifier/108/other/2817 b/results/classifier/108/other/2817
new file mode 100644
index 000000000..2c807d158
--- /dev/null
+++ b/results/classifier/108/other/2817
@@ -0,0 +1,66 @@
+performance: 0.868
+device: 0.806
+PID: 0.780
+graphic: 0.777
+network: 0.771
+files: 0.756
+permissions: 0.736
+socket: 0.713
+debug: 0.699
+semantic: 0.699
+vnc: 0.686
+other: 0.579
+boot: 0.560
+KVM: 0.260
+
+Strange floating-point behaviour under Windows with some CPU models
+Description of problem:
+I'm encountering a very weird bug with some floating-point maths code, but only under very specific configurations. First I thought it was a Clang bug, but then further digging eventually showed it to only occur under Windows VMs with specific QEMU CPU options, I'm not certain whether it is a QEMU/KVM bug or a Windows bug, but thought starting here would be easiest.
+
+When compiled under MSVC Clang with modern CPU instructions disabled (e.g. `-march=pentium3` or `-march=pentium-mmx`), the `floorf()` call in the following program always returns 0.0, while the truncation works correctly:
+
+```
+#include <math.h>
+#include <stdio.h>
+#include <stdlib.h>
+
+int main(int argc, char **argv)
+{
+	float n = atof(argv[1]);
+	printf("n = %f\n", n);
+	
+	float f = floorf(n);
+	printf("f = %f\n", f);
+	
+	float c = (int)(n);
+	printf("c = %f\n", c);
+	
+	return 0;
+}
+```
+
+Example output on an affected VM:
+
+```
+C:\Users\Administrator> floorf-p3.exe 10
+n = 10.000000
+f = 0.000000
+c = 10.000000
+
+C:\Users\Administrator> floorf-p4.exe 10
+n = 10.000000
+f = 10.000000
+c = 10.000000
+```
+
+(`floorf-p3.exe` was compiled with `-march=pentium3` and `floorf-p4.exe` with `-march=pentium4` above)
+
+I've tried a few QEMU CPU models on a variety of Intel/AMD VM hosts and two different Windows versions (10 and Server 2022), and observed the following:
+
+* `host-passthrough` - works (on AMD and Intel hosts)
+* `qemu64` - broken
+* `EPYC-Milan` - works
+* `Westmere` - works
+* `Penryn` - broken
+
+(I also reported this via the mailing list, but I think it might've swallowed my post)
diff --git a/results/classifier/108/other/2818 b/results/classifier/108/other/2818
new file mode 100644
index 000000000..ddef10fb2
--- /dev/null
+++ b/results/classifier/108/other/2818
@@ -0,0 +1,22 @@
+graphic: 0.883
+performance: 0.866
+device: 0.848
+network: 0.789
+semantic: 0.788
+debug: 0.761
+other: 0.715
+socket: 0.629
+PID: 0.612
+vnc: 0.601
+files: 0.590
+boot: 0.552
+KVM: 0.273
+permissions: 0.209
+
+Passing `-M microvm` and `-smbios type=11...` results in smbios args being silently dropped
+Description of problem:
+(reporting as requested by `danpb` on IRC)
+
+Using the `-machine microvm` flag with the `smbios type=11...` argument results in the smbios options being silently discarded, because the microvm target doesn't seem to support the smbios feature.
+
+danpb on IRC suggested that passing those two incompatible flags should result in an error.
diff --git a/results/classifier/108/other/2819 b/results/classifier/108/other/2819
new file mode 100644
index 000000000..d1c6f10d5
--- /dev/null
+++ b/results/classifier/108/other/2819
@@ -0,0 +1,132 @@
+other: 0.706
+device: 0.705
+debug: 0.684
+graphic: 0.682
+KVM: 0.679
+vnc: 0.667
+performance: 0.661
+semantic: 0.660
+permissions: 0.658
+network: 0.654
+socket: 0.652
+PID: 0.646
+files: 0.642
+boot: 0.622
+
+QEMU 9.2.0 hangs with 100% CPU when using `-vnc` on Loongarch (3A6000 and 3C6000)
+Description of problem:
+When launching VMs with the `-vnc` parameter (generated by `<graphics type='vnc'>`) on a Loongarch (Loongson 3A6000 or Loongson 3C6000) machine. QEMU process hangs indefinitely with 100% CPU usage, no VNC output.
+Steps to reproduce:
+1. Create a VM using libvirt (Cockpit-Machines or virt-manager).
+2. Configure VNC graphics as follows in libvirt XML, which is provided by Cockpit-Machines by default.
+```xml
+<graphics type='vnc' port='-1' autoport='yes' listen='127.0.0.1'>
+  <listen type='address' address='127.0.0.1'/>
+</graphics>
+```
+3. Start the VM: QEMU process hangs indefinitely with 100% CPU usage, no VNC output.
+Additional information:
+- Removing the `-vnc` parameter from the QEMU command line (via removing <graphics ... In libvirt XML) resolves the issue.
+- The issue appears to stem from changes introduced after QEMU 9.0.1, as downgrading resolves the problem.
+- Libvirtd log: https://aosc.io/paste/detail?id=da60d57c-5040-4326-a622-6a692eab488a
+- QEMU command line: https://aosc.io/paste/detail?id=30c97bd5-e666-4578-adfd-236cc1fe02ef
+- Full Libvirt VM XML: https://aosc.io/paste/detail?id=6bff0fed-d805-4c36-afb7-d14f29d6313b
+- No activity in `strace` during the hang.
+- GDB backtrace shows the process stuck in `ppoll` (full trace below):
+```
+(gdb) bt
+ #0  0x00007ffff189cad0 in __GI_ppoll (fds=0x7fffa4068d00, nfds=10, timeout=<optimized out>, sigmask=0x0)
+     at ../sysdeps/unix/sysv/linux/ppoll.c:42
+ #1  0x0000555557e67320 in qemu_poll_ns ()
+ #2  0x0000555557e636a4 in main_loop_wait ()
+ #3  0x0000555557a0c4d4 in qemu_main_loop ()
+ #4  0x0000555557d79cc8 in qemu_default_main ()
+ #5  0x00007ffff17c8f30 in __libc_start_call_main
+     (main=main@entry=0x5555577969c0 <main>, argc=argc@entry=119, argv=argv@entry=0x7ffffbad5508)
+     at ../sysdeps/nptl/libc_start_call_main.h:58
+ #6  0x00007ffff17c9020 in __libc_start_main_impl
+     (main=0x5555577969c0 <main>, argc=119, argv=0x7ffffbad5508,  init=<optimized out>, fini=<optimized out>,  rtld_fini=<optimized out>, stack_end=<optimized out>) at  ../csu/libc-start.c:360
+ #7  0x0000555557797b70 in _start ()
+```
+- Qemu full command line:
+```
+LC_ALL=C \
+PATH=/usr/local/bin:/usr/bin \
+USER=root \
+HOME=/var/lib/libvirt/qemu/domain-5-buildbot-new \
+XDG_DATA_HOME=/var/lib/libvirt/qemu/domain-5-buildbot-new/.local/share \
+XDG_CACHE_HOME=/var/lib/libvirt/qemu/domain-5-buildbot-new/.cache \
+XDG_CONFIG_HOME=/var/lib/libvirt/qemu/domain-5-buildbot-new/.config \
+/usr/bin/qemu-system-loongarch64 \
+-name guest=buildbot-new,debug-threads=on \
+-S \
+-object '{"qom-type":"secret","id":"masterKey0","format":"raw","file":"/var/lib/libvirt/qemu/domain-5-buildbot-new/master-key.aes"}' \
+-blockdev '{"driver":"file","filename":"/usr/share/qemu/edk2-loongarch64-code.fd","node-name":"libvirt-pflash0-storage","auto-read-only":true,"discard":"unmap"}' \
+-blockdev '{"node-name":"libvirt-pflash0-format","read-only":true,"driver":"raw","file":"libvirt-pflash0-storage"}' \
+-blockdev '{"driver":"file","filename":"/var/lib/libvirt/qemu/nvram/buildbot-new_VARS.fd","node-name":"libvirt-pflash1-storage","read-only":false}' \
+-machine virt,usb=off,dump-guest-core=off,memory-backend=loongarch.ram,pflash0=libvirt-pflash0-format,pflash1=libvirt-pflash1-storage,acpi=on \
+-accel kvm \
+-cpu la464 \
+-m size=1048576k \
+-object '{"qom-type":"memory-backend-ram","id":"loongarch.ram","size":1073741824}' \
+-overcommit mem-lock=off \
+-smp 1,sockets=1,dies=1,clusters=1,cores=1,threads=1 \
+-uuid c56a24b5-c539-4240-9c72-39fd0d0de860 \
+-no-user-config \
+-nodefaults \
+-chardev socket,id=charmonitor,fd=33,server=on,wait=off \
+-mon chardev=charmonitor,id=monitor,mode=control \
+-rtc base=utc \
+-no-shutdown \
+-boot strict=on \
+-device '{"driver":"pcie-root-port","port":8,"chassis":1,"id":"pci.1","bus":"pcie.0","multifunction":true,"addr":"0x1"}' \
+-device '{"driver":"pcie-root-port","port":9,"chassis":2,"id":"pci.2","bus":"pcie.0","addr":"0x1.0x1"}' \
+-device '{"driver":"pcie-root-port","port":10,"chassis":3,"id":"pci.3","bus":"pcie.0","addr":"0x1.0x2"}' \
+-device '{"driver":"pcie-root-port","port":11,"chassis":4,"id":"pci.4","bus":"pcie.0","addr":"0x1.0x3"}' \
+-device '{"driver":"pcie-root-port","port":12,"chassis":5,"id":"pci.5","bus":"pcie.0","addr":"0x1.0x4"}' \
+-device '{"driver":"pcie-root-port","port":13,"chassis":6,"id":"pci.6","bus":"pcie.0","addr":"0x1.0x5"}' \
+-device '{"driver":"pcie-root-port","port":14,"chassis":7,"id":"pci.7","bus":"pcie.0","addr":"0x1.0x6"}' \
+-device '{"driver":"pcie-root-port","port":15,"chassis":8,"id":"pci.8","bus":"pcie.0","addr":"0x1.0x7"}' \
+-device '{"driver":"pcie-root-port","port":16,"chassis":9,"id":"pci.9","bus":"pcie.0","multifunction":true,"addr":"0x2"}' \
+-device '{"driver":"pcie-root-port","port":17,"chassis":10,"id":"pci.10","bus":"pcie.0","addr":"0x2.0x1"}' \
+-device '{"driver":"pcie-root-port","port":18,"chassis":11,"id":"pci.11","bus":"pcie.0","addr":"0x2.0x2"}' \
+-device '{"driver":"pcie-root-port","port":19,"chassis":12,"id":"pci.12","bus":"pcie.0","addr":"0x2.0x3"}' \
+-device '{"driver":"pcie-root-port","port":20,"chassis":13,"id":"pci.13","bus":"pcie.0","addr":"0x2.0x4"}' \
+-device '{"driver":"pcie-root-port","port":21,"chassis":14,"id":"pci.14","bus":"pcie.0","addr":"0x2.0x5"}' \
+-device '{"driver":"pcie-root-port","port":22,"chassis":15,"id":"pci.15","bus":"pcie.0","addr":"0x2.0x6"}' \
+-device '{"driver":"pcie-pci-bridge","id":"pci.16","bus":"pci.1","addr":"0x0"}' \
+-device '{"driver":"qemu-xhci","p2":15,"p3":15,"id":"usb","bus":"pci.3","addr":"0x0"}' \
+-device '{"driver":"virtio-scsi-pci","id":"scsi0","bus":"pci.8","addr":"0x0"}' \
+-device '{"driver":"virtio-serial-pci","id":"virtio-serial0","bus":"pci.4","addr":"0x0"}' \
+-blockdev '{"driver":"file","filename":"/mnt/data/aosc-os_installer_20241122_loongarch64.iso","node-name":"libvirt-1-storage","read-only":true}' \
+-device '{"driver":"scsi-cd","bus":"scsi0.0","channel":0,"scsi-id":0,"lun":0,"device_id":"drive-scsi0-0-0-0","drive":"libvirt-1-storage","id":"scsi0-0-0-0"}' \
+-chardev pty,id=charserial0 \
+-serial chardev:charserial0 \
+-chardev socket,id=charchannel0,fd=32,server=on,wait=off \
+-device '{"driver":"virtserialport","bus":"virtio-serial0.0","nr":1,"chardev":"charchannel0","id":"channel0","name":"org.qemu.guest_agent.0"}' \
+-chardev spicevmc,id=charchannel1,name=vdagent \
+-device '{"driver":"virtserialport","bus":"virtio-serial0.0","nr":2,"chardev":"charchannel1","id":"channel1","name":"com.redhat.spice.0"}' \
+-device '{"driver":"usb-tablet","id":"input0","bus":"usb.0","port":"1"}' \
+-device '{"driver":"usb-kbd","id":"input1","bus":"usb.0","port":"2"}' \
+-audiodev '{"id":"audio1","driver":"spice"}' \
+-vnc 127.0.0.1:0,audiodev=audio1 \
+-spice port=5901,addr=127.0.0.1,disable-ticketing=on,image-compression=off,seamless-migration=on \
+-device '{"driver":"virtio-gpu-pci","id":"video0","max_outputs":1,"bus":"pci.7","addr":"0x0"}' \
+-device '{"driver":"ich9-intel-hda","id":"sound0","bus":"pci.16","addr":"0x1"}' \
+-device '{"driver":"hda-duplex","id":"sound0-codec0","bus":"sound0.0","cad":0,"audiodev":"audio1"}' \
+-device '{"driver":"virtio-balloon-pci","id":"balloon0","bus":"pci.5","addr":"0x0"}' \
+-object '{"qom-type":"rng-random","id":"objrng0","filename":"/dev/urandom"}' \
+-device '{"driver":"virtio-rng-pci","rng":"objrng0","id":"rng0","bus":"pci.6","addr":"0x0"}' \
+-sandbox on,obsolete=deny,elevateprivileges=deny,spawn=deny,resourcecontrol=deny \
+-msg timestamp=on
+```
+- I tried to reproduce the bug with a simple command but failed, not sure what is the real cause. Following commands works fine.
+```
+qemu-system-loongarch64 -m 2G \
+  -cpu la464 \
+  -machine virt \
+  -smp 2 \
+  -bios /usr/share/qemu/edk2-loongarch64-code.fd \
+  -vnc 127.0.0.1:0 \
+  -device virtio-gpu-pci
+```