This bug is missing log files that will aid in diagnosing the problem.
>From a terminal window please run:
and then change the status of the bug to 'Confirmed'.
If, due to the nature of the issue you have encountered, you are unable
to run this command, please add a comment stating that fact and change
the bug status to 'Confirmed'.
This change has been made by an automated script, maintained by the
Ubuntu Kernel Team.
** Changed in: linux (Ubuntu)
Status: New => Incomplete
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
Please enable CONFIG_VFIO_NOIOMMU
Status in dpdk package in Ubuntu:
Status in linux package in Ubuntu:
for certain cases a user might want to use VFIO in NO IOMMU mode.
This only enables it to be an option, it doesn't change things unless
"enable_unsafe_noiommu_mode" is set. See this reference:
https://patchwork.kernel.org/patch/7906971/ for more details.
This is used for some setups of DPDK see this http://dpdk-
Usually the reason to pick vfio over uio is the isolation. But there
are some cases where vfio is required for extra features but can't
work unless NO-IOMMU mode is used.
I watched the topic a while checking if there is some major "oh crap
what have we done" but there was none. An since by only enabling it in
the kernel it shouldn't change a lot I wanted to ask if you could
enable this config in the kernel for Z*.
Technically it would be nice to get it in Yakkety as well, but I think
we should be fine only working forward and enabling it in the Z
To manage notifications about this bug go to:
Mailing list: https://launchpad.net/~kernel-packages
Post to : email@example.com
Unsubscribe : https://launchpad.net/~kernel-packages
More help : https://help.launchpad.net/ListHelp