add gitlab issues in toml format

1 files changed, 26 insertions, 0 deletions

diff --git a/gitlab/issues/target_missing/host_missing/accel_missing/807.toml b/gitlab/issues/target_missing/host_missing/accel_missing/807.toml
new file mode 100644
index 00000000..a6d2d874
--- /dev/null
+++ b/gitlab/issues/target_missing/host_missing/accel_missing/807.toml
@@ -0,0 +1,26 @@
+id = 807
+title = "TigerVNC client to built-in VNC server causes VM to crash/freeze"
+state = "closed"
+created_at = "2022-01-08T19:59:36.970Z"
+closed_at = "2022-02-28T18:19:16.043Z"
+labels = ["GUI"]
+url = "https://gitlab.com/qemu-project/qemu/-/issues/807"
+host-os = "n/a"
+host-arch = "n/a"
+qemu-version = "n/a"
+guest-os = "n/a"
+guest-arch = "n/a"
+description = """Connecting to the built-in VNC server via TigerVNC upon disconnect the whole VM process freezes/crashes. The process continues to exist but does not respond to any network connection and the monitor socket is dead too. Killing it with TERM doesn't work.
+
+Using tigervnc-viewer 1.10.1+dfsg-3 (Ubuntu 20.04) with default options like `vncviwer localhost:0`"""
+reproduce = """* `qemu-system-x86_64 -vnc 127.0.0.1:0`
+ * Connect to built-in VNC server via TigerVNC 
+ * Keep the VNC connection open and wait some period of time (usually 5-10 minutes is enough though sometimes hours) then disconnect/reconnect VNC. If the reconnect succeeds then wait again for a period of time then disconnect and try again until failure. Often just connecting and disconnecting to the VNC once is enough to make the VM eventually crash/freeze even if running only in the background but this is less reproducible.
+ * Observe VM is no longer responsive to anything
+
+If TigerVNC is never connected/disconnected from the VM then this doesn't happen."""
+additional = """Note due to the nature of this issue it might be hard to reproduce for unknown reasons. The VM always eventually freezes though. The qemu process has no output when it freezes.
+
+As far as I can tell connecting to the built-in VNC server via `gvncviwer` seems to be OK and doesn't cause an issue (?). I'm not sure about other VNC clients (eg. TurboVNC).
+
+I am connecting to the VNC server from a completely different machine than the host via SSH port redirection (the host is headless). Not sure if that matters."""