add gitlab issues in toml format

1 files changed, 22 insertions, 0 deletions

diff --git a/gitlab/issues/target_missing/host_missing/accel_missing/1841.toml b/gitlab/issues/target_missing/host_missing/accel_missing/1841.toml
new file mode 100644
index 000000000..d53890633
--- /dev/null
+++ b/gitlab/issues/target_missing/host_missing/accel_missing/1841.toml
@@ -0,0 +1,22 @@
+id = 1841
+title = "qemu version with 7.2.5 or earlier than 7.2.5 with nvme disk has  I/O QID 22 timeout, Aborting errors"
+state = "closed"
+created_at = "2023-08-23T06:08:43.486Z"
+closed_at = "2024-04-07T14:11:02.515Z"
+labels = ["VFIO"]
+url = "https://gitlab.com/qemu-project/qemu/-/issues/1841"
+host-os = "CentOS Linux release 8.4.2105"
+host-arch = "X86"
+qemu-version = "7.2.5"
+guest-os = "CentOS Linux release 7.7.1908 (Core)"
+guest-arch = "x86"
+description = """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)"""
+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"""
+additional = "n/a"