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

["Luis F Urrea" <lfurrea@xxxxxxxxx>]

Would that be a parameter in grub?

such as:

kernel          /xen-3.3.0.gz console=tty0 msi

On Thu, Dec 4, 2008 at 9:49 AM, Keir Fraser <keir.fraser@xxxxxxxxxxxxx> wrote:

Add 'msi' to Xen's command line.

 -- Keir

On 04/12/2008 15:39, "Luis F Urrea" <lfurrea@xxxxxxxxx> 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 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 <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 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

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