From mboxrd@z Thu Jan 1 00:00:00 1970 From: Keir Fraser Subject: Re: Xen 3.3.0 PCI passthrough with pciback.hide Date: Thu, 04 Dec 2008 15:49:01 +0000 Message-ID: References: Mime-Version: 1.0 Content-Type: multipart/mixed; boundary="===============1159142350==" Return-path: In-Reply-To: List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Sender: xen-devel-bounces@lists.xensource.com Errors-To: xen-devel-bounces@lists.xensource.com To: Luis F Urrea , xen-devel@lists.xensource.com List-Id: xen-devel@lists.xenproject.org > This message is in MIME format. Since your mail reader does not understand this format, some or all of this message may not be legible. --===============1159142350== Content-type: multipart/alternative; boundary="B_3311250541_3425124" > This message is in MIME format. Since your mail reader does not understand this format, some or all of this message may not be legible. --B_3311250541_3425124 Content-type: text/plain; charset="ISO-8859-1" Content-transfer-encoding: quoted-printable Add =8Cmsi=B9 to Xen=B9s command line. -- Keir On 04/12/2008 15:39, "Luis F Urrea" wrote: > Hi all, >=20 > I am trying to configure a Dom U to act as a firewall and therefore I nee= d to > pass one of the two ethernet cards to the Dom-U. >=20 > I configured the Xen kernel to build pciback as part of the kernel instea= d of > module and I am passing the hide option via boot parameters. >=20 > /boot/grub/menu.lst >=20 > title Xen 3.3.0 / Debian GNU/Linux, kernel 2.6.18.8-xen > root (hd0,1) > kernel /xen-3.3.0.gz console=3Dtty0 > module /vmlinuz-2.6.18.8-xen > root=3DUUID=3Dba92848e-0fd0-4f78-ae59-c77c1fb\ > 7d88a ro console=3Dtty0 pciback.permissive pciback.hide=3D(0000:02:00.0) > module /initrd.img-2.6.18.8-xen >=20 > I boot the pv machine via pygrub and I am able to see the ethernet device= in > Dom U as follows: >=20 > Dom-U#lspci > 02:00.0 Ethernet controller: Broadcom Corporation NetXtreme BCM5722 Gigab= it > Ethernet PCI Express >=20 > When I load the driver the eth device comes up: >=20 > Dom-U#modprobe tg3 >=20 > eth1: Tigon3 [partno(BCM95722) rev a200 PHY(5722/5756)] (PCI Express) > 10/100/1000Base-T Ethernet 00:1e:c9:53:53:a3 > eth1: RXcsums[1] LinkChgREG[0] MIirq[0] ASF[0] WireSpeed[1] TSOcap[1] > eth1: dma_rwctrl[76180000] dma_mask[64-bit] >=20 > However when I try to bring up the interface using >=20 > #ifup eth1 >=20 > I get the following: >=20 > get owner for dev 0 get 1 > error enable msi for guest 1 status fffffff0 > SIOCSIFFLAGS: Function not implemented > Sending on LPF/eth1/00:1e:c9:53:53:a3 > Sending on Socket/fallback > receive_packet failed on eth1: Network is down > DHCPDISCOVER on eth1 to 255.255.255.255 port 6= 7 > interval 4 > send_packet: Network is down >=20 > Dom-U dmesg shows the following: > pci frontend enable msi failed for dev 2:0 > pci frontend enable msi failed for dev 2:0 > pci frontend enable msi failed for dev 2:0 > pci frontend enable msi failed for dev 2:0 > pci frontend enable msi failed for dev 2:0 > pci frontend enable msi failed for dev 2:0 >=20 > Dom-0 dmesg shows: > PCI: Enabling device 0000:02:00.0 (0000 -> 0002) > ACPI: PCI Interrupt 0000:02:00.0[A] -> Link [LNK2] -> GSI 19 (level, low)= -> > IRQ 16 > PCI: Setting latency timer of device 0000:02:00.0 to 64 > pciback 0000:02:00.0: Driver tried to write to a read-only configuration = space > field at offset 0x68, size 4. This may be harmless, but if you have probl= ems > with your device: > 1) see permissive attribute in sysfs > 2) report problems to the xen-devel mailing list along with details of yo= ur > device obtained from lspci. > get owner for dev 0 get 1 > error enable msi for guest 1 status fffffff0 > get owner for dev 0 get 1 > error enable msi for guest 1 status fffffff0 > get owner for dev 0 get 1 > error enable msi for guest 1 status fffffff0 > get owner for dev 0 get 1 > error enable msi for guest 1 status fffffff0 >=20 > Your help will be greatly appreciated. >=20 > Regards, >=20 > Luis >=20 > _______________________________________________ > Xen-devel mailing list > Xen-devel@lists.xensource.com > http://lists.xensource.com/xen-devel --B_3311250541_3425124 Content-type: text/html; charset="ISO-8859-1" Content-transfer-encoding: quoted-printable Re: [Xen-devel] Xen 3.3.0 PCI passthrough with pciback.hide Add ‘msi’ to Xen’s command line.

 -- Keir

On 04/12/2008 15:39, "Luis F Urrea" <lfurrea@gmail.com> wrote:

<= SPAN STYLE=3D'font-size:11pt'>Hi all,

I am trying to configure a Dom U to act as a firewall and therefore I need = to pass one of the two ethernet cards to the Dom-U.

I configured the Xen kernel to build pciback as part of the kernel instead = of module and I am passing the hide option via boot parameters.

/boot/grub/menu.lst

title           Xen 3.3.0= / Debian GNU/Linux, kernel 2.6.18.8-xen       = ;        
root            (hd0= ,1)             =             &nbs= p;            &n= bsp;            =       
kernel          /xen-3.3.0.gz = console=3Dtty0           &nb= sp;            &= nbsp;            = ; 
module          /vmlinuz-2.6.1= 8.8-xen root=3DUUID=3Dba92848e-0fd0-4f78-ae59-c77c1fb\
7d88a ro console=3Dtty0 pciback.permissive pciback.hide=3D(0000:02:00.0)  =           
module          /initrd.img-2.= 6.18.8-xen

I boot the pv machine via pygrub and I am able to see the ethernet device i= n Dom U as follows:

Dom-U#lspci
02:00.0 Ethernet controller: Broadcom Corporation NetXtreme BCM5722 Gigabit= Ethernet PCI Express

When I load the driver the eth device comes up:

Dom-U#modprobe tg3

eth1: Tigon3 [partno(BCM95722) rev a200 PHY(5722/5756)] (PCI Express) 10/10= 0/1000Base-T Ethernet 00:1e:c9:53:53:a3
eth1: RXcsums[1] LinkChgREG[0] MIirq[0] ASF[0] WireSpeed[1] TSOcap[1]
eth1: dma_rwctrl[76180000] dma_mask[64-bit]

However when I try to bring up the interface using

#ifup eth1

I get the following:

get owner for dev 0 get 1
error enable msi for guest 1 status fffffff0
SIOCSIFFLAGS: Function not implemented
Sending on   LPF/eth1/00:1e:c9:53:53:a3
Sending on   Socket/fallback
receive_packet failed on eth1: Network is down
DHCPDISCOVER on eth1 to 255.255.255.255 <http://255.255.255.255/>  port 67 interval 4
send_packet: Network is down

Dom-U dmesg shows the following:
pci frontend enable msi failed for dev 2:0
pci frontend enable msi failed for dev 2:0
pci frontend enable msi failed for dev 2:0
pci frontend enable msi failed for dev 2:0
pci frontend enable msi failed for dev 2:0
pci frontend enable msi failed for dev 2:0

Dom-0 dmesg shows:
PCI: Enabling device 0000:02:00.0 (0000 -> 0002)
ACPI: PCI Interrupt 0000:02:00.0[A] -> Link [LNK2] -> GSI 19 (level, = low) -> IRQ 16
PCI: Setting latency timer of device 0000:02:00.0 to 64
pciback 0000:02:00.0: Driver tried to write to a read-only configuration sp= ace field at offset 0x68, size 4. This may be harmless, but if you have prob= lems 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.
get owner for dev 0 get 1
error enable msi for guest 1 status fffffff0
get owner for dev 0 get 1
error enable msi for guest 1 status fffffff0
get owner for dev 0 get 1
error enable msi for guest 1 status fffffff0
get owner for dev 0 get 1
error enable msi for guest 1 status fffffff0

Your help will be greatly appreciated.

Regards,

Luis
<= FONT FACE=3D"Consolas, Courier New, Courier">____= ___________________________________________
Xen-devel mailing list
Xen-devel@lists.xensource.com http://lists.xensource.com/x= en-devel
--B_3311250541_3425124-- --===============1159142350== Content-Type: text/plain; charset="us-ascii" MIME-Version: 1.0 Content-Transfer-Encoding: 7bit Content-Disposition: inline _______________________________________________ Xen-devel mailing list Xen-devel@lists.xensource.com http://lists.xensource.com/xen-devel --===============1159142350==--