Bug 2095091

Summary: [RFE][Upstream feature] [virtio-mem] Support setting iommu for virtio-mem
Product: Red Hat Enterprise Linux 9 Reporter: Yiding Liu (Fujitsu) <yidliu>
Component: libvirtAssignee: Michal Privoznik <mprivozn>
libvirt sub component: General QA Contact: yalzhang <yalzhang>
Status: ASSIGNED --- Docs Contact:
Severity: low    
Priority: unspecified CC: dhildenb, dzheng, gshan, jsuchane, lijin, lmen, mprivozn, virt-maint, xuzhang, yalzhang, yanghliu
Version: 9.1Keywords: FutureFeature, Triaged
Target Milestone: rc   
Target Release: ---   
Hardware: All   
OS: Unspecified   
Whiteboard:
Fixed In Version: Doc Type: If docs needed, set a value
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: Type: Feature Request
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Embargoed:
Bug Depends On:    
Bug Blocks: 2047797    

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.