netdev - Re: [Intel-wired-lan] SRIOV on Intel x710 fail to get attached both at VM creation time and VM runtime

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [day] [month] [year] [list]

Message-ID: <CAKgT0Ue1oFzkxiDXR-F1EnQQitMLsyZRjfmXhBWY-BNtANMcjQ@mail.gmail.com>
Date:   Fri, 2 Mar 2018 12:58:41 -0800
From:   Alexander Duyck <alexander.duyck@...il.com>
To:     Stefan Assmann <sassmann@...hat.com>
Cc:     poza@...eaurora.org, Sinan Kaya <okaya@...eaurora.org>,
        Netdev <netdev@...r.kernel.org>,
        intel-wired-lan <intel-wired-lan@...ts.osuosl.org>
Subject: Re: [Intel-wired-lan] SRIOV on Intel x710 fail to get attached both
 at VM creation time and VM runtime

On Thu, Mar 1, 2018 at 11:21 PM, Stefan Assmann <sassmann@...hat.com> wrote:
> On 2018-03-01 19:40, Alexander Duyck wrote:
>> On Thu, Mar 1, 2018 at 8:12 AM,  <poza@...eaurora.org> wrote:
>> > + intel-wired-lan@...ts.osuosl.org
>> >
>> >
>> > On 2018-03-01 21:41, poza@...eaurora.org wrote:
>> >>
>> >> Hi All,
>> >>
>> >> I am facing the following issue on kernel 4.14.14.
>> >>
>> >> Enable SRIOV on Intel x710 card.
>> >> echo 32 > /sys/class/net/eth1/device/sriov_numvfs
>> >> start net_pool
>> >> virsh net-start intel_pool
>> >>
>> >> case 1)
>> >> attach the VF while creatig VM:
>> >> virt-install --accelerate --import --disk /home/disk.img --network
>> >> network=intel_pool  --boot uefi --name poza-guest --os-type linux
>> >> --os-variant rhel7 --ram 8000 --vcpus 4
>> >>
>> >> case 2)
>> >> create VM:
>> >> virt-install --accelerate --import --disk /home/disk.img --boot uefi
>> >> --name poza-guest --os-type linux --os-variant rhel7 --ram 8000
>> >> --vcpus 4
>> >> attach it:
>> >> virsh attach-interface --domain oza-guest --type network --source
>> >> intel_pool --target eth1
>> >>
>> >> kernel logs:
>> >> [44287.825287] i40evf 0000:01:02.0: Unable to send opcode 2 to PF, err
>> >> I40E_ERR_QUEUE_EMPTY, aq_err OK
>> >> [44287.962640] i40e 0000:01:00.0: VF 0 still in reset. Try again.
>> >> error: Failed to attach interface
>> >> error: Cannot set interface MAC/vlanid to 52:54:00:e9:f1:b5/0 for
>> >> ifname eth1 vf 0: Resource temporarily unavailable
>> >>
>> >>
>> >> The same use case works with following card with the same kernel
>> >> version and rootfs.
>> >> Ethernet controller: Mellanox Technologies MT27710 Family [ConnectX-4 Lx]
>> >>
>> >> for details logs please have a look at
>> >> https://bugzilla.kernel.org/show_bug.cgi?id=198959
>> >>
>> >> Regards,
>> >> Oza.
>>
>> So the first question that jumps to mind is what is the firmware
>> version on the PF, ethtool -i should tell you. Are there any issues
>> bringing up the PF and getting it to pass traffic?
>
> There's a patch on Intel-wired-lan titled "i40e: Fix attach VF to VM
> issue" which should fix the problem. It's not upstream yet.
>
> As a workaround you could unload/blacklist the i40evf driver in the
> host.
>
>   Stefan

Either that or there should be an sriov_drivers_autoprobe sysfs value
for the PF that you can set to 0 and that should prevent the VF
drivers from auto-loading.

- Alex