[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

[Xen-users] XCP 1.0 beta Realtek 8168 nic not working


  • To: xen-users@xxxxxxxxxxxxxxxxxxx
  • From: Grant McWilliams <grantmasterflash@xxxxxxxxx>
  • Date: Thu, 23 Dec 2010 18:46:54 -0800
  • Delivery-date: Thu, 23 Dec 2010 18:48:57 -0800
  • Domainkey-signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=mime-version:from:date:message-id:subject:to:content-type; b=myR2tKjtJ49uvHi+RIPkn6XEQ49sNiPLNq+hdl/4xftGM+XO2wstD2+L+y7c6C8Kiv +RmFu4wdb5a1p3FY1uRZ2CMgXar0GZly5/5N8AcjOs2YHGffhu+Tk7oNh8dPwUjwZaw+ cDsZ6lKZngUaxt3vtPcbQrR4wUGKOmGIbZKFY=
  • List-id: Xen user discussion <xen-users.lists.xensource.com>

I'm trying to build out a test cloud using XCP 1.0.0 beta with 3 machines of 18 cores total (Phenom II 1090s). I've built three machines, installed XCP 1.0.0 beta on them and they all three
have the same problem - the Realtek network cards don't work. The following is the output from lspci

03:00.0 Ethernet controller: Realtek Semiconductor Co., Ltd. RTL8111/8168B PCI Express Gigabit Ethernet controller (rev 03)

I also put in an Intel e1000 card in each box and it works. I booted off a live Ubuntu 10.04 CD and both network cards worked beautifully. I booted up on a CentOS 5.5 DVD and went into Rescue mode and both cards worked.
Is this a driver issue with XCP 1.0.0 beta?

If I plug a network cable into eth0 (the Realtek port) I get this from dmesg

r8169: eth0: link up
xenbr0: port 1(eth0) entering forwarding state

Things seem fine. Output of ethtool

[root@cloud1 ~]# ethtool eth0
Settings for eth0:
ÂÂÂ Supported ports: [ TP MII ]
ÂÂÂ Supported link modes:ÂÂ 10baseT/Half 10baseT/Full
ÂÂÂ ÂÂÂÂÂÂÂÂÂÂÂÂÂÂÂÂÂÂÂÂÂÂÂ 100baseT/Half 100baseT/Full
ÂÂÂ ÂÂÂÂÂÂÂÂÂÂÂÂÂÂÂÂÂÂÂÂÂÂÂ 1000baseT/Half 1000baseT/Full
ÂÂÂ Supports auto-negotiation: Yes
ÂÂÂ Advertised link modes:Â Not reported
ÂÂÂ Advertised auto-negotiation: No
ÂÂÂ Speed: 10Mb/s
ÂÂÂ Duplex: Half
ÂÂÂ Port: MII
ÂÂÂ PHYAD: 0
ÂÂÂ Transceiver: internal
ÂÂÂ Auto-negotiation: off
ÂÂÂ Supports Wake-on: pumbg
ÂÂÂ Wake-on: g
ÂÂÂ Current message level: 0x00000033 (51)
ÂÂÂ Link detected: yes

ethtool says the device has auto-negotiate off and running half duplex. Any attempts to use ethtool to fix it fail.

So my biggest frustration is that this network card works on CentOS 5.5. The main difference between CentOS and XCP is kernel so is this a kernel issue or is there a configuration issue?


Grant McWilliams

Some people, when confronted with a problem, think "I know, I'll use Windows."
Now they have two problems.

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

 


Rackspace

Lists.xenproject.org is hosted with RackSpace, monitoring our
servers 24x7x365 and backed by RackSpace's Fanatical Support®.