Hi,
thanks fort the fast response. Sadly that didn't help.
pciback.permissive was already passed to dom0 kernel. I additionaly added
the device to
xend-pci-permissive.sxp.
Still the same error.
Heres a more detailed output of lspci in dom0:
debserv:~# lspci -vv -n -s 03:00.0
03:00.0 0280: 168c:0024 (rev 01)
Subsystem: 106b:0087
Control: I/O+ Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr-
Stepping- SERR- FastB2B- DisINTx-
Status: Cap+ 66MHz- UDF- FastB2B- ParErr- DEVSEL=fast >TAbort-
<TAbort- <MAbort- >SERR- <PERR- INTx-
Latency: 0, Cache Line Size: 64 bytes
Interrupt: pin A routed to IRQ 18
Region 0: Memory at febf0000 (64-bit, non-prefetchable) [size=64K]
Capabilities: [40] Power Management version 2
Flags: PMEClk- DSI- D1+ D2- AuxCurrent=375mA
PME(D0+,D1+,D2-,D3hot+,D3cold-)
Status: D0 PME-Enable- DSel=0 DScale=0 PME-
Capabilities: [50] Message Signalled Interrupts: Mask- 64bit-
Queue=0/0 Enable-
Address: 00000000 Data: 0000
Capabilities: [60] Express (v1) Legacy Endpoint, MSI 00
DevCap: MaxPayload 128 bytes, PhantFunc 0, Latency L0s
<512ns, L1 <64us
ExtTag- AttnBtn- AttnInd- PwrInd- RBE- FLReset-
DevCtl: Report errors: Correctable- Non-Fatal- Fatal-
Unsupported-
RlxdOrd+ ExtTag- PhantFunc- AuxPwr- NoSnoop-
MaxPayload 128 bytes, MaxReadReq 512 bytes
DevSta: CorrErr- UncorrErr+ FatalErr- UnsuppReq+ AuxPwr-
TransPend-
LnkCap: Port #0, Speed 2.5GT/s, Width x1, ASPM L0s L1,
Latency L0 <512ns, L1 <64us
ClockPM- Suprise- LLActRep- BwNot-
LnkCtl: ASPM Disabled; RCB 128 bytes Disabled- Retrain-
CommClk+
ExtSynch- ClockPM- AutWidDis- BWInt- AutBWInt-
LnkSta: Speed 2.5GT/s, Width x1, TrErr- Train- SlotClk+
DLActive- BWMgmt- ABWMgmt-
Capabilities: [90] MSI-X: Enable- Mask- TabSize=1
Vector table: BAR=0 offset=00000000
PBA: BAR=0 offset=00000000
Capabilities: [100] Advanced Error Reporting <?>
Capabilities: [140] Virtual Channel <?>
Kernel driver in use: ath9k
Kernel modules: ath9k
I added 0280: 168c:0024 to xend-pci-permissive.sxp, is this right?
What about adding the device to xend-pci-quirks.sxp? It seems as if this
file is for devices which need access to configuration space. How do I know
which config space fields the device needs access to?
Leo
-----Ursprüngliche Nachricht-----
Von: xen-users-bounces@xxxxxxxxxxxxxxxxxxx
[mailto:xen-users-bounces@xxxxxxxxxxxxxxxxxxx] Im Auftrag von Christian
Tramnitz
Gesendet: Montag, 28. September 2009 12:42
An: xen-users@xxxxxxxxxxxxxxxxxxx
Betreff: [Xen-users] Re: PCI passthrough problem
Leo Krüger wrote:
> Hello,
>
> I'm having huge problems getting pci passthrough to work.
> There is a mini-pcie wlan-card (atheros, requires ath9k) which I want to
> pass to a domU.
> Everytime ath9k is loaded in domU, I get these errors:
>
> PCI memory map error
> ath9k: probe of 0000:00:00.0 failed with error -5
>
> The device is of course hidden with pciback.hide for dom0. Xen Version is
> 3.4.1 and 3.4 (tried both), Kernel in dom0 and domU is 2.6.26 (debian) or
> 2.6.27 (XCI) or 2.6.29.6 (OpenSUSE Xen kernel patches).
>
> Is there anyone on this list who has even a small idea why this isn't
> working?
> I'm kind of frustrated... with xen 3.2 it worked without a problem.
>
> Greetings, Leo
Hi Leo,
the interesting part seems to be:
(XEN) mm.c:740:d1 Non-privileged (1) attempt to map I/O space 000febf0
Try enabling permissive mode of pciback or add the device to
xend-pci-permissive.sxp (both in dom0)
Best regards,
Christian
_______________________________________________
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
|
Home