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


Re: [Xen-devel] 2.6.38 (FC15) with PCI passthrough fails mysteriously wi

To: Konrad Rzeszutek Wilk <konrad.wilk@xxxxxxxxxx>
Subject: Re: [Xen-devel] 2.6.38 (FC15) with PCI passthrough fails mysteriously with iommu=soft..
From: Pasi Kärkkäinen <pasik@xxxxxx>
Date: Thu, 2 Jun 2011 23:49:14 +0300
Cc: Paolo Bonzini <pbonzini@xxxxxxxxxx>, "xen-devel@xxxxxxxxxxxxxxxxxxx" <xen-devel@xxxxxxxxxxxxxxxxxxx>, Laszlo Ersek <lersek@xxxxxxxxxx>
Delivery-date: Thu, 02 Jun 2011 13:49:55 -0700
Envelope-to: www-data@xxxxxxxxxxxxxxxxxxx
In-reply-to: <20110601181317.GA2455@xxxxxxxxxxxx>
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: <4DE60EF8.5060902@xxxxxxxxxx> <4DE61C2A.2000006@xxxxxxxxxx> <20110601143100.GE4081@xxxxxxxxxxxx> <4DE677C6.6040701@xxxxxxxxxx> <20110601181317.GA2455@xxxxxxxxxxxx>
Sender: xen-devel-bounces@xxxxxxxxxxxxxxxxxxx
User-agent: Mutt/1.5.18 (2008-05-17)
On Wed, Jun 01, 2011 at 02:13:17PM -0400, Konrad Rzeszutek Wilk wrote:
> On Wed, Jun 01, 2011 at 07:32:54PM +0200, Laszlo Ersek wrote:
> > On 06/01/11 16:31, Konrad Rzeszutek Wilk wrote:
> > >On Wed, Jun 01, 2011 at 01:02:02PM +0200, Laszlo Ersek wrote:
> > >>(Perhaps it's best to write a separate mail about this.)
> > >
> > >Yes. You did use 'iommu=soft' on your bootup line right?
> > 
> > I thought I did; turns out I was wrong. Sorry for the noise.
> > 
> > Now I tried with "iommu=soft swiotlb=force", but this way the guest
> You don't need the swiotlb=force. I wonder what page talks about that?
> The Wiki mentions it is only required for older kernels - not the new ones.
> > immediately disappears; it doesn't even start to produce console
> It probably was panicing b/c it couldn't swizzle out 64MB
> of DMA32 memory. You can find that out if you do 'earlyprintk=xenboot' and
> that should print out the bootlog in your Xen debug console (if you have
> configured guest_loglvl=all).
> You can also do 'swiotlb=1024' to lower the amount. .. which should have 
> worked,
> except that I found it does not work - so try this patch:
> https://lkml.org/lkml/2011/6/1/554
> Also, you can set this parameter in you guest file to analyze its stack:
> on_crash="preserve"
> using xenctx.

xenctx usage is described here:

-- Pasi

Xen-devel mailing list

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