Bug 528764 - qemu's SDL backend doesn't release the console framebuffer on exit
Summary: qemu's SDL backend doesn't release the console framebuffer on exit
Keywords:
Status: CLOSED WONTFIX
Alias: None
Product: Fedora
Classification: Fedora
Component: qemu
Version: 13
Hardware: All
OS: Linux
low
medium
Target Milestone: ---
Assignee: Justin M. Forbes
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard:
Depends On:
Blocks: F12VirtTarget
TreeView+ depends on / blocked
 
Reported: 2009-10-13 16:03 UTC by Matthew Booth
Modified: 2011-06-27 14:26 UTC (History)
12 users (show)

Fixed In Version:
Clone Of:
Environment:
Last Closed: 2011-06-27 14:26:52 UTC
Type: ---
Embargoed:


Attachments (Terms of Use)

Description Matthew Booth 2009-10-13 16:03:21 UTC
Description of problem:
Change the <graphics/> element to <graphics type='sdl'/>.
Put SELinux into permissive mode (RHBZ#528759).
Start the guest.

The guest will grab the local framebuffer as it starts. The guest's display will work fine. However, there is no longer a way to recover the local display. Powering off the guest, which has to be done in the guest itself as there is no access to any other display, does not cause the local display to be released. The only way to get a desktop back appears to be to reboot.

Version-Release number of selected component (if applicable):
libvirt-0.7.1-11.fc11.x86_64 (virt-preview on F-11)

Comment 1 Mark McLoughlin 2009-10-29 15:29:53 UTC
Okay, moving to qemu - AFAICT, the main problem here is that qemu's SDL backend is releasing the framebuffer when it shuts down

Realistically, I can't see anyone getting to this any time soon - VNC is the only graphics backend we put any effort into supporting

Comment 2 Fedora Admin XMLRPC Client 2010-03-09 16:54:32 UTC
This package has changed ownership in the Fedora Package Database.  Reassigning to the new owner of this component.

Comment 3 Fedora Admin XMLRPC Client 2010-03-09 17:20:12 UTC
This package has changed ownership in the Fedora Package Database.  Reassigning to the new owner of this component.

Comment 4 Bug Zapper 2010-03-15 12:56:28 UTC
This bug appears to have been reported against 'rawhide' during the Fedora 13 development cycle.
Changing version to '13'.

More information and reason for this action is here:
http://fedoraproject.org/wiki/BugZappers/HouseKeeping

Comment 5 Bug Zapper 2011-06-02 17:37:00 UTC
This message is a reminder that Fedora 13 is nearing its end of life.
Approximately 30 (thirty) days from now Fedora will stop maintaining
and issuing updates for Fedora 13.  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 WONTFIX if it remains open with a Fedora 
'version' of '13'.

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 prior to Fedora 13's end of life.

Bug Reporter: Thank you for reporting this issue and we are sorry that 
we may not be able to fix it before Fedora 13 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 please change the 'version' of this 
bug to the applicable version.  If you are unable to change the version, 
please add a comment here and someone will do it for you.

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.

The process we are following is described here: 
http://fedoraproject.org/wiki/BugZappers/HouseKeeping

Comment 6 Bug Zapper 2011-06-27 14:26:52 UTC
Fedora 13 changed to end-of-life (EOL) status on 2011-06-25. Fedora 13 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.

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


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