howto hide pci devices?

[Mike Wright]

Hi all,

Using 3.8.1-201.fc18.x86_64

This kernel has xen-pciback available only as a module so adding it to 
the kernel command line doesn't work.

I added a file:

   /etc/modprobe.d/xen-pciback.conf

that contains one line:

   options xen-pciback hide=(00:14.2)(01:05.1)

thinking that would accomplish the same thing but it doesn't work for me.

Following a reboot lspci shows the devices are still there.

Am I missing a step or is recompiling the kernel the only alternative?

TIA

[Tom Horsley]

On Mon, 11 Mar 2013 12:15:47 -0700
Mike Wright wrote:

>  Am I missing a step or is recompiling the kernel the only
> alternative? 
I don't know if this works, but often you have to re-run
dracut so stuff like this gets copied into the initrd.

[Dario Faggioli]

On lun, 2013-03-11 at 15:54 -0400, Tom Horsley wrote:
>  On Mon, 11 Mar 2013 12:15:47 -0700
>  Mike Wright wrote:
>  
>  > Am I missing a step or is recompiling the kernel the only alternative?
>  
>  I don't know if this works, but often you have to re-run
>  dracut so stuff like this gets copied into the initrd.
>  
Yes, I'm not an expert of initial ramdisks either, but I'd at least
recommend rebuilding the initrd.

Also, as Konrad is saying, I don't think one should expect for the
device to disappear from lspci's output... It's just the driver that
handles them which is different.

Independently from lspci, what happens if you try to start a VM with one
of those devices assigned?

Dario

-- 
<<This happens because I choose it to happen!>> (Raistlin Majere)
-----------------------------------------------------------------
Dario Faggioli, Ph.D, http://about.me/dario.faggioli
Senior Software Engineer, Citrix Systems R&D Ltd., Cambridge (UK)

[Pasi Kärkkäinen]

On Wed, Mar 13, 2013 at 12:03:28PM +0100, Dario Faggioli wrote:
>  On lun, 2013-03-11 at 15:54 -0400, Tom Horsley wrote:
>  > On Mon, 11 Mar 2013 12:15:47 -0700
>  > Mike Wright wrote:
>  > 
>  > > Am I missing a step or is recompiling the kernel the only alternative?
>  > 
>  > I don't know if this works, but often you have to re-run
>  > dracut so stuff like this gets copied into the initrd.
>  >
>  Yes, I'm not an expert of initial ramdisks either, but I'd at least
>  recommend rebuilding the initrd.
>  
>  Also, as Konrad is saying, I don't think one should expect for the
>  device to disappear from lspci's output... It's just the driver that
>  handles them which is different.
>   
Yeah, if you do "lspci -vvv" you'll see that driver in use changes to
xen-pciback.

-- Pasi

[Konrad Rzeszutek Wilk]

On Mon, Mar 11, 2013 at 12:15:47PM -0700, Mike Wright wrote:
>  Hi all,
>  
>  Using 3.8.1-201.fc18.x86_64
>  
>  This kernel has xen-pciback available only as a module so adding it
>  to the kernel command line doesn't work.
>  
>  I added a file:
>  
>    /etc/modprobe.d/xen-pciback.conf
>  
>  that contains one line:
>  
>    options xen-pciback hide=(00:14.2)(01:05.1)
>  
>  thinking that would accomplish the same thing but it doesn't work for me. 
The purpose of the hide is for the initial domain drivers to not usurp
the devices. Meaning that they do not load and use the drivers.

>  
>  Following a reboot lspci shows the devices are still there.
>   
Right. They will be present in the initial domain. They are just not
in usage.

>  Am I missing a step or is recompiling the kernel the only
> alternative?
>  
>  TIA
>  --
>  xen mailing list
>  xen(a)lists.fedoraproject.org
>  https://admin.fedoraproject.org/mailman/listinfo/xen