Re: [Xen-devel] PCI passthrough issue

[Konrad Rzeszutek Wilk <konrad.wilk@xxxxxxxxxx>]

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.

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