summary refs log tree commit diff stats
path: root/gitlab/issues/target_missing/host_missing/accel_missing/1935.toml
diff options
context:
space:
mode:
authorChristian Krinitsin <mail@krinitsin.com>2025-05-21 21:21:26 +0200
committerChristian Krinitsin <mail@krinitsin.com>2025-05-21 21:21:26 +0200
commit4b927bc37359dec23f67d3427fc982945f24f404 (patch)
tree245449ef9146942dc7fffd0235b48b7e70a00bf2 /gitlab/issues/target_missing/host_missing/accel_missing/1935.toml
parentaa8bd79cec7bf6790ddb01d156c2ef2201abbaab (diff)
downloadqemu-analysis-4b927bc37359dec23f67d3427fc982945f24f404.tar.gz
qemu-analysis-4b927bc37359dec23f67d3427fc982945f24f404.zip
add gitlab issues in toml format
Diffstat (limited to 'gitlab/issues/target_missing/host_missing/accel_missing/1935.toml')
-rw-r--r--gitlab/issues/target_missing/host_missing/accel_missing/1935.toml17
1 files changed, 17 insertions, 0 deletions
diff --git a/gitlab/issues/target_missing/host_missing/accel_missing/1935.toml b/gitlab/issues/target_missing/host_missing/accel_missing/1935.toml
new file mode 100644
index 000000000..bab7f3174
--- /dev/null
+++ b/gitlab/issues/target_missing/host_missing/accel_missing/1935.toml
@@ -0,0 +1,17 @@
+id = 1935
+title = "migrate problem when add SCSI reservations with iSCSI backed disks"
+state = "opened"
+created_at = "2023-10-13T07:43:12.625Z"
+closed_at = "n/a"
+labels = ["Migration", "Storage"]
+url = "https://gitlab.com/qemu-project/qemu/-/issues/1935"
+host-os = "n/a"
+host-arch = "n/a"
+qemu-version = "n/a"
+guest-os = "n/a"
+guest-arch = "n/a"
+description = """When performing migrations with QEMU using iSCSI as the backend, it's common for the migration to start successfully. However, in scenarios where Persistent Reservations are added in the guest, the target host, under the precopy mode, preempts the Persistent Reservations right from the beginning, causing migration issues. Is there a way to control the Persistent Reservations lock within QEMU at an appropriate time, ensuring that it's only preempted during the switchover phase?
+
+Isn't libiscsi thread-safe? Can multiple threads operate on Persistent Reservations lock simultaneously?"""
+reproduce = "n/a"
+additional = "n/a"