Bug 1273106 (spice_4k_res) - [RFE] SPICE 4K resolution support
Summary: [RFE] SPICE 4K resolution support
Keywords:
Status: CLOSED DUPLICATE of bug 1260751
Alias: spice_4k_res
Product: Red Hat Enterprise Virtualization Manager
Classification: Red Hat
Component: RFEs
Version: 3.6.0
Hardware: Unspecified
OS: Unspecified
unspecified
unspecified
Target Milestone: ovirt-4.0.0-alpha
: 4.0.0
Assignee: Scott Herold
QA Contact: Gil Klein
URL:
Whiteboard: spice
: 1210362 (view as bug list)
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2015-10-19 15:40 UTC by Andrei Stepanov
Modified: 2016-02-10 19:20 UTC (History)
17 users (show)

Fixed In Version:
Doc Type: Enhancement
Doc Text:
Clone Of:
Environment:
Last Closed: 2015-11-26 16:21:07 UTC
oVirt Team: Spice
Target Upstream Version:
Embargoed:

Attachments (Terms of Use)
virt-viewer log (35.09 KB, text/plain)
2015-10-19 15:42 UTC, Andrei Stepanov 		no flags Details
qemu-kvm with SPICE_DEBUG_LEVEL=5 (first run) (183.78 KB, text/plain)
2015-10-19 15:44 UTC, Andrei Stepanov 		no flags Details
qemu-kvm with SPICE_DEBUG_LEVEL=5 (second run) (222.90 KB, text/plain)
2015-10-19 15:44 UTC, Andrei Stepanov 		no flags Details
qemu-kvm with SPICE_DEBUG_LEVEL=5 (qxl video) (48.36 KB, text/plain)
2015-10-19 15:55 UTC, Andrei Stepanov 		no flags Details
virt-viewer log (qxl video) (127.96 KB, text/plain)
2015-10-19 15:58 UTC, Andrei Stepanov 		no flags Details
View All

Description Andrei Stepanov 2015-10-19 15:40:00 UTC 
virt-viewer with --full-screen parameter on 4k monitor doesn't update resolution of guest VM

virt-viewer v2.0-48 (Windows 7 32)

client's native resolution is: 3840x2160
virt-viewer -f spice:\\xx.xx.xx.xx:3000 -f

It works as expected on the same client/monitor with resolution 1920x1080
Comment 1 Andrei Stepanov 2015-10-19 15:42:23 UTC 
Created attachment 1084446 [details]
virt-viewer log
Comment 2 Andrei Stepanov 2015-10-19 15:44:01 UTC 
Created attachment 1084447 [details]
qemu-kvm with SPICE_DEBUG_LEVEL=5 (first run)
Comment 3 Andrei Stepanov 2015-10-19 15:44:54 UTC 
Created attachment 1084449 [details]
qemu-kvm with SPICE_DEBUG_LEVEL=5 (second run)
Comment 4 Andrei Stepanov 2015-10-19 15:53:39 UTC 
Host is:
kernel-3.10.0-323.el7.x86_64
spice-server-0.12.4-15.el7.x86_64

Guest is:
spice-vdagent-0.14.0-10.el7
xorg-x11-drv-qxl-0.1.1-18-el7
Comment 5 Andrei Stepanov 2015-10-19 15:55:08 UTC 
Created attachment 1084452 [details]
qemu-kvm with SPICE_DEBUG_LEVEL=5 (qxl video)
Comment 7 Andrei Stepanov 2015-10-19 15:58:27 UTC 
Created attachment 1084453 [details]
virt-viewer log (qxl video)
Comment 8 Andrei Stepanov 2015-10-19 16:02:57 UTC 
Switching from window mode, using menu View->Full Screen also is broken.
Resolutions stays the same as it was for window mode.
Comment 9 Pavel Grunt 2015-10-20 06:17:58 UTC 
the client is virt-viewer v2.0-48 (Windows 7 32), changing product & component to rhevm
Comment 10 Pavel Grunt 2015-10-20 06:23:26 UTC 
How the VM was created?

Most likely it doesn't have enough memory for the 4k resolution. In that case the RHEL guest fallbacks to the previous used resolution.
Comment 12 Andrei Stepanov 2015-10-20 10:03:46 UTC 
Changing from

<model type='qxl' ram='65536' vram='65536' vgamem='16384' heads='1'/>

to

<model type='qxl' ram='131072' vram='131072' vgamem='32768' heads='1'/>

-vga qxl -global qxl-vga.ram_size=134217728 -global qxl-vga.vram_size=134217728 -global qxl-vga.vgamem_mb=32

Allows to go in 4k full screen mode
Comment 13 Yaniv Kaul 2015-10-20 10:28:00 UTC 
(In reply to Andrei Stepanov from comment #12)
> Changing from
> 
> <model type='qxl' ram='65536' vram='65536' vgamem='16384' heads='1'/>
> 
> to
> 
> <model type='qxl' ram='131072' vram='131072' vgamem='32768' heads='1'/>
> 
> -vga qxl -global qxl-vga.ram_size=134217728 -global
> qxl-vga.vram_size=134217728 -global qxl-vga.vgamem_mb=32
> 
> Allows to go in 4k full screen mode

Was it tested? What's the overall performance of a VM with more graphics memory? What's the graphics performance?
Can it be migrated, for example?
Comment 17 Yaniv Lavi 2015-10-28 14:41:00 UTC 
*** Bug 1210362 has been marked as a duplicate of this bug. ***
Comment 18 Yaniv Kaul 2015-11-26 16:21:07 UTC 

*** This bug has been marked as a duplicate of bug 1260751 ***
Note You need to log in before you can comment on or make changes to this bug.