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] igb pciback and e1000e pciback not work.

To: xen-users@xxxxxxxxxxxxxxxxxxx
Subject: [Xen-users] igb pciback and e1000e pciback not work.
From: 贺鹏 <xnhp0320@xxxxxxxxx>
Date: Sun, 5 Sep 2010 10:48:14 +0800
Delivery-date: Sat, 04 Sep 2010 19:50:36 -0700
Dkim-signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:received:mime-version:received:from:date :message-id:subject:to:content-type; bh=WLoJN8wOc2EwxsWOlQnzNjWlgkWwsWNF3gPh/IJ6bDg=; b=TdOdqcUPl67mOBZR7FYX4KaYj6Lq/IFV3ng0CM3+eirXcxZUvPrQT8rhQ1xo5IeeqJ yurA6f55WAn+5eQ9x23P1wRGIqvm/cd4BjUyUCdnyiK3SvUGYXeVod1wEQ+V6o+Qn606 ZhP8tm4md4D1SiMJB34uqB/4RJZoMOiooLJOs=
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=
Envelope-to: www-data@xxxxxxxxxxxxxxxxxxx
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/mailman/listinfo/xen-users>, <mailto:xen-users-request@lists.xensource.com?subject=subscribe>
List-unsubscribe: <http://lists.xensource.com/mailman/listinfo/xen-users>, <mailto:xen-users-request@lists.xensource.com?subject=unsubscribe>
Sender: xen-users-bounces@xxxxxxxxxxxxxxxxxxx
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
<Prev in Thread] Current Thread [Next in Thread>
  • [Xen-users] igb pciback and e1000e pciback not work., 贺鹏 <=