7 files changed, 173 insertions, 0 deletions
diff --git a/results/classifier/108/other/272 b/results/classifier/108/other/272
new file mode 100644
index 000000000..f2131a858
--- /dev/null
+++ b/results/classifier/108/other/272
@@ -0,0 +1,16 @@
+device: 0.792
+performance: 0.638
+debug: 0.430
+vnc: 0.370
+semantic: 0.350
+socket: 0.294
+graphic: 0.293
+network: 0.183
+boot: 0.169
+other: 0.117
+permissions: 0.083
+PID: 0.049
+files: 0.026
+KVM: 0.002
+
+QEMU: block/vvfat driver issues
diff --git a/results/classifier/108/other/2721 b/results/classifier/108/other/2721
new file mode 100644
index 000000000..991a26ea8
--- /dev/null
+++ b/results/classifier/108/other/2721
@@ -0,0 +1,16 @@
+device: 0.816
+performance: 0.684
+debug: 0.674
+boot: 0.646
+network: 0.558
+graphic: 0.539
+files: 0.484
+semantic: 0.412
+vnc: 0.279
+other: 0.148
+permissions: 0.120
+PID: 0.087
+socket: 0.077
+KVM: 0.008
+
+Failure with macOS 15.2 on ARM64: Property 'host-arm-cpu.sme' not found
diff --git a/results/classifier/108/other/2722 b/results/classifier/108/other/2722
new file mode 100644
index 000000000..61d88afdc
--- /dev/null
+++ b/results/classifier/108/other/2722
@@ -0,0 +1,63 @@
+graphic: 0.884
+semantic: 0.869
+vnc: 0.867
+permissions: 0.866
+other: 0.854
+device: 0.846
+debug: 0.841
+boot: 0.835
+PID: 0.829
+performance: 0.826
+socket: 0.782
+network: 0.775
+files: 0.774
+KVM: 0.757
+
+TLB Invalidation time out on i915 SR-IOV passthrough
+Description of problem:
+Hello,
+
+I tried to use SR-IOV on i915 driver freshly available on the [LTS intel kernel](https://github.com/intel/linux-intel-lts) with this [kernel version ](https://github.com/intel/linux-intel-lts/tree/lts-v6.6.34-linux-240626T131354Z) for pci passthrough purpose.
+After setting up SR-IOV (kernel compilation, kernel cmdline, vfio-pci driver attribution to the new pci..)
+ I've got my two new pci.
+
+```
+00:02.0 VGA compatible controller: Intel Corporation Alder Lake-P Integrated Graphics Controller (rev 0c)
+DeviceName: Onboard IGD
+
+Subsystem: Hewlett-Packard Company Alder Lake-P Integrated Graphics Controller
+Kernel driver in use: i915
+
+00:02.1 VGA compatible controller: Intel Corporation Alder Lake-P Integrated Graphics Controller (rev 0c)
+Subsystem: Hewlett-Packard Company Alder Lake-P Integrated Graphics Controller
+Kernel driver in use: vfio-pci
+
+00:02.2 VGA compatible controller: Intel Corporation Alder Lake-P Integrated Graphics Controller (rev 0c)
+Subsystem: Hewlett-Packard Company Alder Lake-P Integrated Graphics Controller
+Kernel driver in use: vfio-pci
+```
+I gave one of those pci to my VM with this qemu cmdline:
+```
+-cpu host,migratable=on,hv-time,hv-relaxed,hv-vapic,hv-spinlocks=0x1fff,hv-passthrough,hv-vendor-id=IrisXE
+...
+-device vfio-pci-nohotplug,host=0000:00:02.1,id=hostdev0,bus=pci.4,addr=0x0
+```
+Sometimes it working properly when I start the qemu cmdline but most of the time I've got those kernel errors and a GPU hang:
+```
+    kernel [ 2252.208134] i915 0000:00:02.0: [drm] ERROR GT0: GUC: TLB invalidation response timed out for seqno 9679
+    kernel [ 2252.208134] i915 0000:00:02.0: [drm] ERROR GT0: GUC: TLB invalidation response timed out for seqno 9679
+    kernel i915 0000:00:02.0: [drm] ERROR GT0: GUC: TLB invalidation response timed out for seqno 9679
+    kernel i915 0000:00:02.0: [drm] ERROR GT0: GUC: TLB invalidation response timed out for seqno 9679
+    ....
+    kernel Fence expiration time out i915-0000:00:02.0:renderThread22381:6e0!
+    kernel i915 0000:00:02.0: [drm] GT0: GuC firmware i915/adlp_guc_70.bin version 70.13.1
+    kernel i915 0000:00:02.0: [drm] GT0: HuC firmware i915/tgl_huc.bin version 7.9.3
+    kernel i915 0000:00:02.0: [drm] GT0: HuC: authenticated for all workloads
+    kernel i915 0000:00:02.0: [drm] GT0: GUC: submission enabled
+    kernel i915 0000:00:02.0: [drm] GT0: GUC: SLPC enabled
+    kernel [ 2730.991019] i915 0000:00:02.0: [drm] GPU HANG: ecode 12:1:85dfbfff, in renderThread [22381]
+    kernel [ 2730.991084] i915 0000:00:02.0: [drm] renderThread22381 context reset due to GPU hang
+```
+It mostly appears when Qemu is starting..
+
+Any help would be appreciate, thanks a lot
diff --git a/results/classifier/108/other/2725 b/results/classifier/108/other/2725
new file mode 100644
index 000000000..5da2cf389
--- /dev/null
+++ b/results/classifier/108/other/2725
@@ -0,0 +1,16 @@
+device: 0.803
+graphic: 0.648
+files: 0.532
+semantic: 0.508
+debug: 0.506
+performance: 0.481
+other: 0.406
+network: 0.378
+PID: 0.343
+vnc: 0.276
+permissions: 0.245
+boot: 0.092
+socket: 0.085
+KVM: 0.013
+
+multi-arch build at AMD64 for ARM64 fails without flag "F"
diff --git a/results/classifier/108/other/2726 b/results/classifier/108/other/2726
new file mode 100644
index 000000000..b1c5b2829
--- /dev/null
+++ b/results/classifier/108/other/2726
@@ -0,0 +1,16 @@
+device: 0.801
+performance: 0.694
+graphic: 0.552
+network: 0.514
+permissions: 0.496
+semantic: 0.450
+other: 0.279
+PID: 0.212
+boot: 0.204
+debug: 0.201
+socket: 0.135
+files: 0.092
+vnc: 0.049
+KVM: 0.004
+
+please make qemu-img capable of using with pipes
diff --git a/results/classifier/108/other/2727 b/results/classifier/108/other/2727
new file mode 100644
index 000000000..f0f222064
--- /dev/null
+++ b/results/classifier/108/other/2727
@@ -0,0 +1,16 @@
+network: 0.890
+device: 0.802
+debug: 0.529
+vnc: 0.496
+graphic: 0.455
+boot: 0.368
+PID: 0.353
+semantic: 0.262
+socket: 0.222
+files: 0.162
+performance: 0.139
+other: 0.105
+permissions: 0.032
+KVM: 0.008
+
+`Debian testing` (2024-12-16) - `qemu-system-x86_64 9.2.0` : bug with the `virtio-net` and a DHCP connection with a virtual bridge.
diff --git a/results/classifier/108/other/2728 b/results/classifier/108/other/2728
new file mode 100644
index 000000000..78bfcf9d4
--- /dev/null
+++ b/results/classifier/108/other/2728
@@ -0,0 +1,30 @@
+graphic: 0.876
+device: 0.610
+performance: 0.383
+socket: 0.375
+semantic: 0.346
+boot: 0.287
+permissions: 0.257
+PID: 0.234
+other: 0.184
+vnc: 0.163
+network: 0.160
+debug: 0.123
+files: 0.088
+KVM: 0.020
+
+QEMU/Virt-Manager + QXL 4k Resolution + Win 10 and Win 11 Guest freeze
+Description of problem:
+I use two 4k displays in my VM with 150% display scaling. After a random amount of time the screen locks up. It can lock up before i can log in or it can wait a few minutes into using it before it stops responding. It still pings but is unresponsive via the display. I've tried several different builds of the guest drivers but that did not work, the only solution has been to revert to QEMU v9.0.2-1.
+Steps to reproduce:
+1.Create new x86 VM using QXl video, Install Windows 10 or Windows 11 and latest guest drivers from spice and fedora
+2.Open with virt viewer and resize both screens to 3840 x 2160 or use autosize 
+3.Set display scaling to 150%
+4.Lockup occurs at some point after that but not more than 5 minutes.
+Additional information:
+There seems to be a similar bug here:https://gitlab.com/qemu-project/qemu/-/issues/1628#note_214460662
+also a debian forum post here: https://forums.debian.net/viewtopic.php?t=160631
+QEMU v9.0.2-1 does not have this problem, eliminating the guest drivers as a culprit
+
+
+/label ~"kind::Bug"