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

Re: [Xen-users] Using a dedicated NIC in domU

To: "Rainer Sokoll" <rainer@xxxxxxxxxx>
Subject: Re: [Xen-users] Using a dedicated NIC in domU
From: "Todd Deshane" <deshantm@xxxxxxxxx>
Date: Thu, 7 Feb 2008 12:08:19 -0500
Cc: xen-users@xxxxxxxxxxxxxxxxxxx
Delivery-date: Thu, 07 Feb 2008 09:08:55 -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:reply-to:to:subject:cc:in-reply-to:mime-version:content-type:content-transfer-encoding:content-disposition:references; bh=ZCxscgsHeDCXpv9PPqLHTxaEASu7CfhbEJORA/EXBEI=; b=Y20maJx8fbuzanQPd2ouGg1wMf8zgJvutkJc/iibqDGNN2IQQH+xPzsmOqSwiP18ueXLd2vnECa7UHJfa4bt8Kg1qvlvmwOhSn2ovoHfzpDDNEquqnmGpK9smje8fkdWZ5qohacl7raJZHsOa6JR7whzM9et7wjqHDJ1kNDSJdE=
Domainkey-signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=message-id:date:from:reply-to:to:subject:cc:in-reply-to:mime-version:content-type:content-transfer-encoding:content-disposition:references; b=dQ3bEwDjrVys3XxRUN8oZM27iaSEHoxwOOkU8vwHrvsvFBuOpyTl+XVLmJ5dOBz69R2Jcrowlo9D/3uH4MxfrbfqflUkZkJqzecRvFpCpjCPRa7jzuTIpLEoyzhkOlxTMWS1jBcEIEJVhYgHCr9p918UXAwoP5ndtEbjco5RTSk=
Envelope-to: www-data@xxxxxxxxxxxxxxxxxx
In-reply-to: <20080206125708.GK20695@xxxxxxxxxxxxxxxxxxxxxxx>
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>
References: <20080206125708.GK20695@xxxxxxxxxxxxxxxxxxxxxxx>
Reply-to: deshantm@xxxxxxxxx
Sender: xen-users-bounces@xxxxxxxxxxxxxxxxxxx
Hi,

On Feb 6, 2008 7:57 AM, Rainer Sokoll <rainer@xxxxxxxxxx> wrote:
> 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
> #
>


Can you send your complete kernel config file?

I haven't had a similar problem, but I haven't tried with CentOS. I
have had it work fine with Debian and Ubuntu xen kernels.

Everything else except the "system does not support PCI" messages
looks right to me.

Todd

> Any help is appreciated,
>
> Rainer
>
> _______________________________________________
> Xen-users mailing list
> Xen-users@xxxxxxxxxxxxxxxxxxx
> http://lists.xensource.com/xen-users
>

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

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