WARNING - OLD ARCHIVES

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/
   
 
 
Xen 
 
Home Products Support Community News
 
   
 

xen-devel

[Xen-devel] DMI and other BIOS hooks

To: <xen-devel@xxxxxxxxxxxxxxxxxxx>
Subject: [Xen-devel] DMI and other BIOS hooks
From: "King, Steven R" <steven.r.king@xxxxxxxxx>
Date: Tue, 26 Jul 2005 11:11:52 -0700
Delivery-date: Tue, 26 Jul 2005 18:26:40 +0000
Envelope-to: www-data@xxxxxxxxxxxxxxxxxxx
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: AcWRSZApBFRebCSETWmdUWOZlIIlzgArwEXAAARYALA=
Thread-topic: DMI and other BIOS hooks
Hi Folks,
Can someone please offer an explanation or pointer to docs for how Xen
maps BIOS facilities into guest space?  Specifically, I have a DMI BIOS
problem that is causing Xen to call domain_crash() on Dom0 during
boot-up.

Here's a few specific questions:
1) Does Xen map the platform's 0xF0000-0xFFFFF BIOS space to guests, or
is this region virtualized?
2) If virtualized, how Xen map BIOS facilities to guests?

In my case, Dom0 finds the _DMI_ entry point, which appears to overlap
with physical RAM.  This ultimately causes the domain_crash() for Dom0.
Looks like a bad BIOS, but I'm unclear as to the degree which Xen plays
man-in-the-middle.

Any thoughts are most appreciated.

Thanks for your time,
-steve




_______________________________________________
Xen-devel mailing list
Xen-devel@xxxxxxxxxxxxxxxxxxx
http://lists.xensource.com/xen-devel

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