thr3ads.net - Xen users - [Xen-users] problems delegating PCI device to domU (broadcom wlan chip) [May 2008]

If this information is useful, please help other people find it:
Share via:

Enrico Weigelt

2008-May-09 09:01 UTC

[Xen-users] problems delegating PCI device to domU (broadcom wlan chip)

Hi folks,


I''d like to delegate my broadcom wlan device to an domU.
Follewed the instructions I found on the net (pciback.hide boot 
param and pci= assignment in the domu config). 

Strange: the device still shows up in dom0''s lspci, but also 
in domU''s. Some howto''s say, it shouldn''t be visible
in the dom0.

When I insmod the domU driver (bcm43xx), it segfaults in 
bcm43xx_attach_board(). Syslog says:

PCI: Enabling device 0000:03:00.0 (0000 -> 0002)
ACPI: PCI Interrupt 0000:03:00.0[A] -> Link [LK1E] -> GSI 23 (level, high)
-> IRQ 16
PCI: Setting latency timer of device 0000:03:00.0 to 64
pciback 0000:03:00.0: Driver tried to write to a read-only \
    configuration space field at offset 0xb4, ize 4. 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

Dom0 lspci:

00:00.0 RAM memory: nVidia Corporation C51 Host Bridge (rev a2)
00:00.1 RAM memory: nVidia Corporation C51 Memory Controller 0 (rev a2)
00:00.2 RAM memory: nVidia Corporation C51 Memory Controller 1 (rev a2)
00:00.3 RAM memory: nVidia Corporation C51 Memory Controller 5 (rev a2)
00:00.4 RAM memory: nVidia Corporation C51 Memory Controller 4 (rev a2)
00:00.5 RAM memory: nVidia Corporation C51 Host Bridge (rev a2)
00:00.6 RAM memory: nVidia Corporation C51 Memory Controller 3 (rev a2)
00:00.7 RAM memory: nVidia Corporation C51 Memory Controller 2 (rev a2)
00:02.0 PCI bridge: nVidia Corporation C51 PCI Express Bridge (rev a1)
00:03.0 PCI bridge: nVidia Corporation C51 PCI Express Bridge (rev a1)
00:05.0 VGA compatible controller: nVidia Corporation MCP51 PCI-X GeForce Go
6100 (rev a2)
00:09.0 RAM memory: nVidia Corporation MCP51 Host Bridge (rev a2)
00:0a.0 ISA bridge: nVidia Corporation MCP51 LPC Bridge (rev a3)
00:0a.1 SMBus: nVidia Corporation MCP51 SMBus (rev a3)
00:0a.3 Co-processor: nVidia Corporation MCP51 PMU (rev a3)
00:0b.0 USB Controller: nVidia Corporation MCP51 USB Controller (rev a3)
00:0b.1 USB Controller: nVidia Corporation MCP51 USB Controller (rev a3)
00:0d.0 IDE interface: nVidia Corporation MCP51 IDE (rev f1)
00:0e.0 IDE interface: nVidia Corporation MCP51 Serial ATA Controller (rev f1)
00:10.0 PCI bridge: nVidia Corporation MCP51 PCI Bridge (rev a2)
00:10.1 Audio device: nVidia Corporation MCP51 High Definition Audio (rev a2)
00:14.0 Bridge: nVidia Corporation MCP51 Ethernet Controller (rev a3)
00:18.0 Host bridge: Advanced Micro Devices [AMD] K8 [Athlon64/Opteron]
HyperTransport Technology Configuration
00:18.1 Host bridge: Advanced Micro Devices [AMD] K8 [Athlon64/Opteron] Address
Map
00:18.2 Host bridge: Advanced Micro Devices [AMD] K8 [Athlon64/Opteron] DRAM
Controller
00:18.3 Host bridge: Advanced Micro Devices [AMD] K8 [Athlon64/Opteron]
Miscellaneous Control
03:00.0 Network controller: Broadcom Corporation BCM94311MCG wlan mini-PCI (rev
02)

DomU lspci:

00:00.0 Network controller: Broadcom Corporation BCM94311MCG wlan mini-PCI (rev
02)



Does anyone have an idea what''s wrong here ?


thx
-- 
----------------------------------------------------------------------
 Enrico Weigelt, metux IT service -- http://www.metux.de/

 cellphone: +49 174 7066481   email: info@metux.de   skype: nekrad666
----------------------------------------------------------------------
 Embedded-Linux / Portierung / Opensource-QM / Verteilte Systeme
----------------------------------------------------------------------

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

Todd Deshane

2008-May-09 14:25 UTC

head link

Re: [Xen-users] problems delegating PCI device to domU (broadcom wlan chip)

Hi Enrico,

On Fri, May 9, 2008 at 5:01 AM, Enrico Weigelt <weigelt@metux.de> wrote:
>
> Hi folks,
>
>
> I''d like to delegate my broadcom wlan device to an domU.
> Follewed the instructions I found on the net (pciback.hide boot
> param and pci= assignment in the domu config).
>
> Strange: the device still shows up in dom0''s lspci, but also
> in domU''s. Some howto''s say, it shouldn''t be
visible in the dom0.
>
>From my experience this is the behavior too.
did you try adding pciback.permissive to the dom0 kernel line as well?

Also see:
http://xen.markmail.org/search/?q=pciback+permissive

Regards,
Todd


> When I insmod the domU driver (bcm43xx), it segfaults in
> bcm43xx_attach_board(). Syslog says:
>
> PCI: Enabling device 0000:03:00.0 (0000 -> 0002)
> ACPI: PCI Interrupt 0000:03:00.0[A] -> Link [LK1E] -> GSI 23 (level,
high)
> -> IRQ 16
> PCI: Setting latency timer of device 0000:03:00.0 to 64
> pciback 0000:03:00.0: Driver tried to write to a read-only \
>    configuration space field at offset 0xb4, ize 4. 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
>
> Dom0 lspci:
>
> 00:00.0 RAM memory: nVidia Corporation C51 Host Bridge (rev a2)
> 00:00.1 RAM memory: nVidia Corporation C51 Memory Controller 0 (rev a2)
> 00:00.2 RAM memory: nVidia Corporation C51 Memory Controller 1 (rev a2)
> 00:00.3 RAM memory: nVidia Corporation C51 Memory Controller 5 (rev a2)
> 00:00.4 RAM memory: nVidia Corporation C51 Memory Controller 4 (rev a2)
> 00:00.5 RAM memory: nVidia Corporation C51 Host Bridge (rev a2)
> 00:00.6 RAM memory: nVidia Corporation C51 Memory Controller 3 (rev a2)
> 00:00.7 RAM memory: nVidia Corporation C51 Memory Controller 2 (rev a2)
> 00:02.0 PCI bridge: nVidia Corporation C51 PCI Express Bridge (rev a1)
> 00:03.0 PCI bridge: nVidia Corporation C51 PCI Express Bridge (rev a1)
> 00:05.0 VGA compatible controller: nVidia Corporation MCP51 PCI-X GeForce
> Go 6100 (rev a2)
> 00:09.0 RAM memory: nVidia Corporation MCP51 Host Bridge (rev a2)
> 00:0a.0 ISA bridge: nVidia Corporation MCP51 LPC Bridge (rev a3)
> 00:0a.1 SMBus: nVidia Corporation MCP51 SMBus (rev a3)
> 00:0a.3 Co-processor: nVidia Corporation MCP51 PMU (rev a3)
> 00:0b.0 USB Controller: nVidia Corporation MCP51 USB Controller (rev a3)
> 00:0b.1 USB Controller: nVidia Corporation MCP51 USB Controller (rev a3)
> 00:0d.0 IDE interface: nVidia Corporation MCP51 IDE (rev f1)
> 00:0e.0 IDE interface: nVidia Corporation MCP51 Serial ATA Controller (rev
> f1)
> 00:10.0 PCI bridge: nVidia Corporation MCP51 PCI Bridge (rev a2)
> 00:10.1 Audio device: nVidia Corporation MCP51 High Definition Audio (rev
> a2)
> 00:14.0 Bridge: nVidia Corporation MCP51 Ethernet Controller (rev a3)
> 00:18.0 Host bridge: Advanced Micro Devices [AMD] K8 [Athlon64/Opteron]
> HyperTransport Technology Configuration
> 00:18.1 Host bridge: Advanced Micro Devices [AMD] K8 [Athlon64/Opteron]
> Address Map
> 00:18.2 Host bridge: Advanced Micro Devices [AMD] K8 [Athlon64/Opteron]
> DRAM Controller
> 00:18.3 Host bridge: Advanced Micro Devices [AMD] K8 [Athlon64/Opteron]
> Miscellaneous Control
> 03:00.0 Network controller: Broadcom Corporation BCM94311MCG wlan mini-PCI
> (rev 02)
>
> DomU lspci:
>
> 00:00.0 Network controller: Broadcom Corporation BCM94311MCG wlan mini-PCI
> (rev 02)
>
>
>
> Does anyone have an idea what''s wrong here ?
>
>
> thx
> --
> ----------------------------------------------------------------------
>  Enrico Weigelt, metux IT service -- http://www.metux.de/
>
>  cellphone: +49 174 7066481   email: info@metux.de   skype: nekrad666
> ----------------------------------------------------------------------
>  Embedded-Linux / Portierung / Opensource-QM / Verteilte Systeme
> ----------------------------------------------------------------------
>
> _______________________________________________
> Xen-users mailing list
> Xen-users@lists.xensource.com
> http://lists.xensource.com/xen-users
>

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

Enrico Weigelt

2008-May-10 13:53 UTC

head link

Re: [Xen-users] problems delegating PCI device to domU (broadcom wlan chip)

* Todd Deshane <deshantm@gmail.com> wrote:
> did you try adding pciback.permissive to the dom0 kernel line as well?
> 
> Also see:
> http://xen.markmail.org/search/?q=pciback+permissive
Yep. But this didn''t work (even writing to the permissive file failed).
Now, after a day of downtime, it works - and it seems the pci device
is now automatically bound to pciback :)

my boot config:

    pciback.permissive=(03:00.0)
    pciback.hide=(03:00.0)
    pci=routeirq
    
(03:00.0 is my broadcom chip)

The driver now loads fine, so I can work on it (my broadcom chip is detected, 
but the chip revision isnt supported yet).


cu
-- 
----------------------------------------------------------------------
 Enrico Weigelt, metux IT service -- http://www.metux.de/

 cellphone: +49 174 7066481   email: info@metux.de   skype: nekrad666
----------------------------------------------------------------------
 Embedded-Linux / Portierung / Opensource-QM / Verteilte Systeme
----------------------------------------------------------------------

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

Xen users - May 2008 - problems delegating PCI device to domU (broadcom wlan chip)

[Xen-users] problems delegating PCI device to domU (broadcom wlan chip)

Re: [Xen-users] problems delegating PCI device to domU (broadcom wlan chip)

Re: [Xen-users] problems delegating PCI device to domU (broadcom wlan chip)