WARNING - OLD ARCHIVES

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/
   
 
 
Xen 
 
Home Products Support Community News
 
   
 

xen-users

Re: [Xen-users] Xen 3.2.1 and PCI passthrough

To: uxbod@xxxxxxxxxxxx
Subject: Re: [Xen-users] Xen 3.2.1 and PCI passthrough
From: Sadique Puthen <sputhenp@xxxxxxxxxx>
Date: Mon, 25 Aug 2008 00:03:42 +0530
Cc: xen-users@xxxxxxxxxxxxxxxxxxx
Delivery-date: Sun, 24 Aug 2008 11:35:45 -0700
Envelope-to: www-data@xxxxxxxxxxxxxxxxxxx
In-reply-to: <25459266.131219399570289.JavaMail.root@xxxxxxxxxxxxxxxxxxx>
List-help: <mailto:xen-users-request@lists.xensource.com?subject=help>
List-id: Xen user discussion <xen-users.lists.xensource.com>
List-post: <mailto:xen-users@lists.xensource.com>
List-subscribe: <http://lists.xensource.com/mailman/listinfo/xen-users>, <mailto:xen-users-request@lists.xensource.com?subject=subscribe>
List-unsubscribe: <http://lists.xensource.com/mailman/listinfo/xen-users>, <mailto:xen-users-request@lists.xensource.com?subject=unsubscribe>
References: <25459266.131219399570289.JavaMail.root@xxxxxxxxxxxxxxxxxxx>
Sender: xen-users-bounces@xxxxxxxxxxxxxxxxxxx
User-agent: Thunderbird 2.0.0.14 (X11/20080501)
--[ UxBoD ]-- wrote:
> Hi,
>
> Have just brought a Digium TDM400P card for my Asterisk server but appear to 
> be having trouble getting it to be hidden from DOM-0.  Here is what dmesg 
> shows :-
>
> pciback 0000:02:07.0: Driver tried to write to a read-only configuration 
> space field at offset 0x44, size 2. This may be harmless, but if you have 
> problems with your device:
> 1) see permissive attribute in sysfs
> 2) report problems to the xen-devel mailing list along with details of your 
> device obtained from lspci.
> PCI: Enabling device 0000:02:07.0 (0000 -> 0003)
> ACPI: PCI Interrupt 0000:02:07.0[A] -> GSI 26 (level, low) -> IRQ 20
> ACPI: PCI interrupt for device 0000:02:07.0 disabled
> pciback: vpci: 0000:02:07.0: assign to virtual slot 0
> PCI: Enabling device 0000:02:07.0 (0000 -> 0003)
>
> and from the lspci :-
>
> 02:07.0 Network controller: Tiger Jet Network Inc. Tiger3XX Modem/ISDN 
> interface
>       Subsystem: Unknown device b100:0001
>       Flags: bus master, medium devsel, latency 64, IRQ 20
>       I/O ports at a800 [size=256]
>       Memory at fc7ff000 (32-bit, non-prefetchable) [size=4K]
>       Capabilities: [40] Power Management version 2
>
> In my rc.local I have the following :-
>
> modprobe pciback
> sleep 2
> SLOT=0000:02:07.0
>   

You missed.

echo -n $SLOT > /sys/bus/pci/drivers/<driver>/unbind

> echo -n $SLOT > /sys/bus/pci/drivers/pciback/new_slot
> echo -n $SLOT > /sys/bus/pci/drivers/pciback/bind
>
> Does this look okay ? or should I contact the devel list ?
>   

You better need to use your /etc/modprobe.conf to hide the device while
pciback module is loaded to the kernel. I have the below two lines in my
/etc/modprobe.conf to hid a broadcom network card which uses bnx2 driver.

install bnx2 /sbin/modprobe pciback ; /sbin/modprobe --first-time
--ignore-install bnx2
options pciback hide=(0000:09:00.0) verbose_request=1

--Sadique

>
> Regards,
>
>   


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