From mboxrd@z Thu Jan  1 00:00:00 1970
From: Konrad Rzeszutek Wilk <konrad.wilk@oracle.com>
Subject: Re: PCI passthrough issue
Date: Fri, 25 Feb 2011 09:40:35 -0500
Message-ID: <20110225144035.GA7228@dumpdata.com>
References: <4D4BBEC6.8070809@jbfavre.org> <4D4BD121.2080505@jbfavre.org>
	<1296817460.13091.646.camel@zakaz.uk.xensource.com>
	<4D4BE212.1090400@jbfavre.org>
	<1296818935.13091.648.camel@zakaz.uk.xensource.com>
	<4D4BFBE4.6080809@jbfavre.org>
	<1296827449.13091.670.camel@zakaz.uk.xensource.com>
	<4D4C06BB.8010907@jbfavre.org> <4D52658E.9060907@jbfavre.org>
	<4D5EE125.6040208@jbfavre.org>
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Return-path: <xen-devel-bounces@lists.xensource.com>
Content-Disposition: inline
In-Reply-To: <4D5EE125.6040208@jbfavre.org>
List-Unsubscribe: <http://lists.xensource.com/mailman/listinfo/xen-devel>,
	<mailto:xen-devel-request@lists.xensource.com?subject=unsubscribe>
List-Post: <mailto:xen-devel@lists.xensource.com>
List-Help: <mailto:xen-devel-request@lists.xensource.com?subject=help>
List-Subscribe: <http://lists.xensource.com/mailman/listinfo/xen-devel>,
	<mailto:xen-devel-request@lists.xensource.com?subject=subscribe>
Sender: xen-devel-bounces@lists.xensource.com
Errors-To: xen-devel-bounces@lists.xensource.com
To: xen-devel@lists.xensource.com, Jean Baptiste Favre <xen-devel@jbfavre.org>
List-Id: xen-devel@lists.xenproject.org

On Fri, Feb 18, 2011 at 10:14:13PM +0100, Jean Baptiste Favre wrote:
> Hello,
> Back online after my exams :)
> 
> Had some time to perform tests with my Debian Squeeze 32bits domU and
> 2.6.37 kernel from experimental.

I am bit lost now.. Can you refresh my memory whether the 'copy_break'
parameter worked or not?

Experimental is the stock kernel or was that a new proposed kernel?
Where are the sources for the experimental kernel?

> DomU config is:
> *****************************************************************
> kernel       = '/cluster/kernels/vmlinuz-2.6.37-trunk-686-bigmem'
> ramdisk      = '/cluster/kernels/initrd.img-2.6.37-trunk-686-bigmem'
> #kernel       = '/cluster/kernels/vmlinuz-2.6.37-trunk-686-bigmem-sky2'
> #ramdisk      = '/cluster/kernels/initrd.img-2.6.37-trunk-686-bigmem-sky2'
> builder      = 'linux'
> memory=268
> vcpus        = '1'
> cpus         = '2'
> localtime    = 0
> serial       = 'pty'
> boot         = 'cdn'
> disk         = [ 'drbd:xps-106,xvda,w' ]
> on_poweroff  = 'destroy'
> on_reboot    = 'restart'
> on_crash     = 'restart'
> name         = 'xps-106'
> hostname     = 'xps-106.clichy.jbfavre.org'

I had a box with a sky2 adapter that looked to have a similar issue but
found the culprit to be the switch. So at this point I am having no luck
reproducing this. Would it be possible for you to stick the kernel + dist
image somewhere so I can try it out on my box?

> 
> extra = "root=/dev/mapper/xps--106-root ro iommu=soft swiotlb=force
> console=hvc0 xencons=tty"

Try without 'swiotlb=force' on any kernel that is PVOPS. Only the older
ones (lenny) required that. And you don't need 'xencons=tty' either with
PVOPS kernels.