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

[Xen-devel] Option iommu=1 causes hypervisor to start debugger

To: xen-devel@xxxxxxxxxxxxxxxxxxx
From: Alexia Benington <alexbenington@xxxxxxxxx>
Date: Mon, 2 Feb 2009 16:16:20 -0500
Delivery-date: Mon, 02 Feb 2009 13:18:46 -0800
Domainkey-signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=mime-version:date:message-id:subject:from:to:content-type :content-transfer-encoding; b=BjTzvyX1cBsLL+ls0SZLzYBTk4Fp10FZaqGnOfCPg0rjJXJYupVFCYt7ZAKejc7Dkp oD1EiZ20KowVCob7VqSSLzvUqteI9XwpwrVLIOzT/ThJooNVxL2T5KAaX5ttHABWeT/u KH+Cmx+hcJ7/4CFe7lZWkdZwqR3ediNu5HK7g=
List-id: Xen developer discussion <xen-devel.lists.xensource.com>

Hi,

In changeset 19130:c8962b24fb50, when using iommu=1, it goes into the
hypervisor debugger. Why is this so? Thanks.

-Alex

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

Follow-Ups:
- Re: [Xen-devel] Option iommu=1 causes hypervisor to start debugger
  - From: Keir Fraser

Prev by Date: Re: [Xen-devel] pv_ops dom0 kernel failure with ata_piix / irq problems
Next by Date: Re: [Xen-devel] pv_ops dom0 kernel failure with ata_piix / irq problems
Previous by thread: [Xen-devel] FW: Xen 3.3.0 - QEMU COW disk image with sparse backing file - VM fails to start
Next by thread: Re: [Xen-devel] Option iommu=1 causes hypervisor to start debugger
Index(es):
- Date
- Thread

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