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 915631 - win2008r2 guest do S3 can not resume after guest migration
Summary: win2008r2 guest do S3 can not resume after guest migration
Keywords:
Status: CLOSED WONTFIX
Alias: None
Product: Red Hat Enterprise Linux 7
Classification: Red Hat
Component: qemu-kvm
Version: 7.0
Hardware: Unspecified
OS: Unspecified
medium
medium
Target Milestone: rc
: ---
Assignee: Amit Shah
QA Contact: Virtualization Bugs
URL:
Whiteboard:
Depends On:
Blocks: Virt-S3/S4-7.0
TreeView+ depends on / blocked
 
Reported: 2013-02-26 08:54 UTC by langfang
Modified: 2015-03-04 05:22 UTC (History)
13 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2015-03-04 05:22:28 UTC
Target Upstream Version:
Embargoed:

Attachments (Terms of Use)

Description langfang 2013-02-26 08:54:14 UTC 
Description of problem:
Do S3 more than twice times--->do local migration, after migration finished,then do S3 -->can not resume

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

HOst:
# uname -r
3.7.0-0.36.el7.x86_64
# rpm -q qemu-kvm
qemu-kvm-1.3.0-6.el7.x86_64

Guest:win2008R2

drivers:
virtio-win-1.6.3-3.el6 

How reproducible:

90%

Steps to Reproduce:
1.Boot win2008r2 guest
2.After guest boot up,do S3 at least twice times in guest
Choose "sleep"
3.Do local migration
(qemu)migrate -d tcp:10.66.7.227:5999

3.After migrate finished.Do s3

  
Actual results:

do S3 --->can not resume 

Expected results:
After do S3 ,can be resume successfully

Additional info:

1.Tried use rhel7 guest ,not hit the problem
2.If remove step2, not hit the problem
3.Not add parameters "-global PIIX4_PM.disable_s3=0,-global PIIX4_PM.disable_s4=0",because S3/S4 enable in default  on rhel7 now.
4.The same steps,do S4,will see dark screen 
3.MY CLI:
/usr/libexec/qemu-kvm -M pc-1.3 -enable-kvm -m 8G -smp 4,sockets=2,cores=2,threads=1 -uuid 03272402-4538-4a7f-aa3e-3df4da3d5f48  -no-user-config -nodefaults -rtc base=utc  -drive file=/home/win2008r2-64-virtio.qcow2,format=qcow2,if=none,id=drive-ide0-0-0-0,werror=stop,rerror=stop,cache=none -device virtio-blk-pci,drive=drive-ide0-0-0-0,id=ide0-0-0- -netdev tap,id=hostnet0,vhost=on,script=/etc/qemu-ifup -device virtio-net-pci,netdev=hostnet0,id=net0,mac=52:54:00:60:3f:29,bus=pci.0  -device virtio-balloon-pci,id=balloon0,bus=pci.0,addr=0x7 -device virtio-serial-pci,id=virtio-serial0,max_ports=16,bus=pci.0,addr=0x6 -chardev socket,id=channel0,path=/tmp/tty0,server,nowait -device virtserialport,chardev=channel0,name=org.linux-kvm.port.1,bus=virtio-serial0.0,id=port1 -chardev socket,path=/tmp/qga.sock,server,nowait,id=qga0 -device  virtio-serial -device virtserialport,chardev=qga0,name=org.qemu.guest_agent.0 -monitor stdio  -boot menu=on,order=c -spice port=5900,disable-ticketing -vga qxl  -drive file=/usr/share/virtio-win/virtio-win.iso,if=none,id=drive-ide0-1-0,readonly=on,format=raw -device ide-cd,bus=ide.1,unit=0,drive=drive-ide0-1-0,id=ide0-1-0  -usb -device usb-tablet,id=input0 -incoming tcp:0:5999
Comment 2 langfang 2013-03-01 11:20:30 UTC 
Test this bug without any virtio device hit the same problem
 
/usr/libexec/qemu-kvm  -M pc-1.3 -enable-kvm -m 4G -smp 4,sockets=2,cores=2,threads=1 -uuid a779cceb-9d82-41bb-8110-c5b61cd0f4c8  -no-user-config -nodefaults -rtc base=utc  -drive file=/home/win2008r2-64-virtio.qcow2,format=qcow2,if=none,id=drive-ide0-0-0-0,werror=stop,rerror=stop,cache=none -device ide-drive,drive=drive-ide0-0-0-0,id=ide0-0-0 -netdev tap,id=hostnet0,vhost=on,script=/etc/qemu-ifup -device rtl8139,netdev=hostnet0,id=net0,mac=52:54:00:60:3f:29,bus=pci.0,addr=0x4  -monitor stdio  -boot menu=on,order=c -spice port=5900,disable-ticketing -vga qxl  -usb -device usb-tablet,id=input0
Comment 3 Amit Shah 2013-11-14 13:27:20 UTC 
It's not clear if you're doing this:

1. Issue S3
2. Migrate
3. Resume

or this:

1. Migrate
2. S3
3. Resume

If it's the 2nd one, looks like a dup of https://bugzilla.redhat.com/show_bug.cgi?id=915672.
Comment 6 juzhang 2014-07-14 08:06:10 UTC 
Hi Sluo,

Since flang is on pto, could you handle this issue?

Best Regards,
Junyi
Note You need to log in before you can comment on or make changes to this bug.