Bug 1549597

Summary:	Add support in virtio-balloon Windows driver for VIRTIO_F_IOMMU_PLATFORM virtio feature
Product:	Red Hat Enterprise Linux 8	Reporter:	Yvugenfi <yvugenfi>
Component:	virtio-win	Assignee:	Yvugenfi <yvugenfi>
virtio-win sub component:	virtio-win-prewhql	QA Contact:	xiagao
Status:	CLOSED ERRATA	Docs Contact:
Severity:	low
Priority:	low	CC:	ailan, jinzhao, knoel, lijin, lmiksik
Version:	8.0	Keywords:	FutureFeature
Target Milestone:	rc	Flags:	knoel: mirror+
Target Release:	8.0
Hardware:	Unspecified
OS:	Windows
Whiteboard:
Fixed In Version:	virtio-win-prewhql-0.1-174	Doc Type:	If docs needed, set a value
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:	2020-04-28 16:05:15 UTC	Type:	Feature Request
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:	1682882
Bug Blocks:	1549577, 1558351

Description Yvugenfi@redhat.com 2018-02-27 13:30:41 UTC

Description of problem:
virtio-win drivers are not reporting VIRTIO_F_IOMMU_PLATFORM feature.

There are several things that should be done to fix it:

1. Ensure that Windows drivers are using Windows kernel DMA (easier for storage and network drivers that are already using framework specific APIs, additional work should be done for WDF based drivers).

2. Report the feature.

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


How reproducible:


Steps to Reproduce:
1.
2.
3.

Actual results:


Expected results:


Additional info:

Comment 4 Yvugenfi@redhat.com 2019-12-11 12:59:02 UTC

Changes are in: https://github.com/virtio-win/kvm-guest-drivers-windows/pull/418

Comment 7 xiagao 2019-12-16 05:47:02 UTC

Verify this bug with virtio-win-prewhql-174.

Boot up guest with ',iommu_platform=on,ats=on' for virtio-balloon-pci device,driver is installed successfully and virito-balloon device works well.

Comment 13 errata-xmlrpc 2020-04-28 16:05:15 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/RHEA-2020:1757