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] Problems with pci passthrough with Xen 3.4.2

On Mon, Dec 14, 2009 at 01:06:10PM +0100, francisco javier funes nieto wrote:
> Yes!
> 
> This is the lspci output from dom0:
> 
> main:/etc/xen# lspci |grep Ethernet
> 04:00.0 Ethernet controller: Intel Corporation 80003ES2LAN Gigabit
> Ethernet Controller (Copper) (rev 01)
> 04:00.1 Ethernet controller: Intel Corporation 80003ES2LAN Gigabit
> Ethernet Controller (Copper) (rev 01)
> 
> 
> And the lspci from domU:
> 
> proxy:~# lspci -v
> 00:00.1 Ethernet controller: Intel Corporation 80003ES2LAN Gigabit
> Ethernet Controller (Copper) (rev 01)
>       Subsystem: Super Micro Computer Inc Device 0000
>       Flags: bus master, fast devsel, latency 0, IRQ 19
>       Memory at da020000 (32-bit, non-prefetchable) [size=128K]
>       I/O ports at 3020 [size=32]
>       Capabilities: [c8] Power Management version 2
>       Capabilities: [d0] Message Signalled Interrupts: Mask- 64bit+ Queue=0/0 
> Enable-
>       Capabilities: [e0] Express Endpoint, MSI 00
>       Capabilities: [100] Advanced Error Reporting <?>
>       Capabilities: [140] Device Serial Number 22-6c-32-ff-ff-48-30-00
>       Kernel driver in use: e1000e
>       Kernel modules: e1000e
> 
> From this moment I'm still working in this domU to use this Ethernet
> passed by passthrough as primary interface for the Squid Proxy.
> 
> The dom0 works as expected!
>

Btw current xen-unstable (upcoming Xen 4.0) doesn't need the "disable FLR" 
patch, 
it has an option you can use to overcome this:

http://lists.xensource.com/archives/html/xen-devel/2009-12/msg00682.html

"Actually we have such a xend option in the xen-unstable tree:
The option is at the end of /etc/xen/xend-config.sxp: 
(pci-passthrough-strict-check yes). Uncomment it and change it to no and
do a "xend restart".

-- Pasi

> 
> I'll put iperf results as soon I configure the Squid.
> 
> 
> Thanks!
> 
> J.
> 
> 
> 
> 2009/12/14 Pasi Kärkkäinen <pasik@xxxxxx>:
> > On Mon, Dec 14, 2009 at 12:30:09PM +0100, francisco javier funes nieto 
> > wrote:
> >> Thanks to all, it works like a charm.
> >>
> >> Now I have the Ethernet device in the DomU, once I patched the Xen
> >> Source Tree and recompile with the FLR patch.
> >>
> >> Great!
> >>
> >> Really Great!
> >>
> >
> > Hello.
> >
> > Just to confirm, with the FLR patch, you're able to use the first port
> > in dom0, and passthrough the second port to domU?
> >
> > Thanks!
> >
> > -- Pasi
> >
> >> Javier
> >>
> >> 2009/12/9 Stefan Kuhne <stefan.kuhne@xxxxxxx>:
> >> > francisco javier funes nieto schrieb:
> >> >> Thank's Stefan but I've not found a diff path to apply the source code
> >> >> of Xen... I'll do a deep search, thank's again.
> >> >>
> >> > I've found it in my archiv:
> >> > http://old.nabble.com/Error:-pci:-0000:02:06.0-must-be-co-assigned-to-the-same-guest-with-0000:02:05.0-td21280150.html
> >> >
> >> > Stefan Kuhne
> >> >
> >> >
> >>
> >>
> >>
> >> --
> >> _____________________________________________
> >>
> >> Francisco Javier Funes Nieto [esencia@xxxxxxxxx]
> >> CANONIGOS
> >> Servicios Informáticos para PYMES.
> >> Cl. Cruz 2, 1º Oficina 7
> >> Tlf: 958.536759 / 661134556
> >> Fax: 958.521354
> >> GRANADA - 18002
> >>
> >> _______________________________________________
> >> Xen-users mailing list
> >> Xen-users@xxxxxxxxxxxxxxxxxxx
> >> http://lists.xensource.com/xen-users
> >
> 
> 
> 
> -- 
> _____________________________________________
> 
> Francisco Javier Funes Nieto [esencia@xxxxxxxxx]
> CANONIGOS
> Servicios Informáticos para PYMES.
> Cl. Cruz 2, 1º Oficina 7
> Tlf: 958.536759 / 661134556
> Fax: 958.521354
> GRANADA - 18002

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

<Prev in Thread] Current Thread [Next in Thread>