Xen users - Dec 2008 - Xen 3.3.0 PCI passthrough with pciback.hide

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 a module and I am passing
the hide option via boot parameters.

I boot the pv machine via pygrub and I am able to see the ethernet device in
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:

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]

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 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
space field at offset 0x68, size 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.
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


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

On Wed, Dec 3, 2008 at 10:47 PM, Luis F Urrea <lfurrea@gmail.com>
wrote:
> 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 a module and I am passing
> the hide option via boot parameters.
>
> I boot the pv machine via pygrub and I am able to see the ethernet device
in
> 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:
>
> 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]
>
> 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 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
> space field at offset 0x68, size 4. This may be harmless, but if you have
> problems with your device:
> 1) see permissive attribute in sysfs
did you try to add pciback.permissive on the same line as the pciback.hide
line in your grub config?
> 2) report problems to the xen-devel mailing list along with details of your
> device obtained from lspci.
If that doesn''t work, then following Step number 2 may be the
right approach

Cheers,
Todd

-- 
Todd Deshane
http://todddeshane.net
http://runningxen.com

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