diff options
Diffstat (limited to 'gitlab/issues/target_missing/host_missing/accel_missing/1596.toml')
| -rw-r--r-- | gitlab/issues/target_missing/host_missing/accel_missing/1596.toml | 28 |
1 files changed, 0 insertions, 28 deletions
diff --git a/gitlab/issues/target_missing/host_missing/accel_missing/1596.toml b/gitlab/issues/target_missing/host_missing/accel_missing/1596.toml deleted file mode 100644 index 0a2ca555e..000000000 --- a/gitlab/issues/target_missing/host_missing/accel_missing/1596.toml +++ /dev/null @@ -1,28 +0,0 @@ -id = 1596 -title = "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)" -state = "opened" -created_at = "2023-04-12T18:55:47.369Z" -closed_at = "n/a" -labels = [] -url = "https://gitlab.com/qemu-project/qemu/-/issues/1596" -host-os = "Fedora 37" -host-arch = "x86_64" -qemu-version = "QEMU emulator version 7.0.0 (qemu-7.0.0-15.fc37)" -guest-os = "Fedora 37" -guest-arch = "x86_64" -description = """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: - -""" -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 = """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:""" |