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 _______________________________________________ Xen-users mailing list Xen-users@lists.xensource.com http://lists.xensource.com/xen-users
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 -- hepeng ICT _______________________________________________ Xen-devel mailing list Xen-devel@lists.xensource.com http://lists.xensource.com/xen-devel
Pasi Kärkkäinen
2010-Sep-05 10:47 UTC
Re: [Xen-devel] igb pciback and e1000e pciback not work.
On Sun, Sep 05, 2010 at 10:55:35AM +0800, ?????? wrote:> 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 ? >Hello, The latest kernel version in xen/stable-2.6.32.x branch is 2.6.32.21. Dunno if it has any fixes that are relevant to you. Anyway, did you read: http://wiki.xensource.com/xenwiki/XenPCIpassthrough -- Pasi _______________________________________________ Xen-devel mailing list Xen-devel@lists.xensource.com http://lists.xensource.com/xen-devel
Thank you for your advise. I update the kernel and xen to the newest version. Now both Dom0 and DomU''s kernels are 2.6.32.21-xen still the e1000e driver in DomU complains about the "Detected Tx Unit Hang", but there is no kernel oops. It seems the new kernel has fixed a bug about pciback. Maybe I should change the /etc/xen/xend-pci-permissive.sxp and /etc/xen/xend-pci-quirks.sxp file ,because I found this in Dom0 dmesg: [ 385.007473] pciback 0000:09:00.1: Driver tried to write to a read-only configuration space field at offset 0xe8, size 2. This may be harmless, but if you have problems with your device: [ 385.007475] 1) see permissive attribute in sysfs [ 385.007475] 2) report problems to the xen-devel mailing list along with details of your device obtained from lspci. note: 09:00.0 is the pci interface I move to DomU . But I don''t know how to change this. I remove the e1000e driver in Dom0 , still it can''t fix the problem. Anyone knows about that? thanks. 2010/9/5 Pasi Kärkkäinen <pasik@iki.fi>> On Sun, Sep 05, 2010 at 10:55:35AM +0800, ?????? wrote: > > 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 ? > > > > Hello, > > The latest kernel version in xen/stable-2.6.32.x branch is 2.6.32.21. > Dunno if it has any fixes that are relevant to you. > > Anyway, did you read: http://wiki.xensource.com/xenwiki/XenPCIpassthrough > > -- Pasi > > > _______________________________________________ > Xen-devel mailing list > Xen-devel@lists.xensource.com > http://lists.xensource.com/xen-devel >-- hepeng ICT _______________________________________________ Xen-devel mailing list Xen-devel@lists.xensource.com http://lists.xensource.com/xen-devel
Pasi Kärkkäinen
2010-Sep-06 09:11 UTC
Re: [Xen-devel] igb pciback and e1000e pciback not work.
On Mon, Sep 06, 2010 at 12:58:48PM +0800, ?????? wrote:> Thank you for your advise. > I update the kernel and xen to the newest version. Now both Dom0 and > DomU''s kernels are 2.6.32.21-xenOk.> still the e1000e driver in DomU complains about the "Detected Tx Unit > Hang", but there is no kernel oops. > It seems the new kernel has fixed a bug about pciback. > Maybe I should change the /etc/xen/xend-pci-permissive.sxp and > /etc/xen/xend-pci-quirks.sxp file ,because I found this in Dom0 dmesg: > [  385.007473] pciback 0000:09:00.1: Driver tried to write to a read-only > configuration space field at offset 0xe8, size 2. This may be harmless, > but if you have problems with your device: > [  385.007475] 1) see permissive attribute in sysfs > [  385.007475] 2) report problems to the xen-devel mailing list along > with details of your device obtained from lspci. > note: 09:00.0 is the pci interface I move to DomU . > But I don''t know how to change this. > I remove the e1000e driver in Dom0 , still it can''t fix the problem. >You shouldn''t use the device (at all) in dom0 when you''re passing it thru to domU! Some questions: - Is that a multiport nic? - Are you using another nic port in dom0? - Do you have the "iommu=soft swiotlb=force" options for the domU kernel? - How much memory does your domU have? -- Pasi> Anyone knows about that? > thanks. > 2010/9/5 Pasi KÀrkkÀinen <[1]pasik@iki.fi> > > On Sun, Sep 05, 2010 at 10:55:35AM +0800, ?????? wrote: > >   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 ? > > > > Hello, > > The latest kernel version in xen/stable-2.6.32.x branch is 2.6.32.21. > Dunno if it has any fixes that are relevant to you. > > Anyway, did you read: > [2]http://wiki.xensource.com/xenwiki/XenPCIpassthrough > > -- Pasi > > _______________________________________________ > Xen-devel mailing list > [3]Xen-devel@lists.xensource.com > [4]http://lists.xensource.com/xen-devel > > -- > hepeng > ICT > > References > > Visible links > 1. mailto:pasik@iki.fi > 2. http://wiki.xensource.com/xenwiki/XenPCIpassthrough > 3. mailto:Xen-devel@lists.xensource.com > 4. http://lists.xensource.com/xen-devel_______________________________________________ Xen-devel mailing list Xen-devel@lists.xensource.com http://lists.xensource.com/xen-devel