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 996479

Summary:	RFE:pvpanic driver for windows guest
Product:	Red Hat Enterprise Linux 7	Reporter:	Qunfang Zhang <qzhang>
Component:	virtio-win	Assignee:	Gal Hammer <ghammer>
Status:	CLOSED ERRATA	QA Contact:	Virtualization Bugs <virt-bugs>
Severity:	medium	Docs Contact:
Priority:	medium
Version:	7.0	CC:	areis, chayang, crobinso, ghammer, juzhang, knoel, lijin, marcel, michen, mkenneth, mst, rbalakri, rpacheco, shawn, sherold, tzheng, van.zantvoort, virt-maint, vrozenfe
Target Milestone:	beta	Keywords:	FutureFeature
Target Release:	7.1
Hardware:	Unspecified
OS:	Unspecified
Whiteboard:
Fixed In Version:	virtio-win-prewhql-0.1-103	Doc Type:	Enhancement
Doc Text:	PVPanic is a paravirtualized device for reporting guest system crash (The famous Windows "Blue Screen of Death") to the management tools.	Story Points:	---
Clone Of:		Environment:
Last Closed:	2015-11-24 08:38:48 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 Qunfang Zhang 2013-08-13 08:54:46 UTC

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:

Comment 4 Ronen Hod 2013-08-13 14:33:23 UTC

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.

Comment 8 Mike Cao 2013-08-14 13:53:15 UTC

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

Comment 17 lijin 2015-06-09 09:23:47 UTC

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.

Comment 19 errata-xmlrpc 2015-11-24 08:38:48 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-2015-2513.html