Note: This bug is displayed in read-only format because the product is no longer active in Red Hat Bugzilla.

RHEL Engineering is moving the tracking of its product development work on RHEL 6 through RHEL 9 to Red Hat Jira (issues.redhat.com). If you're a Red Hat customer, please continue to file support cases via the Red Hat customer portal. If you're not, please head to the "RHEL project" in Red Hat Jira and file new tickets here. Individual Bugzilla bugs in the statuses "NEW", "ASSIGNED", and "POST" are being migrated throughout September 2023. Bugs of Red Hat partners with an assigned Engineering Partner Manager (EPM) are migrated in late September as per pre-agreed dates. Bugs against components "kernel", "kernel-rt", and "kpatch" are only migrated if still in "NEW" or "ASSIGNED". If you cannot log in to RH Jira, please consult article #7032570. That failing, please send an e-mail to the RH Jira admins at rh-issues@redhat.com to troubleshoot your issue as a user management inquiry. The email creates a ServiceNow ticket with Red Hat. Individual Bugzilla bugs that are migrated will be moved to status "CLOSED", resolution "MIGRATED", and set with "MigratedToJIRA" in "Keywords". The link to the successor Jira issue will be found under "Links", have a little "two-footprint" icon next to it, and direct you to the "RHEL project" in Red Hat Jira (issue links are of type "https://issues.redhat.com/browse/RHEL-XXXX", where "X" is a digit). This same link will be available in a blue banner at the top of the page informing you that that bug has been migrated.

Bug 1433994

Summary:	libvirt attempts migration of a domain with intel-iommu device
Product:	Red Hat Enterprise Linux 7	Reporter:	Ján Tomko <jtomko>
Component:	libvirt	Assignee:	Ján Tomko <jtomko>
Status:	CLOSED NOTABUG	QA Contact:	Jingjing Shao <jishao>
Severity:	low	Docs Contact:
Priority:	low
Version:	7.3	CC:	dyuan, peterx, rbalakri, xuzhang, yalzhang, zpeng
Target Milestone:	rc
Target Release:	---
Hardware:	Unspecified
OS:	Unspecified
Whiteboard:
Fixed In Version:		Doc Type:	If docs needed, set a value
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:	2017-03-24 12:11:04 UTC	Type:	Bug
Regression:	---	Mount Type:	---
Documentation:	---	CRM:
Verified Versions:		Category:	---
oVirt Team:	---	RHEL 7.3 requirements from Atomic Host:
Cloudforms Team:	---	Target Upstream Version:
Embargoed:

Description Ján Tomko 2017-03-20 14:01:10 UTC

Description of problem:
Attempt to save a domain with intel-iommu results in an error from qemu

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


How reproducible:
100 %

Steps to Reproduce:
1. Start a domain with <iommu model='intel'/> device
2. virsh save <domain> <path>

Actual results:
error: internal error: unable to execute QEMU command 'migrate': State blocked by non-migratable device 'iommu-intel'

Expected results:
Libvirt reports an error before attempting to migrate.

Additional info:
https://bugzilla.redhat.com/show_bug.cgi?id=1235581#c16

Comment 1 Ján Tomko 2017-03-23 10:17:13 UTC

Upstream patch:
https://www.redhat.com/archives/libvir-list/2017-March/msg01065.html

Comment 2 Ján Tomko 2017-03-23 15:42:11 UTC

Pushed upstream as:
commit b7118623ad5a8e6ea75d693881c08873eefa3e28
Author:     Ján Tomko <jtomko>
CommitDate: 2017-03-23 16:35:40 +0100

    qemu: forbid migration with an IOMMU device
    
    https://bugzilla.redhat.com/show_bug.cgi?id=1433994

git describe: v3.1.0-243-gb711862

Comment 4 Peter Xu 2017-03-24 11:02:21 UTC

Maybe forbid IOMMU migration from libvirt side for 7.4 is a good idea. However logically speaking upstream QEMU should have already supported general VT-d migration since commit:

commit 8cdcf3c1e58d04b6811956d7608efeb66c42d719
Author: Peter Xu <peterx>
Date:   Fri Jan 6 12:06:13 2017 +0800

    intel_iommu: allow migration

Thanks,

Comment 5 Ján Tomko 2017-03-24 12:11:04 UTC

Oops, reverted now:

commit da17090b8ce4f9a2df9529227cbe502cfab21c8f
Author:     Ján Tomko <jtomko>
CommitDate: 2017-03-24 12:52:07 +0100

    Revert "qemu: forbid migration with an IOMMU device"

git describe: v3.1.0-254-gda17090

Seems there is no way to tell whether this is supported or not other than trying it.