summaryrefslogtreecommitdiffstats
path: root/results/classifier/105/boot/997
diff options
context:
space:
mode:
Diffstat (limited to 'results/classifier/105/boot/997')
-rw-r--r--results/classifier/105/boot/99730
1 files changed, 0 insertions, 30 deletions
diff --git a/results/classifier/105/boot/997 b/results/classifier/105/boot/997
deleted file mode 100644
index a6e80f9a..00000000
--- a/results/classifier/105/boot/997
+++ /dev/null
@@ -1,30 +0,0 @@
-boot: 0.873
-device: 0.846
-instruction: 0.791
-graphic: 0.705
-semantic: 0.678
-vnc: 0.662
-network: 0.568
-other: 0.449
-mistranslation: 0.425
-socket: 0.372
-assembly: 0.304
-KVM: 0.204
-
-Iothread is stuck at 100% CPU usage with virtio-scsi on QEMU 7.0.0
-Description of problem:
-Starting with QEMU 7.0.0, the iothread associated attached to a virtio-scsi controller is stuck at 100% CPU usage. Bisected to: https://gitlab.com/qemu-project/qemu/-/commit/826cc32423db2a99d184dbf4f507c737d7e7a4ae
-
-- Works as expected without the iothread
-- No issue with virtio-blk + iothread
-- Same behavior regardless of io=threads/native/io_uring
-- Same behavior with default vs increased queue count
-- The issue is triggered when the guest OS initializes the virtio driver
-Steps to reproduce:
-1. Add virtio-scsi controller with iothread
-2. Boot VM
-3. Check per-thread CPU usage such as in htop
-Additional information:
-[fedora.log](/uploads/776fbf8e5b823d0ab326946684ef9022/fedora.log)
-
-[fedora.xml](/uploads/54879e5adfb227ddef79d382e86fc608/fedora.xml)