This is an archived copy of the Xen.org mailing list, which we have preserved to ensure that existing links to archives are not broken. The live archive, which contains the latest emails, can be found at http://lists.xen.org/
Home Products Support Community News


RE: [Xen-devel] X11 on domU

To: "Julian Davison" <julian-xen_devel@xxxxxxxxxxxxxxxxxxx>, <xen-devel@xxxxxxxxxxxxxxxxxxx>
Subject: RE: [Xen-devel] X11 on domU
From: "Ian Pratt" <m+Ian.Pratt@xxxxxxxxxxxx>
Date: Tue, 29 Aug 2006 22:23:52 +0100
Delivery-date: Tue, 29 Aug 2006 14:24:17 -0700
Envelope-to: www-data@xxxxxxxxxxxxxxxxxx
List-help: <mailto:xen-devel-request@lists.xensource.com?subject=help>
List-id: Xen developer discussion <xen-devel.lists.xensource.com>
List-post: <mailto:xen-devel@lists.xensource.com>
List-subscribe: <http://lists.xensource.com/cgi-bin/mailman/listinfo/xen-devel>, <mailto:xen-devel-request@lists.xensource.com?subject=subscribe>
List-unsubscribe: <http://lists.xensource.com/cgi-bin/mailman/listinfo/xen-devel>, <mailto:xen-devel-request@lists.xensource.com?subject=unsubscribe>
Sender: xen-devel-bounces@xxxxxxxxxxxxxxxxxxx
Thread-index: AcbLqUbjgArm7iHzQdCyG9x5QXntpQABrEZQ
Thread-topic: [Xen-devel] X11 on domU
> It results in a leap forward, but still falls short :)
> I did need the VGA BIOS (0x277FFF) which results in
> X starting up(ish) but displaying a black screen with
> a white square near the middle, then stalling.
> A ctrl-C in the starting terminal causes X to exit,
> with the error:
> -------------- copy of end of X log starts --------------
> Error in I810WaitLpRing(), now is 1534883518, start is 1534881517
> pgetbl_ctl: 0x0 pgetbl_err: 0x10
> ipeir: 0 iphdr: 0
> LP ring tail: 40 head: 0 len: f001 start 342000
> eir: 0 esr: 10 emr: 3d
> instdone: ff7a instpm: 0
> memmode: 4 instps: c10
> hwstam: 9ac7 ier: 0 imr: 9ac7 iir: 0
> space: 65464 wanted 65528
> Fatal server error:
> lockup

This is pretty weird. I wander if its relying on an interrupt that isn't
getting plumbed through? Is there any mention of an interrupt in the X
startup logs? Please could you post these.

[In fact, how does the X server get hold an interrupt from user space
(hence enabling it to block)? ]

Does the i810 driver cause any nasty kernel modules to be loaded such as
agpgart or something? The domU would need to be given access rights to
the GART, but I can't immediately think why it wouldn't work. Obviously,
the GART couldn't be shared between domU's.

One other option might be to try and use the fbdev driver in the kernel
(and X's fbdev module) rather than X's i810 driver.

Xen-devel mailing list

<Prev in Thread] Current Thread [Next in Thread>