Hey, On Mon, Oct 23, 2017 at 09:51:51AM +0200, Javier Celaya wrote: > Hello list, > > Recently, we updated the Qemu version being used by flexVDI. We were > using a pre-3.3 QXL device, so it did not provide the > client_monitors_config callback and that message was getting through to > the VDAgent, which in turn changed the resolution of the guest. This > was working flawlessly both on Windows and Linux guests. > > With the new version (we are using qemu v2.6.0 from RHEV 7.3 and spice- > server v0.12.8 from RHEL 7.4, with a couple of small changes), the > client_monitors_config callback gets called. This works correctly on > Windows guests, but on Linux guests (tested mainly with Fedora 25, > stock vdagent and QXL Xorg driver, which are quite up to date) the > following happens when a resolution change is requested by the client: > - The new resolution is detected by the Xorg server, it can be seen > with xrandr. > - If the old resolution was a custom one, the display changes to the > new one. > - If the old resolution was a standard one (like 640x480, 1024x768, > 1920x1080, etc), the display DOES NOT change to the new one. > I have read quickly through the list archive but found nothing about > this problem. Is there something we are missing? Something else we > should be upgrading too? With client-monitors-config, the qxl-kms driver is going to notify of resolution changes through a hotplug-mode-update drm property. It then needs cooperation from the window manager to react to this property change. See https://bugzilla.gnome.org/show_bug.cgi?id=711216 and https://git.gnome.org/browse/mutter/commit/?id=9575132 How are you triggering the resolution change to a standard resolution? Which window manager/desktop environment are you running in the VM? Christophe
Attachment:
signature.asc
Description: PGP signature
_______________________________________________ Spice-devel mailing list Spice-devel@xxxxxxxxxxxxxxxxxxxxx https://lists.freedesktop.org/mailman/listinfo/spice-devel