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] X under dom0

To: Daisaku Watanabe <masakichi@xxxxxxxxxxxxxxxxxx>
Subject: Re: [Xen-devel] X under dom0
From: Ian Pratt <Ian.Pratt@xxxxxxxxxxxx>
Date: Sun, 15 Aug 2004 20:52:30 +0100
Cc: xen-devel@xxxxxxxxxxxxxxxxxxxxx, Ian.Pratt@xxxxxxxxxxxx
Delivery-date: Sun, 15 Aug 2004 20:54:25 +0100
Envelope-to: steven.hand@xxxxxxxxxxxx
In-reply-to: Your message of "Mon, 16 Aug 2004 03:07:03 +0900." <20040816030703.3bb63bcc.masakichi@xxxxxxxxxxxxxxxxxx>
List-archive: <http://sourceforge.net/mailarchive/forum.php?forum=xen-devel>
List-help: <mailto:xen-devel-request@lists.sourceforge.net?subject=help>
List-id: List for Xen developers <xen-devel.lists.sourceforge.net>
List-post: <mailto:xen-devel@lists.sourceforge.net>
List-subscribe: <https://lists.sourceforge.net/lists/listinfo/xen-devel>, <mailto:xen-devel-request@lists.sourceforge.net?subject=subscribe>
List-unsubscribe: <https://lists.sourceforge.net/lists/listinfo/xen-devel>, <mailto:xen-devel-request@lists.sourceforge.net?subject=unsubscribe>
Sender: xen-devel-admin@xxxxxxxxxxxxxxxxxxxxx
> X (Xorg-x11) fails under dom0 (unstable-tree) on my environment.
> If it works for me, it's very appreciated.
> <Symptom>
>  - X fails with the message 
>   ...(snip)
>   (II) VESA(0): initializing int10
>   (EE) VESA(0): Cannot map SYS BIOS

The VESA Xorg/xfree86 driver is not currently supported under
Xen/Linux. Most chipset specific drivers should work fine, and
typically work better anyhow.

Support VESA drivers doesn't work for two reasons: 1) it tries to
map pages in the bottom megabyte of machine memory, and 2) it
needs to make call backs to the BIOS. #1 is trivially
implemented, and it might make sense for dom0 to have access to
the bottom megabyte of machine memory for other reasons
(e.g. ACPI). I don't know enough about the mechanism used for
protected mode BIOS calls to know how best to implement them, but
I suspect we'd have to bounce them via Xen. 

Anyhow, can you try a chipset specific driver?


SF.Net email is sponsored by Shop4tech.com-Lowest price on Blank Media
100pk Sonic DVD-R 4x for only $29 -100pk Sonic DVD+R for only $33
Save 50% off Retail on Ink & Toner - Free Shipping and Free Gift.
Xen-devel mailing list

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