* Re: PCI passthrough of 40G ethernet interface (Openstack/KVM)
2015-03-19 8:15 ` Stefan Assmann
@ 2015-03-19 14:00 ` jacob jacob
2015-03-19 14:04 ` [Qemu-devel] " jacob jacob
` (2 subsequent siblings)
3 siblings, 0 replies; 19+ messages in thread
From: jacob jacob @ 2015-03-19 14:00 UTC (permalink / raw)
To: Stefan Assmann
Cc: kvm-devel, netdev, Shannon Nelson, Alex Williamson,
QEMU Developers, Bandan Das
I was going to try this on fedora 21...now not very sure if that makes
much sense..
On Thu, Mar 19, 2015 at 4:15 AM, Stefan Assmann <sassmann@redhat.com> wrote:
> On 18.03.2015 23:06, Shannon Nelson wrote:
>> On Wed, Mar 18, 2015 at 3:01 PM, Shannon Nelson
>> <shannon.nelson@intel.com> wrote:
>>>
>>>
>>> On Wed, Mar 18, 2015 at 8:40 AM, jacob jacob <opstkusr@gmail.com> wrote:
>>>>
>>>> On Wed, Mar 18, 2015 at 11:24 AM, Bandan Das <bsd@redhat.com> wrote:
>>>>>
>>>>> Actually, Stefan suggests that support for this card is still sketchy
>>>>> and your best bet is to try out net-next
>>>>> http://git.kernel.org/cgit/linux/kernel/git/davem/net-next.git
>>>>>
>>>>> Also, could you please post more information about your hardware setup
>>>>> (chipset/processor/firmware version on the card etc) ?
>>>>
>>>> Host CPU : Model name: Intel(R) Xeon(R) CPU E5-2630 v2 @ 2.60GHz
>>>>
>>>> Manufacturer Part Number: XL710QDA1BLK
>>>> Ethernet controller: Intel Corporation Ethernet Controller XL710 for
>>>> 40GbE QSFP+ (rev 01)
>>>> #ethtool -i enp9s0
>>>> driver: i40e
>>>> version: 1.2.6-k
>>>> firmware-version: f4.22 a1.1 n04.24 e800013fd
>>>> bus-info: 0000:09:00.0
>>>> supports-statistics: yes
>>>> supports-test: yes
>>>> supports-eeprom-access: yes
>>>> supports-register-dump: yes
>>>> supports-priv-flags: no
>>>>
>>
>> Jacob,
>>
>> It looks like you're using a NIC with the e800013fd firmware from last
>> summer, and from a separate message that you saw these issues with
>> both the 1.2.2-k and the 1.2.37 version drivers. I suggest the next
>> step would be to update the NIC firmware as there are some performance
>> and stability updates available that deal with similar issues. Please
>> see the Intel Networking support webpage at
>> https://downloadcenter.intel.com/download/24769 and look for the
>> NVMUpdatePackage.zip. This should take care of several of the things
>> Stefan might describe as "sketchy" :-).
>
> Interesting, the following might explain why my XL710 feels a bit
> sketchy then. ;-)
> # ethtool -i p4p1
> driver: i40e
> version: 1.2.37-k
> firmware-version: f4.22.26225 a1.1 n4.24 e12ef
> Looks like the firmware on this NIC is even older.
>
> I tried to update the firmware with nvmupdate64e and the first thing I
> noticed is that you cannot update the firmware even with todays linux
> git. The tool errors out because it cannot access the NVM. Only with a
> recent net-next kernel I was able to update the firmware.
> ethtool -i p4p1
> driver: i40e
> version: 1.2.37-k
> firmware-version: f4.33.31377 a1.2 n4.42 e1932
>
> However during the update I got a lot of errors in dmesg.
> [ 301.796664] i40e 0000:82:00.0: ARQ Error: Unknown event 0x0702 received
> [ 301.893933] i40e 0000:82:00.0: ARQ Error: Unknown event 0x0703 received
> [ 302.005223] i40e 0000:82:00.0: ARQ Error: Unknown event 0x0703 received
> [...]
> [ 387.884635] i40e 0000:82:00.0: ARQ Error: Unknown event 0x0703 received
> [ 387.896862] i40e 0000:82:00.0: ARQ Overflow Error detected
> [ 387.902995] i40e 0000:82:00.0: ARQ Error: Unknown event 0x0703 received
> [...]
> [ 391.583799] i40e 0000:82:00.0: NVMUpdate write failed err=-53 status=0x0 errno=-16 module=70 offset=0x0 size=2
> [ 391.714217] i40e 0000:82:00.0: NVMUpdate write failed err=-53 status=0x0 errno=-16 module=70 offset=0x0 size=2
> [ 391.842656] i40e 0000:82:00.0: NVMUpdate write failed err=-53 status=0x0 errno=-16 module=70 offset=0x0 size=2
> [ 391.973080] i40e 0000:82:00.0: NVMUpdate write failed err=-53 status=0x0 errno=-16 module=70 offset=0x0 size=2
> [ 392.107586] i40e 0000:82:00.0: NVMUpdate write failed err=-53 status=0x0 errno=-16 module=70 offset=0x0 size=2
> [ 392.244140] i40e 0000:82:00.0: NVMUpdate write failed err=-53 status=0x0 errno=-16 module=70 offset=0x0 size=2
> [ 392.373966] i40e 0000:82:00.0: ARQ Error: Unknown event 0x0703 received
>
> Not sure if that flash was actually successful or not.
>
> Stefan
^ permalink raw reply [flat|nested] 19+ messages in thread* Re: [Qemu-devel] PCI passthrough of 40G ethernet interface (Openstack/KVM)
2015-03-19 8:15 ` Stefan Assmann
2015-03-19 14:00 ` jacob jacob
@ 2015-03-19 14:04 ` jacob jacob
2015-03-19 14:18 ` Stefan Assmann
2015-03-19 16:26 ` Shannon Nelson
2015-03-19 21:04 ` jacob jacob
3 siblings, 1 reply; 19+ messages in thread
From: jacob jacob @ 2015-03-19 14:04 UTC (permalink / raw)
To: Stefan Assmann
Cc: Shannon Nelson, Bandan Das, Alex Williamson, QEMU Developers,
kvm-devel, netdev
Hi Stefan,
have you been able to get PCI passthrough working without any issues
after the upgrade?
Thanks
Jacob
On Thu, Mar 19, 2015 at 4:15 AM, Stefan Assmann <sassmann@redhat.com> wrote:
> On 18.03.2015 23:06, Shannon Nelson wrote:
>> On Wed, Mar 18, 2015 at 3:01 PM, Shannon Nelson
>> <shannon.nelson@intel.com> wrote:
>>>
>>>
>>> On Wed, Mar 18, 2015 at 8:40 AM, jacob jacob <opstkusr@gmail.com> wrote:
>>>>
>>>> On Wed, Mar 18, 2015 at 11:24 AM, Bandan Das <bsd@redhat.com> wrote:
>>>>>
>>>>> Actually, Stefan suggests that support for this card is still sketchy
>>>>> and your best bet is to try out net-next
>>>>> http://git.kernel.org/cgit/linux/kernel/git/davem/net-next.git
>>>>>
>>>>> Also, could you please post more information about your hardware setup
>>>>> (chipset/processor/firmware version on the card etc) ?
>>>>
>>>> Host CPU : Model name: Intel(R) Xeon(R) CPU E5-2630 v2 @ 2.60GHz
>>>>
>>>> Manufacturer Part Number: XL710QDA1BLK
>>>> Ethernet controller: Intel Corporation Ethernet Controller XL710 for
>>>> 40GbE QSFP+ (rev 01)
>>>> #ethtool -i enp9s0
>>>> driver: i40e
>>>> version: 1.2.6-k
>>>> firmware-version: f4.22 a1.1 n04.24 e800013fd
>>>> bus-info: 0000:09:00.0
>>>> supports-statistics: yes
>>>> supports-test: yes
>>>> supports-eeprom-access: yes
>>>> supports-register-dump: yes
>>>> supports-priv-flags: no
>>>>
>>
>> Jacob,
>>
>> It looks like you're using a NIC with the e800013fd firmware from last
>> summer, and from a separate message that you saw these issues with
>> both the 1.2.2-k and the 1.2.37 version drivers. I suggest the next
>> step would be to update the NIC firmware as there are some performance
>> and stability updates available that deal with similar issues. Please
>> see the Intel Networking support webpage at
>> https://downloadcenter.intel.com/download/24769 and look for the
>> NVMUpdatePackage.zip. This should take care of several of the things
>> Stefan might describe as "sketchy" :-).
>
> Interesting, the following might explain why my XL710 feels a bit
> sketchy then. ;-)
> # ethtool -i p4p1
> driver: i40e
> version: 1.2.37-k
> firmware-version: f4.22.26225 a1.1 n4.24 e12ef
> Looks like the firmware on this NIC is even older.
>
> I tried to update the firmware with nvmupdate64e and the first thing I
> noticed is that you cannot update the firmware even with todays linux
> git. The tool errors out because it cannot access the NVM. Only with a
> recent net-next kernel I was able to update the firmware.
> ethtool -i p4p1
> driver: i40e
> version: 1.2.37-k
> firmware-version: f4.33.31377 a1.2 n4.42 e1932
>
> However during the update I got a lot of errors in dmesg.
> [ 301.796664] i40e 0000:82:00.0: ARQ Error: Unknown event 0x0702 received
> [ 301.893933] i40e 0000:82:00.0: ARQ Error: Unknown event 0x0703 received
> [ 302.005223] i40e 0000:82:00.0: ARQ Error: Unknown event 0x0703 received
> [...]
> [ 387.884635] i40e 0000:82:00.0: ARQ Error: Unknown event 0x0703 received
> [ 387.896862] i40e 0000:82:00.0: ARQ Overflow Error detected
> [ 387.902995] i40e 0000:82:00.0: ARQ Error: Unknown event 0x0703 received
> [...]
> [ 391.583799] i40e 0000:82:00.0: NVMUpdate write failed err=-53 status=0x0 errno=-16 module=70 offset=0x0 size=2
> [ 391.714217] i40e 0000:82:00.0: NVMUpdate write failed err=-53 status=0x0 errno=-16 module=70 offset=0x0 size=2
> [ 391.842656] i40e 0000:82:00.0: NVMUpdate write failed err=-53 status=0x0 errno=-16 module=70 offset=0x0 size=2
> [ 391.973080] i40e 0000:82:00.0: NVMUpdate write failed err=-53 status=0x0 errno=-16 module=70 offset=0x0 size=2
> [ 392.107586] i40e 0000:82:00.0: NVMUpdate write failed err=-53 status=0x0 errno=-16 module=70 offset=0x0 size=2
> [ 392.244140] i40e 0000:82:00.0: NVMUpdate write failed err=-53 status=0x0 errno=-16 module=70 offset=0x0 size=2
> [ 392.373966] i40e 0000:82:00.0: ARQ Error: Unknown event 0x0703 received
>
> Not sure if that flash was actually successful or not.
>
> Stefan
^ permalink raw reply [flat|nested] 19+ messages in thread
* Re: [Qemu-devel] PCI passthrough of 40G ethernet interface (Openstack/KVM)
2015-03-19 14:04 ` [Qemu-devel] " jacob jacob
@ 2015-03-19 14:18 ` Stefan Assmann
2015-03-20 20:55 ` jacob jacob
0 siblings, 1 reply; 19+ messages in thread
From: Stefan Assmann @ 2015-03-19 14:18 UTC (permalink / raw)
To: jacob jacob
Cc: Shannon Nelson, Bandan Das, Alex Williamson, QEMU Developers,
kvm-devel, netdev
On 19.03.2015 15:04, jacob jacob wrote:
> Hi Stefan,
> have you been able to get PCI passthrough working without any issues
> after the upgrade?
My XL710 fails to transfer regular TCP traffic (netperf). If that works
for you then you're already one step ahead of me. Afraid I can't help
you there.
Stefan
> Thanks
> Jacob
>
> On Thu, Mar 19, 2015 at 4:15 AM, Stefan Assmann <sassmann@redhat.com> wrote:
>> On 18.03.2015 23:06, Shannon Nelson wrote:
>>> On Wed, Mar 18, 2015 at 3:01 PM, Shannon Nelson
>>> <shannon.nelson@intel.com> wrote:
>>>>
>>>>
>>>> On Wed, Mar 18, 2015 at 8:40 AM, jacob jacob <opstkusr@gmail.com> wrote:
>>>>>
>>>>> On Wed, Mar 18, 2015 at 11:24 AM, Bandan Das <bsd@redhat.com> wrote:
>>>>>>
>>>>>> Actually, Stefan suggests that support for this card is still sketchy
>>>>>> and your best bet is to try out net-next
>>>>>> http://git.kernel.org/cgit/linux/kernel/git/davem/net-next.git
>>>>>>
>>>>>> Also, could you please post more information about your hardware setup
>>>>>> (chipset/processor/firmware version on the card etc) ?
>>>>>
>>>>> Host CPU : Model name: Intel(R) Xeon(R) CPU E5-2630 v2 @ 2.60GHz
>>>>>
>>>>> Manufacturer Part Number: XL710QDA1BLK
>>>>> Ethernet controller: Intel Corporation Ethernet Controller XL710 for
>>>>> 40GbE QSFP+ (rev 01)
>>>>> #ethtool -i enp9s0
>>>>> driver: i40e
>>>>> version: 1.2.6-k
>>>>> firmware-version: f4.22 a1.1 n04.24 e800013fd
>>>>> bus-info: 0000:09:00.0
>>>>> supports-statistics: yes
>>>>> supports-test: yes
>>>>> supports-eeprom-access: yes
>>>>> supports-register-dump: yes
>>>>> supports-priv-flags: no
>>>>>
>>>
>>> Jacob,
>>>
>>> It looks like you're using a NIC with the e800013fd firmware from last
>>> summer, and from a separate message that you saw these issues with
>>> both the 1.2.2-k and the 1.2.37 version drivers. I suggest the next
>>> step would be to update the NIC firmware as there are some performance
>>> and stability updates available that deal with similar issues. Please
>>> see the Intel Networking support webpage at
>>> https://downloadcenter.intel.com/download/24769 and look for the
>>> NVMUpdatePackage.zip. This should take care of several of the things
>>> Stefan might describe as "sketchy" :-).
>>
>> Interesting, the following might explain why my XL710 feels a bit
>> sketchy then. ;-)
>> # ethtool -i p4p1
>> driver: i40e
>> version: 1.2.37-k
>> firmware-version: f4.22.26225 a1.1 n4.24 e12ef
>> Looks like the firmware on this NIC is even older.
>>
>> I tried to update the firmware with nvmupdate64e and the first thing I
>> noticed is that you cannot update the firmware even with todays linux
>> git. The tool errors out because it cannot access the NVM. Only with a
>> recent net-next kernel I was able to update the firmware.
>> ethtool -i p4p1
>> driver: i40e
>> version: 1.2.37-k
>> firmware-version: f4.33.31377 a1.2 n4.42 e1932
>>
>> However during the update I got a lot of errors in dmesg.
>> [ 301.796664] i40e 0000:82:00.0: ARQ Error: Unknown event 0x0702 received
>> [ 301.893933] i40e 0000:82:00.0: ARQ Error: Unknown event 0x0703 received
>> [ 302.005223] i40e 0000:82:00.0: ARQ Error: Unknown event 0x0703 received
>> [...]
>> [ 387.884635] i40e 0000:82:00.0: ARQ Error: Unknown event 0x0703 received
>> [ 387.896862] i40e 0000:82:00.0: ARQ Overflow Error detected
>> [ 387.902995] i40e 0000:82:00.0: ARQ Error: Unknown event 0x0703 received
>> [...]
>> [ 391.583799] i40e 0000:82:00.0: NVMUpdate write failed err=-53 status=0x0 errno=-16 module=70 offset=0x0 size=2
>> [ 391.714217] i40e 0000:82:00.0: NVMUpdate write failed err=-53 status=0x0 errno=-16 module=70 offset=0x0 size=2
>> [ 391.842656] i40e 0000:82:00.0: NVMUpdate write failed err=-53 status=0x0 errno=-16 module=70 offset=0x0 size=2
>> [ 391.973080] i40e 0000:82:00.0: NVMUpdate write failed err=-53 status=0x0 errno=-16 module=70 offset=0x0 size=2
>> [ 392.107586] i40e 0000:82:00.0: NVMUpdate write failed err=-53 status=0x0 errno=-16 module=70 offset=0x0 size=2
>> [ 392.244140] i40e 0000:82:00.0: NVMUpdate write failed err=-53 status=0x0 errno=-16 module=70 offset=0x0 size=2
>> [ 392.373966] i40e 0000:82:00.0: ARQ Error: Unknown event 0x0703 received
>>
>> Not sure if that flash was actually successful or not.
>>
>> Stefan
^ permalink raw reply [flat|nested] 19+ messages in thread
* Re: [Qemu-devel] PCI passthrough of 40G ethernet interface (Openstack/KVM)
2015-03-19 14:18 ` Stefan Assmann
@ 2015-03-20 20:55 ` jacob jacob
2015-03-23 7:19 ` Stefan Assmann
0 siblings, 1 reply; 19+ messages in thread
From: jacob jacob @ 2015-03-20 20:55 UTC (permalink / raw)
To: Stefan Assmann
Cc: Shannon Nelson, Bandan Das, Alex Williamson, QEMU Developers,
kvm-devel, netdev
On Thu, Mar 19, 2015 at 10:18 AM, Stefan Assmann <sassmann@redhat.com> wrote:
> On 19.03.2015 15:04, jacob jacob wrote:
>> Hi Stefan,
>> have you been able to get PCI passthrough working without any issues
>> after the upgrade?
>
> My XL710 fails to transfer regular TCP traffic (netperf). If that works
> for you then you're already one step ahead of me. Afraid I can't help
> you there.
I have data transfer working when trying the test runs on the host
itself. Are you seeing problems when directly trying the TCP traffic
from the host itself?
The issues that i am seeing are specific to the case when the devices
are passed via PCI passthrough into the VM.
Any ideas whether this would be a kvm/qemu or i40e driver issue?
(Updating to the latest firmware and using latest i40e driver didn't
seem to help.)
>
> Stefan
>
>> Thanks
>> Jacob
>>
>> On Thu, Mar 19, 2015 at 4:15 AM, Stefan Assmann <sassmann@redhat.com> wrote:
>>> On 18.03.2015 23:06, Shannon Nelson wrote:
>>>> On Wed, Mar 18, 2015 at 3:01 PM, Shannon Nelson
>>>> <shannon.nelson@intel.com> wrote:
>>>>>
>>>>>
>>>>> On Wed, Mar 18, 2015 at 8:40 AM, jacob jacob <opstkusr@gmail.com> wrote:
>>>>>>
>>>>>> On Wed, Mar 18, 2015 at 11:24 AM, Bandan Das <bsd@redhat.com> wrote:
>>>>>>>
>>>>>>> Actually, Stefan suggests that support for this card is still sketchy
>>>>>>> and your best bet is to try out net-next
>>>>>>> http://git.kernel.org/cgit/linux/kernel/git/davem/net-next.git
>>>>>>>
>>>>>>> Also, could you please post more information about your hardware setup
>>>>>>> (chipset/processor/firmware version on the card etc) ?
>>>>>>
>>>>>> Host CPU : Model name: Intel(R) Xeon(R) CPU E5-2630 v2 @ 2.60GHz
>>>>>>
>>>>>> Manufacturer Part Number: XL710QDA1BLK
>>>>>> Ethernet controller: Intel Corporation Ethernet Controller XL710 for
>>>>>> 40GbE QSFP+ (rev 01)
>>>>>> #ethtool -i enp9s0
>>>>>> driver: i40e
>>>>>> version: 1.2.6-k
>>>>>> firmware-version: f4.22 a1.1 n04.24 e800013fd
>>>>>> bus-info: 0000:09:00.0
>>>>>> supports-statistics: yes
>>>>>> supports-test: yes
>>>>>> supports-eeprom-access: yes
>>>>>> supports-register-dump: yes
>>>>>> supports-priv-flags: no
>>>>>>
>>>>
>>>> Jacob,
>>>>
>>>> It looks like you're using a NIC with the e800013fd firmware from last
>>>> summer, and from a separate message that you saw these issues with
>>>> both the 1.2.2-k and the 1.2.37 version drivers. I suggest the next
>>>> step would be to update the NIC firmware as there are some performance
>>>> and stability updates available that deal with similar issues. Please
>>>> see the Intel Networking support webpage at
>>>> https://downloadcenter.intel.com/download/24769 and look for the
>>>> NVMUpdatePackage.zip. This should take care of several of the things
>>>> Stefan might describe as "sketchy" :-).
>>>
>>> Interesting, the following might explain why my XL710 feels a bit
>>> sketchy then. ;-)
>>> # ethtool -i p4p1
>>> driver: i40e
>>> version: 1.2.37-k
>>> firmware-version: f4.22.26225 a1.1 n4.24 e12ef
>>> Looks like the firmware on this NIC is even older.
>>>
>>> I tried to update the firmware with nvmupdate64e and the first thing I
>>> noticed is that you cannot update the firmware even with todays linux
>>> git. The tool errors out because it cannot access the NVM. Only with a
>>> recent net-next kernel I was able to update the firmware.
>>> ethtool -i p4p1
>>> driver: i40e
>>> version: 1.2.37-k
>>> firmware-version: f4.33.31377 a1.2 n4.42 e1932
>>>
>>> However during the update I got a lot of errors in dmesg.
>>> [ 301.796664] i40e 0000:82:00.0: ARQ Error: Unknown event 0x0702 received
>>> [ 301.893933] i40e 0000:82:00.0: ARQ Error: Unknown event 0x0703 received
>>> [ 302.005223] i40e 0000:82:00.0: ARQ Error: Unknown event 0x0703 received
>>> [...]
>>> [ 387.884635] i40e 0000:82:00.0: ARQ Error: Unknown event 0x0703 received
>>> [ 387.896862] i40e 0000:82:00.0: ARQ Overflow Error detected
>>> [ 387.902995] i40e 0000:82:00.0: ARQ Error: Unknown event 0x0703 received
>>> [...]
>>> [ 391.583799] i40e 0000:82:00.0: NVMUpdate write failed err=-53 status=0x0 errno=-16 module=70 offset=0x0 size=2
>>> [ 391.714217] i40e 0000:82:00.0: NVMUpdate write failed err=-53 status=0x0 errno=-16 module=70 offset=0x0 size=2
>>> [ 391.842656] i40e 0000:82:00.0: NVMUpdate write failed err=-53 status=0x0 errno=-16 module=70 offset=0x0 size=2
>>> [ 391.973080] i40e 0000:82:00.0: NVMUpdate write failed err=-53 status=0x0 errno=-16 module=70 offset=0x0 size=2
>>> [ 392.107586] i40e 0000:82:00.0: NVMUpdate write failed err=-53 status=0x0 errno=-16 module=70 offset=0x0 size=2
>>> [ 392.244140] i40e 0000:82:00.0: NVMUpdate write failed err=-53 status=0x0 errno=-16 module=70 offset=0x0 size=2
>>> [ 392.373966] i40e 0000:82:00.0: ARQ Error: Unknown event 0x0703 received
>>>
>>> Not sure if that flash was actually successful or not.
>>>
>>> Stefan
>
^ permalink raw reply [flat|nested] 19+ messages in thread
* Re: [Qemu-devel] PCI passthrough of 40G ethernet interface (Openstack/KVM)
2015-03-20 20:55 ` jacob jacob
@ 2015-03-23 7:19 ` Stefan Assmann
2015-03-24 14:13 ` jacob jacob
0 siblings, 1 reply; 19+ messages in thread
From: Stefan Assmann @ 2015-03-23 7:19 UTC (permalink / raw)
To: jacob jacob
Cc: Shannon Nelson, Bandan Das, Alex Williamson, QEMU Developers,
kvm-devel, netdev
On 20.03.2015 21:55, jacob jacob wrote:
> On Thu, Mar 19, 2015 at 10:18 AM, Stefan Assmann <sassmann@redhat.com> wrote:
>> On 19.03.2015 15:04, jacob jacob wrote:
>>> Hi Stefan,
>>> have you been able to get PCI passthrough working without any issues
>>> after the upgrade?
>>
>> My XL710 fails to transfer regular TCP traffic (netperf). If that works
>> for you then you're already one step ahead of me. Afraid I can't help
>> you there.
>
> I have data transfer working when trying the test runs on the host
> itself. Are you seeing problems when directly trying the TCP traffic
> from the host itself?
Correct.
> The issues that i am seeing are specific to the case when the devices
> are passed via PCI passthrough into the VM.
>
> Any ideas whether this would be a kvm/qemu or i40e driver issue?
> (Updating to the latest firmware and using latest i40e driver didn't
> seem to help.)
Hard to say, that's probably something for Intel to look into.
Stefan
^ permalink raw reply [flat|nested] 19+ messages in thread
* Re: [Qemu-devel] PCI passthrough of 40G ethernet interface (Openstack/KVM)
2015-03-23 7:19 ` Stefan Assmann
@ 2015-03-24 14:13 ` jacob jacob
2015-03-24 14:53 ` Shannon Nelson
0 siblings, 1 reply; 19+ messages in thread
From: jacob jacob @ 2015-03-24 14:13 UTC (permalink / raw)
To: Stefan Assmann
Cc: Shannon Nelson, Bandan Das, Alex Williamson, QEMU Developers,
kvm-devel, netdev
After update to latest firmware and using version 1.2.37 of i40e
driver, things are looking better with PCI passthrough.
]# ethtool -i eth3
driver: i40e
version: 1.2.37
firmware-version: f4.33.31377 a1.2 n4.42 e1930
bus-info: 0000:00:07.0
supports-statistics: yes
supports-test: yes
supports-eeprom-access: yes
supports-register-dump: yes
supports-priv-flags: yes
There are still issues running dpdk 1.8.0 from the VM using the pci
passthrough devices and looks like it puts the devices in a bad state.
i40e driver will not bind after this happens and a host reboot is
required to recover.
I'll post further updates as i make progress.
Thanks for all the help.
On Mon, Mar 23, 2015 at 3:19 AM, Stefan Assmann <sassmann@redhat.com> wrote:
> On 20.03.2015 21:55, jacob jacob wrote:
>> On Thu, Mar 19, 2015 at 10:18 AM, Stefan Assmann <sassmann@redhat.com> wrote:
>>> On 19.03.2015 15:04, jacob jacob wrote:
>>>> Hi Stefan,
>>>> have you been able to get PCI passthrough working without any issues
>>>> after the upgrade?
>>>
>>> My XL710 fails to transfer regular TCP traffic (netperf). If that works
>>> for you then you're already one step ahead of me. Afraid I can't help
>>> you there.
>>
>> I have data transfer working when trying the test runs on the host
>> itself. Are you seeing problems when directly trying the TCP traffic
>> from the host itself?
>
> Correct.
>
>> The issues that i am seeing are specific to the case when the devices
>> are passed via PCI passthrough into the VM.
>>
>> Any ideas whether this would be a kvm/qemu or i40e driver issue?
>> (Updating to the latest firmware and using latest i40e driver didn't
>> seem to help.)
>
> Hard to say, that's probably something for Intel to look into.
>
> Stefan
^ permalink raw reply [flat|nested] 19+ messages in thread
* Re: [Qemu-devel] PCI passthrough of 40G ethernet interface (Openstack/KVM)
2015-03-24 14:13 ` jacob jacob
@ 2015-03-24 14:53 ` Shannon Nelson
2015-03-24 15:04 ` jacob jacob
0 siblings, 1 reply; 19+ messages in thread
From: Shannon Nelson @ 2015-03-24 14:53 UTC (permalink / raw)
To: jacob jacob
Cc: Stefan Assmann, Bandan Das, Alex Williamson, QEMU Developers,
kvm-devel, netdev
On Tue, Mar 24, 2015 at 7:13 AM, jacob jacob <opstkusr@gmail.com> wrote:
> After update to latest firmware and using version 1.2.37 of i40e
> driver, things are looking better with PCI passthrough.
>
> ]# ethtool -i eth3
> driver: i40e
> version: 1.2.37
> firmware-version: f4.33.31377 a1.2 n4.42 e1930
> bus-info: 0000:00:07.0
> supports-statistics: yes
> supports-test: yes
> supports-eeprom-access: yes
> supports-register-dump: yes
> supports-priv-flags: yes
I'm glad the updates helped as we expected.
>
> There are still issues running dpdk 1.8.0 from the VM using the pci
> passthrough devices and looks like it puts the devices in a bad state.
> i40e driver will not bind after this happens and a host reboot is
> required to recover.
Did you make sure to unbind the i40e device from pci-stub after you
were done with using it in the VM?
> I'll post further updates as i make progress.
> Thanks for all the help.
>
Good luck,
sln
^ permalink raw reply [flat|nested] 19+ messages in thread
* Re: PCI passthrough of 40G ethernet interface (Openstack/KVM)
2015-03-24 14:53 ` Shannon Nelson
@ 2015-03-24 15:04 ` jacob jacob
2015-03-26 1:00 ` [Qemu-devel] " Shannon Nelson
0 siblings, 1 reply; 19+ messages in thread
From: jacob jacob @ 2015-03-24 15:04 UTC (permalink / raw)
To: Shannon Nelson
Cc: kvm-devel, netdev, Alex Williamson, QEMU Developers, Bandan Das,
Stefan Assmann
On Tue, Mar 24, 2015 at 10:53 AM, Shannon Nelson
<shannon.nelson@intel.com> wrote:
> On Tue, Mar 24, 2015 at 7:13 AM, jacob jacob <opstkusr@gmail.com> wrote:
>> After update to latest firmware and using version 1.2.37 of i40e
>> driver, things are looking better with PCI passthrough.
>>
>> ]# ethtool -i eth3
>> driver: i40e
>> version: 1.2.37
>> firmware-version: f4.33.31377 a1.2 n4.42 e1930
>> bus-info: 0000:00:07.0
>> supports-statistics: yes
>> supports-test: yes
>> supports-eeprom-access: yes
>> supports-register-dump: yes
>> supports-priv-flags: yes
>
> I'm glad the updates helped as we expected.
>
>>
>> There are still issues running dpdk 1.8.0 from the VM using the pci
>> passthrough devices and looks like it puts the devices in a bad state.
>> i40e driver will not bind after this happens and a host reboot is
>> required to recover.
>
> Did you make sure to unbind the i40e device from pci-stub after you
> were done with using it in the VM?
The issue is running dpdk from within the vm itself. Is it possible
that the igb_uio driver needs additional updates/functionality to be
at parity with 1.2.37 version of i40e driver?
>
>> I'll post further updates as i make progress.
>> Thanks for all the help.
>>
>
> Good luck,
> sln
^ permalink raw reply [flat|nested] 19+ messages in thread
* Re: [Qemu-devel] PCI passthrough of 40G ethernet interface (Openstack/KVM)
2015-03-24 15:04 ` jacob jacob
@ 2015-03-26 1:00 ` Shannon Nelson
0 siblings, 0 replies; 19+ messages in thread
From: Shannon Nelson @ 2015-03-26 1:00 UTC (permalink / raw)
To: jacob jacob
Cc: Stefan Assmann, Bandan Das, Alex Williamson, QEMU Developers,
kvm-devel, netdev
On Tue, Mar 24, 2015 at 8:04 AM, jacob jacob <opstkusr@gmail.com> wrote:
>
> The issue is running dpdk from within the vm itself. Is it possible
> that the igb_uio driver needs additional updates/functionality to be
> at parity with 1.2.37 version of i40e driver?
>
At this point I think you need to work with the DPDK folks. We don't
directly support or test the PF driver in a passthru mode, and DPDK
folks will have a better idea how this might affect their driver.
sln
^ permalink raw reply [flat|nested] 19+ messages in thread
* Re: [Qemu-devel] PCI passthrough of 40G ethernet interface (Openstack/KVM)
2015-03-19 8:15 ` Stefan Assmann
2015-03-19 14:00 ` jacob jacob
2015-03-19 14:04 ` [Qemu-devel] " jacob jacob
@ 2015-03-19 16:26 ` Shannon Nelson
2015-03-19 21:04 ` jacob jacob
3 siblings, 0 replies; 19+ messages in thread
From: Shannon Nelson @ 2015-03-19 16:26 UTC (permalink / raw)
To: Stefan Assmann
Cc: jacob jacob, Bandan Das, Alex Williamson, QEMU Developers,
kvm-devel, netdev
On Thu, Mar 19, 2015 at 1:15 AM, Stefan Assmann <sassmann@redhat.com> wrote:
> Interesting, the following might explain why my XL710 feels a bit
> sketchy then. ;-)
> # ethtool -i p4p1
> driver: i40e
> version: 1.2.37-k
> firmware-version: f4.22.26225 a1.1 n4.24 e12ef
> Looks like the firmware on this NIC is even older.
>
> I tried to update the firmware with nvmupdate64e and the first thing I
> noticed is that you cannot update the firmware even with todays linux
> git. The tool errors out because it cannot access the NVM. Only with a
> recent net-next kernel I was able to update the firmware.
> ethtool -i p4p1
> driver: i40e
> version: 1.2.37-k
> firmware-version: f4.33.31377 a1.2 n4.42 e1932
>
> However during the update I got a lot of errors in dmesg.
> [ 301.796664] i40e 0000:82:00.0: ARQ Error: Unknown event 0x0702 received
> [ 301.893933] i40e 0000:82:00.0: ARQ Error: Unknown event 0x0703 received
> [ 302.005223] i40e 0000:82:00.0: ARQ Error: Unknown event 0x0703 received
> [...]
> [ 387.884635] i40e 0000:82:00.0: ARQ Error: Unknown event 0x0703 received
> [ 387.896862] i40e 0000:82:00.0: ARQ Overflow Error detected
> [ 387.902995] i40e 0000:82:00.0: ARQ Error: Unknown event 0x0703 received
These are bogus messages should not have been generated, but it seems
there's a case statement missing in the upstream code. I'll get a
patch together for this later today.
> [...]
> [ 391.583799] i40e 0000:82:00.0: NVMUpdate write failed err=-53 status=0x0 errno=-16 module=70 offset=0x0 size=2
> [ 391.714217] i40e 0000:82:00.0: NVMUpdate write failed err=-53 status=0x0 errno=-16 module=70 offset=0x0 size=2
> [ 391.842656] i40e 0000:82:00.0: NVMUpdate write failed err=-53 status=0x0 errno=-16 module=70 offset=0x0 size=2
> [ 391.973080] i40e 0000:82:00.0: NVMUpdate write failed err=-53 status=0x0 errno=-16 module=70 offset=0x0 size=2
> [ 392.107586] i40e 0000:82:00.0: NVMUpdate write failed err=-53 status=0x0 errno=-16 module=70 offset=0x0 size=2
> [ 392.244140] i40e 0000:82:00.0: NVMUpdate write failed err=-53 status=0x0 errno=-16 module=70 offset=0x0 size=2
> [ 392.373966] i40e 0000:82:00.0: ARQ Error: Unknown event 0x0703 received
These are an annoying result of a user tool issue.
>
> Not sure if that flash was actually successful or not.
Since the driver was able to restart and give you the version
information from ethtool -i, the update was successful. You are not
supposed to have to powercycle your system after the NVM update, but
it's a good idea anyway, especially when updating the older firmware
like what you had.
sln
^ permalink raw reply [flat|nested] 19+ messages in thread
* Re: [Qemu-devel] PCI passthrough of 40G ethernet interface (Openstack/KVM)
2015-03-19 8:15 ` Stefan Assmann
` (2 preceding siblings ...)
2015-03-19 16:26 ` Shannon Nelson
@ 2015-03-19 21:04 ` jacob jacob
2015-03-19 21:42 ` Shannon Nelson
3 siblings, 1 reply; 19+ messages in thread
From: jacob jacob @ 2015-03-19 21:04 UTC (permalink / raw)
To: Stefan Assmann
Cc: Shannon Nelson, Bandan Das, Alex Williamson, QEMU Developers,
kvm-devel, netdev
I have updated to latest firmware and still no luck.
]# ethtool -i eth1
driver: i40e
version: 1.2.37
firmware-version: f4.33.31377 a1.2 n4.42 e1930
bus-info: 0000:00:05.0
supports-statistics: yes
supports-test: yes
supports-eeprom-access: yes
supports-register-dump: yes
supports-priv-flags: yes
Seeing similar results as before :
1)Everything works fine on host (used i40e version 1.2.37 and dpdk 1.8.0)
2)In vm tried both i40e driver version 1.2.37 and dpdk 1.8.0 and data
tx fails (I have 2 40G interfaces passed through to a VM):See the
following error now in the VM which looks interesting...
[ 5.449672] i40e 0000:00:06.0: f4.33.31377 a1.2 n4.42 e1930
[ 5.525061] i40e 0000:00:06.0: FCoE capability is disabled
[ 5.528786] i40e 0000:00:06.0: MAC address: 68:05:ca:2e:80:50
[ 5.534491] i40e 0000:00:06.0: SAN MAC: 68:05:ca:2e:80:54
[ 5.544081] i40e 0000:00:06.0: AQ Querying DCB configuration failed: aq_err 1
[ 5.545870] i40e 0000:00:06.0: DCB init failed -53, disabled
[ 5.547462] i40e 0000:00:06.0: fcoe queues = 0
[ 5.548970] i40e 0000:00:06.0: irq 43 for MSI/MSI-X
[ 5.548987] i40e 0000:00:06.0: irq 44 for MSI/MSI-X
[ 5.549012] i40e 0000:00:06.0: irq 45 for MSI/MSI-X
[ 5.549028] i40e 0000:00:06.0: irq 46 for MSI/MSI-X
[ 5.549044] i40e 0000:00:06.0: irq 47 for MSI/MSI-X
[ 5.549059] i40e 0000:00:06.0: irq 48 for MSI/MSI-X
[ 5.549074] i40e 0000:00:06.0: irq 49 for MSI/MSI-X
[ 5.549089] i40e 0000:00:06.0: irq 50 for MSI/MSI-X
[ 5.549103] i40e 0000:00:06.0: irq 51 for MSI/MSI-X
[ 5.549117] i40e 0000:00:06.0: irq 52 for MSI/MSI-X
[ 5.549132] i40e 0000:00:06.0: irq 53 for MSI/MSI-X
[ 5.549146] i40e 0000:00:06.0: irq 54 for MSI/MSI-X
[ 5.549160] i40e 0000:00:06.0: irq 55 for MSI/MSI-X
[ 5.549174] i40e 0000:00:06.0: irq 56 for MSI/MSI-X
[ 5.579062] i40e 0000:00:06.0: enabling bridge mode: VEB
[ 5.615344] i40e 0000:00:06.0: PHC enabled
[ 5.636028] i40e 0000:00:06.0: PCI-Express: Speed 8.0GT/s Width x8
[ 5.639822] audit: type=1305 audit(1426797692.463:4): audit_pid=345
old=0 auid=4294967295 ses=4294967295
subj=system_u:system_r:auditd_t:s0 res=1
[ 5.651225] i40e 0000:00:06.0: Features: PF-id[0] VFs: 128 VSIs:
130 QP: 4 RX: 1BUF RSS FD_ATR FD_SB NTUPLE PTP
[ 12.720451] SELinux: initialized (dev tmpfs, type tmpfs), uses
transition SIDs
[ 15.909477] SELinux: initialized (dev tmpfs, type tmpfs), uses
transition SIDs
[ 61.553491] i40e 0000:00:06.0 eth2: NIC Link is Down
[ 61.554132] i40e 0000:00:06.0 eth2: the driver failed to link
because an unqualified module was detected. <<<<<<<<<<<<<<<<<<<<
[ 61.555331] IPv6: ADDRCONF(NETDEV_UP): eth2: link is not ready
With dpdk, see the following output in the VM:
testpmd> stop
Telling cores to stop...
Waiting for lcores to finish...
---------------------- Forward statistics for port 0 ----------------------
RX-packets: 41328971 RX-dropped: 0 RX-total: 41328971
TX-packets: 0 TX-dropped: 0 TX-total: 0
----------------------------------------------------------------------------
---------------------- Forward statistics for port 1 ----------------------
RX-packets: 0 RX-dropped: 0 RX-total: 0
TX-packets: 41328972 TX-dropped: 0 TX-total: 41328972
----------------------------------------------------------------------------
+++++++++++++++ Accumulated forward statistics for all ports+++++++++++++++
RX-packets: 41328971 RX-dropped: 0 RX-total: 41328971
TX-packets: 41328972 TX-dropped: 0 TX-total: 41328972
++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++
Here it can be seen that one of the ports transmits just fine. I have
verified that it is not a card,pci port or any such hw issues..
On Thu, Mar 19, 2015 at 4:15 AM, Stefan Assmann <sassmann@redhat.com> wrote:
> On 18.03.2015 23:06, Shannon Nelson wrote:
>> On Wed, Mar 18, 2015 at 3:01 PM, Shannon Nelson
>> <shannon.nelson@intel.com> wrote:
>>>
>>>
>>> On Wed, Mar 18, 2015 at 8:40 AM, jacob jacob <opstkusr@gmail.com> wrote:
>>>>
>>>> On Wed, Mar 18, 2015 at 11:24 AM, Bandan Das <bsd@redhat.com> wrote:
>>>>>
>>>>> Actually, Stefan suggests that support for this card is still sketchy
>>>>> and your best bet is to try out net-next
>>>>> http://git.kernel.org/cgit/linux/kernel/git/davem/net-next.git
>>>>>
>>>>> Also, could you please post more information about your hardware setup
>>>>> (chipset/processor/firmware version on the card etc) ?
>>>>
>>>> Host CPU : Model name: Intel(R) Xeon(R) CPU E5-2630 v2 @ 2.60GHz
>>>>
>>>> Manufacturer Part Number: XL710QDA1BLK
>>>> Ethernet controller: Intel Corporation Ethernet Controller XL710 for
>>>> 40GbE QSFP+ (rev 01)
>>>> #ethtool -i enp9s0
>>>> driver: i40e
>>>> version: 1.2.6-k
>>>> firmware-version: f4.22 a1.1 n04.24 e800013fd
>>>> bus-info: 0000:09:00.0
>>>> supports-statistics: yes
>>>> supports-test: yes
>>>> supports-eeprom-access: yes
>>>> supports-register-dump: yes
>>>> supports-priv-flags: no
>>>>
>>
>> Jacob,
>>
>> It looks like you're using a NIC with the e800013fd firmware from last
>> summer, and from a separate message that you saw these issues with
>> both the 1.2.2-k and the 1.2.37 version drivers. I suggest the next
>> step would be to update the NIC firmware as there are some performance
>> and stability updates available that deal with similar issues. Please
>> see the Intel Networking support webpage at
>> https://downloadcenter.intel.com/download/24769 and look for the
>> NVMUpdatePackage.zip. This should take care of several of the things
>> Stefan might describe as "sketchy" :-).
>
> Interesting, the following might explain why my XL710 feels a bit
> sketchy then. ;-)
> # ethtool -i p4p1
> driver: i40e
> version: 1.2.37-k
> firmware-version: f4.22.26225 a1.1 n4.24 e12ef
> Looks like the firmware on this NIC is even older.
>
> I tried to update the firmware with nvmupdate64e and the first thing I
> noticed is that you cannot update the firmware even with todays linux
> git. The tool errors out because it cannot access the NVM. Only with a
> recent net-next kernel I was able to update the firmware.
> ethtool -i p4p1
> driver: i40e
> version: 1.2.37-k
> firmware-version: f4.33.31377 a1.2 n4.42 e1932
>
> However during the update I got a lot of errors in dmesg.
> [ 301.796664] i40e 0000:82:00.0: ARQ Error: Unknown event 0x0702 received
> [ 301.893933] i40e 0000:82:00.0: ARQ Error: Unknown event 0x0703 received
> [ 302.005223] i40e 0000:82:00.0: ARQ Error: Unknown event 0x0703 received
> [...]
> [ 387.884635] i40e 0000:82:00.0: ARQ Error: Unknown event 0x0703 received
> [ 387.896862] i40e 0000:82:00.0: ARQ Overflow Error detected
> [ 387.902995] i40e 0000:82:00.0: ARQ Error: Unknown event 0x0703 received
> [...]
> [ 391.583799] i40e 0000:82:00.0: NVMUpdate write failed err=-53 status=0x0 errno=-16 module=70 offset=0x0 size=2
> [ 391.714217] i40e 0000:82:00.0: NVMUpdate write failed err=-53 status=0x0 errno=-16 module=70 offset=0x0 size=2
> [ 391.842656] i40e 0000:82:00.0: NVMUpdate write failed err=-53 status=0x0 errno=-16 module=70 offset=0x0 size=2
> [ 391.973080] i40e 0000:82:00.0: NVMUpdate write failed err=-53 status=0x0 errno=-16 module=70 offset=0x0 size=2
> [ 392.107586] i40e 0000:82:00.0: NVMUpdate write failed err=-53 status=0x0 errno=-16 module=70 offset=0x0 size=2
> [ 392.244140] i40e 0000:82:00.0: NVMUpdate write failed err=-53 status=0x0 errno=-16 module=70 offset=0x0 size=2
> [ 392.373966] i40e 0000:82:00.0: ARQ Error: Unknown event 0x0703 received
>
> Not sure if that flash was actually successful or not.
>
> Stefan
^ permalink raw reply [flat|nested] 19+ messages in thread* Re: [Qemu-devel] PCI passthrough of 40G ethernet interface (Openstack/KVM)
2015-03-19 21:04 ` jacob jacob
@ 2015-03-19 21:42 ` Shannon Nelson
2015-03-19 21:53 ` jacob jacob
0 siblings, 1 reply; 19+ messages in thread
From: Shannon Nelson @ 2015-03-19 21:42 UTC (permalink / raw)
To: jacob jacob
Cc: Stefan Assmann, Bandan Das, Alex Williamson, QEMU Developers,
kvm-devel, netdev
On Thu, Mar 19, 2015 at 2:04 PM, jacob jacob <opstkusr@gmail.com> wrote:
> I have updated to latest firmware and still no luck.
[...]
> [ 61.554132] i40e 0000:00:06.0 eth2: the driver failed to link
> because an unqualified module was detected. <<<<<<<<<<<<<<<<<<<<
> [ 61.555331] IPv6: ADDRCONF(NETDEV_UP): eth2: link is not ready
>
So I assume you're getting traffic on the other port and it doesn't
complain about "unqualified module"? Does the problem move if you
swap the cables? The usual problem here is a QSFP connector that
isn't compatible with the NIC. I don't have a pointer handy to the
official list, but you should be able to get that from your NIC
supplier.
sln
^ permalink raw reply [flat|nested] 19+ messages in thread
* Re: [Qemu-devel] PCI passthrough of 40G ethernet interface (Openstack/KVM)
2015-03-19 21:42 ` Shannon Nelson
@ 2015-03-19 21:53 ` jacob jacob
2015-03-19 23:37 ` jacob jacob
0 siblings, 1 reply; 19+ messages in thread
From: jacob jacob @ 2015-03-19 21:53 UTC (permalink / raw)
To: Shannon Nelson
Cc: Stefan Assmann, Bandan Das, Alex Williamson, QEMU Developers,
kvm-devel, netdev
On Thu, Mar 19, 2015 at 5:42 PM, Shannon Nelson
<shannon.nelson@intel.com> wrote:
> On Thu, Mar 19, 2015 at 2:04 PM, jacob jacob <opstkusr@gmail.com> wrote:
>> I have updated to latest firmware and still no luck.
>
> [...]
>
>> [ 61.554132] i40e 0000:00:06.0 eth2: the driver failed to link
>> because an unqualified module was detected. <<<<<<<<<<<<<<<<<<<<
>> [ 61.555331] IPv6: ADDRCONF(NETDEV_UP): eth2: link is not ready
>>
>
> So I assume you're getting traffic on the other port and it doesn't
> complain about "unqualified module"? Does the problem move if you
> swap the cables? The usual problem here is a QSFP connector that
> isn't compatible with the NIC. I don't have a pointer handy to the
> official list, but you should be able to get that from your NIC
> supplier.
No. That is not the case.
The traffic counters are for the dpdk test run which uses igb_uio driver.
As i mentioned earlier, have tried all combinations of cable, pci slot
, card etc to isolate any hw issues.
^ permalink raw reply [flat|nested] 19+ messages in thread
* Re: PCI passthrough of 40G ethernet interface (Openstack/KVM)
2015-03-19 21:53 ` jacob jacob
@ 2015-03-19 23:37 ` jacob jacob
0 siblings, 0 replies; 19+ messages in thread
From: jacob jacob @ 2015-03-19 23:37 UTC (permalink / raw)
To: Shannon Nelson
Cc: kvm-devel, netdev, Alex Williamson, QEMU Developers, Bandan Das,
Stefan Assmann
On Thu, Mar 19, 2015 at 5:53 PM, jacob jacob <opstkusr@gmail.com> wrote:
> On Thu, Mar 19, 2015 at 5:42 PM, Shannon Nelson
> <shannon.nelson@intel.com> wrote:
>> On Thu, Mar 19, 2015 at 2:04 PM, jacob jacob <opstkusr@gmail.com> wrote:
>>> I have updated to latest firmware and still no luck.
>>
>> [...]
>>
>>> [ 61.554132] i40e 0000:00:06.0 eth2: the driver failed to link
>>> because an unqualified module was detected. <<<<<<<<<<<<<<<<<<<<
>>> [ 61.555331] IPv6: ADDRCONF(NETDEV_UP): eth2: link is not ready
>>>
>>
>> So I assume you're getting traffic on the other port and it doesn't
>> complain about "unqualified module"? Does the problem move if you
>> swap the cables? The usual problem here is a QSFP connector that
>> isn't compatible with the NIC. I don't have a pointer handy to the
>> official list, but you should be able to get that from your NIC
>> supplier.
>
> No. That is not the case.
>
> The traffic counters are for the dpdk test run which uses igb_uio driver.
>
> As i mentioned earlier, have tried all combinations of cable, pci slot
> , card etc to isolate any hw issues.
Everything works fine on the host and hence the
modules are verified to be working.
The issue is seen only when the device is passed through to a VM
running on the same host.
^ permalink raw reply [flat|nested] 19+ messages in thread