[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

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


  • To: "Stefan Bauer" <stefan.bauer@xxxxxxxxxxx>
  • From: "Ross Philipson" <Ross.Philipson@xxxxxxxxxx>
  • Date: Wed, 29 Oct 2008 15:50:38 -0400
  • Cc: xen-devel@xxxxxxxxxxxxxxxxxxx
  • Delivery-date: Wed, 29 Oct 2008 12:51:41 -0700
  • List-id: Xen developer discussion <xen-devel.lists.xensource.com>
  • Thread-index: Ack5/k/I/NZazrQKQneQJ9Ljfk/0cQAAI6jg
  • Thread-topic: [Xen-devel] iommu: mapping reserved region failed - Q35 -VT-DIssue

For rebuilding the xen part - the messages are coming out of the
hypervisor. E.g:

xen-unstable.hg/xen/make install debug=y

Ross

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

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

_______________________________________________
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


 


Rackspace

Lists.xenproject.org is hosted with RackSpace, monitoring our
servers 24x7x365 and backed by RackSpace's Fanatical Support®.