Bug 1955681 - [RFE] Support vDPA devices without enabling real-time policy
Summary: [RFE] Support vDPA devices without enabling real-time policy
Keywords:
Status: CLOSED CURRENTRELEASE
Alias: None
Product: Red Hat OpenStack
Classification: Red Hat
Component: openstack-nova
Version: unspecified
Hardware: Unspecified
OS: Unspecified
high
high
Target Milestone: ---
: ---
Assignee: David Vallee Delisle
QA Contact: OSP DFG:Compute
URL:
Whiteboard:
Depends On: 1873409 1939776
Blocks:
TreeView+ depends on / blocked
 
Reported: 2021-04-30 16:19 UTC by Stephen Finucane
Modified: 2023-03-21 19:42 UTC (History)
8 users (show)

Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed: 2022-02-03 18:14:50 UTC
Target Upstream Version: Wallaby
Embargoed:


Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
Red Hat Issue Tracker OSP-3495 0 None None None 2021-11-18 18:09:54 UTC

Description Stephen Finucane 2021-04-30 16:19:25 UTC
Description of problem:

During Wallaby, we added support for creating instances with vDPA network devices. However, due to how this was implemented by QEMU/libvirt, it was necessary for users to enable the real-time policy ('hw:cpu_realtime=yes') to enable locked memory. Users shouldn't need to set this mostly unrelated set of tweaks to simply use vDPA. This could be resolved either by libvirt, which could increase the memlock limit via prlimit(2) as it does for VFIO devices, or nova could provide a way for users to request locked memory and only locked memory. This RFE tracks testing of the chosen solution along with any potential work needed in nova along the way.

Comment 2 Artom Lifshitz 2022-02-03 18:14:50 UTC
Closed by libvirt libvirt-7.4.0-1.el8 in BZ 1939776.


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