add deepseek and gemma results

1 files changed, 21 insertions, 0 deletions

diff --git a/results/classifier/gemma3:12b/vnc/1596 b/results/classifier/gemma3:12b/vnc/1596
new file mode 100644
index 000000000..4293c4dc6
--- /dev/null
+++ b/results/classifier/gemma3:12b/vnc/1596
@@ -0,0 +1,21 @@
+
+VNC console with 4K resolutions is cut off on the right side and mouse coordinates are offset (or horizontal res greater than 2600-3000 pixels)
+Description of problem:
+For some reason when connecting to the VNC console of a QEMU VM, when you use a resolution that has its horizontal size of about 3000 pixels or more, it gets cut off by about 1/4 of the screen from the right, and the mouse position is offset by that value towards the left. See image for explanation:
+
+![QEMU_2023-04-12_12-18](/uploads/42311339ffb1048e5d4b5e45ce25e529/QEMU_2023-04-12_12-18.png)
+Steps to reproduce:
+1. Create a Fedora 37 VM
+2. Use `virtio-vga-gl` and `egl-headless`
+3. Set the resolution to 4K (3840x2160) or anything with the horizontal resolution greater than 3000 pixels
+4. Use Windows to connect to the VNC console. Issue happens with TightVNC Viewer and RealVNC Viewer
+Additional information:
+I also tried `-device virtio-vga-gl,edid=off,xres=3840,yres=2160`. Same result, but `edid=off` helps to make 2560x1600 appear, making it bearable.
+
+This also happens with Wayland and Xorg.
+
+Please note that while it's possible to use Gnome's Screen Sharing (RDP/VNC) options, as well as NoMachine or other options, this is an undesirable behavior in QEMU's VNC server/console that should be fixed (and can, the VNC protocol perfectly supports 4K without issues)
+
+Not to mention that, at least in my use case, the VNC console is faster than the alternatives, even SPICE (connecting from Windows is barely unusable at 4K res - it's a bliss from Linux. Both cases from a remote machine in the same LAN, but that is unrelated to this bug).
+
+I would happily try different use cases to try to help nail down this bug :smile: