Bug 449386 - xen sdl frame buffer broken under pv
xen sdl frame buffer broken under pv
Status: CLOSED CURRENTRELEASE
Product: Fedora
Classification: Fedora
Component: xen (Show other bugs)
8
All Linux
low Severity low
: ---
: ---
Assigned To: Markus Armbruster
Fedora Extras Quality Assurance
:
Depends On:
Blocks:
  Show dependency treegraph
 
Reported: 2008-06-02 11:36 EDT by Michael Young
Modified: 2008-11-26 12:37 EST (History)
3 users (show)

See Also:
Fixed In Version: F8
Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of:
Environment:
Last Closed: 2008-11-26 12:37:42 EST
Type: ---
Regression: ---
Mount Type: ---
Documentation: ---
CRM:
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---


Attachments (Terms of Use)

  None (edit)
Description Michael Young 2008-06-02 11:36:57 EDT
If I uncomment the vfb = [ 'type=sdl' ] line in my guests configuration file in
/etc/xen and start it it pauses for a long time then gives the error
Error: Device 0 (vkbd) could not be connected. Hotplug scripts not working.
in xend.log there is the line
DEBUG (vfbif:9) Spawn ['/usr/lib/xen/bin/xen-sdlfb']
which I believe indicates the problem since this file is no longer in the xen
package (this is with xen-3.1.2-2.fc8)

[As an aside I tried rebuilding the xen-3.2.0-10 package from fedora 9 on this
machine and stealing a xen.gz file from fedora 9. With this the boot succeeded
but it launched a vnc console rather than an sdl one.]
Comment 1 Michael Young 2008-06-02 12:24:20 EDT
As a follow up to the aside, xen-3.2.1 does do sdl again (based on taking the
xen-3.2.0-10.fc9 source package and the 3.2.1 tar ball, and editing the spec
file to change the base_version and hv_build settings (since I might as well
have a new hypervisor) and commenting out Patches 9, 16 and 17, then building it
on Fedora 8).
Comment 2 Bug Zapper 2008-11-26 05:48:43 EST
This message is a reminder that Fedora 8 is nearing its end of life.
Approximately 30 (thirty) days from now Fedora will stop maintaining
and issuing updates for Fedora 8.  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 '8'.

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 8'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 8 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 3 Jon Stanley 2008-11-26 12:37:42 EST
As this bug is in MODIFIED, Fedora believes that a fix has been committed that resolves the problem listed in this bug report.

If this is not the case, please re-open this report, noting the version of the package that you reproduced the bug against.

Thanks for the report!

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