From mboxrd@z Thu Jan 1 00:00:00 1970 From: Stefan Bauer Subject: Re: iommu: mapping reserved region failed - Q35 - VT-D Issue Date: Wed, 29 Oct 2008 20:15:53 +0100 Message-ID: <4908B669.7080108@cubewerk.de> References: <49089D18.4030405@cubewerk.de> <409D32C55C48D34DB5E31C8AB29EB15B071C6E25@FTLPEXCH05.citrite.net> Mime-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-15 Content-Transfer-Encoding: 7bit Return-path: In-Reply-To: <409D32C55C48D34DB5E31C8AB29EB15B071C6E25@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: > 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