Ubuntu 16.10 KVM: kernel 4.8 can not enable SRIOV for power systems
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
linux (Ubuntu) |
Fix Released
|
Undecided
|
Tim Gardner | ||
Yakkety |
Fix Released
|
Undecided
|
Tim Gardner |
Bug Description
---Problem Description---
Using Ubuntu mainline kernel
http://
if we try to enable SRIOV in Mellanox CX4 card it will fail.
# uname -r
4.8.0-040800rc6
root@c158f2u09os:~# echo 7 > /sys/class/
-bash: echo: write error: Cannot allocate memory
logs show:
Sep 16 00:52:46 c158f2u09os kernel: [ 1419.778118] mlx5_core 0005:01:00.0: not enough MMIO resources for SR-IOV
Sep 16 00:52:46 c158f2u09os kernel: [ 1419.778238] mlx5_core 0005:01:00.0: enable sriov failed -12
Sep 16 00:52:46 c158f2u09os kernel: [ 1419.778604] mlx5_core 0005:01:00.0: mlx5_core_
---uname output---
4.8.0-040800rc6
---Additional Hardware Info---
To recreate this you need power system and a Mellanox card that can be used for SRIOV.
Machine Type = P8
---Steps to Reproduce---
with a Mellanox card like CX4 with SRIOV enabled.
just do this echo to the PF interface in this case was enP5p1s0f0.
echo 1 > /sys/class/
If I take kernel 4.8 and I revert the following patch I can get it to work again:
From 5958d19a143eb22
From: Benjamin Herrenschmidt <email address hidden>
Date: Fri, 8 Jul 2016 15:55:43 +1000
Subject: powerpc/pnv/pci: Fix incorrect PE reservation attempt on some 64-bit BARs
tags: | added: architecture-ppc64le bugnameltc-146447 severity-critical targetmilestone-inin1610 |
Changed in ubuntu: | |
assignee: | nobody → Taco Screen team (taco-screen-team) |
affects: | ubuntu → linux (Ubuntu) |
Can you also confirm this with an Ubuntu based v4.8-rc6 kernel (currently available in yakkety-proposed)
https:/ /launchpad. net/ubuntu/ +source/ linux/4. 8.0-11. 12
Based on the bug description, it appears this is a regression which originates from upstream and was introduced in 4.8-rc2:
linux$ git describe --contains 5958d19a143eb22 9e9ece20bd4c781 ad41cb7d24
v4.8-rc2~20^2~9
Upstream is now at v4.8-rc7. If the issue remains, please report this upstream as well.