Bug 2095091 - [RFE][Upstream feature] [virtio-mem] Support setting iommu for virtio-mem
Summary: [RFE][Upstream feature] [virtio-mem] Support setting iommu for virtio-mem
Keywords:
Status: ASSIGNED
Alias: None
Product: Red Hat Enterprise Linux 9
Classification: Red Hat
Component: libvirt
Version: 9.1
Hardware: All
OS: Unspecified
unspecified
low
Target Milestone: rc
: ---
Assignee: Michal Privoznik
QA Contact: yalzhang@redhat.com
URL:
Whiteboard:
Depends On:
Blocks: 2047797
TreeView+ depends on / blocked
 
Reported: 2022-06-09 02:13 UTC by Yiding Liu (Fujitsu)
Modified: 2023-08-04 09:01 UTC (History)
11 users (show)

Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed:
Type: Feature Request
Target Upstream Version:
Embargoed:


Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
Red Hat Issue Tracker RHELPLAN-124738 0 None None None 2022-06-09 02:33:48 UTC

Description Yiding Liu (Fujitsu) 2022-06-09 02:13:24 UTC
Description of problem:

libvirt doesn't support setting iommu for virtio-mem device

As libvirt doc said:
https://libvirt.org/formatdomain.html#virtio-related-options
```
QEMU's virtio devices have some attributes related to the virtio transport under the driver element: The iommu attribute enables the use of emulated IOMMU by the device. The attribute ats controls the Address Translation Service support for PCIe devices. This is needed to make use of IOTLB support (see IOMMU devices). Possible values are on or off. Since 3.5.0
```
E.g. Set <driver iommu='on'>
```
  <devices>
    <memballoon model='virtio'>
      <address type='pci' domain='0x0000' bus='0x00' slot='0x02' function='0x0'/>
      <stats period='10'/>
      <driver iommu='on' ats='on'/>
    </memballoon>
  </devices>
```

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


How reproducible:


Steps to Reproduce:
1.
2.
3.

Actual results:


Expected results:


Additional info:

Comment 1 yalzhang@redhat.com 2022-06-28 10:05:10 UTC
Just for reference, for intel iommu, there is a bug 1598780 closed deferred.


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