Bug 1353593

Summary: ovirt-guest-agent QXL issue
Product: [Fedora] Fedora Reporter: ahauser <alexis.hauser>
Component: spice-vdagentAssignee: Christophe Fergeau <cfergeau>
Status: CLOSED EOL QA Contact: Fedora Extras Quality Assurance <extras-qa>
Severity: unspecified Docs Contact:
Priority: unspecified    
Version: 24CC: alexis.hauser, alon, cfergeau, marcandre.lureau, sandmann, vfeenstr, virt-maint
Target Milestone: ---   
Target Release: ---   
Hardware: x86_64   
OS: Linux   
Whiteboard:
Fixed In Version: Doc Type: If docs needed, set a value
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2017-08-08 15:26:10 UTC Type: Bug
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Embargoed:

Description ahauser 2016-07-07 14:00:14 UTC
Description of problem:

When running Fedora 24 as a guest in RHEV-3.6, using SPICE QXL (from the ovirt-quest-agent package), the windows resize doesn't adapt screen display correctly (and the refresh for it is extremely slow)

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

ovirt-guest-agent-common-1.0.11-2.fc24.3.noarch


How reproducible:
Everytime

Steps to Reproduce:
1. Run Fedora 24 as guest on RHEV
2. Install ovirt-guest-agent
3. Try to resize the window
4. Check dmesg error messages

Actual results:

The windows resize doesn't adapt the screen resolution (in remote-viewer, i.e.) and it extremely slow.
Some errors concerning QXL are shown in dmesg (see additionnal info)

Expected results:

The window resize should adapt to screen resolution and should be faster, like i.e. on rhel7/centOS7 guests.

Additional info:

Please tell me if you need additional logs/informations

Here is the dmesg output :

[   29.324498] input: spice vdagent tablet as /devices/virtual/input/input5
[   87.570570] input: spice vdagent tablet as /devices/virtual/input/input6
[   94.076640] nf_conntrack: automatic helper assignment is deprecated and it will be removed soon. Use the iptables CT target to attach helpers instead.
[   96.480563] qxl 0000:00:02.0: object_init failed for (4620288, 0x00000002)
[   96.480571] [drm:qxl_gem_object_create [qxl]] *ERROR* Failed to allocate GEM object (4619520, 2, 4096, -12)
[   96.480574] [drm:qxl_alloc_surf_ioctl [qxl]] *ERROR* qxl_alloc_surf_ioctl: failed to create gem ret=-12
[  114.374394] qxl 0000:00:02.0: object_init failed for (8302592, 0x00000002)
[  114.374403] [drm:qxl_gem_object_create [qxl]] *ERROR* Failed to allocate GEM object (8302080, 2, 4096, -12)
[  114.374406] [drm:qxl_alloc_surf_ioctl [qxl]] *ERROR* qxl_alloc_surf_ioctl: failed to create gem ret=-12
[  153.165540] qxl 0000:00:02.0: object_init failed for (4923392, 0x00000002)
[  153.165548] [drm:qxl_gem_object_create [qxl]] *ERROR* Failed to allocate GEM object (4920320, 2, 4096, -12)
[  153.165551] [drm:qxl_alloc_surf_ioctl [qxl]] *ERROR* qxl_alloc_surf_ioctl: failed to create gem ret=-12

Comment 1 Vinzenz Feenstra [evilissimo] 2016-07-11 07:09:01 UTC
The ovirt-guest-agent is irrelevant to this feature and it is implemented by the spice-vdagent 

Please ensure it is installed and if it is please report the version. Thanks.

Comment 2 ahauser 2016-07-11 07:47:06 UTC
spice-vdagent-0.16.0-3.fc24.x86_64 is installed

Comment 3 Christophe Fergeau 2016-07-11 08:56:16 UTC
Are you using gnome 3 as a desktop environment or something different?

Comment 4 ahauser 2016-07-11 09:59:43 UTC
Yes, I use default, which seems to be gnome-3
The desktop reactivity seems a bit faster with ovirt-guest-agent-gdm-plugin, however, the video display still doesn't adapt to windows resize.

I think the video memory size parameter is the source of that dmesg error I pasted you. Is there a way to edit this parameter manually using rhev ?

Comment 5 ahauser 2016-07-20 09:53:42 UTC
(In reply to Christophe Fergeau from comment #3)
> Are you using gnome 3 as a desktop environment or something different?

I also tried with lightdm + xfce and the same error is shown in dmesg. However, the behavior of xfce is different : it only doesn't change display settings.

Actually I can confirm it depends of vram_size parameter : with 8MB, the error message appear in dmesg and the following bug happens, with 33MB, no error.

Comment 6 Christophe Fergeau 2017-01-24 15:26:03 UTC
8MB is very low indeed, 33MB sounds better.

Comment 7 Fedora End Of Life 2017-07-25 21:39:07 UTC
This message is a reminder that Fedora 24 is nearing its end of life.
Approximately 2 (two) weeks from now Fedora will stop maintaining
and issuing updates for Fedora 24. It is Fedora's policy to close all
bug reports from releases that are no longer maintained. At that time
this bug will be closed as EOL if it remains open with a Fedora  'version'
of '24'.

Package Maintainer: If you wish for this bug to remain open because you
plan to fix it in a currently maintained version, simply change the 'version'
to a later Fedora version.

Thank you for reporting this issue and we are sorry that we were not
able to fix it before Fedora 24 is end of life. If you would still like
to see this bug fixed and are able to reproduce it against a later version
of Fedora, you are encouraged  change the 'version' to a later Fedora
version prior this bug is closed as described in the policy above.

Although we aim to fix as many bugs as possible during every release's
lifetime, sometimes those efforts are overtaken by events. Often a
more recent Fedora release includes newer upstream software that fixes
bugs or makes them obsolete.

Comment 8 Fedora End Of Life 2017-08-08 15:26:10 UTC
Fedora 24 changed to end-of-life (EOL) status on 2017-08-08. Fedora 24 is
no longer maintained, which means that it will not receive any further
security or bug fix updates. As a result we are closing this bug.

If you can reproduce this bug against a currently maintained version of
Fedora please feel free to reopen this bug against that version. If you
are unable to reopen this bug, please file a new report against the
current release. If you experience problems, please add a comment to this
bug.

Thank you for reporting this bug and we are sorry it could not be fixed.