Bug 117727 - X does not work in Xen
Summary: X does not work in Xen
Status: RESOLVED WONTFIX
Alias: None
Product: SUSE LINUX 10.0
Classification: openSUSE
Component: X.Org (show other bugs)
Version: RC 1
Hardware: i686 SUSE Other
: P5 - None : Major
Target Milestone: ---
Assignee: Stefan Dirsch
QA Contact: Stefan Dirsch
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2005-09-19 08:40 UTC by Michael Schwartzkopff
Modified: 2005-10-17 11:03 UTC (History)
0 users

See Also:
Found By: Other
Services Priority:
Business Priority:
Blocker: ---
Marketing QA Status: ---
IT Deployment: ---

Attachments
Add an attachment (proposed patch, testcase, etc.)

Note You need to log in before you can comment on or make changes to this bug.
Description Michael Schwartzkopff 2005-09-19 08:40:34 UTC 
In installed Xen from the scratch together with the normal kernel. I configured
my system during installation and everything works quite good. Then I rebooted
into Xen and X did not start any more. Symtom: Monitor does not sync any more.

I tried to reconfigure my system under Xen but neither yast2 nor sax2 work. Even
connecting  to the system from an exteral system with ssh -X, calling yast2 and
entering standard values (800x600, 65k colors) does not work. Just no output
from the grafics card.

System: Celeron 1.2 GHz, ATI Tech. Rage 128 PF, Sony 20sfII monitor.
Installed: Basic grafics, (plain X), no KDE, No gnome.

Please feel free to contact me for further information.
Comment 1 Stefan Dirsch 2005-09-19 08:50:37 UTC 
Kurt any experiences with X under Xen?
Comment 2 Kurt Garloff 2005-10-05 20:41:19 UTC 
Stephan, some graphics cards work, others don't. 
 
My ATI works, even including 3D acceleration: 
01:00.0 VGA compatible controller: ATI Technologies Inc Radeon Mobility M7 LW 
[Radeon Mobility 7500] 
 
I fixed up most of the DRM and AGP code in kernel, typical errors are using 
remap_page_range() instead of io_remap_page_range() and confusing bus and 
phys addresses (which happen to be identical on plain x86 and x86_64 but NOT 
on other arches nor on Xen).  
 
What kind of beast is Rage128PF? Does it use agpgart?  
If not, it may have it's own DMA routines in userspace which may have exactly 
the bus vs. phys issue.
Comment 3 Stefan Dirsch 2005-10-05 21:09:23 UTC 
Rage128 *can* use agpgart and drm for 2D and 3D acceleration, when 3D is 
configured, i.e. Load "dri" is specified in /etc/X11/xorg.conf. Therefore I 
would like to see /etc/X11/xorg.conf and /var/log/Xorg.0.log attached. 
Michael, could you provide these? Thanks.
Comment 4 Stefan Dirsch 2005-10-12 13:16:50 UTC 
Still waiting for feedback by the reporter.
Comment 5 Stefan Dirsch 2005-10-17 11:03:35 UTC 
No feedback --> WONTFIX.