Re: [Fedora-xen] Problem assigning a usb or pci port to a domU

Hi,

Looks like default config disables PCI passthrough, 
you can turn it on manually.
see
 http://article.gmane.org/gmane.comp.emulators.xen.user/16007

Thanks,
Yoshi
--
"Pascal Parrot" <pascal_parrot(a)hotmail.com&gt; wrotec:
>  Hi,
>  I am (re)posting this here as I haven't had much luck on the xen user 
>  mailing list.
>  I am using FC5 and xen 3.0.2 (what comes with yum).
>  
>  I am trying to assign a pci or usb port to a domU. I get to the point  
where 
>  pciback seizes the devices (5 usb and 2 pci) by modifying the 
>  /etc/modprobe.conf configuration as explained in 
>  http://wiki.xensourccom/xenwiki/Assign_hardware_to_DomU_with_PCIBack_as_m....
>  
>  I then modified the configuration of the domU with pci = [ '00:1d.0' , 
>  '00:1d.1' , '00:1d.2' , '00:1d.3' , '00:1d.7',
> '02:01.0' , '02:02.0' ]  
but 
>  nothing shows up in the domU. I also tried adding the parameter in
> the 
>  command line (xm create domu pci=...).
>  
>  [root@web ~]# lsusb
>  [root@web ~]# lspci
>  pcilib: Cannot open /proc/bus/pci
>  lspci: Cannot find any working access method.
>  [root@web ~]#
>  
>  How can I make the domU recognize the two LAN interfaces and 2 usb  
devices 
>  (usb drive and ethernet interface) plugged in? Could it be that these
>
>  devices do not have drivers? How can I check/fix that?
>  
>  Here is part of the dmesg
>  pciback 0000:00:1d.0: seizing device
>  pciback 0000:00:1d.1: seizing device
>  pciback 0000:00:1d.2: seizing device
>  pciback 0000:00:1d.3: seizing device
>  pciback 0000:00:1d.7: seizing device
>  pciback 0000:02:01.0: seizing device
>  pciback 0000:02:02.0: seizing device
>  ACPI: PCI Interrupt 0000:02:02.0[A] -> GSI 17 (level, low) -> IRQ 17
>  ACPI: PCI Interrupt 0000:02:01.0[A] -> GSI 22 (level, low) -> IRQ 18
>  ACPI: PCI Interrupt 0000:00:1d.7[D] -> GSI 23 (level, low) -> IRQ 19
>  ACPI: PCI Interrupt 0000:00:1d.3[A] -> GSI 16 (level, low) -> IRQ 20
>  ACPI: PCI Interrupt 0000:00:1d.2[C] -> GSI 18 (level, low) -> IRQ 16
>  ACPI: PCI Interrupt 0000:00:1d.1[B] -> GSI 19 (level, low) -> IRQ 21
>  ACPI: PCI Interrupt 0000:00:1d.0[A] -> GSI 16 (level, low) -> IRQ 20
>  
>  After I start the domU
>  pciback: vpci: 0000:00:1d.0: assign to virtual slot 0
>  pciback: vpci: 0000:00:1d.1: assign to virtual slot 0 func 1
>  pciback: vpci: 0000:00:1d.2: assign to virtual slot 0 func 2
>  pciback: vpci: 0000:00:1d.3: assign to virtual slot 0 func 3
>  pciback: vpci: 0000:00:1d.7: assign to virtual slot 0 func 7
>  pciback: vpci: 0000:02:01.0: assign to virtual slot 1
>  pciback: vpci: 0000:02:02.0: assign to virtual slot 2
>  
>  There is an eror message in xm dmesg but, from what I read, it does  
not seem 
>  to be a problem. (XEN) DOM4: (file=mm.c, line=578) Non-privileged 
attempt to 
>  map I/O space 00000000 (XEN) DOM4: (file=mm.c, line=578) Non-
privileged 
>  attempt to map I/O space 00000000
>  
>  This is what I get from lsusb when I do not assign it to a domU
>  lsusb
>  Bus 005 Device 001: ID 0000:0000
>  Bus 001 Device 001: ID 0000:0000
>  Bus 004 Device 002: ID 05dc:0080 Lexar Media, Inc. Jumpdrive Secure  
64MB
>  Bus 004 Device 001: ID 0000:0000
>  Bus 003 Device 002: ID 0bda:8150 Realtek Semiconductor Corp. RTL8150  
Fast 
>  Ethernet Adapter
>  Bus 003 Device 001: ID 0000:0000
>  Bus 002 Device 001: ID 0000:0000
>  
>  Thanks,
>  Pascal
>  
>  
>  --
>  Fedora-xen mailing list
>  Fedora-xen(a)redhat.com
>  https://www.redhat.com/mailman/listinfo/fedora-xen