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 1384587

Summary:	Backport virtio-win from RHEL-7.3 to RHEL-6.9
Product:	Red Hat Enterprise Linux 6	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, chayang, jherrman, juzhang, lijin, lprosek, michen, vrozenfe, wyu, ymankad
Version:	6.9
Target Milestone:	rc
Target Release:	---
Hardware:	Unspecified
OS:	Unspecified
Whiteboard:
Fixed In Version:	virtio-win-1.8.0-1.el6.src.rpm	Doc Type:	Enhancement
Doc Text:	This update adds support for version 1.0 of the virtio protocol to the following drivers: - virtio-rng - virtio-balloon - virtio-serial - virtio-net - virtio-scsi - virtio-block Improvements in virtio 1.0 include better resource utilization and better performance. Note that if the virtual device supports virtio 1.0 as well as the older protocol (referred to as virtio 0.9.5, 0.9, or legacy), the drivers use virtio 1.0.	Story Points:	---
Clone Of:		Environment:
Last Closed:	2017-03-21 04:00:29 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:	1378334
Bug Blocks:

Description Jeff Nelson 2016-10-13 15:30:42 UTC

Description of problem:
The content of virtio-win that was shipped in RHEL-7.3 needs to be
backported and released on RHEL-6.9. This is so RHV and RHOSP can
depend on the same Windows guest environment on the latest shipping
releases of RHEL-6 and RHEL-7.

Do not ship pvpanic -- there is no pvpanic support in RHEL-6.

Comment 7 lijin 2016-10-31 05:38:03 UTC

Hello,

Any progress of this bug?
QE plan to do rhel6.9 test recently.We'd like to know when rhel6.9 virtio-win package can be generated.

Thanks

Comment 8 Yash Mankad 2016-10-31 20:24:00 UTC

Hi Li Jin,

Sorry for the delay.
The updated drivers have been backported
and are now available in the build virtio-win-1.8.0-1.el6.src.rpm

Thanks,
Yash

Comment 10 lijin 2016-11-01 02:50:14 UTC

check in virtio-win-1.8.0-1.el6,pvpanic driver is removed and other drivers are same with rhel7.3 virtio-win packages(virtio-win-1.9.0-3.el7)

Change status to verified.

Comment 12 errata-xmlrpc 2017-03-21 04:00:29 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-2017-0561.html