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

[Xen-users] Using a dedicated NIC in domU

To: xen-users@xxxxxxxxxxxxxxxxxxx
Subject: [Xen-users] Using a dedicated NIC in domU
From: Rainer Sokoll <rainer@xxxxxxxxxx>
Date: Wed, 6 Feb 2008 13:57:08 +0100
Delivery-date: Wed, 06 Feb 2008 04:57:45 -0800
Envelope-to: www-data@xxxxxxxxxxxxxxxxxx
List-help: <mailto:xen-users-request@lists.xensource.com?subject=help>
List-id: Xen user discussion <xen-users.lists.xensource.com>
List-post: <mailto:xen-users@lists.xensource.com>
List-subscribe: <http://lists.xensource.com/cgi-bin/mailman/listinfo/xen-users>, <mailto:xen-users-request@lists.xensource.com?subject=subscribe>
List-unsubscribe: <http://lists.xensource.com/cgi-bin/mailman/listinfo/xen-users>, <mailto:xen-users-request@lists.xensource.com?subject=unsubscribe>
Sender: xen-users-bounces@xxxxxxxxxxxxxxxxxxx
User-agent: Mutt/1.5.15 (2007-04-06)
Hi,

I saw this covered multiple times in the ML archive, but I did not find
a solution.

Here my environment:
OpenSuse 10.3, dom0 running 2.6.22.16-0.1-xenpae. 2 NICs, Broadcom
Corporation NetXtreme BCM5715 Gigabit Ethernet (rev a3), tg3 driver.
Xen is Suse's latest 3.1.0, both on dom0 and domU.

I was able to hide the 2nd NIC from dom0:
# lspci | grep Ether
0f:04.0 Ethernet controller: Broadcom Corporation NetXtreme BCM5715 Gigabit 
Ethernet (rev a3)
0f:04.1 Ethernet controller: Broadcom Corporation NetXtreme BCM5715 Gigabit 
Ethernet (rev a3)
# dmesg | grep -i pciback
pciback 0000:0f:04.1: seizing device
pciback: vpci: 0000:0f:04.1: assign to virtual slot 0
pciback: vpci: 0000:0f:04.1: assign to virtual slot 0
pciback: vpci: 0000:0f:04.1: assign to virtual slot 0
pciback: vpci: 0000:0f:04.1: assign to virtual slot 0
pciback: vpci: 0000:0f:04.1: assign to virtual slot 0
# ifconfig eth1
eth1: error fetching interface information: Device not found
# 

Now I want to export 0000:0f:04.1 into a domU. In its config, I have:
pci=[ '0f:04.1' ]
netif = 1

But if I do an lspci in domU, it returns nothing. Something in domU
looks strange to me:
# dmesg | grep -i pci
Allocating PCI resources starting at 20000000 (gap: 18800000:e7800000)
PCI: Fatal: No config space access function found
PCI: setting up Xen PCI frontend stub
PCI: System does not support PCI
PCI: System does not support PCI
pcifront pci-0: Installing PCI frontend
pcifront pci-0: Creating PCI Frontend Bus 0000:00
# 

What is that "System does not support PCI"? If I look at the running
kernel, it should:
# zgrep ^CONFIG_PCI /proc/config.gz 
CONFIG_PCI=y
CONFIG_PCI_GOANY=y
CONFIG_PCI_DIRECT=y
CONFIG_PCI_MMCONFIG=y
CONFIG_PCIEPORTBUS=y
CONFIG_PCIEAER=y
CONFIG_PCI_HERMES=m
CONFIG_PCI_ATMEL=m
CONFIG_PCI200SYN=m
CONFIG_PCIPCWATCHDOG=m
# 

Any help is appreciated,

Rainer

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

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