Note: This bug is displayed in read-only format because the product is no longer active in Red Hat Bugzilla.

For bugs related to Red Hat Enterprise Linux 5 product line. The current stable release is 5.10. For Red Hat Enterprise Linux 6 and above, please visit Red Hat JIRA https://issues.redhat.com/secure/CreateIssue!default.jspa?pid=12332745 to report new issues.

Bug 550247

Summary:	Hypercall driver doesn't reset device on power-down.
Product:	Red Hat Enterprise Linux 5	Reporter:	Vadim Rozenfeld <vrozenfe>
Component:	virtio-win	Assignee:	Vadim Rozenfeld <vrozenfe>
Status:	CLOSED CURRENTRELEASE	QA Contact:	Yaniv Kaul <ykaul>
Severity:	medium	Docs Contact:
Priority:	medium
Version:	5.5	CC:	iheim, jkt, mkenneth, tburke, ykaul, yvugenfi
Target Milestone:	rc
Target Release:	---
Hardware:	x86_64
OS:	Windows
Whiteboard:
Fixed In Version:	sm27	Doc Type:	Bug Fix
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:	2010-06-24 14:51:53 UTC	Type:	---
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:	550755
Bug Blocks:

Description Vadim Rozenfeld 2009-12-24 07:04:08 UTC

Description of problem:
Hypercall driver doesn't reset device on power-down.
Dor, please comment: do you need it on power-down or
system shut-down event?  

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


How reproducible:


Steps to Reproduce:
1.
2.
3.
  
Actual results:


Expected results:


Additional info:

Comment 1 Dor Laor 2009-12-24 07:42:47 UTC

Shutdown and driver unload

Comment 2 Vadim Rozenfeld 2009-12-24 07:59:34 UTC

commit #550247 should fix both of them. Can you check it please? New driver on \\file.tlv.redhat.com\vrozenfe\HypercallDrv
TIA

Comment 3 Yaniv Kaul 2009-12-24 08:01:00 UTC

Requires WHQL, I guess.

Comment 4 Vadim Rozenfeld 2009-12-24 08:04:50 UTC

(In reply to comment #3)
> Requires WHQL, I guess.  

Yes please. Especially all sorts of PnP tests.

Comment 5 Yaniv Kaul 2009-12-24 14:23:09 UTC

(In reply to comment #2)
> commit #550247 should fix both of them. Can you check it please? New driver on
> \\file.tlv.redhat.com\vrozenfe\HypercallDrv
> TIA  

Vadim, we need a real build to test and WHQL it. Please coordinate with Barak.

Comment 6 Vadim Rozenfeld 2009-12-24 17:02:30 UTC

(In reply to comment #5)
> (In reply to comment #2)
> > commit #550247 should fix both of them. Can you check it please? New driver on
> > \\file.tlv.redhat.com\vrozenfe\HypercallDrv
> > TIA  
> 
> Vadim, we need a real build to test and WHQL it. Please coordinate with Barak.  

Yes, but hypercall device should be fixed also. 
Yan, could you please merge the latest changes to the integration branch?

Comment 7 Yaniv Kaul 2009-12-24 18:45:37 UTC

(In reply to comment #6)
> (In reply to comment #5)
> > (In reply to comment #2)
> > > commit #550247 should fix both of them. Can you check it please? New driver on
> > > \\file.tlv.redhat.com\vrozenfe\HypercallDrv
> > > TIA  
> > 
> > Vadim, we need a real build to test and WHQL it. Please coordinate with Barak.  
> 
> Yes, but hypercall device should be fixed also. 

- So there should be a blocking QEMU bug as well.
- Does that mean that the new hypercall driver won't work on KVM 5.4?
- Does that mean that the old hypercall driver won't work on KVM 5.5?

> Yan, could you please merge the latest changes to the integration branch?

Comment 8 Vadim Rozenfeld 2009-12-24 18:58:03 UTC

AFAIU it shouldn't break anything, but will be absolutely useless w/o QEMU counterpart.
Dor, can you comment please?