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.

Description of problem:
Create this bz to track the windows pvpanic driver stuff after discuss with Marcel and Gal in bug 991100. We could get the info from there about when the pvpanic driver for windows will be public; what test QE need to implement; whether it will be shipped in rhel6.5, etc.

Version-Release number of selected component (if applicable):
qemu-kvm-0.12.1.2-2.386.el6 

How reproducible:
Always

Steps to Reproduce:
1. After boot up a windows guest, there is an "unknow device" in the device manager. 
2.
3.

Actual results:


Expected results:


Additional info:

The plan is such
1. pvpanic will not be a default device (qemu), so unless you will add "-device pvpanic" in the qemu command line, it will not show up.
2. No driver is planned for 6.5. Actually, we will have a driver, but we do not plan to officially ship it.

Ronen.

Granted QA_ACK 
QE will run WHQL test once the build has born out .

with build 103,we can install pvpanic driver correctly and pvpanic whql jobs all passed.

So this issue has been fixed,change status to verified.

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-2015-2513.html