Note: This is a beta release of Red Hat Bugzilla 5.0. The data contained within is a snapshot of the live data so any changes you make will not be reflected in the production Bugzilla. Also email is disabled so feel free to test any aspect of the site that you want. File any problems you find or give feedback here.
Bug 1365717 - Spice Guest's resolution doesn't update after login the guest
Summary: Spice Guest's resolution doesn't update after login the guest
Status: NEW
Alias: None
Product: Red Hat Enterprise Linux 8
Classification: Red Hat
Component: virt-viewer
Version: 8.1
Hardware: x86_64
OS: Unspecified
Target Milestone: rc
: 8.1
Assignee: Jonathon Jongsma
QA Contact: Virtualization Bugs
Depends On:
TreeView+ depends on / blocked
Reported: 2016-08-10 02:39 UTC by Xiaodai Wang
Modified: 2019-04-10 12:03 UTC (History)
9 users (show)

Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Last Closed:
Type: Bug
Target Upstream Version:

Attachments (Terms of Use)
debug & spice debug for the issue (deleted)
2016-08-10 10:13 UTC, Pavel Grunt
no flags Details

Description Xiaodai Wang 2016-08-10 02:39:35 UTC
Description of problem:
Spice Guest's resolution doesn't update after login the guest

Version-Release number of selected component (if applicable):

How reproducible:

Steps to Reproduce:
1. Prepare a spice guest(I'm using RHEL7) and make sure spice-vdagentd service is running.
2. Open the guest by "virt-viewer -f $guest", then the guest will opened in fullscreen mode and the resolution is updated to adapt real physical monitors resolution.
3. Keep the guest in fullscreen mode, and modify the guest's resolution manually in system settings. For example, set it to 800x600.
4. Close the guest window and destroy the guest.
5. Restart the guest.
6. Open the guest by "virt-viewer -f $guest" and login.

Actual results:
After login, The guest's resolution is not updated to real physical monitors resolution but still keep the value which is set in step3 (800x600).

Expected results:
The guest's resolution should update to real physical monitor's resolution.

Additional info:

Comment 1 Pavel Grunt 2016-08-10 10:13:04 UTC
Created attachment 1189546 [details]
debug & spice debug for the issue

Comment 2 Pavel Grunt 2016-08-10 10:21:16 UTC
From the debug:
(virt-viewer:19659): virt-viewer-DEBUG: Performing full screen auto-conf, 2 host monitors
(virt-viewer:19659): virt-viewer-DEBUG: Set SPICE display 0 to (0,0)-(1920x1080)
(virt-viewer:19659): virt-viewer-DEBUG: Set SPICE display 1 to (1920,0)-(1920x1080)
(virt-viewer:19659): GSpice-DEBUG: channel-main.c:1160 main-1:0: sending new monitors config to guest
(virt-viewer:19659): GSpice-DEBUG: channel-main.c:1177 main-1:0: monitor #0: 1920x1080+0+0 @ 32 bpp
(virt-viewer:19659): GSpice-DEBUG: channel-main.c:1177 main-1:0: monitor #1: 1920x1080+1920+0 @ 32 bpp
(virt-viewer:19659): GSpice-DEBUG: channel-display.c:1713 display-2:0: received new monitors config from guest: n: 2/4
(virt-viewer:19659): GSpice-DEBUG: channel-display.c:1733 display-2:0: monitor id: 0, surface id: 0, +0+0-1920x1080
(virt-viewer:19659): GSpice-DEBUG: channel-display.c:1733 display-2:0: monitor id: 1, surface id: 0, +1920+120-1280x960

There is a race, virt-viewer sends correct size request, but the guest also sends its current display config. It is not a regression, mostlikely changes will be required in other spice components. Lets investigate it for 7.4.

Comment 3 David Blechter 2018-12-10 18:00:52 UTC
Moving to rhel 8

Comment 4 David Blechter 2019-04-10 12:01:03 UTC

Comment 5 David Blechter 2019-04-10 12:01:20 UTC

Note You need to log in before you can comment on or make changes to this bug.