From: poza@codeaurora.org
To: jeffrey.t.kirsher@intel.com, intel-wired-lan@lists.osuosl.rg,
netdev@vger.kernel.org
Cc: okaya@codeaurora.org
Subject: SRIOV on Intel x710 fail to get attached both at VM creation time and VM runtime
Date: Thu, 01 Mar 2018 21:41:14 +0530 [thread overview]
Message-ID: <39dcd27f99192edd77baf4e418443edd@codeaurora.org> (raw)
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.
next reply other threads:[~2018-03-01 16:11 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-03-01 16:11 poza [this message]
2018-03-01 16:12 ` SRIOV on Intel x710 fail to get attached both at VM creation time and VM runtime poza
2018-03-02 3:40 ` Alexander Duyck
2018-03-02 6:11 ` poza
2018-03-02 7:21 ` [Intel-wired-lan] " Stefan Assmann
2018-03-02 20:58 ` Alexander Duyck
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=39dcd27f99192edd77baf4e418443edd@codeaurora.org \
--to=poza@codeaurora.org \
--cc=intel-wired-lan@lists.osuosl.rg \
--cc=jeffrey.t.kirsher@intel.com \
--cc=netdev@vger.kernel.org \
--cc=okaya@codeaurora.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).