On Wed, Nov 10, 2010 at 1:16 PM, Sander Eikelenboom
<linux@xxxxxxxxxxxxxx> wrote:
Hello David,
My suggestions would be:
- use pciback.hide=(03:01.0) option on the kernel line in your bootloader, to seize the device, so dom0 never initializes it.
you mean "pciback.hide=(03:01.0)" going into Dom0 kernel line and on which one:
My grub.conf looks like this:
title CentOS (2.6.18-194.17.4.el5xen)
root (hd0,0)
kernel /xen.gz-3.4.3 dom0_mem=1024M physdev_dom0_hide=(03:01.0) iommu=verbose loglvl=all guest_loglvl=all
module /vmlinuz-2.6.18-194.17.4.el5xen ro root=/dev/gw/root console=hvc0 earlyprintk=xen nomodeset
module /initrd-2.6.18-194.17.4.el5xen.img
- Why do you use the "@1" in your domU config and not just pci=['03:01.0'] ?
Well thst' nothing, I was reading on XEN's pvops kernel docs that you can arbitrarily assign the device to a specific virtual slot.
- I personally always use the passthrough option for pciback when compiling the dom0 kernel, but i don't think that matters much, although perhaps not everything plays nice with a device on 0000:00:00.0
Well I havrn't messed up with kernel compilation, I would like pv_ops kernel so I played a bit with that but not with this 2.6.18, would have to do some research on it.