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 884998

Summary: Windows2k3-64 guest cannot resume after suspended to disk after plenty of pause:resume iterations - rtl8139
Product: Red Hat Enterprise Linux 6 Reporter: Mike Cao <bcao>
Component: qemu-kvmAssignee: jason wang <jasowang>
Status: CLOSED WONTFIX QA Contact: Virtualization Bugs <virt-bugs>
Severity: medium Docs Contact:
Priority: high    
Version: 6.0CC: acathrow, areis, bcao, bsarathy, dblechte, flang, gcosta, juzhang, kcao, llim, mdeng, michen, mkenneth, qzhang, rhod, tburke, virt-maint, yvugenfi
Target Milestone: beta   
Target Release: 6.2   
Hardware: All   
OS: Linux   
Whiteboard:
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: 607510 Environment:
Last Closed: 2014-03-24 07:11:04 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: 607510    
Bug Blocks: 580953, 720669, 761491, 847241, 912287    

Description Mike Cao 2012-12-07 08:49:02 UTC 
Reproduce this issue on windows2k3 w/ rtl8139 on 2.6.32-338.el6.x86_64
qemu-kvm-rhev-0.12.1.2-2.331.el6.x86_64

CLI:/usr/libexec/qemu-kvm -M rhel6.4.0 -m 2G -smp 4 -cpu cpu64-rhel6,+x2apic -usbdevice tablet -drive file=win2k3-64-blk-48.raw,format=raw,if=none,id=drive-virtio0,boot=on,cache=none,werror=stop,rerror=stop -device virtio-blk-pci,drive=drive-virtio0,id=virtio-blk-pci0,bootindex=1 -netdev tap,sndbuf=0,id=hostnet0,script=/etc/qemu-ifup,downscript=no -device rtl8139,netdev=hostnet0,mac=00:10:10:26:43:28,bus=pci.0,addr=0x4 -boot c -uuid dbfc8ac6-c661-40fc-83b6-949644d7fac8 -rtc base=localtime,clock=host,driftfix=slew -no-kvm-pit-reinjection -chardev socket,id=111a,path=/tmp/win2k3-64-blk-48,server,nowait -mon chardev=111a,mode=readline -name win2k3-64-blk-48 -drive file=disk1.raw,if=none,id=drive-virtio1,cache=none,werror=stop,rerror=stop -device virtio-blk-pci,drive=drive-virtio1,id=virtio-blk-pci1 -drive file=disk2.raw,if=none,id=drive-virtio2,cache=none,werror=stop,rerror=stop -device virtio-blk-pci,drive=drive-virtio2,id=virtio-blk-pci2 -drive file=disk3.raw,if=none,id=drive-virtio3,cache=none,werror=stop,rerror=stop -device virtio-blk-pci,drive=drive-virtio3,id=virtio-blk-pci3 -drive file=disk4.raw,if=none,id=drive-virtio4,cache=none,werror=stop,rerror=stop -device virtio-blk-pci,drive=drive-virtio4,id=virtio-blk-pci4 -global PIIX4_PM.disable_s3=0 -global PIIX4_PM.disable_s4=0 -monitor stdio -vnc :1 -vga cirrus


+++ This bug was initially created as a clone of Bug #607510 +++

Description of problem:
just stuck while resuming.


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

How reproducible:
10%


Steps to Reproduce:
1. start vm with command
qemu-kvm -name 'vm8' -monitor tcp:0:6001,server,nowait -drive file=./win7-32.qcow2,if=ide,cache=none,aio=native -net nic,vlan=0,model=rtl8139,macaddr=02:bE:aF:7B:7b:6c -net tap,vlan=0,ifname=rtl8139_0_6001,script=/root/qemu-ifup-switch,downscript=no,vhost=on -m 2048 -smp 1  -soundhw ac97 -redir tcp:5000::22 -vnc :0 -spice port=8000,disable-ticketing -usbdevice tablet -rtc-td-hack -cpu qemu64,+sse2 -no-kvm-pit-reinjection -serial unix:/tmp/serial-20100623-102949-ud1H,server,nowait

2. suspend guest to disk by command
rundll32.exe PowrProf.dll, SetSuspendState

3. after suspended, start the vm again with the same command as in step 1.
  

Actual results:
guest becomes unresponsive while resuming.


Expected results:
guest resumed good, with all states the same as that before suspending.


Additional info:
1.
Comment 2 Ademar Reis 2012-12-07 20:30:25 UTC 
(In reply to comment #0)
> Reproduce this issue on windows2k3 w/ rtl8139 on 2.6.32-338.el6.x86_64
> qemu-kvm-rhev-0.12.1.2-2.331.el6.x86_64
> 
> +++ This bug was initially created as a clone of Bug #607510 +++
> 
> Description of problem:
> just stuck while resuming.
> 

Just to clarify: Bug 607510 has been fixed in the 6.4 cycle. My understanding is that you reproduced the same issue but now in win2k3 using an rtl8139.

How easy is it to reproduce it? The original bug had a rate of 10%.
Comment 3 Mike Cao 2012-12-08 07:07:30 UTC 
(In reply to comment #2)
> (In reply to comment #0)
> > Reproduce this issue on windows2k3 w/ rtl8139 on 2.6.32-338.el6.x86_64
> > qemu-kvm-rhev-0.12.1.2-2.331.el6.x86_64
> > 
> > +++ This bug was initially created as a clone of Bug #607510 +++
> > 
> > Description of problem:
> > just stuck while resuming.
> > 
> 
> Just to clarify: Bug 607510 has been fixed in the 6.4 cycle. My
> understanding is that you reproduced the same issue but now in win2k3 using
> an rtl8139.

Yes ,There is no in-box e1000 driver in win2k3 system ,we use rtl8319 for WHQL Test
> 
> How easy is it to reproduce it? The original bug had a rate of 10%.
seems the rate is same as the original one  .one whql job named named "Common Scenario Stress with DiskIO" will make guest in s4 cycle in hundreds of times ,more or leass 12 times occurs .
We have workaround during whql process ,when guest stuck during resume . (qemu)system_reset it ,and make it re-resume
Comment 4 jason wang 2012-12-10 07:03:17 UTC 
(In reply to comment #3)
> (In reply to comment #2)
> > (In reply to comment #0)
> > > Reproduce this issue on windows2k3 w/ rtl8139 on 2.6.32-338.el6.x86_64
> > > qemu-kvm-rhev-0.12.1.2-2.331.el6.x86_64
> > > 
> > > +++ This bug was initially created as a clone of Bug #607510 +++
> > > 
> > > Description of problem:
> > > just stuck while resuming.
> > > 
> > 
> > Just to clarify: Bug 607510 has been fixed in the 6.4 cycle. My
> > understanding is that you reproduced the same issue but now in win2k3 using
> > an rtl8139.
> 
> Yes ,There is no in-box e1000 driver in win2k3 system ,we use rtl8319 for
> WHQL Test
> > 
> > How easy is it to reproduce it? The original bug had a rate of 10%.
> seems the rate is same as the original one  .one whql job named named
> "Common Scenario Stress with DiskIO" will make guest in s4 cycle in hundreds
> of times ,more or leass 12 times occurs .
> We have workaround during whql process ,when guest stuck during resume .
> (qemu)system_reset it ,and make it re-resume

Since the you have had a workaround and it's only happen on suspend/resume, can we close this? The reltek card has some behavior and it's datasheet is not very clear (or even wrong) on many descriptions ( you can see the upstream netdev discussion about this).
Comment 5 Mike Cao 2012-12-10 07:08:52 UTC 
(In reply to comment #4)
> (In reply to comment #3)
> > (In reply to comment #2)
> > > (In reply to comment #0)
> > > > Reproduce this issue on windows2k3 w/ rtl8139 on 2.6.32-338.el6.x86_64
> > > > qemu-kvm-rhev-0.12.1.2-2.331.el6.x86_64
> > > > 
> > > > +++ This bug was initially created as a clone of Bug #607510 +++
> > > > 
> > > > Description of problem:
> > > > just stuck while resuming.
> > > > 
> > > 
> > > Just to clarify: Bug 607510 has been fixed in the 6.4 cycle. My
> > > understanding is that you reproduced the same issue but now in win2k3 using
> > > an rtl8139.
> > 
> > Yes ,There is no in-box e1000 driver in win2k3 system ,we use rtl8319 for
> > WHQL Test
> > > 
> > > How easy is it to reproduce it? The original bug had a rate of 10%.
> > seems the rate is same as the original one  .one whql job named named
> > "Common Scenario Stress with DiskIO" will make guest in s4 cycle in hundreds
> > of times ,more or leass 12 times occurs .
> > We have workaround during whql process ,when guest stuck during resume .
> > (qemu)system_reset it ,and make it re-resume
> 
> Since the you have had a workaround and it's only happen on suspend/resume,
> can we close this? The reltek card has some behavior and it's datasheet is
> not very clear (or even wrong) on many descriptions ( you can see the
> upstream netdev discussion about this).

Hi, Jason

I still recommend to fix it in next release , WHQL make guest do hundreds of hibernate/resume cycles ,We don't know which time guest fail to resume and QE can not always observe the guest status during job running.
Comment 6 jason wang 2012-12-11 05:46:18 UTC 
(In reply to comment #5)
> (In reply to comment #4)
> > (In reply to comment #3)
> > > (In reply to comment #2)
> > > > (In reply to comment #0)
> > > > > Reproduce this issue on windows2k3 w/ rtl8139 on 2.6.32-338.el6.x86_64
> > > > > qemu-kvm-rhev-0.12.1.2-2.331.el6.x86_64
> > > > > 
> > > > > +++ This bug was initially created as a clone of Bug #607510 +++
> > > > > 
> > > > > Description of problem:
> > > > > just stuck while resuming.
> > > > > 
> > > > 
> > > > Just to clarify: Bug 607510 has been fixed in the 6.4 cycle. My
> > > > understanding is that you reproduced the same issue but now in win2k3 using
> > > > an rtl8139.
> > > 
> > > Yes ,There is no in-box e1000 driver in win2k3 system ,we use rtl8319 for
> > > WHQL Test
> > > > 
> > > > How easy is it to reproduce it? The original bug had a rate of 10%.
> > > seems the rate is same as the original one  .one whql job named named
> > > "Common Scenario Stress with DiskIO" will make guest in s4 cycle in hundreds
> > > of times ,more or leass 12 times occurs .
> > > We have workaround during whql process ,when guest stuck during resume .
> > > (qemu)system_reset it ,and make it re-resume
> > 
> > Since the you have had a workaround and it's only happen on suspend/resume,
> > can we close this? The reltek card has some behavior and it's datasheet is
> > not very clear (or even wrong) on many descriptions ( you can see the
> > upstream netdev discussion about this).
> 
> Hi, Jason
> 
> I still recommend to fix it in next release , WHQL make guest do hundreds of
> hibernate/resume cycles ,We don't know which time guest fail to resume and
> QE can not always observe the guest status during job running.

Ok, let's try to fix it in 6.5. For 6.4, you can use e1000 instead ( or is there a licence issue ?)
Comment 7 Mike Cao 2012-12-11 05:52:41 UTC 
(In reply to comment #6)

> Ok, let's try to fix it in 6.5. For 6.4, you can use e1000 instead ( or is
> there a licence issue ?)

Just finish the WHQL test round using (qemu)system_reset and choose resume again for RHEL6.4.0 .We are Wasting lots of time on it during the test ,that's the reason I suggest to fix in next release .
Comment 8 jason wang 2013-03-04 08:34:55 UTC 
(In reply to comment #7)
> (In reply to comment #6)
> 
> > Ok, let's try to fix it in 6.5. For 6.4, you can use e1000 instead ( or is
> > there a licence issue ?)
> 
> Just finish the WHQL test round using (qemu)system_reset and choose resume
> again for RHEL6.4.0 .We are Wasting lots of time on it during the test
> ,that's the reason I suggest to fix in next release .

Let's try to install e1000 driver in 2k3-64 and try to see if it has issues? If not, I would prefer to close this bug since we'd better stop investigation on 8139 which is out of data and isn't well documented.

Thanks
Comment 10 Min Deng 2013-03-14 09:49:37 UTC 
 Unfortunately,the issue still can be reproduced while doing a whole block whql testing on win2k3 with e1000.(In reply to comment #8)
> (In reply to comment #7)
> > (In reply to comment #6)
> > 
> > > Ok, let's try to fix it in 6.5. For 6.4, you can use e1000 instead ( or is
> > > there a licence issue ?)
> > 
> > Just finish the WHQL test round using (qemu)system_reset and choose resume
> > again for RHEL6.4.0 .We are Wasting lots of time on it during the test
> > ,that's the reason I suggest to fix in next release .
> 
> Let's try to install e1000 driver in 2k3-64 and try to see if it has issues?
> If not, I would prefer to close this bug since we'd better stop
> investigation on 8139 which is out of data and isn't well documented.
> 
> Thanks

  Unfortunately,the issue still can be reproduced while doing block whql testing on win2k3 with e1000.
Comment 13 jason wang 2013-05-21 07:40:19 UTC 
(In reply to dengmin from comment #10)
>  Unfortunately,the issue still can be reproduced while doing a whole block
> whql testing on win2k3 with e1000.(In reply to comment #8)
> > (In reply to comment #7)
> > > (In reply to comment #6)
> > > 
> > > > Ok, let's try to fix it in 6.5. For 6.4, you can use e1000 instead ( or is
> > > > there a licence issue ?)
> > > 
> > > Just finish the WHQL test round using (qemu)system_reset and choose resume
> > > again for RHEL6.4.0 .We are Wasting lots of time on it during the test
> > > ,that's the reason I suggest to fix in next release .
> > 
> > Let's try to install e1000 driver in 2k3-64 and try to see if it has issues?
> > If not, I would prefer to close this bug since we'd better stop
> > investigation on 8139 which is out of data and isn't well documented.
> > 
> > Thanks
> 
>   Unfortunately,the issue still can be reproduced while doing block whql
> testing on win2k3 with e1000.

Why can't you use virtio-net for block whql?