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 1340571

Summary:	Add Windows 2k16 drivers to virtio-win
Product:	Red Hat Enterprise Linux 7	Reporter:	Jeff Nelson <jen>
Component:	virtio-win	Assignee:	Yash Mankad <ymankad>
virtio-win sub component:	distribution	QA Contact:	Virtualization Bugs <virt-bugs>
Status:	CLOSED ERRATA	Docs Contact:
Severity:	unspecified
Priority:	unspecified	CC:	ailan, crobinso, jherrman, juzhang, lijin, lveyde, mkolaja, tlavigne, vrozenfe, wyu, yvugenfi
Version:	7.3
Target Milestone:	rc
Target Release:	---
Hardware:	Unspecified
OS:	Unspecified
Whiteboard:
Fixed In Version:	virtio-win-1.9.0-3.el7	Doc Type:	Enhancement
Doc Text:	The virtio-win package now contains drivers for Windows Server 2016. A new directory has been added to the drivers directory hierarchy to reflect this change. The Windows Server 2016 drivers can be found in the /usr/share/virtio-win/drivers/amd64/Win2016 file, and they have also been added to the VFD and ISO files.	Story Points:	---
Clone Of:		Environment:
Last Closed:	2016-11-04 08:54:47 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 Jeff Nelson 2016-05-27 23:35:12 UTC

Description of problem:
Windows 2016 is expected to release in the RHEL-7.3 timeframe.

We should create a directory hierarchy for Windows 2016, just like we do for the other Windows releases, in which the drivers for the release will be placed.

Windows 2016 drivers should also be incorporated into the .ISO and the .VFD files.


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

How reproducible:
n/a

Steps to Reproduce:
1.
2.
3.

Actual results:


Expected results:


Additional info:

Comment 2 Yash Mankad 2016-09-14 15:48:02 UTC

The 2k16 drivers have been added in the build virtio-win-1.9.0-2.el7

Comment 3 lijin 2016-09-18 05:38:42 UTC

check in virtio-win-1.9.0-2.el7.noarch:
there is no win2016 folder in virtio-win-1.9.0_amd64.vfd

Comment 4 Yash Mankad 2016-09-19 15:30:44 UTC

Good catch!
The Win2016 drivers have been added to the virtio-win-1.9.0_amd64.vfd in the virtio-win-1.9.0-3.el7 build.

Thanks.

Comment 5 lijin 2016-09-20 01:21:30 UTC

Check in virtio-win-1.9.0-3.el7,win2016 is added in the floppy file.
This issue has been fixed,thanks.

Change status to verified

Comment 7 errata-xmlrpc 2016-11-04 08:54:47 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://rhn.redhat.com/errata/RHBA-2016-2609.html