RE: [Xen-devel] iommu: mapping reserved region failed - Q35 - VT-DIssue

["Ross Philipson" <Ross.Philipson@xxxxxxxxxx>]

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.

Also again I was curious - it seems the failure trace you reported below
was during dom0 boot - is this true?

Thanks
Ross

-----Original Message-----
From: xen-devel-bounces@xxxxxxxxxxxxxxxxxxx
[mailto:xen-devel-bounces@xxxxxxxxxxxxxxxxxxx] On Behalf Of Stefan Bauer
Sent: Wednesday, October 29, 2008 3:16 PM
Cc: xen-devel@xxxxxxxxxxxxxxxxxxx
Subject: Re: [Xen-devel] iommu: mapping reserved region failed - Q35 -
VT-DIssue

Ross Philipson schrieb:
> Stefan,
> 
> So those errors happened during booting DOM0 and then you checked xm
> dmesg, correct? Then you started a 2k VM and the system reset. Can you
> rebuild xen with debug=y, you might get more information about why the
> context mapping is failing. We could also put some more trace in there
> to see exactly what happens. 

I only found PCI Backend Debugging in the Xen menue which i
activacted, rebuild kernel and did again xm dmesg without further
informations. Do i have to activate it additionally?

> Can you attach a serial cable and send the output from xen and dom0 to
> COM1 or something like that? There may be some relevant information
> traced out right before the reset that you are not seeing (it is
> probably a crash in xen that is resetting the system).

I'll try it if my laptop becomes available (women...)

-- 

Stefan


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

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