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:	libvirt	Assignee:	Michal Privoznik <mprivozn>
libvirt sub component:	General	QA Contact:	yalzhang <yalzhang>
Status:	CLOSED MIGRATED	Docs Contact:
Severity:	low
Priority:	unspecified	CC:	dhildenb, dzheng, gshan, jsuchane, lijin, lmen, mprivozn, virt-maint, xuzhang, yalzhang, yanghliu
Version:	9.1	Keywords:	FutureFeature, MigratedToJIRA, 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:	2023-09-22 17:37:16 UTC	Type:	Story
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.

Comment 3 RHEL Program Management 2023-09-22 17:31:48 UTC

Issue migration from Bugzilla to Jira is in process at this time. This will be the last message in Jira copied from the Bugzilla bug.

Comment 4 RHEL Program Management 2023-09-22 17:37:16 UTC

This BZ has been automatically migrated to the issues.redhat.com Red Hat Issue Tracker. All future work related to this report will be managed there.

Due to differences in account names between systems, some fields were not replicated.  Be sure to add yourself to Jira issue's "Watchers" field to continue receiving updates and add others to the "Need Info From" field to continue requesting information.

To find the migrated issue, look in the "Links" section for a direct link to the new issue location. The issue key will have an icon of 2 footprints next to it, and begin with "RHEL-" followed by an integer.  You can also find this issue by visiting https://issues.redhat.com/issues/?jql= and searching the "Bugzilla Bug" field for this BZ's number, e.g. a search like:

"Bugzilla Bug" = 1234567

In the event you have trouble locating or viewing this issue, you can file an issue by sending mail to rh-issues. You can also visit https://access.redhat.com/articles/7032570 for general account information.