Bug 490595

Summary: Install two PV NIC drivers on one guest and do sleep stress with IO testing,the windows can't hibernate
Product: Red Hat Enterprise Linux 5 Reporter: koka xiong <kxiong>
Component: xenpv-winAssignee: Xen Maintainance List <xen-maint>
Status: CLOSED DUPLICATE QA Contact: Virtualization Bugs <virt-bugs>
Severity: medium Docs Contact:
Priority: low    
Version: 5.3CC: llim, pbonzini, szhou, xen-maint
Target Milestone: rc   
Target Release: ---   
Hardware: All   
OS: Linux   
Whiteboard:
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2010-03-16 13:24:54 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:    
Bug Blocks: 518435    
Attachments:
Description Flags
the testing log none

Description koka xiong 2009-03-17 07:49:50 UTC 
Description of problem:
Install two PV NIC drivers on one guest and do sleep stress with IO testing,the windows can't hibernate

Version-Release number of selected component (if applicable):
xenpv-win-32-bit-1.0.0-1.el5.noarch.rpm

How reproducible:
always

Steps to Reproduce:
1.Install windows 2003 sp1 guest on xen
2.Install the xenpv-win-32-bit according to the install manual
3.Add one network car to the guest,thus the guest has 2 NIC
4.Do Sleep Stress with IO according to http://msdn.microsoft.com/en-us/library/dd450403.aspx
  
Actual results:
The windows will preparing to the hibernate and can't hibernate 

Expected results:
The test can finish running

Additional info:
If I install one NIC pv driver,the Do Sleep Stress with IO can pass.
with two NIC pv drivers,the Do Sleep Stress with IO can't finish
Comment 1 koka xiong 2009-03-17 08:06:54 UTC 
Created attachment 335487 [details]
the testing log
Comment 2 Shirley Zhou 2009-05-27 02:28:52 UTC 
Any update for this issue?

Thanks.
Comment 3 Paolo Bonzini 2010-03-16 13:24:54 UTC 

*** This bug has been marked as a duplicate of bug 497502 ***