summaryrefslogtreecommitdiffstats
path: root/results/classifier/zero-shot/108/none/498039
diff options
context:
space:
mode:
Diffstat (limited to 'results/classifier/zero-shot/108/none/498039')
-rw-r--r--results/classifier/zero-shot/108/none/49803933
1 files changed, 33 insertions, 0 deletions
diff --git a/results/classifier/zero-shot/108/none/498039 b/results/classifier/zero-shot/108/none/498039
new file mode 100644
index 00000000..0216e415
--- /dev/null
+++ b/results/classifier/zero-shot/108/none/498039
@@ -0,0 +1,33 @@
+device: 0.575
+graphic: 0.476
+vnc: 0.330
+semantic: 0.258
+network: 0.252
+other: 0.244
+PID: 0.229
+socket: 0.148
+debug: 0.102
+permissions: 0.091
+performance: 0.091
+boot: 0.072
+files: 0.069
+KVM: 0.053
+
+No copy/paste with VNC display with Windows guest
+
+There is no copy/paste functionality between a Windows guest and the VNC client. This is a significant usability problem.
+
+One work-around is to run VNC inside of the guest. But that appears to have more overhead than qemu's VNC display.
+
+Obviously, qemu's VNC display is just a display device and knows absolutely nothing about the Windows clipboard. Thus, to interface with the guest's clipboard would require a helper app running in the guest that can hook into qemu. This would probably be the best solution.
+
+There are probably not a lot of qemu developers interested in trying to write the helper app. Not exactly an interesting job. But since it is a significant usability problem, and many users would see this as a major oversight, I suggest leaving this bug open long-term as a hint so that some volunteer later looking for something to do might take pity on everyone and write this helper app.
+
+The qxl display and vdagent running in guest do just this.
+
+Unfortunately, the options needed in qemu command line to make vdagent work with the spice client do not seem to be documented anywhere.
+
+see bug 1452742
+
+Right, this problem should be fixed with Spice, so I'm closing this ticket now.
+