WARNING - OLD ARCHIVES

This is an archived copy of the Xen.org mailing list, which we have preserved to ensure that existing links to archives are not broken. The live archive, which contains the latest emails, can be found at http://lists.xen.org/
   
 
 
Xen 
 
Home Products Support Community News
 
   
 

xen-devel

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

To: 'Stefan Bauer' <stefan.bauer@xxxxxxxxxxx>
Subject: RE: [Xen-devel] iommu: mapping reserved region failed - Q35 -VT-DIssue
From: "Han, Weidong" <weidong.han@xxxxxxxxx>
Date: Thu, 30 Oct 2008 10:14:12 +0800
Accept-language: en-US
Acceptlanguage: en-US
Cc: "'xen-devel@xxxxxxxxxxxxxxxxxxx'" <xen-devel@xxxxxxxxxxxxxxxxxxx>
Delivery-date: Wed, 29 Oct 2008 19:14:44 -0700
Envelope-to: www-data@xxxxxxxxxxxxxxxxxxx
In-reply-to: <4908C6FC.9030307@xxxxxxxxxxx>
List-help: <mailto:xen-devel-request@lists.xensource.com?subject=help>
List-id: Xen developer discussion <xen-devel.lists.xensource.com>
List-post: <mailto:xen-devel@lists.xensource.com>
List-subscribe: <http://lists.xensource.com/mailman/listinfo/xen-devel>, <mailto:xen-devel-request@lists.xensource.com?subject=subscribe>
List-unsubscribe: <http://lists.xensource.com/mailman/listinfo/xen-devel>, <mailto:xen-devel-request@lists.xensource.com?subject=unsubscribe>
References: <49089D18.4030405@xxxxxxxxxxx><409D32C55C48D34DB5E31C8AB29EB15B071C6E25@xxxxxxxxxxxxxxxxxxxxxx><4908B669.7080108@xxxxxxxxxxx><409D32C55C48D34DB5E31C8AB29EB15B071C6E74@xxxxxxxxxxxxxxxxxxxxxx> <4908BC3C.3070307@xxxxxxxxxxx> <409D32C55C48D34DB5E31C8AB29EB15B071C6EA7@xxxxxxxxxxxxxxxxxxxxxx> <4908C6FC.9030307@xxxxxxxxxxx>
Sender: xen-devel-bounces@xxxxxxxxxxxxxxxxxxx
Thread-index: Ack6BMAZPwG+nd5mT5WF0pGcIwE3BwALscqw
Thread-topic: [Xen-devel] iommu: mapping reserved region failed - Q35 -VT-DIssue
Stefan Bauer wrote:
> Ross Philipson schrieb:
>> For rebuilding the xen part - the messages are coming out of the
>> hypervisor. E.g: 
>> 
>> xen-unstable.hg/xen/make install debug=y
> 
> Done, xenddebug.log attached.
> 
> HTH
> 
> Regards

Stefan,

xenddebug.log is not helpful. when you compile xen, pls use: make xen debug=y

or add "loglvl=all loglvl_guest=all" in grub kernel line like:
        kernel /boot/xen.gz dom0_mem=512m iommu=1 loglvl=all loglvl_guest=all

Per xm-dmesg in your another mail, I am very curious on why 
domain_context_mapping failed (which also result in failure of reserved memory 
mapping). 

Per dom0 failure info (pci_bus_probe_wapper()), which is caused by 
pci_remove_device(), I suspect the devices are not added to alldevs_list.

Pls use above method to catch more debug info, then we can analyse the info 
easily.

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

<Prev in Thread] Current Thread [Next in Thread>