Comparing the spice debug logs, where I see this with QEMU 4.0.0 without the bug:
(remote-viewer:19270): GSpice-DEBUG: 00:05:21.201: channel-display.c:1979 display-2:0: received new monitors config from guest: n: 1/4 (remote-viewer:19270): GSpice-DEBUG: 00:05:21.201: channel-display.c:1997 display-2:0: monitor id: 0, surface id: 0, +0+0-1024x768 I see this with QEMU 4.1.0 with the bug: (remote-viewer:19896): GSpice-DEBUG: 00:07:40.019: channel-display.c:1975 display-2:0: received empty monitor config (remote-viewer:19896): GSpice-DEBUG: 00:07:40.049: channel-cursor.c:542 cursor-4:0: cursor_handle_reset, init_done: 1 (remote-viewer:19896): GSpice-DEBUG: 00:07:40.049: channel-display.c:1951 display-2:0: 0: FIXME primary destroy, but is display really disabled? -- You received this bug notification because you are a member of qemu- devel-ml, which is subscribed to QEMU. https://bugs.launchpad.net/bugs/1843151 Title: Regression: QEMU 4.1.0 qxl and KMS resoluiton only 4x10 Status in QEMU: New Bug description: Host is Arch Linux. linux 5.2.13, qemu 4.1.0. virt-viewer 8.0. Guest is Arch Linux Sept 2019 ISO. linux 5.2.11. Have replicated this both on a system using amdgpu and one using integrated ASPEED graphics. Downgrading from 4.1.0 to 4.0.0 works as usual, see: https://www.youtube.com/watch?v=NyMdcYwOCvY Going back to 4.1.0 reproduces, see: https://www.youtube.com/watch?v=H3nGG2Mk6i0 4.1.0 displays fine until KMS kicks in. Using 4.1.0 with virtio-vga doesn't cause this. To manage notifications about this bug go to: https://bugs.launchpad.net/qemu/+bug/1843151/+subscriptions
