summary refs log tree commit diff stats
path: root/results/classifier/gemma3:12b/hypervisor/1841
diff options
context:
space:
mode:
authorChristian Krinitsin <mail@krinitsin.com>2025-07-03 07:27:52 +0000
committerChristian Krinitsin <mail@krinitsin.com>2025-07-03 07:27:52 +0000
commitd0c85e36e4de67af628d54e9ab577cc3fad7796a (patch)
treef8f784b0f04343b90516a338d6df81df3a85dfa2 /results/classifier/gemma3:12b/hypervisor/1841
parent7f4364274750eb8cb39a3e7493132fca1c01232e (diff)
downloadqemu-analysis-d0c85e36e4de67af628d54e9ab577cc3fad7796a.tar.gz
qemu-analysis-d0c85e36e4de67af628d54e9ab577cc3fad7796a.zip
add deepseek and gemma results
Diffstat (limited to 'results/classifier/gemma3:12b/hypervisor/1841')
-rw-r--r--results/classifier/gemma3:12b/hypervisor/184113
1 files changed, 13 insertions, 0 deletions
diff --git a/results/classifier/gemma3:12b/hypervisor/1841 b/results/classifier/gemma3:12b/hypervisor/1841
new file mode 100644
index 000000000..793049fc3
--- /dev/null
+++ b/results/classifier/gemma3:12b/hypervisor/1841
@@ -0,0 +1,13 @@
+
+qemu version with 7.2.5 or earlier than 7.2.5 with nvme disk has  I/O QID 22 timeout, Aborting errors
+Description of problem:
+When I use the 7.2.5 version of qemu or versions earlier than 7.2.5 to compile and start the virtual machine, the machine has an nvme disk which is SAMSUNG MZQL23T8HCLS-00B7C and passed through by VFIO. When i use fio to perform pressure test on the nvme disk in vm, dmesg shows message like this nvme nvme0: I/O QID 22 timeout, Aborting, the picture below shows its details. Howerver, when i use 8.0.0 version of qemu to compile and start vm, and using fio to perform pressure test on the nvme disk in vm, it does not have the problem like that. I have using different kernel version, however, the probelem persists, so i think this is not a kernel issue, but a qemu problem.
+
+
+if the irqbalance is running in vm, the problem happens very often, however if the irqbalance is stopped, the problem disappear.
+
+![image](/uploads/180a13da3a29032e4f07f5eb83da959c/image.png)
+Steps to reproduce:
+1. using the 7.2.5 or versions earlier than 7.2.5 and start vm which has an nvme disk 
+2. the nvme disk is passed through by VFIO
+3. using FIO to perform pressure test on the nvme disk in vm