From mboxrd@z Thu Jan 1 00:00:00 1970 From: Manuel Bernhardt Subject: Re: Problem access hardware with xen 3.0 unstable Date: Sat, 08 Oct 2005 12:49:27 +0200 Message-ID: <4347A437.3020600@prodigy7.de> References: <4346E3E6.6090507@prodigy7.de> <33c739e861969414035002017fb56184@cl.cam.ac.uk> <43479BEC.2020302@prodigy7.de> <6d32c7c140ca5de53b58065cd01c4d48@cl.cam.ac.uk> Mime-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Return-path: In-Reply-To: <6d32c7c140ca5de53b58065cd01c4d48@cl.cam.ac.uk> List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Sender: xen-devel-bounces@lists.xensource.com Errors-To: xen-devel-bounces@lists.xensource.com To: Keir Fraser Cc: xen-devel@lists.xensource.com List-Id: xen-devel@lists.xenproject.org It's ok so - i think stabilisation and domU interface freezes for production use in the industrie is a "little bit" more important like my problems which appears during "home use" of xen :-) manuel Keir Fraser schrieb: > > I'm afraid so. We currently have no interface for unprivileged domains > to access PCI space. If we gave a domU unfettered access to PCI space > and BIOS tables there would be a big conflict betwene that domain and > domain0. > > This isn't going to be very hard to fix, but stabilisation and domU > interface freezes come first. > > -- Keir >