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

[Xen-users] igb pciback and e1000e pciback not work.


  • To: xen-users@xxxxxxxxxxxxxxxxxxx
  • From: èé <xnhp0320@xxxxxxxxx>
  • Date: Sun, 5 Sep 2010 10:48:14 +0800
  • Delivery-date: Sat, 04 Sep 2010 19:50:36 -0700
  • Domainkey-signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=mime-version:from:date:message-id:subject:to:content-type; b=oEml9SD80Py3l2R/P9YOj87+KnVBmagS+Uy19T0uGEPUXnWhZQsF0/r310TTK8sOXK 6J6sCzdgCuIg2GLAX8WDpTwDdekgNeTdako5rrlW3a2Ik5YRc0H/D3QsIVMeGTYpAuc5 TOy9O/Tnds4+kpSi1J2/NRzsaJpgnVnrXoAxc=
  • List-id: Xen user discussion <xen-users.lists.xensource.com>

I'm using Xen 4.01 and jeremy's pvops kernel, the kernel version is 2.6.32.18.
At first I want to test the performance of pci passthrough Âwhen it comes to the network card 82571EB

I'm using the Jeremy's kernel 2.6.32.18 as DomU kernel too.

And I found if the interface is not connected, I mean the network card receives no packet, ( the network card doesn't connect to the switch ),
it's fine. when I connect it to a switch , I got a lot of "Detected Tx Unit Hang" in dmesg of the DomU kernel
and a kernel oops saying:

Pid: 0, comm: swapper Not tained 2.6.32.18-xen #4
warn_slowpath_fmt+0x41/0x50

the ooops image is in the attachment of this post.

I've checked the mailing list, some one said it's about the e1000e driver with a wrong
config of the EEPROM.

So I switch to use the network card 82575EB with igb driver
It seems to work well,Â
until I find it can't receive any packets in DomU.

And I see a lot of packets dropped when I ifconfig these interfaces.

Anyone knows how to deal with this ?
--
hepeng
ICT

Attachment: Screenshot.png
Description: PNG image

_______________________________________________
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®.