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.
Description of problem:
Guest OS will down when scsi controller enable the IOMMU for Virtio
Version-Release number of selected component (if applicable):
qemu-kvm-rhev-2.9.0-14.el7.x86_64
host kernel: 3.10.0-691.el7.x86_64
guest kernel : 3.10.0-691.el7.x86_64
How reproducible:
100%
Steps to Reproduce:
1. In host, add "iommu=pt intel_iommu=on" to kernel line
2. Add "intel_iommu=on" to kernel line of q35 guest
3. Add the xml as below in the guest
<features>
<ioapic driver='qemu'/>
</features>
...
<iommu model='intel'>
<driver intremap='on' iotlb='on'/>
</iommu>
4. Add the iommu='on' ats='on' to scsi controller and change the disk bus to scsi.
....
<controller type='scsi' index='0' model='virtio-scsi'>
<driver iommu='on' ats='on'/>
</controller>
....
<disk type='file' device='disk'>
<driver name='qemu' type='qcow2' cache='none iommu='on' ats='on'/>
<source file='/nfs/rhel7.3-q35.qcow2'/>
<target dev='vda' bus='scsi'/>
<address type='pci' domain='0x0000' bus='0x00' slot='0x07' function='0x0'/>
</disk>
5. Start the guest and find the guest can not be accessed.
Actual results:
As the step 5 shows.
Expected results:
The guest can be accessed successfully
Additional info:
N/A
Comment 16Wainer dos Santos Moschetta
2017-09-28 13:13:21 UTC
Since the problem described in this bug report should be
resolved in a recent advisory, it has been closed with a
resolution of ERRATA.
For information on the advisory, and where to find the updated
files, follow the link below.
If the solution does not work for you, open a new bug report.
https://access.redhat.com/errata/RHBA-2018:0814
Description of problem: Guest OS will down when scsi controller enable the IOMMU for Virtio Version-Release number of selected component (if applicable): qemu-kvm-rhev-2.9.0-14.el7.x86_64 host kernel: 3.10.0-691.el7.x86_64 guest kernel : 3.10.0-691.el7.x86_64 How reproducible: 100% Steps to Reproduce: 1. In host, add "iommu=pt intel_iommu=on" to kernel line 2. Add "intel_iommu=on" to kernel line of q35 guest 3. Add the xml as below in the guest <features> <ioapic driver='qemu'/> </features> ... <iommu model='intel'> <driver intremap='on' iotlb='on'/> </iommu> 4. Add the iommu='on' ats='on' to scsi controller and change the disk bus to scsi. .... <controller type='scsi' index='0' model='virtio-scsi'> <driver iommu='on' ats='on'/> </controller> .... <disk type='file' device='disk'> <driver name='qemu' type='qcow2' cache='none iommu='on' ats='on'/> <source file='/nfs/rhel7.3-q35.qcow2'/> <target dev='vda' bus='scsi'/> <address type='pci' domain='0x0000' bus='0x00' slot='0x07' function='0x0'/> </disk> 5. Start the guest and find the guest can not be accessed. Actual results: As the step 5 shows. Expected results: The guest can be accessed successfully Additional info: N/A