summary refs log tree commit diff stats
path: root/results/scraper/launchpad-without-comments/1894818
diff options
context:
space:
mode:
authorChristian Krinitsin <mail@krinitsin.com>2025-06-30 12:24:58 +0000
committerChristian Krinitsin <mail@krinitsin.com>2025-06-30 12:27:06 +0000
commit33606b41d35115f887ea688b1a16f2ff85bf2fe4 (patch)
tree406b2c7b19a087ba437c68f3dbf0b589fa1d6150 /results/scraper/launchpad-without-comments/1894818
parentadedf8771bc4de3113041ca21bd4d0d1c0014b6a (diff)
downloadqemu-analysis-33606b41d35115f887ea688b1a16f2ff85bf2fe4.tar.gz
qemu-analysis-33606b41d35115f887ea688b1a16f2ff85bf2fe4.zip
add launchpad bug reports without comments
Diffstat (limited to 'results/scraper/launchpad-without-comments/1894818')
-rw-r--r--results/scraper/launchpad-without-comments/189481819
1 files changed, 19 insertions, 0 deletions
diff --git a/results/scraper/launchpad-without-comments/1894818 b/results/scraper/launchpad-without-comments/1894818
new file mode 100644
index 000000000..85e0f406a
--- /dev/null
+++ b/results/scraper/launchpad-without-comments/1894818
@@ -0,0 +1,19 @@
+COLO's guest VNC client hang after failover
+
+Hello,
+
+After setting up COLO's primary and secondary VMs,
+I installed the vncserver and xrdp (apt install tightvncserver xrdp) inside the VM.
+
+I access the VM from another PC via VNC/RDP client, and everything is OK.
+Then, kill the primary VM and issue the failover commands.
+
+The expected result is that the VNC/RDP client can resume after failover.
+But in my test, the VNC client's screen hangs and cannot be recovered no longer.
+
+BTW, it works well after killing SVM.
+
+Thanks.
+
+Regards,
+Derek
\ No newline at end of file