RHEL Engineering is moving the tracking of its product development work on RHEL 6 through RHEL 9 to Red Hat Jira (issues.redhat.com). If you're a Red Hat customer, please continue to file support cases via the Red Hat customer portal. If you're not, please head to the "RHEL project" in Red Hat Jira and file new tickets here. Individual Bugzilla bugs in the statuses "NEW", "ASSIGNED", and "POST" are being migrated throughout September 2023. Bugs of Red Hat partners with an assigned Engineering Partner Manager (EPM) are migrated in late September as per pre-agreed dates. Bugs against components "kernel", "kernel-rt", and "kpatch" are only migrated if still in "NEW" or "ASSIGNED". If you cannot log in to RH Jira, please consult article #7032570. That failing, please send an e-mail to the RH Jira admins at rh-issues@redhat.com to troubleshoot your issue as a user management inquiry. The email creates a ServiceNow ticket with Red Hat. Individual Bugzilla bugs that are migrated will be moved to status "CLOSED", resolution "MIGRATED", and set with "MigratedToJIRA" in "Keywords". The link to the successor Jira issue will be found under "Links", have a little "two-footprint" icon next to it, and direct you to the "RHEL project" in Red Hat Jira (issue links are of type "https://issues.redhat.com/browse/RHEL-XXXX", where "X" is a digit). This same link will be available in a blue banner at the top of the page informing you that that bug has been migrated.
Bug 1210362 - Hard freezes after setting maximum resolution with increased vgamem (vgamem = ram/2)
Summary: Hard freezes after setting maximum resolution with increased vgamem (vgamem =...
Keywords:
Status: CLOSED DUPLICATE of bug 1273106
Alias: None
Product: Red Hat Enterprise Linux 8
Classification: Red Hat
Component: spice-qxl-xddm
Version: ---
Hardware: Unspecified
OS: Unspecified
unspecified
low
Target Milestone: rc
: ---
Assignee: Default Assignee for SPICE Bugs
QA Contact: SPICE QE bug list
URL:
Whiteboard: spice
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2015-04-09 14:06 UTC by David Jaša
Modified: 2023-09-14 02:57 UTC (History)
10 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2015-10-28 14:41:00 UTC
Type: Bug
Target Upstream Version:
Embargoed:

Attachments (Terms of Use)
screenshot (3.12 MB, image/png)
2015-04-09 14:06 UTC, David Jaša 		no flags Details
full log with qxl debug and guest debug (668.75 KB, text/plain)
2015-04-09 14:09 UTC, David Jaša 		no flags Details
View All

Description David Jaša 2015-04-09 14:06:42 UTC 
Created attachment 1012700 [details]
screenshot

Description of problem:
I'm getting hard guest freeze when I choose resolution that approaches qxl memory limit with increased vgamem option of qxl device

Version-Release number of selected component (if applicable):
guest: win7 32b
  qxl-win 0.1-21
host: rhel 7.1
  qemu-kvm-1.5.3-86.el7_1.1.x86_64

How reproducible:
frequent

Steps to Reproduce:
1. set up qemu qxl's ram/vgamem/vram to 64/32/32 MB respectively, launch the VM
2. go to screen resolution, select 3840 * 2160, select Apply
3. if you don't see the freeze, select lower res, Apply and go back to 3840x2160

Actual results:
guest freezes in state like in the screenshot. It doesn't respond to ctrl-alt-del or similar shortcuts and qxl device log doesn't show anything suspicious either:
qxl/guest-0: 22965554321: qxldd: ReleaseOutput 0x95484170
qxl/guest-0: 22965559369: qxldd: ReleaseOutput done
qxl/guest-0: 22965632710: qxldd: AddRes
qxl/guest-0: 22965639026: qxldd: AddRes: done
qxl/guest-0: 22965644956: qxldd: WaitForCmdRing: 0xfe7ff010
qxl/guest-0: 22965650119: qxldd: DoCopy: done
qxl/guest-0: 22966744736: qxldd: DrvCopyBits
qxl/guest-0: 22966757463: qxldd: _BitBlt
qxl/guest-0: 22966762582: qxldd: __DrvBitBlt
qxl/guest-0: 22966766884: qxldd: DoCopy
qxl/guest-0: 22966772926: qxldd: GetDrawable 0x954cf450
qxl/guest-0: 22966777133: qxldd: SetClip
qxl/guest-0: 22966781610: qxldd: AddRes
qxl/guest-0: 22966785605: qxldd: AddRes: done
qxl/guest-0: 22966789624: qxldd: SetClip: done
qxl/guest-0: 22966793764: qxldd: GetBitmap
qxl/guest-0: 22966797797: qxldd: QXLGetBitmap
qxl/guest-0: 23260973926: qxldd: ReleaseOutput 0x95484250
qxl/guest-0: 23261086848: qxldd: ReleaseOutput done
// freeze


Expected results:
guest OS keeps operating


Additional info:
There is a workaround available: increase of ram region as well so it is 4 * vgamem like in the default configuration so maybe this bug needs just documentation (given the expected move to the wddm driver)

Just for the record, linux system don't freeze in this scenario (both UMS and KMS).
Comment 1 David Jaša 2015-04-09 14:09:09 UTC 
Created attachment 1012701 [details]
full log with qxl debug and guest debug
Comment 2 David Blechter 2015-06-05 11:18:20 UTC 
moving to 3.7. The resolution  > 4 mp is not currently supported in rhevm.
Comment 4 Red Hat Bugzilla Rules Engine 2015-10-20 15:36:55 UTC 
Target release should be placed once a package build is known to fix a issue. Since this bug is not modified, the target version has been reset. Please use target milestone to plan a fix for a oVirt release.
Comment 5 Sandro Bonazzola 2015-10-26 12:31:35 UTC 
this is an automated message. oVirt 3.6.0 RC3 has been released and GA is targeted to next week, Nov 4th 2015.
Please review this bug and if not a blocker, please postpone to a later release.
All bugs not postponed on GA release will be automatically re-targeted to

- 3.6.1 if severity >= high
- 4.0 if severity < high
Comment 6 Yaniv Lavi 2015-10-28 14:41:00 UTC 

*** This bug has been marked as a duplicate of bug 1273106 ***
Comment 7 David Blechter 2019-10-10 13:54:11 UTC 
moving from RHEVM product to RHEL 8
Comment 8 Red Hat Bugzilla 2023-09-14 02:57:49 UTC 
The needinfo request[s] on this closed bug have been removed as they have been unresolved for 1000 days
Note You need to log in before you can comment on or make changes to this bug.