Bug 1539256

Summary: Unable to install virtio-scsi driver if option iommu_platform=on is specified
Product: Red Hat Enterprise Linux 7 Reporter: Ping Li <pingl>
Component: virtio-winAssignee: Yvugenfi <yvugenfi>
Status: CLOSED ERRATA QA Contact: lijin <lijin>
Severity: high Docs Contact:
Priority: high    
Version: 7.5CC: chayang, coli, jinzhao, juzhang, knoel, lijin, michen, mtessun, ngu, phou, pingl, virt-maint, vrozenfe, xuwei, yvugenfi
Target Milestone: rcKeywords: FutureFeature, Reopened
Target Release: ---   
Hardware: Unspecified   
OS: Unspecified   
Whiteboard:
Fixed In Version: Doc Type: If docs needed, set a value
Doc Text:
NO_DOCS
Story Points: ---
Clone Of: Environment:
Last Closed: 2018-10-30 16:21:49 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:
Bug Depends On:    
Bug Blocks: 1549577, 1558351    
Attachments:
Description Flags
cml to boot qemu-kvm
none
Blue screen none

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 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