This bug is missing log files that will aid in diagnosing the problem.
>From a terminal window please run:

apport-collect 1634050

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.


Status in dpdk package in Ubuntu:
Status in linux package in Ubuntu:

Bug description:
  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: 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:
Post to     :
Unsubscribe :
More help   :

Reply via email to