diff options
Diffstat (limited to 'results/classifier/118/graphic/1596')
| -rw-r--r-- | results/classifier/118/graphic/1596 | 50 |
1 files changed, 50 insertions, 0 deletions
diff --git a/results/classifier/118/graphic/1596 b/results/classifier/118/graphic/1596 new file mode 100644 index 00000000..27dea8d5 --- /dev/null +++ b/results/classifier/118/graphic/1596 @@ -0,0 +1,50 @@ +graphic: 0.997 +device: 0.943 +semantic: 0.905 +vnc: 0.898 +virtual: 0.896 +performance: 0.829 +debug: 0.805 +architecture: 0.799 +ppc: 0.757 +network: 0.710 +hypervisor: 0.636 +register: 0.606 +mistranslation: 0.540 +permissions: 0.539 +arm: 0.535 +PID: 0.499 +assembly: 0.497 +user-level: 0.423 +socket: 0.419 +peripherals: 0.379 +risc-v: 0.315 +boot: 0.303 +x86: 0.253 +files: 0.221 +kernel: 0.210 +VMM: 0.200 +TCG: 0.156 +i386: 0.106 +KVM: 0.020 + +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: + + +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: |