Bug 692178 - Kernel does not display X properly when run in Xen Dom0
Summary: Kernel does not display X properly when run in Xen Dom0
Keywords:
Status: CLOSED WONTFIX
Alias: None
Product: Fedora
Classification: Fedora
Component: kernel
Version: 15
Hardware: Unspecified
OS: Unspecified
unspecified
unspecified
Target Milestone: ---
Assignee: Kernel Maintainer List
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2011-03-30 15:57 UTC by W. Michael Petullo
Modified: 2011-06-02 04:16 UTC (History)
5 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2011-06-02 04:16:20 UTC
Type: ---


Attachments (Terms of Use)

Description W. Michael Petullo 2011-03-30 15:57:57 UTC
Description of problem:
kernel-2.6.38-1.fc15.x86_64 does not work with a range of graphics hardware when booted in Xen Dom0 (the same hardware works fine with the kernel on bare metal). Michael Young's recent Xen-patched kernel fixs this problem. Michael applies patches from the Xen team that are not yet in Linus' kernel. See also http://lists.fedoraproject.org/pipermail/xen/2011-January/005322.html.

Version-Release number of selected component (if applicable):
kernel-2.6.38-1.fc15.x86_64

How reproducible:
Every time

Steps to Reproduce:
My machine has a graphics adapter that it identified as "02:00.0 VGA compatible controller: nVidia Corporation GeForce 9400M (rev b1)." Boot the kernel in Xen Dom0 on this hardware.
  
Actual results:
System begins booting, but display freezes as X loads.

Expected results:
X should load when the kernel is run in Xen Dom0.

Additional info:
This blocks a Fedora feature: http://fedoraproject.org/wiki/Features/XenPvopsDom0

Comment 1 W. Michael Petullo 2011-06-02 04:16:20 UTC
kernel-2.6.39-0.fc15.x86_64 works fine. I don't expect this kernel to make Fedora 15, but it should be sufficient for Fedora 16. I will close this bug as "won't fix" as the XenPvopsDom0 feature has been punted to Fedora 16.


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