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

["Devdutt Patnaik" <xendevid@xxxxxxxxx>]

I tried to hide my 2nd NIC too from Dom0 using Xen 3.2.1 with the appropriate entries in modprobe.conf but it didnt work.
I reverted back to using Xen 3.1 where it worked fine.

I'd like to know how this goes with 3.2.1.

-Devdutt.

On Fri, Aug 22, 2008 at 6:06 AM, --[ UxBoD ]-- <uxbod@xxxxxxxxxxxx> 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
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 ?


Regards,

--
--[ UxBoD ]--
// PGP Key: "curl -s http://www.splatnix.net/uxbod.asc | gpg --import"
// Fingerprint: F57A 0CBD DD19 79E9 1FCC A612 CB36 D89D 2C5A 3A84
// Keyserver: www.keyserver.net Key-ID: 0x2C5A3A84
// Phone: +44 845 869 2749 SIP Phone: uxbod@xxxxxxxxxxxxxxxx

--
This message has been scanned for viruses and
dangerous content by MailScanner, and is
believed to be clean.


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

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