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 869476 - [virtio-win][block]Resume from S3 status guest quits automatically
Summary: [virtio-win][block]Resume from S3 status guest quits automatically
Keywords:
Status: CLOSED ERRATA
Alias: None
Product: Red Hat Enterprise Linux 6
Classification: Red Hat
Component: virtio-win
Version: 6.4
Hardware: Unspecified
OS: Unspecified
medium
medium
Target Milestone: rc
: ---
Assignee: Vadim Rozenfeld
QA Contact: Virtualization Bugs
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2012-10-24 03:13 UTC by Min Deng
Modified: 2013-11-22 00:00 UTC (History)
8 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Cause: Falling a system into Sleep (S3) with subsequent resume. Consequence: System cannot be resumed after S3 without BSOB Fix: in Seabios code Result: after updating seabios system can be resumed from S3.
Clone Of:
Environment:
Last Closed: 2013-11-22 00:00:10 UTC
Target Upstream Version:
Embargoed:

Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
Red Hat Product Errata RHBA-2013:1729 0 normal SHIPPED_LIVE virtio-win bug fix and enhancement update 2013-11-21 00:39:25 UTC

Description Min Deng 2012-10-24 03:13:07 UTC 
Description of problem:
The guest will quit while waking up from guest's S3 status
Version-Release number of selected component (if applicable):
virtio-win-prewhql-01-41
qemu-kvm-rhev-debuginfo-0.12.1.2-2.327.el6.x86_64
qemu-kvm-rhev-tools-0.12.1.2-2.327.el6.x86_64
qemu-kvm-rhev-0.12.1.2-2.327.el6.x86_64

How reproducible:
5 times / 3 reproduced

Steps to Reproduce:
1.boot up guest with the following CLI and install virtio block driver.
  /usr/libexec/qemu-kvm -m 2G -smp 2 -cpu host,+x2apic -usb -device usb-tablet -drive file=win2k8-R2.qcow2,format=qcow2,if=none,id=drive-ide0-0-0,werror=stop,rerror=stop,cache=writethrough -device virtio-blk-pci,drive=drive-ide0-0-0,id=ide0-0-0,bootindex=1 -netdev tap,id=hostnet0,script=/etc/qemu-ifup -device e1000,netdev=hostnet0,mac=10:10:1a:75:59:03,bus=pci.0,addr=0x4 -uuid `uuidgen` -rtc base=localtime -no-kvm-pit-reinjection -monitor stdio -name win2k8-64-fun -device virtio-balloon-pci,addr=0x6,bus=pci.0,id=balloon1 -chardev socket,id=111a,path=/tmp/monitor-win2k8-64-balloon-30,server,nowait -mon chardev=111a,mode=readline -cdrom /home/en_windows_server_2008_r2_standard_enterprise_datacenter_and_web_with_sp1_x64_dvd_617601.iso -drive file=disk1.qcow2,format=qcow2,if=none,id=drive-virtio1,cache=writethrough,werror=stop,rerror=stop -device virtio-blk-pci,drive=drive-virtio1,id=virtio-blk-pci1 -drive file=disk2.qcow2,format=qcow2,if=none,id=drive-virtio2,cache=writethrough,werror=stop,rerror=stop -device virtio-blk-pci,drive=drive-virtio2,id=virtio-blk-pci2 -drive file=disk3.qcow2,format=qcow2,if=none,id=drive-virtio3,cache=writethrough,werror=stop,rerror=stop -device virtio-blk-pci,drive=drive-virtio3,id=virtio-blk-pci3 -drive file=disk4.qcow2,format=qcow2,if=none,id=drive-virtio4,cache=writethrough,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 -spice disable-ticketing,port=5931 -vga qxl
2.install crystal disk mark and run it on more than 3 disks
3.Do S3 and resume it back after a while 
  tips,let the Crystal Disk Mark running several minutes and then do S3/resume

Actual results:
The guest can not be resumed and quit automatically at last.

Expected results:
The guest is resumed by  keyboard or mouse.

Additional info:
Comment 1 Min Deng 2012-10-24 03:22:52 UTC 
I cannot reproduce the issue if I did not use Crystal Disk Mark.
Comment 4 Ronen Hod 2012-10-29 13:09:14 UTC 
This looks like an excellent test, but it is too late for RHEL6.4, and probably not a regression.
Postponed to RHEL6.5
Comment 7 Ronen Hod 2013-07-29 09:24:55 UTC 
Please check with the 6.4 drivers. We think that it is solved.
The latest drivers have a regression.
Comment 8 Mike Cao 2013-07-31 06:47:41 UTC 
dengmin

Pls retest it on virtio-win-prewhql-65 & virtio-win-1.6.5-5 w/ seabios-28
Comment 9 Min Deng 2013-08-01 08:13:44 UTC 
Hi Mike,(In reply to Mike Cao from comment #8)
> dengmin
> 
> Pls retest it on virtio-win-prewhql-65 & virtio-win-1.6.5-5 w/ seabios-28

Hi Mike and Ronen,

   The issue was reproduced via build 41 
   Actual results:
   The guest can not be resumed and quit automatically at last.
   Expected results:
   The guest is resumed by keyboard or mouse.
   QE re-test the bug via build 66 & virti-win-1.6.5-6 with seabios 28.
Detail Steps,
1./usr/libexec/qemu-kvm -m 2G -smp 2 -cpu host,+x2apic -usb -device usb-tablet -drive file=win2k8-R2-0724.raw,format=raw,if=none,id=drive-ide0-0-0,werror=stop,rerror=stop,cache=writethrough -device virtio-blk-pci,drive=drive-ide0-0-0,id=ide0-0-0,bootindex=1 -netdev tap,id=hostnet0,script=/etc/qemu-ifup -device e1000,netdev=hostnet0,mac=10:10:1a:75:59:03,bus=pci.0,addr=0x4 -uuid `uuidgen` -rtc base=localtime -no-kvm-pit-reinjection -monitor stdio -name win2k8-64-fun -device virtio-balloon-pci,addr=0x6,bus=pci.0,id=balloon1 -chardev socket,id=111a,path=/tmp/monitor-win2k8-64-balloon-30,server,nowait -mon chardev=111a,mode=readline -drive file=disk1.qcow2,format=qcow2,if=none,id=drive-virtio1,cache=writethrough,werror=stop,rerror=stop -device virtio-blk-pci,drive=drive-virtio1,id=virtio-blk-pci1 -drive file=disk2.qcow2,format=qcow2,if=none,id=drive-virtio2,cache=writethrough,werror=stop,rerror=stop -device virtio-blk-pci,drive=drive-virtio2,id=virtio-blk-pci2 -drive file=disk3.qcow2,format=qcow2,if=none,id=drive-virtio3,cache=writethrough,werror=stop,rerror=stop -device virtio-blk-pci,drive=drive-virtio3,id=virtio-blk-pci3 -drive file=disk4.qcow2,format=qcow2,if=none,id=drive-virtio4,cache=writethrough,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 -spice disable-ticketing,port=5931 -vga qxl

2.install crystal disk mark and run it on more than 3 disks

3.Sleep and resume it back after a while 
  Tips,let the Crystal Disk Mark running several minutes and then sleep&resume

Actual results,the guest can sleep&resume successfully.
Expected results,the guest can sleep&resume successfully.

  So the original issue has been fixed,thanks.

Best Regards,
Min
Comment 10 Mike Cao 2013-08-01 08:49:48 UTC 
Move status to VERIFIED according to comment #9
Comment 12 errata-xmlrpc 2013-11-22 00:00:10 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.

http://rhn.redhat.com/errata/RHBA-2013-1729.html
Note You need to log in before you can comment on or make changes to this bug.