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/
Home Products Support Community News


[Xen-users] Re: About swiotlb and " ...PCI-DMA: Out of SW-IOMMU..."error

To: xen-users@xxxxxxxxxxxxxxxxxxx
Subject: [Xen-users] Re: About swiotlb and " ...PCI-DMA: Out of SW-IOMMU..."error
From: "Shaun R." <mailinglists@xxxxxxxxxxxxxxxx>
Date: Thu, 6 Dec 2007 12:24:56 -0800
Delivery-date: Thu, 06 Dec 2007 12:33:28 -0800
Envelope-to: www-data@xxxxxxxxxxxxxxxxxx
In-reply-to: <1196952716.5725.11.camel@miriam>
List-help: <mailto:xen-users-request@lists.xensource.com?subject=help>
List-id: Xen user discussion <xen-users.lists.xensource.com>
List-post: <mailto:xen-users@lists.xensource.com>
List-subscribe: <http://lists.xensource.com/cgi-bin/mailman/listinfo/xen-users>, <mailto:xen-users-request@lists.xensource.com?subject=subscribe>
List-unsubscribe: <http://lists.xensource.com/cgi-bin/mailman/listinfo/xen-users>, <mailto:xen-users-request@lists.xensource.com?subject=unsubscribe>
References: <1196952716.5725.11.camel@miriam>
Sender: xen-users-bounces@xxxxxxxxxxxxxxxxxxx
I have the same problem with xen 3.1 and adding swiotlb=128 to my grub conf just caused xen to crash/panic. Not only that but this problem killed my dom0 root partition forcing all of the data into /lost+found which is oh so much fun. The only solution i've found to stopping this from happening is to force dom0 to use less than 2GB of ram. In my case i forced my dom0 to use 1024MB of ram leaving the rest (around 15GB) on vacation. Not a big deal since before 3.1 i always forced dom0 to use only 1024MB of ram anyway leaving the rest for the domU's.

I'm running 3ware 9560 controllers btw too if it matters.


Xen-users mailing list