From mboxrd@z Thu Jan 1 00:00:00 1970 From: Stefan Bauer Subject: Re: iommu: mapping reserved region failed - Q35 - VT-DIssue Date: Wed, 29 Oct 2008 20:40:44 +0100 Message-ID: <4908BC3C.3070307@cubewerk.de> References: <49089D18.4030405@cubewerk.de><409D32C55C48D34DB5E31C8AB29EB15B071C6E25@FTLPEXCH05.citrite.net> <4908B669.7080108@cubewerk.de> <409D32C55C48D34DB5E31C8AB29EB15B071C6E74@FTLPEXCH05.citrite.net> Mime-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-15 Content-Transfer-Encoding: 7bit Return-path: In-Reply-To: <409D32C55C48D34DB5E31C8AB29EB15B071C6E74@FTLPEXCH05.citrite.net> List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Sender: xen-devel-bounces@lists.xensource.com Errors-To: xen-devel-bounces@lists.xensource.com Cc: xen-devel@lists.xensource.com List-Id: xen-devel@lists.xenproject.org Ross Philipson schrieb: > I meant rebuild xen with debug=y. There is a bunch of tracing in the > routines that are trying to setup the context mapping that indicate what > is going on including tracing out what device it was dealing with when > things failed. Also (as mentioned in another email just sent), we can > enhance that logging in these routines to see if the hardware remapping > unit is missing for this device or something related. debug=y can just be applied right after make linux-2.6-xen-build? or where do i supply that debug=y ? > Also again I was curious - it seems the failure trace you reported below > was during dom0 boot - is this true? Yes it's all during dom0 booting. -- Stefan