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 1539256 - Unable to install virtio-scsi driver if option iommu_platform=on is specified
Summary: Unable to install virtio-scsi driver if option iommu_platform=on is specified
Keywords:
Status: CLOSED ERRATA
Alias: None
Product: Red Hat Enterprise Linux 7
Classification: Red Hat
Component: virtio-win
Version: 7.5
Hardware: Unspecified
OS: Unspecified
high
high
Target Milestone: rc
: ---
Assignee: Yvugenfi@redhat.com
QA Contact: lijin
URL:
Whiteboard:
Depends On:
Blocks: 1549577 1558351
TreeView+ depends on / blocked
 
Reported: 2018-01-27 11:24 UTC by Ping Li
Modified: 2018-10-30 16:23 UTC (History)
15 users (show)

Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
NO_DOCS
Clone Of:
Environment:
Last Closed: 2018-10-30 16:21:49 UTC
Target Upstream Version:
Embargoed:

Attachments (Terms of Use)
cml to boot qemu-kvm (3.21 KB, text/plain)
2018-01-27 11:24 UTC, Ping Li 		no flags Details
Blue screen (25.97 KB, image/png)
2018-01-27 13:06 UTC, Ping Li 		no flags Details
View All


Links
System ID Private Priority Status Summary Last Updated
Red Hat Product Errata RHBA-2018:3413 0 None None None 2018-10-30 16:23:53 UTC

Description Ping Li 2018-01-27 11:24:42 UTC 
Created attachment 1386841 [details]
cml to boot qemu-kvm

Description of problem:
When boot a guest specifying the option iommu_platform=on, virtio-scsi driver cannot be installed.

Version-Release number of selected component (if applicable):
kernel-3.10.0-837.el7.x86_64
qemu-kvm-rhev-2.10.0-18.el7

How reproducible:
100%

Steps to Reproduce:
1. Boot a guest specifying the option "iommu_platform=on"
    -machine q35,kernel-irqchip=split  \
    -device intel-iommu,intremap=on,eim=on,device-iotlb=on \
    -device pcie-root-port,id=pcie.0-root-port-3,slot=3,chassis=3,addr=0x3,bus=pcie.0 \
    -device virtio-scsi-pci,id=virtio_scsi_pci0,bus=pcie.0-root-port-3,addr=0x0,iommu_platform=on,ats=on \
    -drive id=drive_image1,if=none,snapshot=off,aio=threads,cache=none,format=raw,file=/home/tests/diskfile/win2012r2.img,werror=stop,rerror=stop \
    -device scsi-hd,id=image1,drive=drive_image1,bootindex=0 \
    -drive id=drive_cd1,if=none,snapshot=off,aio=threads,cache=unsafe,media=cdrom,file=/home/kvm_autotest_root/iso/ISO/Win2012R2/en_windows_server_2012_r2_with_update_x64_dvd_6052708.iso \
    -device ide-cd,id=cd1,drive=drive_cd1,bootindex=1,bus=ide.0,unit=0 \
    -drive id=drive_winutils,if=none,snapshot=off,aio=threads,cache=unsafe,media=cdrom,file=/home/kvm_autotest_root/iso/windows/winutils.iso \
    -device ide-cd,id=winutils,drive=drive_winutils,bootindex=2,bus=ide.1,unit=0 \
    -drive id=drive_virtio,if=none,snapshot=off,aio=threads,cache=unsafe,media=cdrom,file=/home/kvm_autotest_root/iso/windows/virtio-win-1.9.4-2.el7.iso \

2. Load driver from virtio-win-1.9.4-2.el7.iso. Select vioscsi -> 2k12R2 -> amd64, then click OK. Get result that we couldn't find any drivers.

3. Remove the option "iommu_platform=on", then the driver could be installed successfully.

Actual results:
virtio-scsi driver cannot be installed.

Expected results:
virtio-scsi driver can be installed.

Additional info:
Comment 2 Ping Li 2018-01-27 13:06:52 UTC 
Created attachment 1386847 [details]
Blue screen

BSOD occurs when try to boot the image with "iommu_platform=on". Before that, image could be booted successfully.
Comment 3 Ping Li 2018-01-27 13:10:35 UTC 
IOMMU is enabled in the host kernel 
# journalctl -k | grep -i "IOMMU enabled" 
Jan 26 22:55:34 localhost kernel: DMAR: IOMMU enabled
# journalctl -k | grep -i "DMAR: Intel(R) Virtualization Technology for Directed I/O"
Jan 26 22:55:34 localhost kernel: DMAR: Intel(R) Virtualization Technology for Directed I/O
Comment 6 CongLi 2018-01-31 06:52:51 UTC 

*** This bug has been marked as a duplicate of bug 1530210 ***
Comment 7 Yvugenfi@redhat.com 2018-02-27 13:02:17 UTC 
Per Amnon request - opening BZ for each individual driver.
Comment 10 Yvugenfi@redhat.com 2018-03-20 13:25:26 UTC 
https://github.com/virtio-win/kvm-guest-drivers-windows/pull/261
Comment 11 Peixiu Hou 2018-04-17 09:57:52 UTC 
Hi Yan,

I tested this issue with virtio-win-prewhql-150 on win2012-r2 and win2016.

on win2016, cannot reproduce this issue.
on win2012-r2, also can reproduce this issue.

So could you help to confirm if the virtio-win for iommu feature only supported on win2016 and win10(guess from https://bugzilla.redhat.com/show_bug.cgi?id=1549587#c2)?

Thanks a lot~
Comment 12 Yvugenfi@redhat.com 2018-04-17 10:57:29 UTC 
(In reply to Peixiu Hou from comment #11)
> Hi Yan,
> 
> I tested this issue with virtio-win-prewhql-150 on win2012-r2 and win2016.
> 
> on win2016, cannot reproduce this issue.
> on win2012-r2, also can reproduce this issue.
> 
> So could you help to confirm if the virtio-win for iommu feature only
> supported on win2016 and win10(guess from
> https://bugzilla.redhat.com/show_bug.cgi?id=1549587#c2)?
> 
> Thanks a lot~

Hi,

Yes - it is supported only for Windows 10, Windows 2016 and up.
Comment 13 Peixiu Hou 2018-04-18 08:21:10 UTC 
(In reply to Yan Vugenfirer from comment #12)
> (In reply to Peixiu Hou from comment #11)
> > Hi Yan,
> > 
> > I tested this issue with virtio-win-prewhql-150 on win2012-r2 and win2016.
> > 
> > on win2016, cannot reproduce this issue.
> > on win2012-r2, also can reproduce this issue.
> > 
> > So could you help to confirm if the virtio-win for iommu feature only
> > supported on win2016 and win10(guess from
> > https://bugzilla.redhat.com/show_bug.cgi?id=1549587#c2)?
> > 
> > Thanks a lot~
> 
> Hi,
> 
> Yes - it is supported only for Windows 10, Windows 2016 and up.

Thanks a lot~
Comment 16 errata-xmlrpc 2018-10-30 16:21:49 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:3413
Note You need to log in before you can comment on or make changes to this bug.