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-devel

[Xen-devel] Xen 3.3.0 PCI passthrough with pciback.hide

To: xen-devel@xxxxxxxxxxxxxxxxxxx
Subject: [Xen-devel] Xen 3.3.0 PCI passthrough with pciback.hide
From: "Luis F Urrea" <lfurrea@xxxxxxxxx>
Date: Thu, 4 Dec 2008 09:39:30 -0600
Delivery-date: Thu, 04 Dec 2008 07:39:58 -0800
Dkim-signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:received:received:message-id:date:from:to :subject:mime-version:content-type; bh=LgVTo+aclDh0o0OsPZkL2mTV7vbz+QAHwgQlsOi32DU=; b=RNtBv5YPSfukrZulNNbotX66xlpINZ0xzEOSizOXRg4tCZ1z/8bXqBoiptN/sKz7ah bYr+hfAhmqx08tDW/xS1k1Cgfbm8iUtoGX5nRIEXfziAsfFSU8ltJATmBF7GMjB9ZxnZ kQWelxUQvdBNB2fSNurp7xqO0Yf9g2Fszf9kk=
Domainkey-signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=message-id:date:from:to:subject:mime-version:content-type; b=l+TK01ZmmZiN3GQXDSyJ6e1k/geQxqCitkSwEDZyNRQzWlHv8lWIVmtpdDSJQNNNjA EF1En3Co1+3oFZJsoONtWns4NLUBqMjHiL9urMn2YIsD0L7wxV8WQh1V+8rdG5ze2dp9 idjx588Bm3Gesk7HeJY9S7JbnLZ213cxfvv+g=
Envelope-to: www-data@xxxxxxxxxxxxxxxxxxx
List-help: <mailto:xen-devel-request@lists.xensource.com?subject=help>
List-id: Xen developer discussion <xen-devel.lists.xensource.com>
List-post: <mailto:xen-devel@lists.xensource.com>
List-subscribe: <http://lists.xensource.com/mailman/listinfo/xen-devel>, <mailto:xen-devel-request@lists.xensource.com?subject=subscribe>
List-unsubscribe: <http://lists.xensource.com/mailman/listinfo/xen-devel>, <mailto:xen-devel-request@lists.xensource.com?subject=unsubscribe>
Sender: xen-devel-bounces@xxxxxxxxxxxxxxxxxxx
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)                                                        
kernel          /xen-3.3.0.gz console=tty0                                     
module          /vmlinuz-2.6.18.8-xen root=UUID=ba92848e-0fd0-4f78-ae59-c77c1fb\
7d88a ro console=tty0 pciback.permissive pciback.hide=(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 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:

Dom-U#modprobe tg3

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-devel mailing list
Xen-devel@xxxxxxxxxxxxxxxxxxx
http://lists.xensource.com/xen-devel
<Prev in Thread] Current Thread [Next in Thread>