Bug 1762087 - [RFE] support vIOMMU device in nova
Summary: [RFE] support vIOMMU device in nova
Keywords:
Status: CLOSED DEFERRED
Alias: None
Product: Red Hat OpenStack
Classification: Red Hat
Component: openstack-nova
Version: 17.0 (Wallaby)
Hardware: Unspecified
OS: Linux
high
high
Target Milestone: ---
: ---
Assignee: OSP DFG:Compute
QA Contact: OSP DFG:Compute
URL:
Whiteboard:
Depends On:
Blocks: 1821561
TreeView+ depends on / blocked
 
Reported: 2019-10-16 00:58 UTC by smooney
Modified: 2024-10-01 16:21 UTC (History)
14 users (show)

Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
: 1821561 (view as bug list)
Environment:
Last Closed: 2023-04-14 13:51:05 UTC
Target Upstream Version:
Embargoed:


Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
Red Hat Issue Tracker OSP-24195 0 None None None 2023-12-06 20:12:50 UTC
Red Hat Issue Tracker OSPRH-69 0 None None None 2023-12-06 20:11:27 UTC

Description smooney 2019-10-16 00:58:32 UTC
Description of problem:

Libvirt and qemu have supported vIOMMU emulation for some time now.
nova curretly does not expose the vIOMMU as a configurable paramter.
using the q35 machine type and vIOMMU feature can enable better securty in
the guest when using dpdk or pci device passsthough by allowing the viommu
to work with the host iommu to restrict the the meory the passthough or dpdk
device can acess in the guest.

in some case this can also improve performance by reducing the cost of phyical page traslation.

by enableing support for vIOMMU emultaiton in the guest this will also enable
futrue work to allow nested sriov passhtough or other more advanced configurations that require a IOMMU to funciton correcly such as using vfio-pci in the guest.

Version-Release number of selected component (if applicable):


How reproducible:


Steps to Reproduce:
1.
2.
3.

Actual results:


Expected results:


Additional info:

Comment 4 Artom Lifshitz 2023-04-14 13:51:05 UTC
Tracked in https://issues.redhat.com/browse/OSPRH-69


Note You need to log in before you can comment on or make changes to this bug.